120 likes | 135 Views
API – Achievements 2001 Goals 2002 Resources. GEANT4 ANAPHE CERNLIB. J ürgen Knobloch LCG-PEB, 22 January 2002. API – mode of operation. API constitutes a small but essential part of larger development projects
E N D
API – Achievements 2001Goals 2002Resources GEANT4 ANAPHE CERNLIB Jürgen Knobloch LCG-PEB, 22 January 2002
API – mode of operation • API constitutes a small but essential part of larger development projects • The main goal is to help develop and maintain common software components for LHC (and other HEP experiments) • Goals and priorities should be governed by the needs of the LHC experiments • Formal input and review has decreased with the suspension of the LCB • However regular open meetings for Anaphe and organizational structure for GEANT4 (TSB, CB) • We expect improvement with the LHC computing project organization (SC2, PEB) API
API Achievements 2001 • General • Improvement in common software process • User and developer documentation • GEANT4 • New physics models • (CHIPS and longitudinal string decay) • Contribution to physics validation of Geant4 • resulting in BaBar choosing Geant4 for its 2001 production. • Contribution to Atlas comparisons in test beams • Releases: • 1 major and 2 minor releases, monthly development releases API
API Achievements 2001 – cont. • ANAPHE • release of "fully functional" version of Lizard • (mid July) ("PAW replacement" tool) • first "license-free" version of Anaphe/Lizard • (mid September) based on re-used functions from CERNLIB (HBook, Minuit) • AIDA interfaces version 2.2 released (end Nov) • (implementation in Anaphe starts 2002) • CERNLIB • unscheduled release on all platforms in June • for CASTOR compatibility • SDT • Introduction of Together and RUP API
API GOALS for 2002 • General • be guided by user requirements • improve • tutorials, examples, documentation and Web • direct user support & collaboration with experiments • implement chosen persistency scheme • enable running on a GRID fabric • participate in benchmarking • Software process - general improvement and • improve testing and QA • improve configuration management API
API Goals – GEANT4 • Physics comparisons & validation • Support experiment’s comparisons in particular for hadronic physics • Developments • Cascade models • Event biasing (for radiation studies) • Model approach for e.m. physics • Usability • Physics lists: improve tailoring; provide examples for specific use cases • Provide stand-alone demo API
API Goals - Anaphe • Implement AIDA 2.2 compliance • Continue strategy for license-free versions • Implement new input modules: • column-wise n-tuples • ascii and XML tables • ROOT-files • Extend from scripting to GUI • Iguana and/or Python-GUI • Components • call components from Python level • make e.g. Qplotter stand-alone API
Goals – other activities • CERNLIB • produce last ever release • consolidate to allow longer-term use by LEP experiments • remove dependency Castor - CERNLIB • help users to move to other solutions • SDT • has moved to the PS group – provide input for the SDT requirements of the group • TIPS (Tools for Innovative Publishing in Science) • Conclude the project as planned mid-2002 • EDMS (Bertrand Rousseau contribution sponsored by IT/API) API
API Resources – GEANT4 • 3 Staff • Apostolakis (spokesman), Cosmo (release coordinator), Folger (infrastructure, hadronic physics) • 2 Fellows • Chytracek (10/02) (GDML), Dressel (event biasing) • 4 Associates • Project Associates: Grichine (6/02) (e.m. physics, geometry), Ivantchenko (e.m. & hadronic physics) • Associates: Kosov (07/02) (hadronic physics), Sadilov (07/02) (testing) API
API Resources – ANAPHE • 4 Staff • Pfeiffer (project leader), Couet (50% graphics), Moneta (Aida 2.2 in Lizard), Papadopoulos (starting 03/02) • 3 Fellows • Molnar (04/02) (n-tuples), Sang (I/O module, web), Moscicki (03/02) (fitting, Grid) API
API Resources – other • CERNLIB • McLaren, Besson (1/2-time) • COMPASS & SC2 secretary • Lamanna • EDMS • Rousseau • Compilers & Accelerator Simulation • McIntosh • TIPS Project • Goossens API
Conclusions • We are ready to adjust our goals according to the needs of the LHC experiments • User assistance and support needs to be strengthened • We do not currently have the resources to fulfill the goals at the required level API