This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
2015:groups:higgs:dmhiggs:monoh [2016/01/19 00:30] jory.sonneveld [Information/HowTo] |
2015:groups:higgs:dmhiggs:monoh [2016/01/23 22:49] nicola.de_filippis |
||
---|---|---|---|
Line 41: | Line 41: | ||
==== Parton Events ==== | ==== Parton Events ==== | ||
The **lhe files** for the different models are here: | The **lhe files** for the different models are here: | ||
+ | |||
+ | ==2HDM== | ||
+ | * https://cernbox.cern.ch/index.php/s/LALgzaMjbgj8rNX | ||
==hhxx== | ==hhxx== | ||
Line 154: | Line 157: | ||
Let me start with the necessary installation steps: | Let me start with the necessary installation steps: | ||
- Download and install HepMC from here [[http://lcgapp.cern.ch/project/simu/HepMC/download/HepMC-2.06.09.tar.gz]]. In the following I will call the directory /hepmcdir | - Download and install HepMC from here [[http://lcgapp.cern.ch/project/simu/HepMC/download/HepMC-2.06.09.tar.gz]]. In the following I will call the directory /hepmcdir | ||
- | - Download the latest Pythia8 from here [[http://home.thep.lu.se/~torbjorn/pythia8/pythia8209.tgz]]. Note that I had problems using any older version (even 8205!). If you do have an older version of Pythia lying around, set your library path to start with this pythia version: 'export LD_LIBRARY_PATH=/pythia8dir/lib'; | + | - Download the latest Pythia8 from here [[http://home.thep.lu.se/~torbjorn/pythia8/pythia8209.tgz]]. Note that I had problems using any older version (even 8205!). If you do have an older version of Pythia lying around, set your library path to start with this pythia version: 'export LD_LIBRARY_PATH=/pythia8dir/lib:$LD_LIBRARY_PATH'; |
- <nowiki>./configure --enable-shared --with-hepmc2=/hepmcdir; make; make install</nowiki>. Even if you have Pythia, if you did not compile it with enable-shared options before you **cannot** run the Pythia-Delphes chain! In that case you have to install Pythia8 anew! In the following I will call the directory /pythiadir | - <nowiki>./configure --enable-shared --with-hepmc2=/hepmcdir; make; make install</nowiki>. Even if you have Pythia, if you did not compile it with enable-shared options before you **cannot** run the Pythia-Delphes chain! In that case you have to install Pythia8 anew! In the following I will call the directory /pythiadir | ||
- | - Download and install Delphes from here [[http://cp3.irmp.ucl.ac.be/downloads/Delphes-3.2.0.tar.gz]] | + | - Download and install the last verion of Delphes (currently 3.3.2) via github: do 'git clone https://github.com/delphes/delphes.git' |
- Within the Delphes folder, do 'export PYTHIA8=/pythia8dir; make HAS_PYTHIA8=true DelphesPythia8' | - Within the Delphes folder, do 'export PYTHIA8=/pythia8dir; make HAS_PYTHIA8=true DelphesPythia8' | ||
- In order to run Delphes, do './DelphesPythia8 detectorcard.tcl pythiasettings.in output.root'. | - In order to run Delphes, do './DelphesPythia8 detectorcard.tcl pythiasettings.in output.root'. | ||
- | * For the detector card, you can use the one in delphes/cards/delphes_card_CMS_pileup.tcl until we have decided on the actual settings. **If you want to use the above PileUp sample, you have to explicitly put the file path in the "set PileUpFile" line!** | + | * For the detector card, you can use the one in delphes/cards/delphes_card_CMS_pileup.tcl but that actually does not match the performance of the muon/electron reconstruction and isolation so we are now using the file: '/afs/cern.ch/user/n/ndefilip/delphes_card_CMS_pileup.tcl'. Since we are working on tunings we could still decide to change the actual settings. **If you want to use the above PileUp sample, you have to explicitly put the file path in the "set PileUpFile" line!** . Make sure to uncomment any lines in the ROOT Tree writer at the bottom of the file |
+ | |||
+ | add Branch TrackMerger/tracks Track Track | ||
+ | add Branch Calorimeter/towers Tower Tower | ||
+ | |||
+ | as this information is used in the analysis (see github link below). | ||
* For the pythiasettings, there is a working example below (which you can just store in a text file) | * For the pythiasettings, there is a working example below (which you can just store in a text file) | ||
Line 318: | Line 326: | ||
**Final remarks** | **Final remarks** | ||
Ideally, every analysis chain comprises two independent modules: event by event, the first module takes as input the nominal (experiment or framework-dependent) objects and a particular point in the space of systematic parameters and outputs the re-calibrated framework-independent objects, ideally, as vectors of ''TParticle'' objects, while the second module takes as input the re-calibrated ''TParticle'' objects and outputs histograms and, or, flat ntuples. The second module should have no knowledge of the provenance of the ''TParticle'' objects. If we wrote our analysis codes this way, they would become framework-independent reusable modules. But, I've just realized I have been dreaming! | Ideally, every analysis chain comprises two independent modules: event by event, the first module takes as input the nominal (experiment or framework-dependent) objects and a particular point in the space of systematic parameters and outputs the re-calibrated framework-independent objects, ideally, as vectors of ''TParticle'' objects, while the second module takes as input the re-calibrated ''TParticle'' objects and outputs histograms and, or, flat ntuples. The second module should have no knowledge of the provenance of the ''TParticle'' objects. If we wrote our analysis codes this way, they would become framework-independent reusable modules. But, I've just realized I have been dreaming! | ||
+ | |||
+ | ====== Proceedings ====== | ||
+ | |||
+ | We started to work on the proceeding. The deadline is end of February. You can find the last version at link: | ||
+ | |||
+ | {{:2015:groups:higgs:dmhiggs:proceeding.zip|}} | ||