1. CPT Week, November 2002 http://iguana.cern.chNovember 4, 2002 Lassi A. Tuura, Northeastern University Core Framework Infrastructure Lassi A. Tuura Northeastern University, Boston

2. November 4, 2002 Lassi A. Tuura, Northeastern University http://iguana.cern.ch 2 Frameworks: Structure Federationwizards Detector/EventDisplay Data Browser Analysis job wizards Generic analysis Tools ORCA FAMOS LCGtools GRID OSCAR COBRA Distributed Data Store & Computing Infrastructure CMStools Consistent User Interface Coherent basic tools and mechanisms

3. November 4, 2002 Lassi A. Tuura, Northeastern University http://iguana.cern.ch 3 Federation wizards Detector/Event Display Data Browser Analysis job wizards Generic analysis Tools ORCA FAMOS OSCAR Focus Of This Presentation Consistent User Interface Coherent basic tools and mechanisms LCGtools GRID CMStools Distributed Data Store & Computing Infrastructure COBRA

4. November 4, 2002 Lassi A. Tuura, Northeastern University http://iguana.cern.ch 4 ODBMS GEANT 3 / 4 CLHEP PAW Replacement C++ Standard Library + Extension Toolkits C++ Standard Library + Extension Toolkits Frameworks: Layering Calibration Objects Calibration Objects Generic Application Framework Physics modules Grid-Uploadable BasicServices Adapters and Extensions Configuration Objects Configuration Objects Event Objects Event Objects (Grid-aware) Data-Products SpecificFrameworks Event Filter Reconstruction Algorithms Physics Analysis Data Monitoring

5. November 4, 2002 Lassi A. Tuura, Northeastern University http://iguana.cern.ch 5 GEANT 3 / 4 Boost Classlib LCG Tools C++ Standard Library + Extension Toolkits C++ Standard Library + Extension Toolkits Tool Components Layer Calibration Objects Calibration Objects Generic Application Framework Physics modules Grid-Uploadable BasicServices Adapters and Extensions Configuration Objects Configuration Objects Event Objects Event Objects (Grid-aware) Data-Products SpecificFrameworks Event Filter Reconstruction Algorithms Physics Analysis Data Monitoring

6. November 4, 2002 Lassi A. Tuura, Northeastern University http://iguana.cern.ch 6 Tool Components Focus v Unification r Gathering basic services within CMS projects into one place r Selection and merging where duplication exists r In co-operation with LCG tools project r Using existing high-quality 3rd party libraries where possible – Adaptation to CMS environment v Attention on quality improvements r Better documentation r More examples r More test cases (regression checked where possible) r Ensure consistent usage within CCS software

7. November 4, 2002 Lassi A. Tuura, Northeastern University http://iguana.cern.ch 7Classification v Language extensions r Extended type info, reflection, … r Library utilities: hash maps, map iterators, … v Rich base of tools from simple to sophisticated r “Mini utilities” collection (signals, timers, environment, uuids, dns, users …) r Bits & numerics tools r Debugging, robustness, logging r System abstraction r I/O: basics; files, file systems; IPC; high-level streams r Compression, archives tools

8. November 4, 2002 Lassi A. Tuura, Northeastern University http://iguana.cern.ch 8 GEANT 3 / 4 Qt Classlib Open Inventor Open Inventor C++ Standard Library + Extension Toolkits C++ Standard Library + Extension Toolkits Framework Components Layer Physics modules Grid-Uploadable Basic Services Adapters and Extensions SpecificFrameworks Event Filter Reconstruction Algorithms Physics Analysis Data Monitoring Calibration Objects Calibration Objects Generic Application Framework Configuration Objects Configuration Objects Event Objects Event Objects (Grid-aware) Data-Products

9. November 4, 2002 Lassi A. Tuura, Northeastern University http://iguana.cern.ch 9Componentisation v Main technical focus: componentisation r COBRA and IGUANA already have fairly well developed component models r Focus on making those modules more clearly defined – Technically, components and dynamic loading can be orthogonal – Documentation, including how-to guides – Build infrastructure to be made more evident and convenient v Introduction of the plug-in architecture r More on this on subsequent slides… v Don’t forget the other important changes already going on! r See other presentations: – Transition to ROOT, POOL (LCG Persistency) – GRID/Production environment evolution – Mantis for OSCAR 2.x

10. November 4, 2002 Lassi A. Tuura, Northeastern University http://iguana.cern.ch 10Modules v What’s a module? r An (extension) component to a framework (often dynamically loaded) r Framework knows only that a module extends a particular API (usually abstract interfaces), not how and what it needs to do so r Examples abound: Netscape plug-ins, Apache modules, Python and PERL modules, Illustrator and PhotoShop extensions, … r Already used in many ways in CMS projects: package builders, detector units, hit/digi readers and writers, and many algorithms are essentially extensions of APIs provided by COBRA, and “subframeworks” in ORCA v Why modules? r Eases management—framework doesn’t need to know lots of details about the modules, but can simply load them and gain additional capabilities r Helps to give symbolic names to capabilities and allow framework to reason about them: “here’s all you will need to read data product X” r Allows better services to external parties (Python, GRID, IGUANA, …) without having to put that knowledge into many applications

11. November 4, 2002 Lassi A. Tuura, Northeastern University http://iguana.cern.ch 11 Plug-In Architecture v Moving the implementation from IGUANA to CMS core r We already have a couple of years of experience with these tools… v Major benefits ahead r Easier application composition: a logical component larger than a single library can be defined as a real module (building on SCRAM groups) r Separation of higher level concepts (e.g. data products) from technical implementation details (e.g. which libraries are involved, whether to use dynamic loading or statically built applications) r More flexible and dynamic application composition r Available to all high-level frameworks, not just COBRA or IGUANA r Gives us more breathing room with the ever faster development v Gradual introduction first into COBRA, then elsewhere r Starting with simple, easy to understand build and usage model r Rewriting the IGUANA how-to guides for more generic use r Hand in hand with improved core component definitions

12. November 4, 2002 Lassi A. Tuura, Northeastern University http://iguana.cern.ch 12Summary v Exciting times ahead! v Amazing progress in many areas r Both CCS and PRS software v We are making sure we have a foundation that is able to sustain all these development with sufficient ease