Task list

• Pixel analysis for pPb run in 2013 (urgent)
• Definition of trigger and datasets for 2015 pp data taking (by early 2015)
• Implementation of the Pixel input for luminosity analysis framework (by early 2015)
• Pixel analysis for the first VdM scans in 2015 (~mid 2015)

Documentation

• 2012 pp analysis PAS and AN
• 2013 pPb analysis PAS
• Lumi Paper

Instructions for running the luminosity framework

• the structure of the framework is given in this presentation (slide 3): slides
• the instructions step-by-step (based on the framework version as available by 24/11/2014): instructions

Instruction for the pixel analysis code

• Set the CMSSW envirnoment (in SLC6 machines). A prerelease is needed (for example CMSSW_5_3_15_patch1)
• Check out the code from SVN: svn co https://svn.cern.ch/reps/CMSUserCode/trunk/jhegeman/LumiStudies/
• Compile LumiStudies package
• Update PixelLumi to the version 558 (svn update -r 558 PixelLumi)
• after cmsenv, execute: setenv PYTHONPATH "$PYTHONPATH":/usr/lib/python2.6/site-packages/ (or export PYTHONPATH=$PYTHONPATH:/usr/lib/python2.6/site-packages/)

Instructions for the VdM scan analysis

Goal: get the calibration constant needed for the luminosity determination with pixel cluster counting Here I put the example of how to run the analysis on the run 207871 (=fill 3316 ) ) i.e. for the pp analysis. For the moment we don't have ingredients necessary to do this withe heavy ion data. We are working on that !

Data to be used (for pPb/Pbp)

• Zero Bias data: /ZeroBiasX/RECO/PromptReco-v1 where X = 1, 2, 3, 4
• available also in eos: /eos/cms/store/hidata/HIRun2013/
• special VdM dedicated runs are
  • pPb: run 210986, LS [513-804] (corresponding to the Fill 3503)
  • Pbp: run 211561, LS [392-616] (corresponding to the Fill 3537)

step 1: produce TTrees from the data

code: /LumiStudies/LumiTuplers
command: cmsRun pixellumitupler_cfg.py : need to be configured depending on the datastream that we use (AlCaLumiPixels or ZeroBias)
output: this will create a file with TTree with name pixellumitupler_*.root.
Example of the TTree for the run 207871 is in /eos/cms/store/group/comm_luminosity/jhegeman/pixel_lumi/2012/scans/run_207871/ZeroBias3_Run2012D-PromptReco-v1_RECO/

The output TTree for the full pPb 210986 run is:
/afs/cern.ch/work/m/malek/public/ZeroBias/run_210986/pixellumitupler_VdM_Run210986.root

step 2: creating the VdM TTree

From the TTree created by LumiTupler create the VdM TTree
code: LumiStudies/PixelLumi/scripts
command: python build_pixel_scan_tree.py ZeroBias VdM /eos/cms/store/group/comm_luminosity/jhegeman/pixel_lumi/2012/scans/run_207871 pixel_lumi_tupler_zb 207871
output: pixel_vdm_tree_207871_pixel_lumi_tupler_zb.root

The output VdM TTree for the full pPb 210986 run is:
/afs/cern.ch/work/m/malek/public/ZeroBias/run_210986/pixel_vdm_tree_210986_pixel_lumi_tupler_zb.root

step 3: processing the VdM TTree

Process the TTree created by build_pixel_scan_tree.py
code: LumiStudies/PixelLumi/scripts
command: python process_pixel_scan_tree_vdm.py pixel_lumi_tupler_zb 207871
output: pixel_vdm_graphs_207871.root

step 4: Fit the VdM TTree

Fit processed by process_pixel_scan_tree_vdm.py TTree
code: LumiStudies/PixelLumi/scripts
command:python fit_pixel_vdm.py 207871 pixel model1a (558 version is running, the latest one has some extra corrections)

Instruction to access the LHC Timber database to get the files with beam parameters for the VdM scan analysis

• install java on your computer
• go to the LHC page: http://lpc.web.cern.ch/lpc/
• in the LHC quick info section go to the link LHC logging database (timber)
• download the file timber.jnlpx
• open the timber.jnlpx with java
• this will open a window of the LHC database
• extract relevant variables (list below) for the fill that we need: use Metadata option to get header

VARIABLE: A6R4.B1:BEAM_INTENSITY
VARIABLE: A6R4.B2:BEAM_INTENSITY
VARIABLE: A6R4.B1:BUNCH_INTENSITY (Select Correction ad RAW)
VARIABLE: A6R4.B2:BUNCH_INTENSITY (Select Correction ad RAW)
VARIABLE: LHC.BSRTS.5L4.B2:BEAM_NORM_EMIT_H
VARIABLE: LHC.BSRTS.5L4.B2:BEAM_NORM_EMIT_V
VARIABLE: LHC.BSRTS.5R4.B1:BEAM_NORM_EMIT_H
VARIABLE: LHC.BSRTS.5R4.B1:BEAM_NORM_EMIT_V

Instruction for the pixel analysis: luminosity from pixel cluster counting ToDo later once we have VdM scan analysis completed !

Data to be used (for pPb/Pbp): once we have the calibration constant from the VdM scan analysis

/AlCaLumiPixels/HIRun2013-LumiPixels-PromptReco-v1/ALCARECO

step 1: produce TTrees

step 2: reading and analysis of TTrees

• In this method the calibration factor is known (obtained from the analysis of the VdM scan).
• Codes in /LumiStudies/PixelLumi
• Input is the root file produced in the step 1
• Modify LumiStudies/PixelLumi/python/misc.py in order to have a correct path to the eos (in our case eos = "/afs/cern.ch/project/eos/installation/0.3.15/bin/eos.select")
• Run pixel_cluster_counts_from_pixel_lumi_tuple.py. Below the command that we wee using for testing the workflow:

python pixel_cluster_counts_from_pixel_lumi_tuple.py 'pixellumitupler.*\.root' 2012 /eos/cms/store/group/comm_luminosity/mzanetti/pixel_lumi/2012/pixel_lumi/Run2012A/AlCaLumiPixels pixel_lumi_tupler_zb 193112

=> This will produce a root file with histograms (nb of events/LS and weighted by sum of pixel clusters nb of events). In this case pixel_lumi_counting_hists_AlCaLumiPixels_193112.root

• Run modified version of process_pixel_lumi.py, called process_pixel_lumi_noBeamFlag.py on the file created in the step above. Below the command that i used for testing

python process_pixel_lumi_noBeamFlag.py AlCaLumiPixels 2012

=> This will give in output the print with integrated luminosity and some plots

Additional Info

• PPD EPR list

-- MarcoZanetti - 18 Sep 2014