Versions Compared

Old Version 13

changes.mady.by.user Leon Rochester

Saved on

compared with

New Version Current

changes.mady.by.user Kelly (Arrighi), Heather

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 4.0

...

  • OnboardFilter (the algorithm) - just the important ones*# "UseMootConfig" - set to false by default, true means get configuration info from Mootb)
    1. "RejectEvents" - set to false by default, true means OnboardFilter will use "active" filters to accept/reject eventsc)
    2. "FailNoEbfData" - set to false by default, true means OnboardFilter "crashes" (gracefully) if ebf data is missing
    3. "FilterList" - this is a list of filters to configure and run, the default is Gamma, MIP, HIP, DGN and
    4. "FilterTrack" (grabs track info for GRB)The rest are highly specialized and don't matter.

...

  • GammaFilterTool - this controls the Gamma Filter*# "LeakAllEvents" - set to true by default, causes the Gamma Filter to report on all events which means it runs all stages of the filterb)
    1. "Configuration" - set to "" by default, if set this will override the configuration in the Master config file (and, Moot too I think)
    2. "GamFilterMask" - set to 0 by default, if set this will mask out veto bits during processing - SHOULD NOT BE USED BY NOVICES
    3. There are also a collection of JO parameters to allow you to change the parameters of the Gamma Filter, these should also NOT BE USED

...

At the same time, we may also run, for example, the MIP filter but will have no configruation information for it from Moot... in this case it will run "normal" mode and use the configuration defined in the master configuration file.If UseMootConfig is "false" then the filters will initialize during the initialize method of OnboardFilter. They will configure according to the master configuration files for each filter and will run in "normal" mode. This can be overridden by JO parameters for the Gamma filter now, and I'll add that for the other filters straight away.Finally, each event OnboardFilter will look for the MetaEvent TDS class. If found then it will check the run mode and see if it has changed from the currently cached value (I wish there was a better way!). If it has changed then it will change modes for all "active" filters only.Ok, let me know if defaults are ok or any other issues that might be obvious from what I wrote (or didn't write).

Thursday June 19, 2008

List of tags to add to GR HEAD:

Trigger v6r3p1
OnboardFilterTds  v0r8p1
AnalysisNtuple v2r43p1
MootSvc v1r1p3
ConfigSvc v0r2p4
Gleam v7r0p7