FWlite and Pattuple (continously updated)
Cose piu' specifiche per l'analisi (UNDER CONSTRUCTION)
Where to find the MC files
The status of MC files can be found here . Go to DBS , click on Navigator, copy the string corresponding to the MC files.
How to run on Grid (UNDER CONSTRUCTION)
The first time:
For all other times:
source /afs/cern.ch/cms/LCG/LCG-2/UI/cms_ui_env.csh voms-proxy-init -voms cms (and Enter the Grid phrase that you have chosen) source /afs/cern.ch/cms/ccs/wm/scripts/Crab/crab.csh
cd myarea/CMSSW_x_x_x/src, like ~/scratch0/StarterKit/CMSSW_2_1_9/src (for the AOD to PAT)
or like ~/scratch0/CMSSW_2_2_4/src/Firenze/Reduction/test (for the PAT to Firenze's ntuples)
eval `scramv1 r -csh`
total_number_of_events=10000 events_per_job = 1000- create a directory in castor for the output file
rfmkdir /castor/cern.ch/user/e/egallo/Zmumu rfchmod +775 /castor/cern.ch/user/e/egallo/Zmumu- in the crab.cfg file specify
### OUTPUT files Management ## output back into UI return_data = 0 ### OUTPUT files INTO A SE copy_data = 1 storage_element = srm-cms.cern.ch storage_path=/srm/managerv2?SFN=/castor/cern.ch lfn=/user/e/egallo/Zmumu (storage_path = /srm/managerv2?SFN=/castor/cern.ch/user/e/egallo/Zmumu IS THE OLD WAY)
crab -h if it is gives error: eval `scramv1 r -csh` crab -create (crea un certo numero di directories) crab -submit crab -status
crab -getoutputThe output file is copied in the subdirectory crab_xxx/res.
To kill
crab -kill all -c crab_0_101125_010648(for instance)More about CRAB and CRAB Faq.
rfdir /castor/cern.ch/user/e/egallo/Zmumu/to see if it is really there. It can be opened in root, as an example, as:
TFile *_file0 = TFile::Open("rfio:/castor/cern.ch/user/e/egallo/Zmumu/PATLayer1_Output.fromAOD_full_1.root")
To try:
crab -copyData [range -dest_se=the official SE name or -dest_endpoint=the
complete endpoint of the remote SE]
Option that can be used only if your output have been previously
copied by CRAB on a remote SE. By default the copyData copies your output
from the remote SE locally on the current CRAB working directory
(under res). Otherwise you can copy the output from the remote SE to
another one, specifying either -dest_se=
or -dest_endpoint=. If dest_se is
used, CRAB finds the correct path where the output can be stored.
Example: crab -copyData --> output copied to crab_working_dir/res
directory
crab -copyData -dest_se=T2_IT_Legnaro --> output copied to
the legnaro SE, directory discovered by CRAB
crab -copyData
-dest_endpoint=srm://:8443/xxx/yyyy/zzzz --> output copied to the
se under
/xxx/yyyy/zzzz directory.
Plots until Apr09
Plots after Apr09
Files for signal MC ,
Files for background MC
Firenze's ntuple from PATtuples
su lxplus, LA PRIMA VOLTA:
scramv1 project CMSSW CMSSW_1_6_7
cd CMSSW_1_6_7/src
eval `scramv1 runtime -csh`
cmscvsroot CMSSW
cvs login
***********************************************************
Logging in to
:pserver:anonymous@cmscvs.cern.ch:2401/cvs_server/repositories/CMSSW
CVS password: ********
***********************************************************
mkdir mydirectory (un nome qualsiasi)
cd mydirectory
mkedanlzr Jet (ad esempio, nome del mio analyzer)
Questo corrisponde al'installazione della software version 1_6_7.
(More about
l'analyzer )
PER TUTTE LE ALTRE VOLTE, basta fare:
eval `scramv1 runtime -csh`
cmscvsroot CMSSW
cd src/mydirectory/Jet/src (lo user code e' in Jet.cc)
(More about scram )
Il file Jet.cc generato automaticamente e' fatto piu' o meno
cosi' .
Un esempio piu' sofisticato preparato da Didar per me e che calcola
un po' di variabili per jets e muoni puo' essere trovato
qui . Per compilarlo sostituire il
file BuildFile in Jet con questo .
Per COMPILARE:
cd ~/work/CMSSW_1_6_7/src/mydirectory/Jet
scramv1 b
Per RUNNARE bisogna prima modificare il file Jet.cfg, che e' il file di configurazione (more about
configuration files) con control cards etc. Va modificato mettendo i files di input etc., il numero di eventi, etc. Un esempio che
runna su files di MC Z+3jets con 10 eventi puo' essere trovato
qui . I files MC possono essere trovati
su
questa pagina (la
versione CMSSW_1_5_2 e' recommended da Didar). Per RUNNARE (cmsRun e' il nome
dell'eseguibile):
cd ~/work/CMSSW_1_6_7/src/mydirectory/Jet
cmsRun Jet.cfg
cmsRun ci mette un po' e crea in questo esempio un file root
con 10 eventi e un po' di variabili in default-filename.root.