1. LHCb Computing Project Status report to LHCC referees J.Harvey Oct 22, 1998

2. J.Harvey : Status report to LHCC referees21/10/98 Slide 2 Focus of Talk qOrganisation and strategy for building new software qUpdate on developments in DAQ and Controls ãFirst results from Myrinet evaluation ãProgress in the CERN Joint COntrols Project (JCOP)

3. A Process for Developing Software Manage Plan, initiate, track, coordinate Set priorities and schedules, resolve conflicts Support Support development processes Manage and maintain components Certify, classify, distribute Document, give feedback Assemble Design application Find and specialise components Develop missing components Integrate components Requirements Existing software systems Build Develop models, Evaluate toolkits Architect components and systems Choose integration standard Engineer reusable components

4. Project Organisation Support Facilities CPU farms Desktop Storage Network System Man. Vendors IT-IPT.. Vendors IT-PDP Vendors IT-ASD Support Software SDE Process Quality Librarian Training Webmaster M Data Management Event, Geometry M M Build Architecture Components Frameworks A Toolkits GUI, visual,…... M Reconstruction M Simulation M Analysis M Controls M Control Room M Assemble DAQ M Manage Steering Group MM C Technical Review EM A LHCb Computing... Arch. Review MA E... M A C E Coordinator Architect Project Manager Project Engineer

5. J.Harvey : Status report to LHCC referees21/10/98 Slide 5 LHCb Offline Software Road Map 200420022000 Working Prototype, ‘retire’ SICB Detailed Implementation Integration and CommissioningExploitation Release Number 2006

6. J.Harvey : Status report to LHCC referees21/10/98 Slide 6 Milestone 1- Working Prototype qBy mid 2000, produce a new working prototype of LHCb software incorporating: ãmodel of the LHCb detector geometry ãdatabase containing ~ 1,000,000 simulated events (~100 GB) ãframework for processing events ãdetector response simulation toolkit ãpattern recognition algorithms for tracking, RICH, calorimetry,.. ãtoolkit of analysis algorithms ãinteractive framework for data analysis qWhen in production, stop development of SICB

7. J.Harvey : Status report to LHCC referees21/10/98 Slide 7 Strategy qWe are convinced of the importance of the architecture qIdentify components, define their interfaces, relationships among them qBuild components ãfirst look around and see what components we can use (Objectivity, OpenInventor, ROOT, WIRED,….) qBuild frameworks from these components ã“framework artefact that guarantees the architecture is respected” qCommon approach in different domains ãapply good principles system-wide and reuse ideas qIncremental approach to development ãnew release every two months ãgradually add functionality ãrapid feedback

8. J.Harvey : Status report to LHCC referees21/10/98 Slide 8 Design Team qArchitect and Project Leader ãexperienced designer qDomain specialists ãdata management ãvisualisation ãalgorithms qTeam of seven people all located at CERN (optimal) qDaily design sessions (4 - 7 p.m.) qConsult with experts from other experiments ã2 day meeting at Orsay/LAL with ATLAS domain architects ãexternal reviewers

9. J.Harvey : Status report to LHCC referees21/10/98 Slide 9 Current Architecture

10. J.Harvey : Status report to LHCC referees21/10/98 Slide 10 Use Cases (scenarios)

11. J.Harvey : Status report to LHCC referees21/10/98 Slide 11 LHCb Detector Description Transient Detector Store Detector Data Service Persistency Service DetElement Persistency Detector Store Converter ToGeant4 Service Converter Geant4 Detector description Detector Elements need to be “identified” Strong hierarchical structure Versioning

12. J.Harvey : Status report to LHCC referees21/10/98 Slide 12 Visualisation Transient Event/ Detector Store Rep. Service Representations Store (graphical, textual) Converter Selector Mark objects in Store Graph Store User Interface

13. J.Harvey : Status report to LHCC referees21/10/98 Slide 13 Architecture Review qBenefits ãForce preparation for the review - Documentation! ãEarly detection of problems with the existing architecture ãValidation of the requirements ãImprovement in Architectures in all experiments qPlanned for last week in November qReview team ãExperience with software architectures ãDomain experts ãFrom other LHC experiments

14. J.Harvey : Status report to LHCC referees21/10/98 Slide 14 Development Environment qDevelopment platform: NT qDesign tool: Rational Rose qCoding/debugging: Visual C++ qCode Management: Visual SourceSafe qCode repository: \\alnts1\Packages\LHCb\ qWeb authoring: Front Page 98 qParticipate in SPIDER project

15. J.Harvey : Status report to LHCC referees21/10/98 Slide 15 LHCb OO Programming Course qFive day course to be held at CERN Dec 7-11 qCovers OO Analysis and Design, and hands-on programming qEstablish use of common methods and notation q16 people registered to attend qSecond course already fixed for Jan 18-22, 1999

16. J.Harvey : Status report to LHCC referees21/10/98 Slide 16 Releases qRelease 1.0 planned for end ‘98 allows user to : ãAccess simulated event data produced by SICB (ZEBRA format) ãOutput results in the form of HBOOK histograms and/or ntuples ãTypical “client”: Sub-detector expert developing a pattern recognition algorithm. qFuture releases will evolve according to user needs, for example to add : ãtransient model of the detector geometry ãpersistent event data store using Objectivity ãvisualisation component to permit event display ã...

17. J.Harvey : Status report to LHCC referees21/10/98 Slide 17 Work Breakdown

18. J.Harvey : Status report to LHCC referees21/10/98 Slide 18 Project Tracking qProgress can be followed from Web page ãhttp://lhcb.cern.ch/computing/offline/html/TNS_Scrapboard.htm q1 week delay for the moment IDTask Name 1User Requirements 2Architecture Design 3SDE preparation 4Review Preparation 5Architecture Review 6Module Development 7Module Design 8Coding 9Module testing 10System Testing 11Documentation 12Release 1.0 25/11 18/12 24/831/87/914/921/928/95/1012/1019/1026/102/119/1116/1123/1130/117/1214/1221/1228/124/1 SeptemberOctoberNovemberDecemberJanuary

19. J.Harvey : Status report to LHCC referees21/10/98 Slide 19 Data Acquisition System

20. J.Harvey : Status report to LHCC referees21/10/98 Slide 20 Event Builder Project ãMyrinet Equipment received and installed. ãFirst program for interface processor written ãFirst measurements of raw speed done

21. J.Harvey : Status report to LHCC referees21/10/98 Slide 21 Myrinet interface-interface bandwidth

22. J.Harvey : Status report to LHCC referees21/10/98 Slide 22 JCOP : OPC Evaluation ROC IOS PLC IOS LHC Exp. Sub-Detectors & Experimental equipment I/O Servers distributed in the experimental area ( PC, VME,…) PLC Analog/Digital channels, PLCs, Field buses, RS232, etc.... LAN WAN Storage Other systems (LHC, Safety,...) Servers & Workstations (Fault tolerant) Configuration DB, Archives, Logfiles, etc. Remote Workstations ROC Readout system OPC (OLE Process Control) OPC interface ã Industrial standard ã Customise interfaces ã Check interoperability ã Write OPC server for CAEN I/f

23. J.Harvey : Status report to LHCC referees21/10/98 Slide 23 Controls Task Architecture Oper console Other consoles Su suisor... Oper console Alarm Handler Subsystem supervisor IOS DCS Database DB Editor Gen. Utility Prog. Visuali- zation Dev server Dev server Dev server Dev server Log+Data archive Data Archiver Servers WS Report Generator Other consoles Status displays External SubSys Other systems parameters devices Sub- systems Expert system

24. J.Harvey : Status report to LHCC referees21/10/98 Slide 24 Controls Software Architecture Hardware: I/O cards, FieldBus I/F, RS232,... DCS Services (Alarm Hand., Archiver, etc.) InputOutput (interface drivers) DeviceLib (device drivers) Distributed I/O Servers DCS DB GUI Client Applications (Consoles, DataViewer, etc.) Sub-System supervisors DBMS Generic Specific Object Network parameters devices Storage Device API subsystems distributed devices Config. & Utility tools