Instructions for analysis

This page contains informations about the BTF Test Beam analysis in Frascati for the I-MCP project.

Launching the reconstruction program

The reconstruction program can be found at: www.github.com/I-MCP The procedure to correctly compile and execute this program from shell is the following:

First connect to cmsrm-ui02.roma1.infn.it Next, from shell:

> git clone https://github.com/I-MCP/BTF_TB_SW.git //this will clone the program in your directory
> SCRAM_ARCH=slc5_amd64_gcc472 //set the scram architecture
> scram p CMSSW_6_2_0 //Install the CMSSW right release
> cd CMSSW_6_2_0
> cmsenv
> cd ..
> cd BFT_TB_SW
> make clean
> make all //Compile everything

To execute the program, just follow the instruction written in the README.md

> scripts/runSimpleRecoTreeProducer.py -i /t3/users/cmsdaqtb/data/data/BTF/IMCP/dataTree/run_IMCP_94_20140521-052300_beam.root -o outDir -L lib/

The whole run list is in the directory: /t3/users/cmsdaqtb/data/data/BTF/IMCP/dataTree/

This procedure will create in the outDir a new .root file with a RECO in the name: run_IMCP_94_20140521-052300_beam_RECO.root

For the moment all the reconstructed files are in /t3/users/cmsdaqtb/data/data/BTF/IMCP/processedDataTree There is another repository for reconstructed events (version 2) in: /t3/users/meridian/BTF/IMCP/processedDataTree/v2/

IMPORTANT: for anyone wanting to execute a script involving these programs in batch mode, use cmsan because it contains the right release of SL

Raw data reconstruction procedure (DIGITIZER)

The procedure to be used for the raw data due to the digitizer analysis is the following:

As before, you need to download the source code from github: https://github.com/I-MCP/BTF_TB_SW.git (same link - so if you've already done it, don't do it again!!)

Always make a CMSSW space for compiling and executing the program; to launch it the command is:

> scripts/runCheckDRS4Calibration.py -i /t3/users/cmsdaqtb/data/data/BTF/IMCP/dataTree/run_IMCP_290_20140523-110749_LED.root -o outDir -L lib/ -c 0,1 -t XXXX,YYYY,ZZZZ,...

Options

  • The -c option indicates the channel you are going to analyze (which actually have seen the pulser signal).
  • The -t option indicates the thresholds used (can be comma separated list and plots will be created for each threshold)

The Output file is: run_IMCP_290_20140523-110749_LED_checkDRS4Histos.root made by several histograms describing the behavior of each channel, showing the values of every single sample taken during the acquisition.

RUNS EXPLOITABLE FOR THIS ANALYSIS: 286, 287, 288, 289, 290.

Corresponding to: run 286: CH0 - CH1 run 287: CH1 - CH2 run 288: CH1 - CH3 run 289: CH4 - CH5 run 290: CH4 - CH6

Simulation part

To run the simulation part, just use the command:

scripts/runSimulatePulses.py -p data/testWaveProfiles.root -L `pwd`/lib -o testSimulation -n 1000 -s 1.4

where s stands for: RMS of the noise amplitude.

-- SimoneGelli - 02 Jul 2014

Topic attachments
I Attachment History Action Size Date Who Comment
PDFpdf thresh_cross_ch1_run288.pdf r1 manage 16.7 K 2014-07-10 - 10:39 UnknownUser Here the variation of the threshold doesn't seem to alterate the crossing time
PDFpdf thresh_cross_ch2_run287.pdf r1 manage 16.8 K 2014-07-10 - 10:41 UnknownUser Here, the ch2 isn't calibrated!
Edit | Attach | Watch | Print version | History: r7 < r6 < r5 < r4 < r3 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r7 - 2014-07-18 - FrancescoSantanastasio
 
    • Cern Search Icon Cern Search
    • TWiki Search Icon TWiki Search
    • Google Search Icon Google Search

    Sandbox All webs login

This site is powered by the TWiki collaboration platform Powered by PerlCopyright &© 2008-2023 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
or Ideas, requests, problems regarding TWiki? use Discourse or Send feedback