Difference: AMC13RawDataAnalysis (12 vs. 13)

Revision 1315 Oct 2015 - DanielArcaro

Line: 1 to 1

META TOPICPARENT	name="HcalDTC"

New analysis code being developed for 2014 data format

Line: 44 to 44

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.

CMSSW:

Changed:

<
<

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/

. General instructions to make an analyzer can be found here: https://twiki.cern.ch/twiki/bin/view/CMSPublic/WorkBookWriteFrameworkModule

>
>

and /cmsswtools. General instructions to make an analyzer can be found here: https://twiki.cern.ch/twiki/bin/view/CMSPublic/WorkBookWriteFrameworkModule

Recipe to build the analyzer code:

Changed:

<
<

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

>
>

$ cmsrel CMSSW_#_#_# ($scram list if you want to see the version choices) (The version should match the version that created the root file. Use edmProvDump name.root to check the version.)

$ cd CMSSW_#_#_#/src

Line: 56 to 56

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

Changed:

<
<

$ cd analyzer/parse/plugins

$ pushd somewhere else

$ 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

$ mv _somewhere_else_/unpacker/* ./

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

$ cd .. (to parse folder)

>
>

$ svn co http://edf.bu.edu/svn/edf/arcaro/cms/trunk/cmsswtools

$ scram b

Changed:

<
<

To run the analyzer on a root file use $ cmsRun python/ConfFile_cfg.py.

>
>

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. To then run the analyzer:

Changed:

<
<

Some modifications must be made to the analyzer code depending on the root file type. The only two files that would need to be changed are plugings/parse.cc and python/ConfFile_cfg.py. The ConfFile_cfg.py has the Fed ID input and the root file name. If the root file is local the line process.source = cms.Source("HcalTBSource", should not be commented out, but the one with PoolSource should be. Also, in parse.cc the lines Handle rawdata; iEvent.getByLabel("source",rawdata); should not be commented out, but the one with rawDataCollector should be. If the root file is a global run, the opposite should be done for both files.

>
>

$ cmsRun analyzer/parse/python/ConfFile_cfg.py.

All of this should be done using the same version of CMSSW as what the root file was produced with. To determine this use $ edmProvDump rootfile.root to see the CMSSW version number and other attributes of the file. There are also other edm functions that are quite useful (of course only on lxplus).

View topic | History: r22 < r21 < r20 < r19 | More topic actions...