Context Navigation

Changes between Version 14 and Version 15 of WorkBook/TutorialBologna

Timestamp:: Jun 9, 2016, 6:48:40 PM (8 years ago)
Author:: Michele Selvaggi
Comment:: --

Legend:

: Unmodified
: Added
: Removed
: Modified

WorkBook/TutorialBologna

-              v14
+              v15
 cp modules/ExampleModule.cc modules/Timing.cc
 }}}
 In these two files replace all "ExampleModule" with "Timing".
+In these two files replace all "!ExampleModule" with "Timing".
 ) Add the Timing module in modules/ModulesLinkDef.h:
 …
 You have just added your first empty module in Delphes.
+) Replace the existing "Process"  method in the newly created module. Understand this piece of code.
+    Then edit the rest of the Timing class (both the .cc and .h), in order to comply with this method.
+) Understand the following piece of code and replace the existing "Process" method in the newly created module. Then edit the rest of the Timing class (both the .cc and .h), in order to be able to compile.
 {{{
 …
 }}}
 )  Add the new variables T0, TF, genT0, genTF, ErrorT to the Candidate class. You will have to edit the files classes/DelphesClasses.h and classes/DelphesClasses.cc. The Candidate class is defined in classes/DelphesClasses.h. Other methods involving the Candidate class are defined in classes/DelphesClasses.cc:
+)  Add the new variables T0, TF, genT0, genTF, ErrorT to the Candidate class. For this, you will have to edit the files classes/DelphesClasses.h and classes/DelphesClasses.cc. The Candidate class is defined in classes/DelphesClasses.h. Other methods involving the Candidate class are defined in classes/DelphesClasses.cc:
     - Candidate (constructor)
 …
 If this step is performed properly, you should be able to compile by typing "make"
+We are not done yet... The newly computed timing information is now properly stored and propagated
+inside Delphes. However, we have to decide which objects will display this new information.
+We are not done yet... The newly computed timing information is now properly stored and propagated inside Delphes. However, we have to decide which objects will display this new information.
 ) Let's store this information in Tracks. Find this classes in classes/DelphesClasses.h and add the new variables. Compile.
 )  Now we have to tell Delphes that we want these variables to appear in our final root tree. Store these variables in the Track objects in the ProcessTracks method in modules/TreeWriter.cc. Compile.
+)  Now we have to tell Delphes that we want these variables to appear in our final root tree. Store these variables in the Track objects by editing the !ProcessTracks method in modules/!TreeWriter.cc. Compile.
 )  Finally, call the Timing module in the delphes_card_CMS_PileUp in the detector and configure it.
 …
 ) Set the average pile-up to 200 in the card.
+) Make a simplified detector card that produces only Tracks out of the Timing module.
+) Make two different runs with 20 and 100ps. Open the output trees and plot the new variables.
+) [https://cp3.irmp.ucl.ac.be/projects/delphes/raw-attachment/wiki/WorkBook/TutorialBologna/TimingAnalysis.C Download] and run it. This macro isolates the four highest PT tracks. The hard vertex is taken to be that given by the most energetic track. The difference in time between the first and the fourth track is plotted. Explain what you see.
+) Simplify detector card that produces only Tracks out of the Timing module.
+) Add the following at the top of the card to run on 1k events only:
+{{{
+set MaxEvents 1000
+}}}
+) Make two different runs with 20 and 100ps. Open the output trees and plot the new variables.
+) [https://cp3.irmp.ucl.ac.be/projects/delphes/raw-attachment/wiki/WorkBook/TutorialBologna/TimingAnalysis.C Download] and run it. This macro isolates the four highest PT tracks. The hard vertex is taken to be that given by the most energetic track. The difference in time between the first and the fourth track is plotted. Explain what you see.