PpsCepStudies < Sandbox

<style type="text/css" media="all">
pre {text-align: left; padding: 10px; color: black; font-size: 12px;}
pre.command {background-color: lightgrey;}
pre.config {background-color: lightblue;}
pre.code {background-color: lightpink;}
pre.output {background-color: lightgreen;}
pre.file {background-color: lightyellow;}
pre.note {background-color: white;}
</style>

<br />
<font color="blue" face="verdana" size="6">CT-PPS CEP Studies</font>

   * *CT-PPS Twiki:* [[CMS.CmsTotemPrecisionProtonSpectrometer][here]]
   * *CT-PPS Test Beam 2015:* [[CMS.PPSTestBeamRunControl][here]]
   * *CT-PPS On Line Software:* [[CMS.CTPPSOnlineSoftware#Setup_and_Control_registers_for][here]]
   * *CT-PPS Reconstruction Software:* [[https://github.com/pps-tb-sw/pps-reconstruction][here]]
   * *CT-PPS Fast Simulation:* [[%SCRIPTURL{"view"}%auth/CMS/PPSFastSimulation][here]]
   * *Private code Repository:* [[https://github.com/uerj-cms-cep-studies][here]]

%TOC%

%TWISTY{
prefix="<h4>"
mode="div"
link="Monte Carlo Generators (papers)"
showimgleft="%ICONURLPATH{toggleopen}%"
hideimgleft="%ICONURLPATH{toggleclose}%"
suffix="</h4>"
}%

   * *ExHuME: A Monte Carlo Event Generator for Exclusive Diffraction* [[https://arxiv.org/pdf/hep-ph/0502077v1.pdf][here]]
   * *FPMC: a generator for forward physics* [[http://arxiv.org/abs/1102.2531][here]]

%ENDTWISTY%

%TWISTY{
prefix="<h4>"
mode="div"
link="Related Papers"
showimgleft="%ICONURLPATH{toggleopen}%"
hideimgleft="%ICONURLPATH{toggleclose}%"
suffix="</h4>"
}%

   * *Add paper 1*
   * *Add paper 2*

%ENDTWISTY%

---+ Software Goal

Goal is...

---+ Getting Started

---++ Text background color convention

In this page, the following text background color convention is used:

<verbatim class="command">
GREY: For commands.
</verbatim>
<verbatim class="output">
GREEN: For the output example of the executed commands (nearly what the user should see in his/her terminal).
</verbatim>
<verbatim class="code">
PINK: For CMSSW parameter-set configuration files.
</verbatim>
<verbatim class="config">
BLUE: For configuration files.
</verbatim>
<verbatim class="file">
YELLOW: For any other type of file.
</verbatim>


---++ Checkout PPS FastSim Package

<verbatim class='command'>
cmsrel CMSSW_8_0_0_pre5 # or later
cd CMSSW_8_0_0_pre5/src
git clone  git@github.com:CTPPS/CTPPSFastSim.git .
cmsenv
scram b -j 8
</verbatim>

---++ Git Commands

---++ CRAB3 Quick Start

For more details check: [[CMSPublic.WorkBookCRAB3Tutorial][CRAB3 Tutorial]]

%TWISTY{
prefix="<h4>"
mode="div"
link="Basic commands if you do not have time to loose"
showimgleft="%ICONURLPATH{toggleopen}%"
hideimgleft="%ICONURLPATH{toggleclose}%"
suffix="</h4>"
}%

For LXPLUS users:

<verbatim class='command'>
ssh -XY <username>@lxplus.cern.ch
</verbatim>

Setup CRAB3 by sourcing:

<verbatim class='command'>
source /cvmfs/cms.cern.ch/crab3/crab.sh
</verbatim>

There is also an alternative way to do this by using the light client script. The crab_light.sh script sources the crab.sh script without polluting the environment with extra variables. The sourced CRAB3 Client is the same with both scripts.

<verbatim class='command'>
source /cvmfs/cms.cern.ch/crab3/crab_light.sh
</verbatim>

Check the version being used by executing:

<verbatim class='command'>
which crab
</verbatim>

Get a CMS VO proxy

<verbatim class='command'>
voms-proxy-init --voms cms --valid 168:00
</verbatim>

To submit a task, execute the following CRAB command:

<verbatim class='command'>
crab submit -c crabConfig.py
</verbatim>

To check the status of a task, execute the following CRAB command:

<verbatim class='command'>
crab status --dir/-d <CRAB-project-directory>
</verbatim>

CRAB allows the user to resubmit a task, which will actually resubmit only the failed jobs in the task. The resubmission command is as follows:

<verbatim class='command'>
crab resubmit --dir/-d <CRAB-project-directory>
</verbatim>

In case one wants to retrieve some output ROOT files of a task, one can do so with the following CRAB command:

<verbatim class='command'>
crab getoutput --dir/-d <CRAB-project-directory> [--jobids <comma-separated-list-of-jobs-and/or-job-ranges>]
</verbatim>

%ENDTWISTY%

---+ Monte Carlo Private Samples

---++ Minimum Bias Sample

   * *Release*: CMSSW_8_0_0_pre5

   * *Number of events*: 3775000

   * *DAS Direct Link:* [[https://cmsweb.cern.ch/das/request?input=%2FMinBias_13TeV_TuneCUETP8M1%2Fmdealmei-MinBias_13TeV_TuneCUETP8M1_Realistic50ns13TeVCollision-99069aa9d70f3e36c393d9c453465293%2FUSER&instance=prod%2Fphys03][here]]

   * *cmsDriver command*:
<verbatim class='command'>
cmsDriver.py MinBias_13TeV_pythia8_TuneCUETP8M1_cfi -n 1000 --fast --conditions auto:run2_mc --magField 38T_PostLS1 //
--beamspot Realistic50ns13TeVCollision -s GEN,SIM,RECOBEFMIX --eventcontent FASTPU --datatier GEN-SIM-RECO //
--era Run2_25ns --fileout minbias.root --no_exec
</verbatim>

---++ GluGlu to Dijets with Pile Up

   * *Release*: CMSSW_8_0_0_pre5

   * *Number of events*: 87000 evts

   * *DAS Direct Link:* [[https://cmsweb.cern.ch/das/request?input=%2FGluGluTo2Jets_PU_13TeV_TuneCUETP8M1_Realistic50ns13TeVCollision%2Fmdealmei-GluGluTo2Jets_PU_13TeV_TuneCUETP8M1_Realistic50ns13TeVCollision-3455a400ea82cc1169de5af0fe3c5a9e%2FUSER&instance=prod%2Fphys03][here]]

   * *cmsDriver command*:
<verbatim class='command'>
cmsDriver.py GluGluTo2Jets_M_100_7TeV_exhume_cff.py -n 10 --fast --conditions auto:run2_mc //
--pileup_input das:/RelValMinBiasFS_13_ForMixing/CMSSW_8_0_0-80X_mcRun2_asymptotic_v4_FastSim-v1/GEN-SIM-RECO //
--eventcontent AODSIM -s GEN,SIM,RECOBEFMIX,DIGI:pdigi_valid,RECO --beamspot NominalCollision2015 //
--datatier GEN-SIM-DIGI-RECO --pileup AVE_35_BX_25ns --era Run2_25ns //
--customise FastSimulation/PPSFastSim/customise_FastSimCTPPS_cff.customise_pu_protons_ctpps --pileup_dasoption limit 0 --no_exec
</verbatim>

You sould modify the follow parameters on your configuration fragment:

<verbatim class='config'>
MassRangeHigh = cms.double(2000.0)
MassRangeLow = cms.double(300.0)

comEnergy = cms.double(13000.0)

process.mix.input.fileNames = cms.untracked.vstring([
        'root://cms-xrd-global.cern.ch//store/user/mdealmei/MinBias_13TeV_TuneCUETP8M1/MinBias_13TeV_TuneCUETP8M1_Realistic50ns13TeVCollision/160623_135638/0000/minbias_45.root',
        'other_file.root',
        'last_file.root'
])
</verbatim>

You can check the configuration fragment [[https://cernbox.cern.ch/index.php/s/FFKkqu5CkgMQiIJ][here]] and the crab parameters[[https://cernbox.cern.ch/index.php/s/vEMALzyJwKXpmJr][here]]

---++ CEP Dijets

---++ FPMC

The FPMC generator (unofficial) with HepMC output can be obtained from:
<verbatim class='command'>
git clone https://github.com/ForwardPhysicsMC/fpmc.git
</verbatim>
In the FPMC directory, compile with:
<verbatim class='command'>
make fpmc-hepmc
</verbatim>
and run the code like:
<verbatim class='command'>
./fpmc-hepmc --cfg Datacards/dataQED_WW --comenergy 13000 --fileout FPMC_WW_13TeV.hepmc --nevents 10000
</verbatim>
Warning: The dataQED_WW datacard is working, but some datacards can be not working.

To use the HepMC output in CT-PPS FastSimulation we need a configuration fragment to produce the configuration file to run the FastSimulation.
First go to src directory and do this:
<verbatim class='command'>
mkdir Configuration
cd Configuration
mkdir Generator
cd Generator 
mkdir python
cd python
wget https://raw.githubusercontent.com/uerj-cms-cep-studies/tmp/master/readHepMC_cff.py
</verbatim>
Now you have the fragment in the right place.
In the src directory do:
<verbatim class='command'>
cmsDriver.py readHepMC_cff.py -n 10 --fast --conditions auto:run2_mc --eventcontent AODSIM -s GEN,SIM,RECOBEFMIX,DIGI:pdigi_valid,RECO --beamspot Realistic50ns13TeVCollision --datatier GEN-SIM-DIGI-RECO --pileup NoPileUp --era Run2_25ns --customise FastSimulation/PPSFastSim/customise_FastSimCTPPS_cff.customise --no_exec
</verbatim>
and in readHepMC_cff_py_GEN_SIM_RECOBEFMIX_DIGI_RECO.py file add the line 
<verbatim class='config'>
process.VtxSmeared.src = 'source'
</verbatim>

The configuration file needs a filter, which is used in process.generator. This filter can be obtained doing:
<verbatim class='command'>
mkdir inputHepMC
cd inputHepMC
mkedfltr inputHepMC
</verbatim>
Warning: This filter return true for all events. If you want a specific channel you can modify the filter. For example the WW production decaying in the semileptonic channel is modified like: https://raw.githubusercontent.com/uerj-cms-cep-studies/tmp/master/inputHepMC.cc .

Compile the code:
<verbatim class='command'>
scram b -j 8
</verbatim>
Now you can run the configuration file :)
<verbatim class='command'>
cmsRun readHepMC_cff_py_GEN_SIM_RECOBEFMIX_DIGI_RECO.py
</verbatim>


---+ CT-PPS Tools

The goal of this private package is to provide a set of useful tools for CEP studies using the CT-PPS detector.

---++ DoubleArmFilter

This filter does the following:

   * Check which proton combination reconstruct a vertex compatible (in z) with the hardest vertex in the event, putting their track indices in a std::pair<size_t fwd_track_idx,size_t bkw_track_idx>;

   * All combinations found are put in the event inside a std::vector<std::pair<size_t,size_t> >.

   
To get the filter:
<verbatim class='command'>
$ cd CMSSW_8_0_12/src
$ cmsenv
$ mkdir tmp
$ cd tmp
$ git clone git@github.com:uerj-cms-cep-studies/CTPPSTools.git
$ git clone git@github.com:uerj-cms-cep-studies/DataUtils.git
$ mv CTPPSTools ../
$ mv DataUtils ../
$ rm -rf tmp
$ scram b -j 8
</verbatim>

On your configuration file add the follow statements:
<verbatim class='config'>
process.load('CTPPSTools.Filters.doubleArmFilter_cfi')
process.doubleArmFilter.vertices = 'offlineSlimmedPrimaryVertices'
process.doubleArmFilter.tofRes = 20 # ToF resolution in ps

process.p1 = cms.Path(process.doubleArmFilter * [anything] )
</verbatim>

To get the protons in your analyzer:
<verbatim class='code'>
edm::EDGetTokenT<std::vector<std::pair<size_t,size_t> > > tracks_tk;
edm::Handle<std::vector<std::pair<size_t,size_t> > > tracks;
tracks_tk = consumes<std::vector<std::pair<size_t,size_t> > >(edm::InputTag("doubleArmFilter","tracks"))); // this line must be in your constructor!
event.getByToken(tracks_tk, tracks); // in the event loop
</verbatim>


---+ Tips

---++ How to access CERNBox directly from lxplus

<verbatim class='code'>
source /afs/cern.ch/project/eos/installation/user/etc/setup.sh
export EOS_MGM_URL=root://eosuser.cern.ch
eosmount $HOME/eos
</verbatim>

if it works, you will see something like this:

<verbatim class='output'>
.... trying to create ... /afs/cern.ch/user/m/mdealmei/eos
OK
===> Mountpoint   : /afs/cern.ch/user/m/mdealmei/eos
===> Fuse-Options : kernel_cache,attr_timeout=30,entry_timeout=30,max_readahead=131072,max_write=4194304,fsname=eosuser.cern.ch root://eosuser.cern.ch//eos/
===> xrootd ra             : 131072
===> xrootd cache          : 393216
===> fuse debug            : 0
===> fuse write-cache      : 1
===> fuse write-cache-size : 100000000
</verbatim>


---++ How to merge edm files

edmCopyPickMerge inputFiles_load=~/eos/user/m/mdealmei/ListOfFiles.txt outputFile=~/eos/user/m/mdealmei/output.root

-- Main.MarcoPacheco - 2016-06-24
Topic revision: r12 - 2016-10-03 - MarcoPacheco
Account
- Log In
- Cern Search
- TWiki Search
- Google Search
Sandbox All webs
Edit
Attach
Copyright &© 2008-2021 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