1. Simulation / Reconstruction Working group Toby Burnett University of Washington 11 Jan 2000 T

2. 1/11/2000T. Burnett: Simul/Recon group2 Primary goals Clear separation of simulation/reconstruction –Allow migration to Geant4 –Definition of data formats Parameter system Integrated Menus and command-line options Reconstruction framework

3. 1/11/2000T. Burnett: Simul/Recon group3 Suggested Procedure Create a topic list: is it complete? Does it overlap other working groups? (A proposed one follows) –Topics are usually implemented as packages For each item, prepare a document with: –A description of the item –The current situation –Requirements for the new version –Relative priority –Person who has taken responsibility –Target date based on priority Note that often we can, and should just copy someone else’s solution, concentrating on what is unique to GLAST

4. 1/11/2000T. Burnett: Simul/Recon group4 Tentative list of Topics for discussion Services –exception handling –parameters –error logging –persistency –n-tuple creation Detector description & geometry –Non-active –Active Detector/Event/Recon display Data formats –Raw to IOC –“Digis”: input to recon –Recon output Shared Libraries GUI/command line options Shareables Simulation –Use GEANT4 (G4) –Realism: Tracking configuration & Validation –“fast MC?” –Nuclear interactions Background models –Proton: direct & albedo –Heavies –Albedo gammas Reconstruction –Framework or Architecture –Tracker –Calorimeter –ACD –Level 2/3 –Alignment/calibration

5. 1/11/2000T. Burnett: Simul/Recon group5 Software Design/organization Questions Do we assume that we will continue to use an Object-oriented paradigm? [Flight may be C only] If so, can/should documentation have UML prepared by: –Rose –Together Is it acceptable to organize code into packages ?

6. 1/11/2000T. Burnett: Simul/Recon group6 Example: exception handling Description –Represents need to notify user of an unusual situation, with (at least) two levels of severity. Current practice –Globals warning and fatal: write message to cerr, and/or dialog box, aborting in latter case Requirements –Three severity levels: info, warning, fatal –Control over logging –Easy generation of names Discussion –There is a very complete package from FNAL, called Zmexceptions. Priority: high Responsible person: ? Target date: 1 Feb