1. Genova 10-Dec-2001 Andreas Pfeiffer, CERN/IT-API, andreas.pfeiffer@cern.ch1 Anaphe OO Libraries for Data Analysis using C++ and Python Andreas Pfeiffer CERN IT/API andreas.pfeiffer@cern.ch

2. Genova 10-Dec-2001 Andreas Pfeiffer, CERN/IT-API, andreas.pfeiffer@cern.ch 2 Outline zMotivation yLHC computing challenge zAnaphe Components yC++ zLizard: Interactive Data Analysis yPython zSoftware quality control zSummary

3. Genova 10-Dec-2001 Andreas Pfeiffer, CERN/IT-API, andreas.pfeiffer@cern.ch3 LHC Computing challenge

4. Genova 10-Dec-2001 Andreas Pfeiffer, CERN/IT-API, andreas.pfeiffer@cern.ch 4 LHC & The Alps 27km circumference ~100m deep Interaction Points

5. Genova 10-Dec-2001 Andreas Pfeiffer, CERN/IT-API, andreas.pfeiffer@cern.ch 5 The Large Hadron Collider zA completely new particle collider (start-up in 2006) y the largest superconductor installation in the world zA collision will take place every 25 nanoseconds zBut only one in a billion will be interesting… zAnd only one in a trillion will be really interesting !!! zReal-time data filtering: Petabytes per second to Gigabytes per second zAccumulated data: Petabytes per year zData mining by thousands of geographically dispersed scientists in hundreds of teams

6. Genova 10-Dec-2001 Andreas Pfeiffer, CERN/IT-API, andreas.pfeiffer@cern.ch 6 LHC Computing Challenge z4 experiments will create huge amount of data y>1 PetaByte/year for each experiment ! x10 15 Bytes x1,000 TeraBytes x20,000 Redwood tapes x100,000 dual-sided DVD-RAM disks x1,500,000 sets of the Encyclopaedia Britannica (w/o photos) zNeed lots of CPU power to reconstruct/analyse yabout 1000 PC boxes per experiment (2005 ones !) x40.000 of today’s boxes (dual P-III 800 MHz) xcomplex data models yreconstruction s/w is also used for online filtering xneeds high quality s/w in order not to waste beam time

7. Genova 10-Dec-2001 Andreas Pfeiffer, CERN/IT-API, andreas.pfeiffer@cern.ch 7 Lifetime of LHC software = 25 yrs WWW Thanks to Dino Ferrero Merlino(IT)

8. Genova 10-Dec-2001 Andreas Pfeiffer, CERN/IT-API, andreas.pfeiffer@cern.ch 8 Technology (R)Evolution z10 yrs major cycle length (HW,SW,OS) y~12 evolutionary changes in the market y 1 revolutionary change y towards greater diversity y don’t forget changes of requirements zConsequences ys/w written today most probably will be rewritten tomorrow ywe must anticipate changes

9. Genova 10-Dec-2001 Andreas Pfeiffer, CERN/IT-API, andreas.pfeiffer@cern.ch 9 Anaphe: what it is zModular (OO/C++) replacement of CERNLIB functionality for use in HEP experiments ymemory management yI/O yfoundation classes yhistogramming yminimizing/fitting yvisualization yinteractive data analysis zTrying to use standards wherever possible zTrying to re-use existing class libraries zThis talk will not cover detector simulation (GEANT-4)

10. Genova 10-Dec-2001 Andreas Pfeiffer, CERN/IT-API, andreas.pfeiffer@cern.ch 10 Anaphe Components

11. Genova 10-Dec-2001 Andreas Pfeiffer, CERN/IT-API, andreas.pfeiffer@cern.ch 11 Use of Components with Abstract Interfaces  User Code uses only Interface classes  IHistogram1D * hist = histoFactory-> create1D(‘track quality’, 100, 0., 10.) zActual implementations are selected at run-time yloading of shared libraries zNo change at all to user code but keep freedom to choose implementation Histo- Impl. 2 Histo-IFFitter-IF User Code Fitter- Impl. Y Histo- Impl. 1 Fitter- Impl. X

12. Genova 10-Dec-2001 Andreas Pfeiffer, CERN/IT-API, andreas.pfeiffer@cern.ch 12 The AIDA project zAIDA project (Abstract Interfaces for Data Analysis) was initiated at the HepVis’99 workshop in Orsay zPresently active mainly developers from existing packages yTony Johnson (JAS) yAndreas Pfeiffer (Lizard/Anaphe) yGuy Barrand (OpenScientist ) yMark Dönszelmann (Wired) yDevelopers from LHCb/Gaudi zmore on AIDA tomorrow...

13. Genova 10-Dec-2001 Andreas Pfeiffer, CERN/IT-API, andreas.pfeiffer@cern.ch 13 ‘Layered’ Approach zBasic functionalities (histograms, fitting, etc.) are available as individual C++ class libraries. zEasy replacing one part without throwing away everything yObjectivity/DB to provide persistence yHepODBMS library (“insulating layer”, “tags”) yHistogram library (HTL) yFitting libraries (Gemini, HepFitting) yGraphics libraries (Qt, Qplotter) zInsulate components through Abstract Interfaces y“wrapper” layer to implement Interfaces in terms of existing libs zApply s/w quality control tools ycode checking, testing

14. Genova 10-Dec-2001 Andreas Pfeiffer, CERN/IT-API, andreas.pfeiffer@cern.ch 14 Anaphe Components: Overview

15. Genova 10-Dec-2001 Andreas Pfeiffer, CERN/IT-API, andreas.pfeiffer@cern.ch 15 Anaphe Internals: Abstract Interfaces

16. Genova 10-Dec-2001 Andreas Pfeiffer, CERN/IT-API, andreas.pfeiffer@cern.ch 16 Anaphe components

17. Genova 10-Dec-2001 Andreas Pfeiffer, CERN/IT-API, andreas.pfeiffer@cern.ch 17 Basic 3D Graphic Libraries zOpenGL (basic graphics) yDe-facto industry standard for basic 3D graphics yUsed in CAD/CAE, games, VR, medical imaging zOpenInventor (scene mgmt.) yOO 3D toolkit for graphics yCubes, polygons, text, materials yCameras, lights, picking y3D viewers/editors,animation yBased on OpenGL/MesaGL

18. Genova 10-Dec-2001 Andreas Pfeiffer, CERN/IT-API, andreas.pfeiffer@cern.ch 18 2D Graphics libraries zQt ymulti-platform C++ GUI toolkit xC++ class library, not wrapper around C libs xsuperset of Motif and MFC xavailable on Unix and MS Windows xno change for developer ycommercial but with public domain version ywww.troll.no zQplotter y“add-on” functionality for HEP x“HIGZ/HPLOT”

19. Genova 10-Dec-2001 Andreas Pfeiffer, CERN/IT-API, andreas.pfeiffer@cern.ch 19 Mathematical Libraries zNAG (Numerical Algorithms Group) C Library yCovers a broad range of functionality xLinear algebra xdifferential equations xquadrature, etc. ySpecial functions of CERNLIB added to Mark-6 release xmostly for theory and accelerator xQuality assurance xextensive testing done by NAG ywww.nag.com

20. Genova 10-Dec-2001 Andreas Pfeiffer, CERN/IT-API, andreas.pfeiffer@cern.ch 20 CLHEP - foundation classes zHEP foundation class library yRandom number generators yPhysics vectors x3- and 4- vectors yGeometry yLinear algebra ySystem of units ymore packages recently added xwill continue to evolve zwwwinfo.cern.ch/asd/lhc++/clhep/

21. Genova 10-Dec-2001 Andreas Pfeiffer, CERN/IT-API, andreas.pfeiffer@cern.ch 21 Histograms: the HTL package zHistograms are the basic tool for physics analysis yStatistical information of density distributions zHistogram Template Library (HTL) ydesign based on C++ templates yModular : separation between sampling and display yExtensible : open for user defined binning systems yFlexible: support transient/persistent at the same time yOpen: large use of abstract interfaces yrecent addition: 3D histograms

22. Genova 10-Dec-2001 Andreas Pfeiffer, CERN/IT-API, andreas.pfeiffer@cern.ch 22 Fitting and Minimization zFitting and Minimization Library (FML) ycommon OO interface xNAG-C, MINUIT ybased on Abstract Interfaces  IVector, IModelFunction, … yfitting as a special case of minimization xminimize “distance” between data and model yreplacement for HepFitting (and Gemini) zGemini ycommon interface to minimizer engine yvery thin layer

23. Genova 10-Dec-2001 Andreas Pfeiffer, CERN/IT-API, andreas.pfeiffer@cern.ch23 Opening bracket: Persistency

24. Genova 10-Dec-2001 Andreas Pfeiffer, CERN/IT-API, andreas.pfeiffer@cern.ch 24 Object persistency Two concepts: serial and page I/O z“Sequential access to objects” (streaming) ygood in networking context or serial writes to file(s) ymuch like “good old Fortran” yoften perceived to be “simpler” to implement (“ >”) z“Navigational access to objects” (buffered) yI/O on demand for complex data models ylocation transparent (for user) access to object xtypically by de-referencing of a smart pointer yoptimized for (random) disk access (disks deliver pages) ysequential write to file(s) still ok zBoth concepts need to take care about changes of the internal structure of the objects (schema evolution)

25. Genova 10-Dec-2001 Andreas Pfeiffer, CERN/IT-API, andreas.pfeiffer@cern.ch 25 Architectural Issue: Persistency (“Object-I/O”) zBrings a completely new quality into the design zObjects have now lifetime ydon’t “delete” until you really are sure you want to ypersistency is kind of “intended memory leak” ywould like to see no difference between memory and disk z“Layout” of objects may change during (extended) life y“schema evolution” yadditions/deletions of attributes ychanges of inheritance relations

26. Genova 10-Dec-2001 Andreas Pfeiffer, CERN/IT-API, andreas.pfeiffer@cern.ch 26 Architectural Issue: Persistency (“Object-I/O”) (II) zObjects can be placed (“clustering”) yde-coupling of logical and physical view of data zSpecial care needed to ensure consistency in data set yavoid reading group of objects (tracks, events,...) for which writing/updating is not (yet) complete yclean up if only part of the objects are written ytypically taken care of by using transactions zComplications possible in distributed computing yneed to protect disk access now like memory access in past (“Segmentation violation”)

27. Genova 10-Dec-2001 Andreas Pfeiffer, CERN/IT-API, andreas.pfeiffer@cern.ch 27 Physical Model and Logical Model Physical model may be changed to optimise performance Physical model may be changed to optimise performance Existing applications continue to work transparently ! Existing applications continue to work transparently !

28. Genova 10-Dec-2001 Andreas Pfeiffer, CERN/IT-API, andreas.pfeiffer@cern.ch 28 Object Model Thanks to Vincenzo Innocente (CMS)

29. Genova 10-Dec-2001 Andreas Pfeiffer, CERN/IT-API, andreas.pfeiffer@cern.ch 29 Physical clustering Thanks to Vincenzo Innocente (CMS)

30. Genova 10-Dec-2001 Andreas Pfeiffer, CERN/IT-API, andreas.pfeiffer@cern.ch30 Closing bracket: Persistency

31. Genova 10-Dec-2001 Andreas Pfeiffer, CERN/IT-API, andreas.pfeiffer@cern.ch 31 “Tags”, Ntuples and Events zTags - a special kind of Ntuple yAlways associated with an underlying persistent store yTags may be used to store “ntuple-like” data xextracted from all over the event xminPt, maxEmiss, nJets, nMuon, trigger, … zMain use: speedup data selection for analysis … yTag simplifies selection without loosing complexity zEvents more complex than a tree structure (“CWN”) ylots of cross-references between classes, containers zAssociation from the Tag to the Event may be used to navigate to any other part of the Event yeven from an interactive visualization program

32. Genova 10-Dec-2001 Andreas Pfeiffer, CERN/IT-API, andreas.pfeiffer@cern.ch 32 AIDA compliance of Anaphe zPresently (Anaphe 3.x) only AIDA 1.0 compliant zPlan to implement AIDA 2.2 Interfaces by end 2001 (Anaphe 4.x) yinitially as wrappers to existing interfaces/packages zWill maintain 3.x for some time yensures stability for users zDevelopment will concentrate on 4.x ywhile AIDA will evolve further zSimilar timeschedule as JAS (Tony Johnson) zOpenScientist (Guy Barrand) already there

33. Genova 10-Dec-2001 Andreas Pfeiffer, CERN/IT-API, andreas.pfeiffer@cern.ch33 Lizard: a tool for Interactive Data Analysis

34. Genova 10-Dec-2001 Andreas Pfeiffer, CERN/IT-API, andreas.pfeiffer@cern.ch 34 Interactive Data Analysis zAim: “OO replacement for PAW” (at least) yanalysis of “ntuple-like data” (“Tags”, “Ntuples”, …) yvisualisation of data (Histograms, scatter-plot, “Vectors”) yfitting of histograms (and other data) yaccess to experiment specific data/code zMaximize flexibility and re-use zForesee customization/integration yallow use from within experiment’s s/w zPlan for extensions y“code for now, design for the future” zEnsure maintainability yuse of s/w quality control tools

35. Genova 10-Dec-2001 Andreas Pfeiffer, CERN/IT-API, andreas.pfeiffer@cern.ch 35 Lizard zUn tool di analisi interattiva AIDA compatibile yPython scripting yVisualizzazione con Qt yIstogrammi HTL (via AIDA) yPersistenza con Objectivity yFitting con NAG Libraries (o Minuit) zComponenti disponibili come shared libraries yindipendenti dal linguaggio di scripting ysi possono usare anche in programmi C++ (Geant4)

36. Genova 10-Dec-2001 Andreas Pfeiffer, CERN/IT-API, andreas.pfeiffer@cern.ch 36 Scripting - why zTypical use of scripting is quite different from programming (reconstruction, analysis,...) yhistory “go back to where I was before” yrepetition/looping - with “modifiable parameters” zavoid “one size fits all” or “using power-tool as hammer” yrapid prototyping in “scripting language” xquick turn-around times yperformance critical code in “core language” xexploit richer set of features/functionality (e.g. templates in C++) zscripting languages usually less susceptible to changes than “mainstream languages” ypotentially longer lifes

37. Genova 10-Dec-2001 Andreas Pfeiffer, CERN/IT-API, andreas.pfeiffer@cern.ch 37 Python - why zPython - OO (scripting) language öno “strange $!%-variables” ôsensitive to indentation zMore easy for users yas Java zLots of user supplied modules available and ready for use yscientific, numerics, graphics, GUI, network, OS, games, DBs, …  example: http://www.vex.net/parnassus/  Parnassus Totals: 1173 items in 49 categories. zAlso usable in Java (Jython) yused in JAS for scripting yminimize changes needed within AIDA compliant environments

38. Genova 10-Dec-2001 Andreas Pfeiffer, CERN/IT-API, andreas.pfeiffer@cern.ch 38 Python - how zSWIG to (semi-) automatically create connection to chosen scripting language yallows flexibility to choose amongst several scripting languages yPython, Perl, Tcl, Guile, Ruby, (Java) …  Very easy to use  swig -c++ -python -shadow -c myClass.h  create shared lib from myClass.cpp and myClass_wrap.c  start python and import myClass.h to use it zVery easy to extend ysimply inherit from “swiggified” class in python ymodifications can later be fed back into C++ xperformance, type safety, special language features (templates), …

39. Genova 10-Dec-2001 Andreas Pfeiffer, CERN/IT-API, andreas.pfeiffer@cern.ch 39 PAW -> Lizard translation  Ntuple projection Lizard  lizard --useHBook  :-) nt = ntm.findNtuple(“higgscand.hbk::cands”)  :-) nplot1D(nt, “mass”, “quality=5 && cut > 198”) zNtuple projection PAW  pawX11  paw> h/file 1 higgscand.hbk  paw> nt/pl 10.mass quality=5.and.cut>198  Assuming file higgscand.hbk contains ntuple with number 10 and title cands Any valid C++ expression

40. Genova 10-Dec-2001 Andreas Pfeiffer, CERN/IT-API, andreas.pfeiffer@cern.ch 40 Example script (ntuple) # get list of names of all tuples from tuplemanager ntm.listTuples() nt1=ntm.findNtuple(“Charm1”) # retrieve tuple by name # create 1D histos to project into h1=hm.create1D(10, “mass”,100, 0., 5000.) h2=hm.create1D(20, “mass for pt1>10”,100, 0., 5000.) # project the attribute ”MASS" into histo h1 without cut ("") nt1.project1D( h1, “”, “MASS”) # project the attribute ”MASS" into histo h2 with cut (”PT1>10") nt1.project1D( h2, “PT1>10”, “MASS”)

41. Genova 10-Dec-2001 Andreas Pfeiffer, CERN/IT-API, andreas.pfeiffer@cern.ch 41

42. Genova 10-Dec-2001 Andreas Pfeiffer, CERN/IT-API, andreas.pfeiffer@cern.ch 42 Lizard: History and Present Status zStarted after CHEP-2000 zFull version out since June 2001 y“PAW like” analysis functionality plus: yon-demand loading of compiled code using shared libraries xgives full access to experiment’s analysis code and data ybased on Abstract Interfaces xflexible and extensible z“License free” version since Sep. 2001 yHBook for RWNtuples and Histogram storage yMinuit as minimizer engine

43. Genova 10-Dec-2001 Andreas Pfeiffer, CERN/IT-API, andreas.pfeiffer@cern.ch 43 Users and Collaborations zAIDA spoken here! yIGUANA (CMS visualization) yGAUDI (LHCb/HARP) framework yATHENA (Atlas) framework yAnalyzer modules in Geant 4 yJAS yOpen Scientist y…you?

44. Genova 10-Dec-2001 Andreas Pfeiffer, CERN/IT-API, andreas.pfeiffer@cern.ch44 Software quality control

45. Genova 10-Dec-2001 Andreas Pfeiffer, CERN/IT-API, andreas.pfeiffer@cern.ch 45 Software quality control zUsing tools for testing/checking has started yInsure++, CodeWizard zPackage dependencies: Ignominy ySet of perl and shell scripts by Lassi Tuura (CMS) yIgnominy scans… xMake dependency data produced by the compilers (*.d files) xSource code for #includes (resolved against the ones actually seen) xShared library dependencies (“ldd” output) xDefined and required symbols (“nm” output) yAnd maps… xSource code and binaries into packages x#include dependencies into package dependencies xUnresolved/defined symbols into package dependencies ignominy: dishonour, disgrace, shame; infamy; the condition of being in disgrace, etc. (Oxford English Dictionary)

46. Genova 10-Dec-2001 Andreas Pfeiffer, CERN/IT-API, andreas.pfeiffer@cern.ch 46 Ignominy Analysis of Anaphe zDistribution of tools and utilities for LHC era physics yCombination of commercial, free and HEP software yClaims to be a toolkit zSeems to live up to its toolkit claims yGood work on modularity yClean design is evident in many places yDependency diagrams often split naturally into functional units Thanks to Lassi Tuura (CMS)

47. Genova 10-Dec-2001 Andreas Pfeiffer, CERN/IT-API, andreas.pfeiffer@cern.ch 47 Package Metrics ySize = total amount of source code (not normalised across projects!) yACD = average component dependency (~ libraries linked in) yCCD = cumulative component dependency sum of single-package component dependencies over whole release yNCCD = Measure of CCD compared to a balanced binary tree xA good toolkit’s NCCD will be close to 1.0 x< 1.0: structure is flatter than a binary tree (= independent packages) x> 1.0: structure is more strongly coupled (vertical or cyclic) xAim: NCCD ~ 1 for given software/functionality Thanks to Lassi Tuura (CMS)

48. Genova 10-Dec-2001 Andreas Pfeiffer, CERN/IT-API, andreas.pfeiffer@cern.ch 48 Metrics: NCCD vs Cycles Toolkits & Frameworks ATLAS ORCA IGUANA COBRA G4 ROOT Thanks to Lassi Tuura (CMS) Includes Fortran NCCD (“spaghetti index”)  1.0: good toolkit < 1.0: indep. packages > 1.0: strongly-coupled NCCD (“spaghetti index”)  1.0: good toolkit < 1.0: indep. packages > 1.0: strongly-coupled Anaphe

49. Genova 10-Dec-2001 Andreas Pfeiffer, CERN/IT-API, andreas.pfeiffer@cern.ch 49 Future enhancements zAccess to other implementations of components yHBOOK CWNtuples zReading of ROOT (> V3.0) files ysimilar to Tony Johnson’s (Java) RootIO package zAIDA Ntuple/Histo store yoptimized for Ntuples, Histograms as (compressed) XML zCommunication with Java tools/packages (JAS, Wired) yvia AIDA zAdding other “scripting” languages yPerl, Tcl, cint ?

50. Genova 10-Dec-2001 Andreas Pfeiffer, CERN/IT-API, andreas.pfeiffer@cern.ch 50 Challenge: Distributed Computing zMotivation ymove code to data yparallel analysis zTechniques yservices via AI ylate binding yplug-in architecture zEnd-user (Lizard) ylook-and-feel of local analysis zR&D started and first prototype available soon yCORBA based

51. Genova 10-Dec-2001 Andreas Pfeiffer, CERN/IT-API, andreas.pfeiffer@cern.ch 51 Summary zThe architecture of Anaphe shows some important items for flexible and modular data analysis: yweak coupling between components through use of Abstract Interface ybasic functionality is covered by individual C++ class libraries yemphasis on usability and maintainability zMajor criteria are flexibility, extensibility and interoperability yrecent example: GEANT-4 examples (based on AIDA) zLizard is an Interactive Data Analysis Tool based on Anaphe components and the Python scripting language (through SWIG) yLizard is young but has very solid base in mature Anaphe libraries yreal plug-in structure zSoftware quality control is important ytools help to optimize dependencies / minimize maintenance effort

52. Genova 10-Dec-2001 Andreas Pfeiffer, CERN/IT-API, andreas.pfeiffer@cern.ch 52 More information zcern.ch/Anaphe zcern.ch/Anaphe/Lizard zaida.freehep.org/ zcern.ch/DB zwwwinfo.cern.ch/asd/lhc++/clhep/

53. Genova 10-Dec-2001 Andreas Pfeiffer, CERN/IT-API, andreas.pfeiffer@cern.ch53 Additional slides

54. Genova 10-Dec-2001 Andreas Pfeiffer, CERN/IT-API, andreas.pfeiffer@cern.ch 54 Analysis of Geant4 zFairly large C++ project yVery fine-grained (and multi-level) package structuring ySeems quite clean from the preliminary analysis zFine package subdivision helps in many ways but makes analysis and code understanding more complicated zOne subsystem seems strongly coupled and needs attention zNeed to study the use of the internal command system Thanks to Lassi Tuura (CMS)

55. Genova 10-Dec-2001 Andreas Pfeiffer, CERN/IT-API, andreas.pfeiffer@cern.ch 55 Analysis of ROOT zROOT developers have done a formidable job of breaking binary (shared library) dependencies, but… yFor example: By static analysis, nothing seems to use the postscript package directly (no incoming dependencies), but there is this code: void TPad::Print (const char *filename, Option_t *option) { […] TVirtualPS *psave = gVirtualPS; if (gROOT->LoadClass("TPostScript","Postscript")) return; gROOT->ProcessLineFast("new TPostScript()"); gVirtualPS->Open(psname,pstype); gVirtualPS->SetBit(kPrintingPS); […] } yTaking these and global objects into account makes the dependency diagrams very different zSign of fast growth? Need a “next evolutionary step”? ySo “coherent” that replacing parts could get painful… Thanks to Lassi Tuura (CMS)

56. Genova 10-Dec-2001 Andreas Pfeiffer, CERN/IT-API, andreas.pfeiffer@cern.ch 56 Analysis of ROOT… Binary only Binary + Source + Logical = Real Thanks to Lassi Tuura (CMS)

57. Genova 10-Dec-2001 Andreas Pfeiffer, CERN/IT-API, andreas.pfeiffer@cern.ch 57 Metrics: NCCD vs ACD Toolkits & Frameworks ATLAS ORCA Anaphe IGUANA COBRA G4 ROOT Thanks to Lassi Tuura (CMS)

58. Genova 10-Dec-2001 Andreas Pfeiffer, CERN/IT-API, andreas.pfeiffer@cern.ch 58 Metrics: NCCD vs Size Toolkits & Frameworks ATLAS ORCA Anaphe IGUANA COBRA G4 ROOT Thanks to Lassi Tuura (CMS)

59. Genova 10-Dec-2001 Andreas Pfeiffer, CERN/IT-API, andreas.pfeiffer@cern.ch 59 Metrics: NCCD vs AID Toolkits & Frameworks ATLAS ORCA AnapheIGUANA COBRA G4 ROOT Thanks to Lassi Tuura (CMS)

60. Genova 10-Dec-2001 Andreas Pfeiffer, CERN/IT-API, andreas.pfeiffer@cern.ch 60 Metrics: Packages vs Size Toolkits & Frameworks ATLAS ORCA Anaphe IGUANA COBRA G4 ROOT Thanks to Lassi Tuura (CMS)

61. Genova 10-Dec-2001 Andreas Pfeiffer, CERN/IT-API, andreas.pfeiffer@cern.ch 61 Metrics: Packages vs Size Toolkits & Frameworks ATLAS ORCA Anaphe IGUANA COBRA G4 ROOT Thanks to Lassi Tuura (CMS)

62. Genova 10-Dec-2001 Andreas Pfeiffer, CERN/IT-API, andreas.pfeiffer@cern.ch 62 Scripting in Lizard User Python Controller Shadow classes C++ interfaces C++ implementations Automatically generated by SWIG AIDA Interfaces Anaphe implementations

63. Genova 10-Dec-2001 Andreas Pfeiffer, CERN/IT-API, andreas.pfeiffer@cern.ch 63 Software life cycle for LHC expts. zLHC starts ~ 2006 zat least 10 yr of running zadditionally at least 5 yr of data analysis

64. Genova 10-Dec-2001 Andreas Pfeiffer, CERN/IT-API, andreas.pfeiffer@cern.ch 64 Lifetime of LHC software = 25 yrs WWW SPS 1969 LEP 1989 W and Z 1983 LEP ends 2000 XML 1.0 1997 Linux V 0.01 1991 C++ 1985 Ethernet standar d 1983 IBM PC 1981 K&R C 1978 Unix V6 first public version 1975 Java 1995 Intel Pentium 1992