1. Ties Behnke: EU-LC Simulation and Reconstruction 1 EU-LC Simulation & Reconstruction Full simulation systems: status report The next steps: where do we go from here The simulation challenge: status report The ECFA LC simulation group: Europe: David Ward, Ties Behnke:http://www-zeuthen.de/linear_collider Ties Behnke, DESY

2. Ties Behnke: EU-LC Simulation and Reconstruction 2 The mission Coordinate the creation of appropriate simulation tools Coordinate the creation of appropriate reconstruction tools Provide a frame for the creation of appropriate analysis tools The boundary conditions: System should be long lived Should be lightweight We are not a collaboration: commercial software is difficult (funding) Share across regions as much as possible Little to no personpower available

3. Ties Behnke: EU-LC Simulation and Reconstruction 3 The ingredients Generator Simulator Reconstructor Analyser Detector description “The data highway” IO (persistency) -- files

4. Ties Behnke: EU-LC Simulation and Reconstruction 4 Full simulation BRAHMS: GEANT3/ f77 based TESLA TDR detector updated for recent changes Complete simulation (and reconstruction) MOKKA: GEANT4/ C++ based TESLA TDR detector “more or less” No reconstruction framework BRAHMS is still the most complete package, but MOKKA is quickly getting there, will soon replace BRAHMS SIM

5. Ties Behnke: EU-LC Simulation and Reconstruction 5 The future of the simulator(s) MOKKA is our main GEANT4 based full simulation environment GEANT4 based light weight, C++ code geometry via mysql and C++ drivers Our US collegues are evaluating MOKKA to use it as a base for their GEANT4 simulation environment. MOKKA developments: Improve the detector models allow for more flexible system: concept of user plugins Watch closely CERN geometry developments (GDML) Should look at LCD-G4 – MOKKA and possible synergies / common developments

6. Ties Behnke: EU-LC Simulation and Reconstruction 6 The data highway: LCIO Need definition of a data model: What is a hit What is a track What is a calorimeter cluster etc. Need a common way to store (“persist”) objects JAS ROOT HBOOK Objectivity Anything else ? LCIO: a simple data model with underlying persistency system: Serial packed files with pointer and “block” support Event object Hit objects “Reconstructed Particles”: Track and cluster objects “Reconstructed quantities” objects Complexity

7. Ties Behnke: EU-LC Simulation and Reconstruction 7 LCIO: LC persistency framework JETS Vertex HITS Tracker hits PARTICLES Calorimeter Hits Tracks Clusters OBJECTS MONTE CARLO INFORMATION SIMULATIONRECONSTRUCTIONANALYSIS

8. Ties Behnke: EU-LC Simulation and Reconstruction 8 LCIO data model LCParticle LCReconstructedParticleLCCompound pointer specific extensions type specific extensions tracks cluster unique, complete Kshort pion+ pion- track 17 track 21 cluster 201 Kshort2 The data model for reconstructed objects:

9. Ties Behnke: EU-LC Simulation and Reconstruction 9 LCIO: Status Developed in collaboration between SLAC / DESY / LLR (France) Common data model / persistemcy framework for LC studies Simple API to store and retrieve data Same API in C++, Java (and Fortran) Simple underlying IO format (SIO): can be changed easily at a later time Status: Development started December 2002 First public pre-release in March First public production release for Montpellier: LCIO 1.0 Full C++ implementation Full Java implementation Full Fortran implementation Hit based data model “fully” defined, reconstructed objetcs still rudimentary Status: Development started December 2002 First public pre-release in March First public production release for Montpellier: LCIO 1.0 Full C++ implementation Full Java implementation Full Fortran implementation Hit based data model “fully” defined, reconstructed objetcs still rudimentary

10. Ties Behnke: EU-LC Simulation and Reconstruction 10 LCIO Future developments reconstruction data model – refine data model as discussed … – first implementation soon add convenient methods and tools – analyzing the MCParticle tree (graph) ● iterators for MCParticles, e.g. all stable/final particles ● analyzing parent/daughter relationships – adding convenience iterators for LCIO types ● simplify complex C++ syntax with dynamic_casts etc. add possibility to store generic user data – calibration constants etc. respond to user requests proposal by Frank Gaede

11. Ties Behnke: EU-LC Simulation and Reconstruction 11 LCIO user extensions I want to be able to store data not foreseen in LCIO data model – e.g. calibration constants, prototype data impossible to extend the data model for all users’ needs ! existing LCIntVec and LCFloatVec not very convenient and efficient still keep LCIO files self contained – i.e. data should be readable without additional software/ user code user code independent of file format (SIO) proposal by Frank Gaede

12. Ties Behnke: EU-LC Simulation and Reconstruction 12 LCIO user extensions II allow user classes with some restrictions: – subclasses of LCObject -> store in event collections – properties have to be basic types: ● int, float, double ● can be extended to other types and vectors ! – Properties have to be accessible via user class’ ● data members or ● accessor member functions – Preprocessor macros for C++ and Java static functions for making class known to LCIO proposal by Frank Gaede

13. Ties Behnke: EU-LC Simulation and Reconstruction 13 LCIO user extensions III user classes are stored with data description in the LCIO files data can be read back even if UserClass definition not available to the program: – LGenericObject: – allows access to properties, via: ● names (convenient) ● indices (faster) unknown collections can be analyzed with LCIO tools/browser

14. Ties Behnke: EU-LC Simulation and Reconstruction 14 LCIO user classes, example I class UserClass : public lcio::LCObject{ LCOBJECTINFO_FRIEND() ; protected: int myInt ; float myFloat ; public: UserClass(int i) : myInt(i) {} float getMyFloat() const; void setMyFloat(float f) ; } ; #include "UserClass.h" float UserClass::getMyFloat() const { return myFloat ;} void UserClass::setMyFloat(float f) { myFloat = f; } // Make class known to LCIO LCOBJECTINFO_DEFINE( UserClass ) ; LCOBJECTINFO_PROPERTY_DIRECT( &UserClass::myInt, "myInt" ) ; LCOBJECTINFO_PROPERTY( &UserClass::getMyFloat, &UserClass::setMyFloat, "myFloat" ) ; LCOBJECTINFO_REGISTER( UserClass, "UserClass" ) ; proposal by Frank Gaede

15. Ties Behnke: EU-LC Simulation and Reconstruction 15 LCIO as online data format Both TPC and calorimeter groups look at LCIO as online data format: example: HCAL calorimeter group at DESY/Hamburg calorimeter prototype: minical data-MC comparison of energies in minical First version of “raw data classes” have been defined.

16. Ties Behnke: EU-LC Simulation and Reconstruction 16 Example: Calo hit file (online) Dump of data file: LCIO can be used online eases access to data and comparison to MC

17. Ties Behnke: EU-LC Simulation and Reconstruction 17 Reconstruction BRAHMS/ f77 based reconstruction: Complete and sophisticated tracking Particle flow reconstruction package Tools (n-tuple for analysis, interface to main packages like ZVTOP,...) OO world: No coherent reconstruction frame yet LCIO allows using f77 based reconstruction package on MOKKA output (first version of MOKKA- BRAHMS connection released) We need to move fast towards a OO based reconstruction framework, to enable reconstruction program developments!

18. Ties Behnke: EU-LC Simulation and Reconstruction 18 Reconstruction BRAHMS: sophisticated and complete reconstruction software available OO based: no reconstruction tools available at the moment Status of reconstruction packages:

19. Ties Behnke: EU-LC Simulation and Reconstruction 19 Reconstruction Hits simulated in detector (BRAHMS) Tracks and Pflow objects reconstructed (BRAHMS reco) Plots Karsten Buesser

20. Ties Behnke: EU-LC Simulation and Reconstruction 20 The Plan Develop a plain C++ reconstruction framework LCIO as data model Possibly CGA as geometry access model Very simple interface, no fancy interactive environment for a start Multi language support is no problem (JAVA...) Use LCIO ROOT LCIO JAS to provide a simple user interaction with the reconstruction At this stage: remain independent of any particular environment (root, JAS, PAW,...) be open for future developments be light-weight (minimise the number of libraries the user needs to install) At this stage: remain independent of any particular environment (root, JAS, PAW,...) be open for future developments be light-weight (minimise the number of libraries the user needs to install).... but we are still far from this goal...

21. Ties Behnke: EU-LC Simulation and Reconstruction 21 Fast Simulation SIMDET: fast, parametrised Monte Carlo NEW: interface to used track based ZVTOP in SIMDET improvements to parametrisations SGV: fast, semi-parametrised Monte Carlo (produces hits) NEW: interface to ZVTOP in SGV At the moment, fast simulations work, are producing physics results but in Europe we have no project for a modern fast simulator Our US collegues are developing a similar system

22. Ties Behnke: EU-LC Simulation and Reconstruction 22 Software: Outlook Simulation: Converge towards GEANT4 based MOKKA simulation program should become more flexible and user friendly Close collaboration with our US collegues on simulation establised IO: LC specific persistency scheme and data model established Interface to C++, JAVA and Fortran exists Common development with our US collegues Reconstruction: Next big project Digitisation and reconstruction “complete” in BRAHMS Much effort needed in OO framework: the next project

23. Ties Behnke: EU-LC Simulation and Reconstruction 23 Towards a simulation challenge Software environment: see previous slides Access to data: Need transparent and flexible access system Data volume small compared to LHC, but still significant The plan: User interface/ interaction: use the GRID computing model and software Storage manager: dCache (FNAL and DESY, integrated into GRID) GLOBUS authentication manager The challenge: be able at the end of the current ECFA study to do a “blind” analysis challenge (A. Wagner, Amsterdam)

24. Ties Behnke: EU-LC Simulation and Reconstruction 24 LC Data depository Database interface to data stored under dCache at DESY Current problems: access from outside DESY (being worked on)

25. Ties Behnke: EU-LC Simulation and Reconstruction 25 Summary Software tools present a significant challenge Progress on the simulation: GEANT3 based simulation more stable and complete GEANT4 based simulation becoming available Common persistency scheme is reality Progress on the reconstruction: BRAHMS based reconstruction exists OO reconstruction still in the future LCIO input exists LCIO output being defined Goals: GEANT4 based simultor Simple reconstruction environment independent of particular framework LCIO as basic data format and model to facilitate data exchange Management of data sets through GRID like system