File indexing completed on 2024-04-06 12:19:14
0001 <html>
0002 <body>
0003 <font size=+2><tt>CSCCommissioning</tt></font> package operates with local DAQ data of the
0004 <a href="http://cms-emu-slicetest.web.cern.ch/cms-emu-slicetest/">CSC SliceTest</a>.
0005 Two modules of this package are <tt>CSCFileReader</tt> and <tt>CSCFileDumper</tt>.
0006 First is capable of reading CSC local data and populating CMSSW data stream
0007 (<tt><a href="https://twiki.cern.ch/twiki/bin/view/CMS/WorkBookCMSSWFramework#ProcModel">edm::Event</a></tt>)
0008 with raw CSC data. Second module does an opposite job of selecting CSC data from the
0009 <tt><a href="https://twiki.cern.ch/twiki/bin/view/CMS/WorkBookCMSSWFramework#ProcModel">edm::Event</a></tt>
0010 and dumping them into local DAQ files.
0011 <br>
0012 <br>
0013 CSC DAQ data are composed of up to 40 data streams from independent sources — Readout Units (RUIs).
0014 These streams are gathered in 4 FED crates (FED stands for Front End Driver) and travel
0015 downstream of global DAQ via 4 S-Links. Each FED is assigned with its own FED ID (750-759).
0016 Unlike global data taking, in local mode RUIs log data independently each in a separate set of files.
0017 <br>
0018 <br>
0019 <font color=red>If you are working with plain local DAQ data format (one set of files per each RUI; see
0020 for EmuRUI?? in file name), than you may find this paragraph useful.</font><br>
0021 If you work in CMSSW_1_3_0 or later (package revision V00-04-04 and higher) you should
0022 instruct <tt>CSCFileReader</tt> module to build FED buffers from selected RUIs (see
0023 <a href="http://cmssw.cvs.cern.ch/cgi-bin/cmssw.cgi/CMSSW/IORawData/CSCCommissioning/test/readFile.cfg?rev=1.6&cvsroot=CMSSW&content-type=text/vnd.viewcvs-markup">
0024 test/readFile.cfg</a> for example). To do that you need to specify parameter set (<tt>PSet</tt>)
0025 which defines RUI file sets (<i>RUI00</i>, <i>RUI01</i>, ... <i>RUI09</i>) and then assign each
0026 RUI to the appropriate FED (<i>FED750</i>, <i>FED751</i>, <i>FED752</i>, <i>FED753</i>). The module builds FED buffers
0027 from RUI buffers with the same L1A. Therefore, you should always maintain order of files in
0028 RUI file sets (module expects only incrementing L1A from file to file).
0029 In CMSSW prior to CMSSW_1_3_0 (package revision prior to V00-04-04) you are
0030 able to handle 1 FED with 1 RUI in it. Just specify <i>fileNames</i> as it is done in
0031 <a href="http://cmssw.cvs.cern.ch/cgi-bin/cmssw.cgi/CMSSW/IORawData/CSCCommissioning/test/readFile.cfg?rev=1.4&cvsroot=CMSSW&content-type=text/vnd.viewcvs-markup">
0032 test/readFile.cfg</a>.
0033 <br>
0034 <br>
0035 Module also supports alternative data format, produced by local Event Builder emulator (see FU in
0036 file name). In this case you need to assign <i>FU1</i>, <i>FU2</i>, ... with corresponding
0037 file names and remove FED parameters (though, having them in configuration doesn't affect
0038 anything). Set <i>tfDDUnumber=0</i> if Track-Finder records present in readout or
0039 <i>tfDDUnumber=-1</i> if not. See
0040 <a href="http://cmssw.cvs.cern.ch/cgi-bin/cmssw.cgi/CMSSW/IORawData/CSCCommissioning/test/readFile.cfg?view=markup">test/readFile.cfg</a> for example.
0041
0042 <br>
0043 <br>
0044 Special trigger RUI should not be mixed with DAQ RUIs which were described above (such
0045 configuration is not forbidden, but doesn't make much sense). Instead, trigger RUI solely
0046 goes to FED with ID=760.
0047 <br>
0048 <br>
0049 <tt>CSCFileDumper</tt> module selects CSC FED buffers from CMSSW data stream and
0050 logs them into files specified in <i>output</i> parameter. It automatically appends _FEDID
0051 (_750, _751, ... _760) to the end of every FED file. Be careful: one FED file may contain
0052 several RUIs, while in true local DAQ mode every RUI logs separate file.
0053 <br>
0054 <br>
0055
0056 <hr>
0057 Technical details on <a href="./details.html"><tt>CSCFileReader</tt></a>
0058 </body>
0059 </html>
