For general instructions on the framework, co-ordinate system, reconstruction sequence, etc please refer to
http://cms-hgcal.github.io/TestBeam/

Some specific information about this run with 4 modules is mentioned below, particularly the different electronics map and pedestal files.

DOWNLOAD THE CODE:
RELEASE=CMSSW_8_0_1
scram project ${RELEASE}
cd ${RELEASE}/src/
cmsenv 
git cms-init
git clone [email protected]:CMS-HGCAL/TestBeam.git HGCal/
git checkout FNAL_TB_4Layers
git pull
scram b -j16
(Might need to do scram b more than once till compilation is successful)

Electronics Map[EMAP] and event average pedestal files:
The EMAP for this run "map_FNAL_Layer1234.txt" can be found in CondObjects/data
The event average pedestal files for both low and high gain can be found in
"Ped_LowGain_M1254.txt" and "Ped_HighGain_M1254.txt" also in CondObjects/data
The information of the EMAP is needed by the framework when producing the digis from the 
RAW and is provided in the file RawToDigi/python/hgcaltbdigis_cfi.py
It is also needed in analysis code if a conversion from Detector Id to Electronics Id is needed.
May refer to the example RawToDigi/plugins/DigiPlotter.cc . In the EndJob() function of this same
code the format needed in which the pedestal files are to be written out can be found.
The Pedestal information is needed in the step from Digis to Reco. And it is provided from
Reco/python/hgcaltbrechitproducer_cfi.py


RAW data files:
The RAW files can be found in /afs/cern.ch/user/r/rchatter/public/FNAL_TB_May/FNAL_TB_May_4Module_Runs
This is structured by beam type and for the Electrons further by the energy of the electron beam.

To RUN:
In test_cfg.py the RAW data file to be run is to be provides in the line:
process.source = cms.Source("HGCalTBTextSource",
                            run=cms.untracked.int32(1), ### maybe this should be read from the file
                            fileNames=cms.untracked.vstring("file:FNAL_TB_May_4Module_Runs/PED/HGC_Output_1600.txt")
                             )

In cms.Path: process.hgcaltbdigis produces digis and process.hgcaltbrechits produces the rechits[the ADCToGeV factor is taken as unity until the calibrated numbers are available]. The analyzer to be run can come after this. There are a few provided:
RawToDigi/plugins/DigiPlotter.cc to generate the pedestals
Reco/plugins/RecHitPlotter_HighGain_Correlation_CM.cc for the noise studies starting from pedestal subtracted digis.

The output root file name is set in:
process.TFileService = cms.Service("TFileService", fileName = cms.string("HGC_Output_1600_Reco.root") )


cmsRun test_cfg.py >> /dev/null