r170 - 27 Dec 2014 - 19:23:13 - VictoriaSanchezMartinezYou are here: TWiki >  Main Web  >  TWikiUsers > VictoriaSanchezMartinez



led-purpleVictoriaSanchezMartinez - IFIC - ... in construction ...



Preparing your Digital Certificate

The followings steps should be done to install your certificate in the shell (see the twiki page WorkBookStartingGrid ) either of LXPLUS or AFS AtlasDataProcessingAtIFIC2015:
~> ssh -X vicsanma@ui06.ific.uv.es            ### ssh -X vsanchez@lxplus.cern.ch
~> cd $HOME
~> mkdir -p .globus
~> cd .globus
~> cp /*/myCertificate.p12 .
~> openssl pkcs12 -in myCertificate.p12 -clcerts -nokeys -out usercert.pem
~> openssl pkcs12 -in myCertificate.p12 -nocerts -out userkey.pem
~> chmod 400 userkey.pem
~> chmod 444 usercert.pem
~> source /afs/cern.ch/project/gd/LCG-share/current/etc/profile.d/grid_env.sh
~> voms-proxy-init -voms atlas
usercert.pem is the certificate file and userkey.pem is the private key file.

This certificate myCertificate.p12 should be copied across to your laptop and imported into the browser:

  • Preferences (or Tools) → Advanced → Encryption → View Certificates → Your Certificates → Import
To confirm that the browser certificate is installed and correctly working, we will confirm that you are able to log into AMI (click on Account Validation). If you have any expired certificates this is a good time to remove them - but be careful not to remove current ones.



Athena

The Athena framework (AthenaFramework-I and AthenaFramework-II) is an enhanced version of the Gaudi framework that was originally developed by the LHCb experiment, but is now a common ATLAS-LHCb project and is in use by several other experiments including GLAST and HARP. Athena and Gaudi are concrete realizations of a component-based architecture (also called Gaudi) which was designed for a wide range of physics data-processing applications. The fact that it is component-based has allowed flexibility in developing both a range of shared components and, where appropriate, components that are specific to the particular experiment and better meet its particular requirements.

The ATLAS software is divided into packages, and these are managed through the use of a configuration management tool, CMT. This is used to copy ("check out") code from the main ATLAS repository and handle linking and compilation.

You can check all the athena's releases here:

~> ssh -X vicsanma@ui06.ific.uv.es  
~> ls $VO_ATLAS_SW_DIR/software/
(Beware: before was ~> ls ${VO_ATLAS_SW_DIR}/prod/releases ).


Athena 15.X.Y

Valid for Athena's releases like 15.X.Y. You must prepare your account, in the following way. Note that the cmthome directory does not have to be in $HOME, it can be in any sub-directory, but if so you will need to amend all the following examples accordingly.
~> ssh -X vicsanma@ui06.ific.uv.es
~> cd $HOME
~> mkdir -p AthenaTestArea/15.X.Y/cmthome
~> cd AthenaTestArea/15.X.Y/cmthome
~> emacs requirements &   ###this file is shown below
~> source $VO_ATLAS_SW_DIR/software/15.X.Y/cmtsite/setup.sh
~> cmt config
~> 
~> cd $HOME
~> source AthenaTestArea/15.X.Y/cmthome/setup.sh -tag=15.X.Y,setup
~> 
~> echo $TestArea
~> cd $TestArea
~> cmt show versions PhysicsAnalysis/AnalysisCommon/UserAnalysis   
~> cmt co -r UserAnalysis-00-15-04 PhysicsAnalysis/AnalysisCommon/UserAnalysis
~> cd PhysicsAnalysis/AnalysisCommon/UserAnalysis/cmt/
~> cmt config
~> source setup.sh
~> cmt make

The requirements file is like this:

#---------------------------------------------------------------------
set CMTSITE STANDALONE #establecer el cmtsite???#
###old###set SITEROOT ${VO_ATLAS_SW_DIR}/prod/releases/rel_15-24/
set SITEROOT ${VO_ATLAS_SW_DIR}/software/15.X.Y/
macro ATLAS_DIST_AREA ${SITEROOT}
macro ATLAS_TEST_AREA ${HOME}/AthenaTestArea

apply_tag projectArea
macro SITE_PROJECT_AREA ${SITEROOT}
macro EXTERNAL_PROJECT_AREA ${SITEROOT}
apply_tag simpleTest

set SVNROOT svn+ssh://vsanchez@svn.cern.ch/reps/atlasoff
apply_tag noSVNROOT

use AtlasLogin AtlasLogin-* $(ATLAS_DIST_AREA)
#set CMTCONFIG i686-slc5-gcc43-opt
#---------------------------------------------------------------------

Every time you close and open the terminal, you must set up Athena, doing:

~> cd $HOME
~> source AthenaTestArea/15.X.Y/cmthome/setup.sh -tag=15.X.Y,setup
~> cd $TestArea
~> cd PhysicsAnalysis/AnalysisCommon/UserAnalysis/run


Athena 16.X.Y

Valid for Athena's releases like 16.X.Y.
~> cd $HOME
~> source $VO_ATLAS_SW_DIR/local/setup.sh
~> mkdir -p AthenaTestArea/16.X.Y      ###old###export AtlasSetup=${VO_ATLAS_SW_DIR}/prod/releases/rel_16-2/AtlasSetup
~> export AtlasSetup=${VO_ATLAS_SW_DIR}/software/16.X.Y/AtlasSetup
~> alias asetup='source $AtlasSetup/scripts/asetup.sh'
~> asetup 16.X.Y --testarea=$HOME/AthenaTestArea --svnroot=svn+ssh://vsanchez@svn.cern.ch/reps/atlasoff --multitest --dbrelease "<latest>"
~> 
~> cd $TestArea
~> pwd
~> cmt co -r UserAnalysis-00-15-04 PhysicsAnalysis/AnalysisCommon/UserAnalysis
~> cd PhysicsAnalysis/AnalysisCommon/UserAnalysis/cmt/
~> cmt config
~> source setup.sh
~> cmt make
~> 
~> cd ../run
~> get_files AnalysisSkeleton_topOptions_AutoConfig.py   ###equivalent to: cp ../share/AnalysisSkeleton_topOptions_AutoConfig.py .

Every time you close and open the terminal, you must set up Athena, doing:

~> cd $HOME
~> source /lustre/ific.uv.es/sw/atlas/local/setup.sh
~> export AtlasSetup=${VO_ATLAS_SW_DIR}/software/16.X.Y/AtlasSetup
~> alias asetup='source $AtlasSetup/scripts/asetup.sh'
~> asetup 16.X.Y --testarea=$HOME/AthenaTestArea --svnroot=svn+ssh://vsanchez@svn.cern.ch/reps/atlasoff --multitest 
~> cd $TestArea/PhysicsAnalysis/AnalysisCommon/UserAnalysis/run/



MadGraph


Twikis, webs, information about MadGraph:

ToDo MadGraph is a matrix element creator. Given the process, MadGraph automatically creates the amplitudes for all the relevant subprocesses and produces the mappings for the integration over the phase space. This process-dependent information is packaged into MadEvent, and a self containted code is produced that can be downloaded from the web site and allows the user to calculate cross sections and to obtain unweighted events. Alternatively, events can be also generated directly from the web1, by filling a form and letting the code run over our clusters. Once the events have been generated - event information, (e.g. particle id's, momenta, spin, color connections) is stored in the “Les Houches Event Files” (LHEF) format -, may be passed directly to a shower Monte Carlo program (interface is available for Pythia) or be used as inputs for combined matrix element-shower calculations. A series of standard plots and a rootfile contaning the parton level events are also automatically created for events generated over the web. Optionally, rootfiles containing event at pythia or after a generic simulation of a detector (PGS) can be available.

The code is written in Fortran77 and has been developed using the g77 compiler under Linux. The code is parallel in nature and it is optimized to run on a PC farm. At present, the supported PBS batch managing systems are respectively Torque, proPBS and Condor at Italian, American and Belgian clusters. Process specific codes are self contained and therefore do not need any external library. In principle the matrix-element creator can handle any user's request, however, they are limitations of the code are related to the maximum number of final state QCD particles. Currently, the package is limited to ten thousands diagrams per subprocess. So, for example, W+5 jets which has been calculated, is close to its practical limit.


MadGraph4

MadGraph4. Once this package is compiled, it can be used in any other directory. This can be useful if you want to use the GRID. It was possible to install MG4 in local computers (evaluQ) and after run the package in the UserInterface's temporal, but it didn't achieve to work at MAC laptop.
~> ssh -X vicsanma@evaluQ.ific.uv.es
~> cd $DIRECTORY      ###directory where you want to work
~> gunzip MG4_vX.Y.Z.tar.gz
~> tar -xvf MG4_vX.Y.Z.tar
~> cd MG4_vX.Y.Z/
~> make
~> mkdir myTest
~> cp -a Template/ myTest/
~> cd myTest/
~> emacs Cards/proc_card.dat &      ###put the process which you want
~> bin/newprocess      ###it may take a few minutes...
~> emacs Cards/param_card.dat &      ###modify some properties like mass, width, couplings...
~> emacs Cards/run_card.dat &      ###modify some properties like Nºevents, Ebeam, pdf, scales, cuts...
~> bin/generate_events
     0 
     testName
The most important info after the generation is in testName_unweighted_events.lhe.gz, within the folder Events/. In this folder, there are other file named testName_banner.txt, which is a summary about all cards.dat.
In HTML/ folder, you can find a crossx.html file, which contains more information and feynman diagrams of the process.


MadGraph5

MadGraph5. In order to use MG5 in Ubuntu, we must have Python 2.6.5 y gcc4.4.3 (for now, we couldn't make it work at UserInterface). With MG5 we can work in two different ways:
1) Like we worked with MG4
~> ssh -X vicsanma@evaluQ.ific.uv.es
~> cd $DIRECTORY      ###directory where you want to work
~> gunzip MadGraph5_vX.Y.Z.tar.gz
~> tar -xvf MadGraph5_vX.Y.Z.tar
~> 
~> cd MadGraph5_vX.Y.Z/
~> mkdir myTest
~> cp -a Template/ myTest/
~> cd myTest/
~> emacs Cards/proc_card.dat &      ###put the process which you want
~> bin/newprocess      ###it may take a few minutes...
~> emacs Cards/param_card.dat &      ###modify some properties like mass, width, couplings...
~> emacs Cards/run_card.dat &      ###modify some properties like Nºevents, Ebeam, pdf, scales, cuts...
~> bin/generate_events
     0 
     testName


2) From bin/mg5

~> ssh -X vicsanma@evaluQ.ific.uv.es
~> cd $DIRECTORY      ###directory where you want to work
~> gunzip MG4_vX.Y.Z.tar.gz
~> tar -xvf MG4_vX.Y.Z.tar
~> 
~> cd MG4_vX.Y.Z/
~> bin/mg5
mg5> import model MODEL   ###you pick the MODEL
mg5> generate p p > t t~   ###PROCESS you want
mg5> output myTest   ###
mg5> exit
~> cd myTest/
~> emacs Cards/param_card.dat &
~> emacs Cards/run_card.dat &
~> bin/generate_events
     0 
     testName


LHApdf

To use mstw2008lo in MadGraph5, the users needs to install LHAPDF (see twiki page Using mstw2008lo in MadGraph5 ), which is recommended by MC12.
~> cd $DIRECTORY
~> gunzip lhapdf-5.8.8b1.tar.gz
~> tar -xvf lhapdf-5.8.8b1.tar
~> cd lhapdf-5.8.8b1
~> ./configure
~> make
~> sudo make install
~> bin/lhapdf-getdata cteq
~> bin/lhapdf-getdata mstw
The users must check if all the libraries which they want have been copied correctly. If not, they should copy them manually. With these steps, LHAPDF has been installed right!
~> cd $DIRECTORY/MadGraph5_v1_3_33
~> mkdir myTest
~> cd myTest
~> cp -a Template/ myTest/
~> mv Template/* .
~> rm -r Template/
~> more README.lhapdf       ## Follow these steps to get the libraries which you need
~> emacs Cards/proc_card_mg5.dat &
~> bin/newprocess_mg5
~> emacs Cards/param_card.dat &
~> emacs Cards/run_card.dat &
In your run_card.dat, you have to put the following :
# 'cteq6l1' = pdlabel ! PDF set
'lhapdf' = pdlabel ! PDF set
21000 = lhaid ! PDF number used ONLY for LHAPDF

NOTE: in folder lhapdf_5.8.8b1/ you can find a file name PDFsets.index. This file shows the correspondence between lhapdf's name and code.


right Table1 - This table compares the cross sections for samples with the same pdf but different center of mass energy. The samples have been generated with MadGraph5.v1.3.33
(the generated process was pp > o1 > tt~, where o1=KKG with m=1TeV):

lhaPDF
ECM (TeV)
cross-section
plot
cteq6l1
7
3.3689 pb mass
mstw2008lo68cl (21000)
7
3.8424 pb
cteq6l1
8
4.8214 pb mass
mstw2008lo68cl (21000)
8
5.4768 pb


right Table2 - This table shows the matching at different center of mass energy. The samples have been generated with MadGraph5.v1.3.33
(the generated process was pp > o1 > tt~ (+) pp > o1 > tt~g, where o1=KKG with m=1TeV):

lhaPDF
ECM (TeV)
cross-section
Matching
plot
mstw2008lo68cl (21000)
7
5.9556 pb 0 graph_CrossSection-Matching
mstw2008lo68cl (21000)
7
6.9326 pb 1
mstw2008lo68cl (21000)
7
xxx pb 2
mstw2008lo68cl (21000)
7
6.9160 pb 3
mstw2008lo68cl (21000)
8
8.6002 pb 0
mstw2008lo68cl (21000)
8
10.0930 pb 1
mstw2008lo68cl (21000)
8
xxx pb 2
mstw2008lo68cl (21000)
8
10.0450 pb 3


KKgluon with MSTW2008

KKgluon samples has been generated in three final states: dileptonic, semileptonic and allHadronic. In the following table, you can get the cards.dat used at the generation with MadGraph5_v1.3.33 & lhapdf_5.8.8b1(pdf=mstw2008) (using topBSM_v4.tar):

right Table3.1

Dilepton
Semilepton
Hadronic
generic
pp > o1 >tt~
t > b w+, w+ > l+ vl
t~ > b~ w-, w- > l- vl~
pp > o1 >tt~
t > b w+, w+ > l+ vl
t~ > b~ w-, w- > j j
pp > o1 >tt~
t > b w+, w+ > j j
t~ > b~ w-, w- > j j
pp > o1 >tt~
proc_card_KKGdilepton.dat proc_card_KKGsemilepton.dat proc_card_KKGhadronic.dat proc_card_KKG.dat
param_card_KKG.dat
run_card_KKG.dat
(Beware: this cards are for Ecm=7TeV!!!)


right Table3.2 - This table shows some information obtained in the generation at 7TeV and 8TeV (ptj,pta,ptl=0 and ptjmax,ptamax,ptlmax=infinity):

mass (GeV)
LHE sample name
# events
cross-section
mass plot
1000
kkgluon_MadGraph_dilepton_1000_7TeV
10k
0.2135 pb
mass
kkgluon_MadGraph_semilepton_1000_7TeV
10k
1.2812 pb
mass
kkgluon_MadGraph_hadronic_1000_7TeV
10k
1.9182 pb
mass
kkgluon_MadGraph_generic_1000_7TeV
10k
3.8427 pb
mass
kkgluon_MadGraph_dilepton_1000_8TeV
10k
0.3037 pb
mass
kkgluon_MadGraph_semilepton_1000_8TeV
10k
1.8290 pb
mass
kkgluon_MadGraph_hadronic_1000_8TeV
10k
2.7386 pb
mass
kkgluon_MadGraph_generic_1000_8TeV
10k
5.4812 pb
mass


right Table3.3 - This table shows some information obtained in the generation of pp > o1 > tt~ process with pdf=mstw2008 (ptj,pta,ptl=0 and ptjmax,ptamax,ptlmax=infinity):

mass (GeV)
LHE sample name
# events
cross-section
mass plot
proc
param
run
2200
test_KKG_2200_7TeV_unweighted.lhe
10k
0.044007 pb
mass
proc
param
run
2400
test_KKG_2400_7TeV_unweighted.lhe
10k
0.025679 pb
mass
2600
test_KKG_2600_7TeV_unweighted.lhe
10k
0.015819 pb
mass
2200
test_KKG_2200_8TeV_unweighted.lhe
10k
0.076869 pb
mass
2400
test_KKG_2400_8TeV_unweighted.lhe
10k
0.044984 pb
mass
2600
test_KKG_2600_8TeV_unweighted.lhe
10k
0.027520 pb
mass
(Beware: you have to change the values of mass, widht, scales and beam energy within the param_card.dat and run_card.dat).


NEW Matching Study

All the samples have been generation with MadGraph5_v1.3.33 & lhapdf_5.8.8b1(pdf=mstw2008).
This is an example of how the matching value affects at the cross section. To carry out this study, we've used different processes, all of them at semileptonic final state.

right Table4.1 - This table shows the different processes generated:

name
Process
more info
test1
A: p p > o1, o1 > t t~
B: p p > o1, o1 > t t~, (t > W+ b, W+ > l+ vl), (t~ > W- b~, W- > j j)
add: p p > o1, o1 > t t~, (t > W+ b, W+ > j j), (t~ > W- b~, W- > l- vl~)
C (ISR): p p > o1 j, o1 > t t~, (t > W+ b, W+ > l+ vl), (t~ > W- b~, W- > j j)
add: p p > o1 j, o1 > t t~, (t > W+ b, W+ > j j), (t~ > W- b~, W- > l- vl~)
D (FSR): p p > o1, o1 > t t~ j, (t > W+ b, W+ > l+ vl), (t~ > W- b~, W- > j j)
add: p p > o1, o1 > t t~ j, (t > W+ b, W+ > j j), (t~ > W- b~, W- > l- vl~)
 
test2
A: p p > o1, o1 > t t~
B: p p > o1, o1 > t t~, (t > W+ b, W+ > l+ vl), (t~ > W- b~, W- > j j)
add: p p > o1, o1 > t t~, (t > W+ b, W+ > j j), (t~ > W- b~, W- > l- vl~)
C (ISR): p p > o1 j, o1 > t t~, (t > W+ b, W+ > l+ vl), (t~ > W- b~, W- > j j)
add: p p > o1 j, o1 > t t~, (t > W+ b, W+ > j j), (t~ > W- b~, W- > l- vl~)
D (FSR): p p > o1, o1 > t t~ j, (t > W+ b, W+ > l+ vl), (t~ > W- b~, W- > j j)
add: p p > o1, o1 > t t~ j, (t > W+ b, W+ > j j), (t~ > W- b~, W- > l- vl~)
ΔRjj~0.4
pT(jet)~10GeV
Matching switched off (ickkw=0)
test3
A: p p > o1, o1 > t t~
B: p p > o1, o1 > t t~, (t > W+ b, W+ > l+ vl), (t~ > W- b~, W- > j j)
add: p p > o1, o1 > t t~, (t > W+ b, W+ > j j), (t~ > W- b~, W- > l- vl~)
C (ISR): p p > o1 j, o1 > t t~, (t > W+ b, W+ > l+ vl), (t~ > W- b~, W- > j j)
add: p p > o1 j, o1 > t t~, (t > W+ b, W+ > j j), (t~ > W- b~, W- > l- vl~)
D (FSR): p p > o1, o1 > t t~ j, (t > W+ b, W+ > l+ vl), (t~ > W- b~, W- > j j)
add: p p > o1, o1 > t t~ j, (t > W+ b, W+ > j j), (t~ > W- b~, W- > l- vl~)
ΔRjj~0.4
pT(jet)~10GeV
Matching switched on (ickkw=1)

right Table4.2 - This table shows the MATCHING STUDY using different initial process, for a KKG mass=500GeV, Ecm=8TeV and xqcut=10GeV. The param_card.dat used is the same for all the samples (param_card.dat). At MadGraph, jet has been defined as j = g u c d s u~ c~ d~ s~:

LHE sample name
# events
Cross-section
Top_mass plot
#TruthJets pT>20GeV
TruthJets plot
ControlCard
test1-A 10K 81.9790 mass xxx plot card
test1-B 10K 163.9800 mass xxx plot card
test1-C 10K 113.0400 mass xxx plot card
test1-D 10K 9.9047 mass xxx plot card
test2-A 10K 81.9460 mass xxx plot card
test2-B 10K 163.9100 mass xxx plot card
test2-C 10K 112.8400 mass xxx plot card
test2-D 10K 9.8637 mass xxx plot card
test3-A 10K 82.016 mass xxx plot card
test3-B 10K 163.980 mass xxx plot card
test3-C 10K 182.630 mass xxx plot card
test3-D 10K 11.352 mass xxx plot card
(you can find the ControlCards at /afs/cern.ch/user/v/vsanchez/public/Matching/ControlCards)


OLD Matching Study

This is an example of how the matching value affects at the cross section. To carry out this study, we've used differents processes:

right Table5.1 - This table shows the different initial process used:

name
Process
more info
test1
pp>o1>tt~  
test2
A: pp>o1>tt~ > bblvjj
B: pp>o1>tt~ > bbjjjj
 
test3
A: pp>o1>tt~ > bblvjj
B: pp>o1>tt~ > bblvjjg
C: pp>o1>tt~g > bblvjjg
ΔRjj~0.4
pT(jet)~10GeV
matching=0
test4
A: pp>o1>tt~ > bblvjj
B: pp>o1>tt~ > bblvjjg
C: pp>o1>tt~g > bblvjjg
ΔRjj~0.4
pT(jet)~10GeV
matching=1

right Table5.2 - This table shows the MATCHING STUDY using different initial process, for a KKG mass=1600GeV and Ecm=7TeV. The param_card.dat used is the same for all the samples (param_card.dat). At MadGraph, jet has been defined as j = g u c d s u~ c~ d~ s~:

LHE sample name
# events
Cross-section
Top_mass plot
#TruthJets pT>20GeV
TruthJets plot
proc
run
test1
10k
0.30868 pb
mass
7.237
jets
proc
run
test2_A
10k
0.15471 pb
mass
6.818
jets
proc
test2_B
10k
0.15492 pb
mass
7.825
jets
proc
test2_A+B
10k
0.30915 pb
mass
7.381
jets
proc
test3_A
10k
0.11528 pb
mass
6.970
jets
proc
run
test3_B
10k
0.01205 pb
mass
7.308
jets
proc
test3_C
10k
0.11423 pb
mass
7.546
jets
proc
test3_A+C
10k
0.22870 pb
mass
7.256
jets
proc
test3_A+B+C
10k
0.24036 pb
mass
7.255
jets
proc
test4_A
10k
0.11473 pb
mass
6.954
jets
proc
run
test4_B
10k
0.02739 pb
mass
7.258
jets
proc
test4_C
10k
0.18694 pb
mass
7.558
jets
proc
test4_A+C
10k
0.30140 pb
mass
7.322
jets
proc
test4_A+B+C
10k
0.32897 pb
mass
7.336
jets
proc

right Table5.3 - This table shows the MATCHING STUDY using different initial process, for a KKG mass=1600GeV and Ecm=8TeV. The param_card.dat used is the same for all the samples (param_card.dat). At MadGraph, jet has been defined as j = g u c d s u~ c~ d~ s~:

LHE sample name
# events
Cross-section
Top_mass plot
#TruthJets pT>20GeV
TruthJets plot
proc
run
test1
10k
0.50108 pb
mass
7.372
jets
proc
run
test2_A
10k
0.25089 pb
mass
6.945
jets
proc
test2_B
10k
0.24933 pb
mass
7.974
jets
proc
test2_A+B
10k
0.49918 pb
mass
7.491
jets
proc
test3_A
10k
0.18230 pb
mass
7.178
jets
proc
run
test3_B
10k
0.01844 pb
mass
7.470
jets
proc
test3_C
10k
0.19143 pb
mass
7.772
jets
proc
test3_A+C
10k
0.37555 pb
mass
7.470
jets
proc
test3_A+B+C
10k
0.39362 pb
mass
7.379
jets
proc
test4_A
10k
0.18296 pb
mass
7.118
jets
proc
run
test4_B
10k
0.04227 pb
mass
7.482
jets
proc
test4_C
10k
0.31355 pb
mass
7.811
jets
proc
test4_A+C
10k
0.49627 pb
mass
7.492
jets
proc
test4_A+B+C
10k
0.54072 pb
mass
7.558
jets
proc

right Table5.4 - This table shows the MATCHING STUDY using different initial process, for a KKG mass=500GeV and Ecm=8TeV. The param_card.dat used is the same for all the samples (param_card.dat). At MadGraph, jet has been defined as j = g u c d s u~ c~ d~ s~:

LHE sample name
# events
Cross-section
Top_mass plot
#TruthJets pT>20GeV
TruthJets plot
proc
run
test1
10k
82.025 pb
mass
7.
jets
proc
run
test2_A
10k
40.970 pb
mass
7.
jets
proc
test2_B
10k
40.990 pb
mass
7.
jets
proc
test2_A+B
10k
81.927 pb
mass
7.
jets
proc
test3_A
10k
38.770 pb
mass
7.
jets
proc
run
test3_B
10k
7.666 pb
mass
7.
jets
proc
test3_C
10k
21.986 pb
mass
7.
jets
proc
test3_A+C
10k
60.823 pb
mass
7.
jets
proc
test3_A+B+C
10k
68.471 pb
mass
7.
jets
proc
test4_A
10k
38.837 pb
mass
7.
jets
proc
run
test4_B
10k
14.982 pb
mass
7.
jets
proc
test4_C
10k
35.192 pb
mass
7.
jets
proc
test4_A+C
10k
74.185 pb
mass
7.
jets
proc
test4_A+B+C
10k
89.046 pb
mass
7.
jets
proc

To obtain the Truth Jets with pT>20GeV plot, you have to get both files classTRUTH.C and classTRUTH.h, and run them over the my.truth.ntup.root file as follow:

~> cd FOLDER   ###this folder contains my.truth.ntup.root and classTRUTH.*
~> root -l -q classTRUTH.C+
~> root
root> .L classTRUTH.C+
root> classTRUTH* t = new classTRUTH; t->Loop();
root> ### save canvas3.C
root> ### save canvas4.C


right KKG's codes:

  • MadGraph: 6000048.
  • Pythia: 5100021.

Validation process (mc12)

To verify that the LHEF samples have been made properly and the new JobOption works, we have to run Generate_trf.py (it takes you around 10min) and Reco_trf.py (it takes you around 25min) over the file.tar.gz (this is the unweighted.lhe file) and use your JobOption. With this script you can obtain the my.truth.ntup.root... With this package you can obtain the my.truth.ntup.root and the validation plots...

right To generate the new JOs files: get this two files (script and template) and run "source New_JO_cambiarNombre.sh". Thus, you'll obtain all the JOs files for the kkg.

right README:

~> Beware!!! log in to @lxplus440 (it works with SL5)
~> Download the package validation_MC12_vsm.tar and untar it.
~> Copy JobOptions file, group file (with extension .events and .tar.gz) inside the validation folder (this will be your work directory).
~> Be sure inside the folder the following files exist:
         parse_evgen_log.py
         MC12JobOpts-00-04-85_v0.tar.gz 
            (http://atlas-computing.web.cern.ch/atlas-computing/links/kitsDirectory/EvgenJobOpts/)
            (more /cvmfs/atlas.cern.ch/repo/sw/Generators/MC12JobOptions/tag   -->   MC12JobOptions-00-10-78/)
~> Open runGenerationValidation.sh file and choose the suitable variables:
         Athena's release (17.2.4.8 for these files and scripts)
         (ls /cvmfs/atlas.cern.ch/repo/sw/software/x86_64-slc6-gcc47-opt/17.8.0/AtlasProduction/17.8.0.3/)
         Mass ($MASS)
         RunNumber ($RUNNUMBER)
         JobOptions name ($JOBOPTIONS)
         GroupFile name ($GroupFile)
         Work directory name ($WORKdirectory)
~> Inside the work directory execute "source runGenerationValidation.sh"
~> Finally, you'll obtain several plots...

~> ls /cvmfs/atlas.cern.ch/repo/sw/software/17.2.4/AtlasProduction/17.2.4.8/Generators/EvgenJobTransforms/scripts/
### Generate_trf.py
~> ls /cvmfs/atlas.cern.ch/repo/sw/software/17.2.4/AtlasProduction/17.2.4.8/Generators/MC12JobOptions/
### TODO  bin  cmt   common   gencontrol  i686-slc5-gcc43-opt  share
~> ls /cvmfs/atlas.cern.ch/repo/sw/software/17.2.4/AtlasProduction/17.2.4.8/InstallArea/jobOptions/MC12JobOptions/
### Pythia8_AU2_MSTW2008LO_Common.py ...
~> ls /cvmfs/atlas.cern.ch/repo/sw/software/x86_64-slc5-gcc43-opt/17.2.4/AtlasProduction/17.2.4.8/InstallArea/share/bin/Generate_trf.py
~> ls /cvmfs/atlas.cern.ch/repo/sw/software/x86_64-slc5-gcc43-opt/17.2.4/AtlasProduction/17.2.4.8/InstallArea/share/bin/Reco_trf.py
~> 
      JOBOPTSEARCHPATH=/cvmfs/atlas.cern.ch/repo/sw/Generators/MC12JobOptions/latest/common:$JOBOPTSEARCHPATH
      JOBOPTSEARCHPATH=/cvmfs/atlas.cern.ch/repo/sw/Generators/MC12JobOptions/latest/gencontrol:$JOBOPTSEARCHPATH
      JOBOPTSEARCHPATH=/cvmfs/atlas.cern.ch/repo/sw/Generators/MC12JobOptions/latest/share/DSID182xxx:$JOBOPTSEARCHPATH

right README for SLC6: for now it doesn't work!!! The only supported MC12 evgen release is 17.2.X.Y. Also, for MC12 reco it is 17.2.X.Y again or 17.3.X.Y for upgrade samples...




MC & DATA - produced samples

FALTA Input files generated with MadGraph5 and different PDFs.
See our private ProducedSamples generated by Exotics Physics Group at IFIC with differents MadGraph's releases.

MC11 - KKgluon

These the produced KKgluon-MC-samples have these features:
  • MG_ME_V4.4.57
  • PDF set = cteq6l1
  • Ecm=7TeV
  • ptj=20; pta,ptl=10 and ptjmax,ptamax,ptlmax=infinity (1d5)

right Table6.1 - This table shows some features about the KKgluon samples generated with MadGraph4.

mass (GeV)
width (GeV)
LHE sample name
# events
cross-section
mass plot
control card
ID
2250
344.25
test_2250_1_KKGLUON.lhe
10k
0.031173 pb
mass
ControlCard
158768
2500
382.50
test_2500_1_KKGLUON.lhe
10k
0.016377 pb
mass
ControlCard
158769


These the produced KKgluon-MC-samples have these features:

  • MadGraph5_v1.3.33
  • PDF set = cteq6l1
  • Ecm=7TeV
  • ptj=20; pta,ptl=10 and ptjmax,ptamax,ptlmax=infinity (1d5)

right Table6.2 - This table shows some features about the KKgluon samples. The control_card.dat is a summary about the proc_card.dat, param_card.dat and run_card.dat used in the production. You can run this script (script) to get all the samples.

mass (GeV)
width (GeV)
LHE sample name
# events
cross-section
mass plot
control card
ID
2250
344.25
test_cteq6l_1_7TeV_mass2250_KKG.lhe
10k
0.033437 pb
mass
ControlCard
158768
2500
382.50
test_cteq6l_1_7TeV_mass2500_KKG.lhe
10k
0.017576 pb
mass
ControlCard
158769


MC12 - KKgluon

All the produced KKgluon-MC-samples have these features:
  • MadGraph5_v1.3.33
  • lhapdf_5.8.8b1(pdf=mstw2008 - lhapdf=21000)
  • Ecm=8TeV
  • ptj,pta,ptl=0 and ptjmax,ptamax,ptlmax=infinity


right Table7.1 - This table shows some features about the KKgluon samples. The ControlCard.txt is a summary about the proc_card.dat, param_card.dat and run_card.dat used in the production. You can run these two scripts (script1 and script2) to get all the samples, but you need to use these templates (KKG_run_card_template.dat and KKG_param_card_template.dat):

mass (GeV)
width (GeV)
LHE sample name
# events
cross-section
mass plot
control card
ID
400
61.20
test_mstw2008_1_8TeV_mass400_KKG.lhe
100k
112.1900 pb
mass
ControlCard
182764
500
76.50
test_mstw2008_1_8TeV_mass500_KKG.lhe
10k
81.9270 pb
mass
ControlCard
115550
600
91.80
test_mstw2008_1_8TeV_mass600_KKG.lhe
10k
45.0410 pb
mass
ControlCard
115551
700
107.10
test_mstw2008_1_8TeV_mass700_KKG.lhe
10k
25.1950 pb
mass
ControlCard
115552
800
122.40
test_mstw2008_1_8TeV_mass800_KKG.lhe
10k
14.6300 pb
mass
ControlCard
115553
900
137.70
test_mstw2008_1_8TeV_mass900_KKG.lhe
10k
8.8067 pb
mass
ControlCard
119318
1000
153.00
test_mstw2008_1_8TeV_mass1000_KKG.lhe
10k
5.4726 pb
mass
ControlCard
115554
1150
175.95
test_mstw2008_1_8TeV_mass1150_KKG.lhe
10k
2.8164 pb
mass
ControlCard
119319
1300
198.90
test_mstw2008_1_8TeV_mass1300_KKG.lhe
10k
1.5233 pb
mass
ControlCard
115555
1600
244.80
test_mstw2008_1_8TeV_mass1600_KKG.lhe
10k
0.5004 pb
mass
ControlCard
115556
1800
275.40
test_mstw2008_1_8TeV_mass1800_KKG.lhe
10k
0.2556 pb
mass
ControlCard
115799
2000
306.00
test_mstw2008_1_8TeV_mass2000_KKG.lhe
10k
0.1369 pb
mass
ControlCard
119582
2250
344.25
test_mstw2008_1_8TeV_mass2250_KKG.lhe
10k
0.0670 pb
mass
ControlCard
158768
2500
382.50
test_mstw2008_1_8TeV_mass2500_KKG.lhe
10k
0.0351 pb
mass
ControlCard
158769
2750
420.75
test_mstw2008_1_8TeV_mass2750_KKG.lhe
10k
0.019606 pb
mass