You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, all trigger bits use the same cut, which is hardcoded in the source. We need the cut limits to be configurable via database parameters. There should be an option to override global cut limits with ones specific to a certain trigger bit. Since this requires new member variables, it will not be binary compatible and so has to wait until release 1.6.
The text was updated successfully, but these errors were encountered:
Implemented a new BdataLoc class hierarchy that handles (decodes) raw
event data from single front end channels and related information.
Supports either crate/slot/channel addressing (including multihit
channels) or crate/header/offset addressing (data identified by header
words in the event buffer). Also supports a new data type Roclen that
reports the event length in a given crate and a new TrigBitLoc class
to handle Hall A-style trigger bits. This last one should eventually
go into the Hall A library. See the top of BdataLoc.C for the full
list of definitions (calls to BdataLoc::DoRegister).
This is pretty much what I had in mind in July 2007 when I wrote the
FIXME comments in the original.
The VDC efficiency calculation has been moved into a separate VDCeff
physics module that will be checked in later.
The database may either be in the legacy format that was understood by
the original code or, preferably, in a new key/value format. For the
latter, one needs database keys like
D.crate = \
syncadc1, 1, 25, 16, \
syncadc2, 2, 24, 48, \
...
where "crate" corresponds to the BdataLoc type one wants to define for
the given variable names. There is exactly one key per BdataLoc type
(NOT per variable!). The key's value is one long string (continued
with \ continuation marks if necessary) containing n-tuples of
configuration parameters, name first. Spaces, commas and tabs are
accepted as delimiters in the database values. Most BdataLocs need
4-tuples as in the example above), however trigger bit variables take
6-tuples:
D.bit = bit1 3 5 64 0 1500
where the values indicate crate, slot, channel, cutlo and cuthi. The
latter two values are the lower and upper limits of the TDC cut to
apply to identify a set bit. (Ask Bob for details on how this hardware
is set up.)
Support for the legacy file format can be enabled by defining of
DECDATA_LEGACY_DB. This is currently the default. In that case,
database files are only assumed to be in new format if they have a
first line comment containing "Version: 2".
The class no longer defines any histograms. Most of the histos in the
original were for the VDC efficiency calculation anyway. If you need
to histogram roclen12 or roclen16, for example, define roclen
variables here and histograms of these variables as output
definitions.
Use Print("FULL") after Init() to see all defined variables, including
channel definitions.
An example key/value type database file is provided in DB/20121201/db_D.dat
Currently, all trigger bits use the same cut, which is hardcoded in the source. We need the cut limits to be configurable via database parameters. There should be an option to override global cut limits with ones specific to a certain trigger bit. Since this requires new member variables, it will not be binary compatible and so has to wait until release 1.6.
The text was updated successfully, but these errors were encountered: