Fork me on GitHub

Changes between Version 11 and Version 12 of WorkBook/TutorialBologna


Ignore:
Timestamp:
Jun 9, 2016, 8:48:21 AM (8 years ago)
Author:
Michele Selvaggi
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • WorkBook/TutorialBologna

    v11 v12  
    385385}}}
    386386
    387 4)  Add the new variables T0, TF, genT0, genTF, ErrorT to the Candidate class.
    388     You will have to edit the files classes/DelphesClasses.h and classes/DelphesClasses.cc.
    389     The Candidate class is defined in classes/DelphesClasses.h. Other methods involving the
    390     Candidate class are defined in classes/DelphesClasses.cc:
     3874)  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:
    391388
    392389    - Candidate (constructor)
     
    396393If this step is performed properly, you should be able to compile by typing "make"
    397394
    398  We are not done yet... The newly computed timing information is now properly stored and propagated
    399    inside Delphes. However, we have to decide which objects will display this new information.
    400 
    401 
    402 5) Let's store this information in Tracks. Find this classes in
    403    classes/DelphesClasses.h and add the new variables. Compile.
    404 
    405 6)  Now we have to tell Delphes that we want these variables to appear in our final root tree.
    406     Store these variables in the Track objects in the ProcessTracks method
    407     in modules/TreeWriter.cc. Compile.
    408 
    409 
    410 7)  Finally, call the Timing module in the delphes_card_CMS_PileUp in the detector and configure it.
    411 
    412     Make two different runs with 20 and 100ps. Open the output trees a plots the new interesting
    413     variables.
    414 
    415 
     395We are not done yet... The newly computed timing information is now properly stored and propagated
     396inside Delphes. However, we have to decide which objects will display this new information.
     397
     3985) Let's store this information in Tracks. Find this classes in classes/DelphesClasses.h and add the new variables. Compile.
     399
     4006)  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.
     401
     4027)  Finally, call the Timing module in the delphes_card_CMS_PileUp in the detector and configure it. Make a simplified detector card that produces only Tracks out of the Timing module. 
     403
     4048) Make two different runs with 20 and 100ps. Open the output trees a plots the new interesting variables.
     405