<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">Hi All,<div><br></div><div> I’ve added a new configuration parameter called “TT:SYSTEMS_TO_PARSE” that will allow you to </div><div>specify which detector system(s) you wish the DAQ plugin to spend time parsing. It does this based</div><div>on rocid and the rocids are determined by looking them up in the Translation Table based on</div><div>the detector system name. The value of the variable should be a comma separated list of detector</div><div>systems. For example:</div><div><br></div><div><font face="Courier">hd_root -PPLUGINS=DAQ,TTab,DAQTree -TT:SYSTEMS_TO_PARSE=BCAL,FCAL file.evio</font></div><div><br></div><div>This can save a lot of time for folks interested in data from only one detector system (with the exception</div><div>of the FDC since it tends to dominate the data volume). It also means you can make smaller ROOT</div><div>files with the DAQTree plugin. In a quick test with a file from run 1515, I saw about a factor of</div><div>10 speed up when parsing just the FCAL compared to parsing all detectors (single threaded). The ROOT</div><div>file size was also nearly a factor of 20 smaller.</div><div><br></div><div>Valid values that could go into the comma separated list of systems are:</div><div><br></div><div>BCAL</div><div>CDC</div><div>FCAL</div><div>FDC</div><div>FDC_CATHODES</div><div>FDC_WIRES</div><div>TOF</div><div>TAGM</div><div>TAGH</div><div>PS</div><div>PSC</div><div>ST</div><div><br></div><div>note that “FDC” is just and alias for “FDC_CATHODES,FDC_WIRES” and “PS” will also</div><div>automatically turn on parsing of “PSC” as well.</div><div><br></div><div>Not specifying the parameter will cause everything to be parsed, just as before.</div><div><br></div><div>Regards,</div><div>-David</div><div><br></div></body></html>