TWiki> Main Web>AtlasSusyCernLocal>SusyView (revision 6)EditAttachPDF

How to run SusyView in 11.0.41

Getting started

  • Set up a release 11.0.41 i use Amir's new-athena-release script for this:
/afs/ 11.0.41 11.0.41
cd 11.0.41
source setup.[c]sh
  • Add the tags (im afraid theres quite a few but these will all go into 11.0.5):
cmt co -r SUSYView-00-00-04 PhysicsAnalysis/SUSYPhys/SUSYView
cmt co -r CompositeParticleEvent-01-01-01 PhysicsAnalysis/AnalysisCommon/CompositeParticleEvent
cmt co -r AnalysisTools-00-00-24 PhysicsAnalysis/AnalysisCommon/AnalysisTools
cmt co -r EventView-00-00-15 PhysicsAnalysis/AnalysisCommon/EventView
cmt co -r EventViewAthenaPool-00-00-06 PhysicsAnalysis/AnalysisCommon/EventViewAthenaPool
cmt co -r EventViewBuilderAlgs-00-00-16 PhysicsAnalysis/EventViewBuilder/EventViewBuilderAlgs
cmt co -r EventViewBuilderUtils-00-00-28 PhysicsAnalysis/EventViewBuilder/EventViewBuilderUtils
cmt co -r EventViewUserData-00-00-12-03 PhysicsAnalysis/EventViewBuilder/EventViewUserData
cmt co -r EventViewSelectors-00-00-03 PhysicsAnalysis/EventViewBuilder/EventViewSelectors
cmt co -r EventViewCombiners-00-00-05 PhysicsAnalysis/EventViewBuilder/EventViewCombiners
cmt co -r EventViewDumpers-00-00-04 PhysicsAnalysis/EventViewBuilder/EventViewDumpers
cmt co -r EventViewInserters-00-00-01-01 PhysicsAnalysis/EventViewBuilder/EventViewInserters
  • Goto SUSYView directory and compile:
cd PhysicsAnalysis/SUSYPhys/SUSYView/SUSYView-*/cmt
source setup.[c]sh
cmt bro cmt config
cmt bro gmake
  • Goto run directory and run:
cd ../run
athena -s -c "mode='wenu';theApp.EvtMax=10;" SUSYView/ SUSYView/ >& susyview.log &
  • here the first python file sets up susyview the second defines the datasets (it uses the python variable mode to chose what to load in and also this is used to set the output file names)
  • you set how many events to run on with theApp.EvtMax=10
  • This will produce root files fullAOD_wenu_Reco.AAN.root and fullAOD_wenu_Truth.AAN.root which have the SUSY variables for reco and truth in them
root -l Reco.AAN.root
  • To run an AtlFast aod file you do:
cd ../run
athena -s -c "mode='test';file='atlfast_10k.pool.root';theApp.EvtMax=10;" SUSYView/ >& susyview_atlfast.log &
  • here it is running on the atlfast pool file defined by the file python variable, mode is just used to set the output file names.
  • This will produce root files fast_test_Truth.AAN.root and fast_test_Reco.AAN.root which have the SUSY variables for fast atlreco and truth in them
  • there is also a simple job option included in susyview for generating your own AtlFast AOD file including event generation in one step. this is described below.

What is there so far...

The reco ntuple

  • I have tailored the standard ntuple to contain the following:
  • A dump of all the reco particles (4-vectors + some detector specific info) and very detailed detector info for electrons and muons. (This is just because i want to study events with a tight electron and muon in them, it can be easily configured how you want)
  • Truth matching of the reco particles to truth particles (and then the 4 vectors of the truth particle)
  • Event shape variables, multiplicities and sums

The truth ntuple

  • The 4-vectors of all the truth particles - as well as the 4-vectors of the matched reco partners
  • The truth particles include neutrino's but at the moment not LSP
  • Event shape, variables, multiplicities and sums (dont include neutrinos in these obviously)

The AtlFast Reco ntuple

  • The 4-vectors of all the reco particles - as well as the 4-vectors of the matched true partners
  • Event shape, variables, multiplicities and sums

The AtlFast Truth ntuple

  • The 4-vectors of all the truth particles (except due to a technical problem in the way truth jets are made - there are no truth jets - this is being looked into - i hoep) - as well as the 4-vectors of the matched reco partners
  • The truth particles include neutrino's but at the moment not LSP
  • Event shape, variables, multiplicities and sums (dont include neutrinos in these obviously)

The variables

  • EVSphericityCalc: calculates the Sphericity, Planarity & Aplanarity from the FS particles in either 2d (transverse - this is default) or 3d. it also stores the 3 sphericity axis in the ntuple as TVector3's
  • EVSimpleSusyVars:
  • EVMeffCalc: calculates Meff using the 4 hardest jets (four_Meff) and also with all jets in the event (all_Meff), at the moment it uses Particle Jets for full reco and truth and TagJets for AtlFast (as there doenst seem to be any Particle jets produced in atl fast - not sure if this is correct).
  • Other quantities are calculated by standard EventView tools - which are configured in the SUSYView python scripts. These include:

Nparticles (), Nleptons (), Njets (), Sum Pt (), Sum E (), Sum Pt1 Pt2 (), Sum Pt1 Pt2 Pt3 (), Highest Pt particle (),

What needs to be added

  • Karina is adding thrust and Fox-Wolfram moments (more shape variables)
  • Its easy to add new variables either by configuring existing tools in the python, or by writing new tools. (see EventView tutorial to see how easy this is).

Using AtlFast and running SusyView on the output

  • It is pretty easy to do this but it is a 2 step proccess heres a quick recipe
  • first run the generator and AtlFast (in one job) to produce an AtlFast aod pool file
run> ln -s genfiles/* . 
run> athena -s -c "file = 'SUSYView/'; outfile = 'test.pool.root';EvtMax = 100" SUSYView/ > & atlfast_test.log &
  • the decay to be generated is defined by the file python variable (so in this case it would be the decay defined by the file SUSYView/
  • i copied the different susy points generator files into the SUSYView/share directory so they should be available after a gmake. For the configuration files needed by the generators i copied these into the SUSYView/run directory. This isnt ideal as if these things change we wont see the change s- but it makes getting started very easy.
  • of course you can generate other things than susy signal by copying over the required generator file.
  • the output aod pool filename is defined by the outfile python variable the default is ./SUSY2.pool.root, the number of events to generate can be changed by the variable EvtMax
  • now you need to run SUSYView on the produced file (test.pool.root) you need to use a slightly different options file (as the fast aod is slightly different from the full AOD) but this is easy
athena -s -c "mode='test';file='test.pool.root';theApp.EvtMax=10;" SUSYView/ >& susyview_atlfast.log &
  • you can also run on some centrally produced AtlFast aod files that are in castor there are examples of these in
  • easy eh!

Some analysis tips

  • So you can do quite a bit of analysis just by plotting things in root using the draw command - for example you can get the Pt resoln of your electron candidates with respect to the truth matched truth candidate by doing:
CollectionTree->Draw("El_p_T - El_true_p_T", "El_true_p_T>0");
  • for some studies you will want to compare variables in the Reco.AAN.root file with those in the True.AAN.root file. this can be done by doing the following:
  TFile t(dir+"fullAOD_"+mode+"_Truth.AAN.root");
  TFile r(dir+"fullAOD_"+mode+"_Reco.AAN.root");
  TTree* tt = (TTree*)t.Get("CollectionTree");
  TTree* rt = (TTree*)r.Get("CollectionTree");
  tt->AddFriend(rt,"r"); // this adds the Tree rt to the tree tt you can access stuff in rt by doing r.Var eg..
  tt->Draw("r.MissingEtTruth:Neutrino_p_T[0]"); // this plots the MissingEtTruth (from the reco ntuple) against the Neutrino PT (from the truth ntuple)
  • Using MakeClass - to do a full analysis where you loop through the events and the candidates in each event you want to use make class function in root. do:
  • this will make a file called class.C and class.h - because of a problem in root (i think) you will need to comment out all reference to fUniqueID,fBits, fX, fY, fZ and TVector3 BlahAxis in the.h file
  • in the class.C file in the Loop method you can define histograms before the event loop and then do stuff in the event loop, one very useful thing to do is to use TLorentzvectors like:
        TLorentzVector mu1;
  • you can then do lots of easy 4-vector manipulation - see this link (remember you need to do:
    #include <TLorentzVector.h>
  • finally to run you do:
> .L class.C++
> class c;
> c.Loop();
> histo->Draw();

What needs to be done

  • Want truth jets from AtlFast - this needs to be fixed by someone (this isnt an EventView / SUSYView problem but more general)
  • Want to be able to get AtlFast ntuple out of running on CSC full MC (so you would get 3 ntuples truth, reco and fast reco) this would be useful for seeing how AtlFast compares to full reco. this info is supposed to be in the CSC MC but it doesnt work for me (the AtlFast ntuple is empty)??
  • Tidy up some stuff - add helper class to take care of require/reject labels scheme, tidy up way python configuration is done.
  • Add LSP to truth ntuples
  • remove some of the overlap info (eg. neutrinos in truth)
  • put neutrinos in as inferred objects - this would make it simpler to schedule tools on all truth particles but not neutrino's
  • if you use MakeClass on the produced tree's you get into problems due to the stored TVector3's - they each have data members called fUniqueID,fBits, fX, fY, fZ you can get round this by commenting them out - but its a bit of a pain. i do like storing them as TVector3's though as you can do:

-- Main.jboyd - 16 Mar 2006

Edit | Attach | Watch | Print version | History: r10 | r8 < r7 < r6 < r5 | Backlinks | Raw View | Raw edit | More topic actions...
Topic revision: r6 - 2006-04-21 - JamieBoyd
    • Cern Search Icon Cern Search
    • TWiki Search Icon TWiki Search
    • Google Search Icon Google Search

    Main All webs login

This site is powered by the TWiki collaboration platform Powered by PerlCopyright & 2008-2020 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback