Difference: AMC13RawDataAnalysis (1 vs. 22)

• First run make in the cpp folder

• The dumpraw analyzer can be built with the same directions as the CMSSW section below.

$svn co http://edf.bu.edu/svn/edf/arcaro/cms/trunk/unpacker and http://edf.bu.edu/svn/edf/arcaro/cms/trunk/tools
$cd tools
$make

Unpacker histogram option

To Do List

https://github.com/elaird/hcalraw

• 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
• 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 Build and Run Instructions

New analysis code being developed for 2014 data format

Finding the Data

Converting Data

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

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/

Unpacker

Build and Run Instructions:

Root and Histogram Options

CMSSW

To Do List

Bugs

• $svn co http://edf.bu.edu/svn/edf/arcaro/cms/trunk/unpacker and .../cms/tools

Finding the Data

See EricFindingCMSData for some help.

$ svn co http://edf.bu.edu/svn/edf/arcaro/cms/trunk/unpacker/ (You can put this anywhere you would like, just make sure the contents of unpacker end up in the plugins folder)

$ popd

• $svn co http://edf.bu.edu/svn/edf/arcaro/cms/trunk/unpacker and /tools

$ cmsrel CMSSW_#_#_# ($scram list if you want to see the version choices)

$ cd CMSSW_#_#_#/src

$ cmsenv (equivalent: eval `scramv1 runtime -csh`)

$ svn co http://edf.bu.edu/svn/edf/arcaro/analyzer/

$ cd analyzer/parse/plugins

$ svn co http://edf.bu.edu/svn/edf/arcaro/unpacker/

$ cp unpacker/* ./

You should now have all the FedEvent source code in the plugins folder alongside BuildFile.xml and parse.cc

$ cd ..

$ scram b

CMSSW:

http://edf.bu.edu/svn/edf/arcaro/analyzer

https://twiki.cern.ch/twiki/bin/view/CMSPublic/WorkBookWriteFrameworkModule

Unpacker:

http://edf.bu.edu/svn/edf/arcaro/

Class documentation: http://ohm.bu.edu/~djarcaro/Documentation/unpacker.pdf

Build and Run Instructions:

• $svn co http://edf.bu.edu/svn/edf/arcaro/unpacker and /tools
• $cd tools
• $make

• dump64: Prints the raw data to screen in hex with 64bits per line. Used to sort through data by hand.
  • use: $ ./dump64 file.dat (usually followed by | less)
• dump: Main dump tool to parse events and check for errors.
  • use: $ ./dump file.dat -v 1 -e 1 -c
  • -v flag for amount of information about the event printed to screen
  • -c flag to turn CRC checking on or off
  • -e flag to print specific errors to screen

Root and Histogram Options:

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.

P.S. If you end up dumping the AMC13 monitor buffers, but would like
to convert the dumps to .root files with TTrees of
std::vector, so that you can use "ordinary" analysis
programs to analyze them, feel free to use this program:
badcoffee.cpp

Bug reports are quite welcome.  (to Ted Laird)

To Do List

Bugs

• 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.
• Add a doxygen configuration file and "doc" target to makefile so one can do 'make doc' and get the doxygen output.

New Features

• 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

New analysis code being developed for 2014 data format

New code is being developed by Daniel Arcaro with help from Eric Hazen and Dan Gastler to analyze the new/final data format documented here: AMC13CommonFirmwareProposal.

A preliminary API is documented below. Three classes are foreseen:

Class	Description <-- -->
AMC13Block	internal block structure of event fragment
FedEvent	one event fragment as received from an AMC13 in response to a single L1A
FedAmc	Payload for one AMC

Each class is documented below:

Class FedEvent

FedAmc

For preliminary HCAL data format used through 2013

TWiki page

To get the tools from our svn and build them:

  $ svn co svn://cms1.bu.edu/Eric
  $ cd Eric/RawAnalysis
  $ make
  $ ./dump_DTC.exe
  usage:  dump_DTC.exe [options] file_name
    -e (check for sequential EvN)
    -h (check for uHTR EvN)
    -v (verbose)
    -d 
       1=DTC header 2=uHTR headers  3=uHTR payload
  $

If you run e.g. ./dump_DTC.exe -h dump1.dat it will check the file dump1.dat for EvN, BcN and OrN errors. The data format is documented here. ("HCAL Upgrade Data Format", latest version).

-- EricHazen - 18 Oct 2013