Difference: AMC13RawDataAnalysis (19 vs. 20)

Revision 2027 Oct 2015 - DanielArcaro

Line: 1 to 1
 
META TOPICPARENT name="HcalDTC"

New analysis code being developed for 2014 data format

Line: 25 to 25
 The two options for file types processed by this code are binary and root files. The code to switch from one to another or vice versa is here:

Binary to Root: https://github.com/elaird/hcalraw (From Ted Laird)

Added:
>
>
  • First run make in the cpp folder
 
  • The main tool for making badcoffee binary files is hcalraw/cpp/badcoffee.cpp. Usage is cat a.dat | ./badcoffee fed#.

Root to Binary: http://edf.bu.edu/svn/edf/arcaro/cms/trunk/pythontools/rootdumper/ or http://edf.bu.edu/svn/edf/arcaro/cms/trunk/analyzer/dumpraw/

  • The dumpraw code is a cmssw analyzer and requires a cmssw environment. The rootdumper only requires root.
  • The rootdumper is built by running the Makefile in rootdumper/cpp.
    • Run the code using ./oneRun.py --rootFile=HTB_007850.root --feds=928 --nEvents=101 --outputFile=data1.dat
Changed:
<
<
  • The dumpraw analyzer can be built with the same directions as the CMSSW section below.
>
>
  • The dumpraw analyzer can be built with the same directions as the CMSSW section below.
 
    • Run the code using cmsRun .../python/ConfFile_cfg.py

Unpacker

Changed:
<
<
Unpacker consists of three classes to parse AMC13 data format: FedEvent, FedBlock, and FedAMC. Various tools have also been created to utilize these classes and analyze the data. All code can be found here: http://edf.bu.edu/svn/edf/arcaro/cms/trunk/
>
>
Unpacker consists of three classes to parse AMC13 data format: FedEvent, FedBlock, and FedAMC. Various tools have also been created to utilize these classes and analyze the data. All code can be found here: http://edf.bu.edu/svn/edf/arcaro/cms/trunk/
  Class documentation: http://ohm.bu.edu/~djarcaro/Documentation/unpacker.pdf
Line: 60 to 61
 

Unpacker histogram option

If root is installed dumptmp.cc can be made by $make root=1. dumptmp is identical to dump but also creates a root file with a histogram of the error array for easier visualization with large files.
Added:
>
>
 

CMSSW

The dump software has also been implemented in a cmssw analyzer to extract raw data from global/local root files and unpack it. This requires a cmssw environment (most likely lxplus). The code can be found here http://edf.bu.edu/svn/edf/arcaro/cms/trunk/analyzer/ and .../trunk/cmsswtools. General instructions to make an analyzer can be found here: https://twiki.cern.ch/twiki/bin/view/CMSPublic/WorkBookWriteFrameworkModule.
Line: 73 to 76
 $ scram b
Changed:
<
<
To run the analyzer first set the parameters in the python file analyzer/parse/python/ConfFile_cfg.py. The most important parameters (besides the file name) are the HcalTBSource vs PoolSource and the rootType string input. Change these to correspond to either a local or global root file. The python script is set to run over multiple files in a directory. To then run the analyzer:
>
>
To run the analyzer first set the parameters in the python file analyzer/parse/python/ConfFile_cfg.py. The most important parameters (besides the file name) are the HcalTBSource vs PoolSource and the rootType string input. Change these to correspond to either a local or global root file. The python script is set to run over multiple files in a directory. To then run the analyzer:
 
$ cmsRun analyzer/parse/python/ConfFile_cfg.py.
Line: 85 to 88
 

To Do List

Deleted:
<
<
  • Add a doxygen configuration file and "doc" target to makefile so one can do 'make doc' and get the doxygen output.
 

New Features

Deleted:
<
<

DONE:

  • In FedEvent::PreParse the expression if(GetNAMC() > 0 || GetNAMC() < 13) is always true. I think you mean to use && instead of ||.
  • In FedEvent::PreParse there are two possibilities for size: a) 2 and b) 4...14. It should throw an exception if any other value is passed. The comments should reflect this.

  • Check for consistency of LMSEPVC bits through an entire event
    • MS should be "10" for first block, "11" for intermediate blocks, "01" for final blocks.
    • C should be 1 when MS="01".
    • EP should always be "11" I think
  • Check Blk_No, AmcNo, BoardID in block headers for consistency throughout event
  • Add option to dump entire AMC payloads

-- EricHazen - 04 Aug 2014

 
META FILEATTACHMENT attachment="unpacker.pdf" attr="" comment="Documentation for classes in unpacker" date="1439568028" name="unpacker.pdf" path="unpacker.pdf" size="128427" stream="unpacker.pdf" tmpFilename="/usr/tmp/CGItemp28297" user="djarcaro" version="1"
 
This site is powered by the TWiki collaboration platform Powered by PerlCopyright © 2008-2018 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback