Concepts, Developments & Advanced Applications

Transcription

1 The PAX Toolkit Concepts, Developments & Advanced Applications CHEP '06 - Computing in High Energy and Nuclear Physics February 2006, T.I.F.R. Mumbai, India S. Kappler M. Erdmann, U. Felzmann, A. Floßdorf, M. Kirsch, G. Müller, G. Quast, C. Saout, A. Schmidt, J. Weng III. Physikalisches Institut A, RWTH Aachen university, Germany Institut f. Exp. Kernphysik, Karlsruhe university, Germany DESY, Hamburg, Germany CERN, Geneva, Switzerland

2 Physics Analysis expert

3 open source toolkit C++ class collection analysis of comple X events

4 Basic Units in Physics Analysis Hit, Cell, Tower, Cluster Track, Jet, Vertex Detector Reconstruction Particle (4-vector) Vertex (3-vector) Collision (multiple interactions) Abstract Physics Objects ' ' Particle Decay Particle Decay Chain Physics -Model (i.e. Feynman diagram) Physics Interpretation of the Evolution of different Combinatorial Hypotheses Evolution of different -Model Hypotheses Classification

5 Basic Units in Physics Analysis Hit, Cell, Tower, Cluster Track, Jet, Vertex Particle (4-vector) Vertex (3-vector) Collision (multiple interactions) ' ' Particle Decay Particle Decay Chain Physics -Model (i.e. Feynman diagram) PAX kernel + accessories Evolution of different Combinatorial Hypotheses Evolution of different -Model Hypotheses Classification

6 Basic Units in PAX Container Relations Collision Vertex Pax presented at: CHEP '06 PAX kernel presented at: HCP '02 CHEP '03 CHEP '04 IEEE NSS '04 CHEP '06 Particle

7 P PAX kernel v2.0.1 ex

8 Physics Objects: Common Features Container Relations Collision Vertex Particle Particle, Vertex & Collision 4 are based on corresponding CLHEP or ROOT objects and provide additional functionality 4 relations can be established to other PAX Physics Objects 4 user data is stored in the so-called user records (string-double pairs) 4 Each PAX Physics Objects may store pointers to arbitrary C++ objects; access to the original reconstruction objects at any time of the analysis

9 Particle: class PaxFourVector Container Particle: "store reco'd properties" ( E, px, py, pz ) user data relations arbitrary pointers PaxLorentzVector Relations Collision Vertex Particle PaxFourVector getpaxid() getpaxname() getparticleid() getcharge() getmass() getsimulated() getstatus() getworkflag()... PaxCollisionRelations PaxFourVectorRelations PaxBeginVertexRelations PaxEndVertexRelations

10 Vertex: class PaxVertex Container Vertex: "realize particle decay" ( x, y, z ) user data relations arbitrary pointers PaxThreeVector Relations Collision Vertex Particle PaxVertex getpaxid() getpaxname() getcharge() getmass() getparticleid()... getstatus() getsimulated() getworkflag() PaxCollisionRelations PaxFourVectorRelations PaxBeginVertexRelations PaxEndVertexRelations

11 Collision: class PaxCollision Collision: "separate multiple interactions" user data relations arbitrary pointers Container Relations Collision Vertex Particle PaxCollision getpaxid() getpaxname()... getworkflag() PaxCollisionRelations PaxFourVectorRelations PaxVertexRelations

12 Arbitrary C++ Pointers: PaxExperiment<Type> pointers to arbitrary C++ objects, e.g. to original reco obj's Container Relations Collision Vertex Particle PaxExperimentClass virtual clone() PaxExperiment<Type> PaxExperiment(Type* ptr) Type* getdata() clone()

13 Relations: class PaxRelationManager manage pointers to related physics objects Container Relations Collision Vertex Particle PaxRelationManager <key, item> PaxCollisionRelations PaxFourVectorRelations PaxVertexRelations PaxIncomingFourVectorRelations PaxBeginVertexRelations PaxOutgoingFourVectorRelations PaxEndVertexRelations

14 Container: PaxMap<key, item> organize pointers to physics objects in (multi-)maps Container Relations Collision Vertex std::map <key, item> PaxMap <key, item> PaxFourVectorMap PaxVertexMap PaxCollisionMap Particle

15 : class PaxInterpret -Interpretation: Container Relations Collision Vertex Particle 4 3 containers for physics objects (i.e. Particles, Vertices & Collisions) 4 user data is stored in the so-called user records (string-double pairs) 4PAX I/O allows storage of PaxInterpret instances to file 4 may store pointers to arbitrary C++ objects

16 : class PaxInterpret -Interpretation: physics obj's with relations user data arbitrary pointers Container Relations Collision Vertex Particle PaxInterpret getpaxid() getpaxname() getvertices() findvertex(...) getworkflag() getfourvectors() findfourvector(...) getcollisions() findcollision(...) PaxFourVectorMap PaxVertexMap PaxCollisionMap

17 : class PaxInterpret -Interpretation: Container physics obj's with relations user data arbitrary pointers Relations PaxInterpret Copy C'tor for deepgetpaxid() copy of: getpaxname() Collision getvertices() getworkflag() 4 physics objects with redirected findvertex(...)relations getcollisions() getfourvectors() 4 datavertex members 4findFourVector(...) user recordsfindcollision(...)... 4 arbitrary pointers... Particle PaxFourVectorMap PaxVertexMap PaxCollisionMap

18 -Persistency: class PaxIoFile -Persistency: write/read PaxInterpret instances including contained objects & relations to/from file multi-version and multi-platform compatibility binary chunk structure based on STL streams also possible: write/read events to/from strings 4 4 storage of events to databases (e.g. SQL) possible dcache access currently being developed

19 PAX Accessories & examples

20 -GUI: VisualPax (File Browser & Editor)

21 -Image: class PaxInterpretTTree -Image into a ROOT tree 4 automatic copy of certain observables, properties or user records of multiple -Interpretations to a TTree in a ROOT file 4 copy is performed according to a user-defined, static copy-model (i.e. a PaxInterpret instance) PaxInterpretTTree 4 the copy-model can be created with VisualPax PaxInterpret TTree TFile ROOT (TTree)

22 , &, & -Interpretation: 4 Copy C'tor of class PaxInterpret allows parallel evolution of: i) different combinatorial hypotheses ("interpretations") of an event according to a certain physics process "ambiguity resolution" l l ET b j j j... b

23 , &, & -Interpretation: 4 Copy C'tor of class PaxInterpret allows parallel evolution of: i) different combinatorial hypotheses ("interpretations") of an event according to a certain physics process ii) different physics process hypotheses ("processes") of an event. l l l b b b b b q b q'

24 : class Pax : "manage different combinatorial t-tbar hypotheses of an event according to a certain physics process" event-interpretations with their physics obj's & relations user data arbitrary pointers Pax getpaxname() virtual beginjob() virtual beginrun(...) getworkflag() getinterprets() findinterpret(...) virtual analyse(...) virtual finish() virtual endrun() virtual endjob()... PaxIterableMap <int, PaxInterpret*>

25 NEW: class PaxAuto Automatic Auto: "have all different combinatorial hypotheses of an event automatically evolved according to a certain process-model" inherits from Pax has a user-defined, static process-model (i.e. a PaxInterpret instance) virtual void analyse() Pax Model: PaxAuto getmodel() setmodel(...) virtual analyse(...) PaxInterpret

26 : class Pax : "manage different physics process hypotheses of an event." processes (Pax, PaxAuto or derivatives) user data arbitrary pointers t-tbar Pax tb+x getpaxname() virtual beginjob() virtual beginrun(...) getworkflag() W+jets getes() findprocess(...) virtual analyse(...) virtual finish() virtual endrun() virtual endjob()... PaxIterableMap <int, Pax*>

27 PAX kernel & Analysis example

28 Step 1: Define -Models interactively

29 Step 2: Run PaxAuto instances PAX Interface DST Reco-Software Pax... Pax Pax Pax Auto Auto Auto tb+x t-tbar W+jets Detector....paxio.root

30 Step 2: Run PaxAuto instances PAX Interface Pax DST Reco-Software Pax Auto tb+x Pax Auto t-tbar Pax Auto W+jets Pax MC tbx Pax MC ttbar Pax MC Wjet Detector- Simulation MC tb+x MC t-tbar MC W+jets MC Generator....paxio.root.paxio.root

31 Step 3: Analyse the Results

32 PAX infrastructure, more Accessories & examples

33 PAX Accessories & Interfaces VisualPax: GUI for PAX I/O file browsing, event editing & process modelling Pax: Pax, Pax, PaxAuto & PaxInterpretTTree PaxTuple & PaxHepMC: Interface classes and example application to fill PAX objects from HEPEVT Ntuples or HepMC files PAX interface classes: Available for various experiments (D0, CDF & CMS)

34 PAX Code & Analysis Examples PAX kernel: see the PAX/test directory, it contains: paxdemo.cc: demo program & coding how-to paxsimpleanalysis.cc: simple Z->mm reconstruction PaxDemoAnalysis: m n m n Introductory code and PAX based C++ classes for a W->mn reconstruction ExPaxAnalysis: The same W->mn analysis in the CMS ORCA framework

35 By the way, PAX......is continuously maintained by 8 core developers and further developed... undergoes quality ensurance (Borland Architect)...can be run (compiled) within ROOT/CINT...is fully documented (manual, doxygen, web navigator)...is managed with a web-browsable CVS repository...is online available at:

36 Summary: Basic units in PAX Container Relations Collision Vertex Particle