5 May 98 1 Jürgen Knobloch Computing Planning for ATLAS ATLAS Software Week 5 May 1998 Jürgen Knobloch Slides also on:

5 May 98 2 Jürgen Knobloch ATLAS MoU - Introduction The ATLAS software will be developed in a defined process involving requirements, design and coding - each being reviewed for quality assurance. The ATLAS data will be stored in an object- oriented database. First estimates of the cost of the computing infrastructure necessary for data storage, reduction and analysis are also contained in the CTP. These costs are not included in the present MoU. Final software planning including human resources and better understanding of computing model and the role of regional centres --> during 1999

5 May 98 3 Jürgen Knobloch 2 year major cycle 8 workweek cycles Software planning  1998Initial version 0 –FORTRAN code further developed, interface to C++ –Overall requirements formulated –Domain decomposition –Simulation and reconstruction framework  Version 1 –Complete detector description in GEANT4, ODBMS  Version 2 –Full functionality of OO software  Version 3 - Integration, performance  2005Production version 4

5 May 98 4 Jürgen Knobloch Software Quality  Functionality –Experience, requirements, software process  Ease of entry for physicists –Documentation, clear architecture  Maintainability –Documentation, software process  Flexibility –changing environment, new requirements  Robustness  Performance –Few O(0) re-processings, CPU, memory, I/O

5 May 98 5 Jürgen Knobloch Current situation  Last major release of FORTRAN simulation  Still work on FORTRAN reconstruction  First release of OO reconstruction imminent  Simulation with GEANT4 - prototypes exist  Difficult to get started  Software process taken seriously  Software release tools being implemented  Platform/compiler/commercial_software –few combinations work

5 May 98 6 Jürgen Knobloch Offline Software Plan

5 May 98 7 Jürgen Knobloch Milestones A detailed list of milestones has been defined in the Computing Technical Proposal. In the following, the major milestones are summarised: OO- Reconstruction frameworkApril 1998 Demonstrate ~1 Tbyte working prototype of event databaseDecember1998 First release of ATLAS OO softwareEnd1999 Functional software for simulation, reconstruction and analysisEnd2001 1% prototype of event-processing farmDecember % event database (disk + robots, not necessarily all tapes)December2004 Provide ~40% of final event processing and analysis farmsDecember2004 Provide full event processing and analysis farmApril2005

5 May 98 8 Jürgen Knobloch  Software workshops –1 week, 4 times / year, 1 CERN  ACOS (Computing steering group) –6 meetings / year (4 during software workshops)  DIG (Domain interface group and support team) –8 meetings / year (4 during software workshops)  Weekly software meetings –Videoconferenced –Tutorial session about OO issues  Working groups: database, graphics, WWCG,... Organisational items

5 May 98 9 Jürgen Knobloch Trigger Domain Decomposition GUI Control Event Display Muon System Magnetic Field Calorimetry Detector Description Inner Detector Data Base Simulation Event Geometry Tools SDE Documentation Muon Reconst. e,  Reconstruction Organisation: Domain architects Domain interface group Support team

5 May Jürgen Knobloch Planning in terms of deliverables Medium term (this year)  Reconstruction framework –Based on ARVE –“Ramped-up” to conform to the ATLAS software process –Event reading from ZEBRA tapes –Reconstruction algorithms >IPATREC >MUON (DATCHA) reconstruction  First public version in “April”  Many things to follow… –Calorimeter prototype, full detector hierarchy, interface to GEANT4, reading from Object Database

5 May Jürgen Knobloch How to go from here to there... FORTRAN and C++ C++ CALOREC IPATREC ABCREC MUONBOX ATRECON DICE 3 GEANT 3GEANT 4 CALOREC++ IPATREC ABCREC MUONBOX ATRECON CALOREC++ IPATREC++ ARVE Event DB Detector DB

5 May Jürgen Knobloch  GEANT4 - ATLAS participation and implementation  Test beam simulation and analysis  ARVE - ATLAS Reconstruction and Visualisation Environment  Object-oriented pattern recognition TRT, IpatRec  Muon reconstruction  ODBMS (RD45) ATLAS participation –Event storage GEANT3, GEANT4, test-beam –Detector database  LHC++ - ATLAS participation - Porting ATLFAST++ to Objectivity Current OO projects

5 May Jürgen Knobloch ATLAS and GEANT4 10  + (1 -> 6 GeV) TGC for trigger studies

5 May Jürgen Knobloch GEANT4 plans  Alpha-05 is comparable to GEANT3 –Physics, tracking, geometry, event persistency  Next steps –Produce beta version –Persistency for geometry –More visualization –Documentation –Extend physics models  Next steps for ATLAS –Detailed field map –produce HITs –detector parameters into DB –Full ATLAS geometry –Test beam geometries –Simulation mock-up –Get more detector people into ATLAS working group

5 May Jürgen Knobloch Database developments  Detector database –Muon geometry description existing in Objectivity –Understand best structure -> other detectors can follow –Possible common project on detector description db  Event storage database –GEANT3 data in Objectivity (Summer 98) –ATLAS testbeam –Event structure to be developed –Replication via network or via “tapes”???  Other experiments –NA45, Compass, BaBar, Star,... - Learn from experience

5 May Jürgen Knobloch Next Tasks  Reconstruction - ARVE –Documentation –Read events from OODB –G3 events to objy –Event display –Magnetic field –Integrate more algorithms –Single particle from GEANT4 –Components –User support  Simulation –Create ATLAS GEANT4 team –Detector description DB –Build ATLAS G4 Framework –Test beam simulations  General –Populate domains –Make ASP “user friendly” –Establish detailed plan –Analysis strategy- try LHC++ – Regional centres

5 May Jürgen Knobloch Conclusions of LCB workshop...  Common vocabulary/glossary  Consensus on need for more sharing –e.g. detector description database tools  Technical forums on specific items –e.g. LHC++, RD45,...  Risk analysis  Learning from experience –Provide OO examples, tutorials, seminars

5 May Jürgen Knobloch ATLAS Computing Model RD45 Regional Centres HPSS Networks Media Simulation Data Structure Cost Manpower Licenses Companies Risk Analysis Sharing Architecture Requirements Technology Flexibility Collaborative Tools Software Process

5 May Jürgen Knobloch Operating Systems  Current (FORTRAN) –HP-UX –AIX –Digital UNIX –LINUX –NT –IRIX (SGI) –Solaris  FUTURE –(HP-UX 10.20) - not 11.xx! >as long as old hardware exists –LINUX >RedHat > 5.0 –NT 4.0  If supported by ATLAS institutes: –Digital UNIX –AIX –Solaris