Difference between revisions of "DAQTree plugin"
|Line 26:||Line 26:|
The object types that will be supported
The object types that will be supported :
Revision as of 11:41, 18 February 2014
DAQTree is a standard JANA plugin that can be used to output information about standard DAQ objects to root trees.
Once everything is set up (as on the gluon cluster), it can be run using the following command:
hd_root -PPLUGINS=DAQ,DAQTree -PHDDM:ENABLE=0 codafile.evt -o outputfile.root
The -PPLUGINS=DAQ is required to generate the low level DAQ object which are then saved to the tree.
The -PHDDM:ENABLE=0 switch is required to stop the analyzer from wasting time trying to interpret the file as a HDDM file. Later developments to the HDDM parser may make this unnecessary.
The DAQ and DAQTree plugins can be run with additional plugins that can construct one type of object from another.
hd_root -PPLUGINS=DAQ_WRD2PI,DAQ,DAQTree -PHDDM:ENABLE=0 codafile.evt -o outputfile.root
The DAQ_WRD2PI pluing needs to come before the DAQ plugin so the factory it uses to create Df250PulseIntegral object will take precidence over the factory coming from the DAQ plugin.
The currently supported object types are:
The object types that will be supported in future are:
Df125PulseIntegral Df125PulseTime Df125TriggerTime DF1TDCHit DF1TDCTriggerTime Df250PulseIntegral Df250PulseRawData Df250PulseTime Df250StreamingRawData Df250TriggerTime Df250WindowRawData Df250WindowSum
DAQTree is currently not compiled or installed by default because it depends on the DAQ plugin. The DAQ plugin is not currently compiled by default since it depends on evio, which is not typically necessary for standard simulation reconstruction. This may change. First compile and install sim-recon, the the DAQ plugin and then the DAQTree plugin.
See the Doxygen entry for this plugin for a look into the internal structure.