1 / 24

LHCb Computing Project

LHCb Computing Project. Status report to LHCC referees J.Harvey Oct 22, 1998. Focus of Talk. Organisation and strategy for building new software Update on developments in DAQ and Controls First results from Myrinet evaluation Progress in the CERN Joint COntrols Project (JCOP).

boylet
Download Presentation

LHCb Computing Project

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

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

  2. Focus of Talk • Organisation and strategy for building new software • Update 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 Build Develop models, Evaluate toolkits Architect components and systems Choose integration standard Engineer reusable components 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

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

  5. LHCb Offline Software Road Map Integration and Commissioning Exploitation Detailed Implementation Release Number Working Prototype, ‘retire’ SICB 2000 2002 2004 2006

  6. Milestone 1- Working Prototype • By 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 • When in production, stop development of SICB

  7. Strategy • We are convinced of the importance of the architecture • Identify components, define their interfaces, relationships among them • Build components • first look around and see what components we can use (Objectivity, OpenInventor, ROOT, WIRED,….) • Build frameworks from these components • “framework artefact that guarantees the architecture is respected” • Common approach in different domains • apply good principles system-wide and reuse ideas • Incremental approach to development • new release every two months • gradually add functionality • rapid feedback

  8. Design Team • Architect and Project Leader • experienced designer • Domain specialists • data management • visualisation • algorithms • Team of seven people all located at CERN (optimal) • Daily design sessions (4 - 7 p.m.) • Consult with experts from other experiments • 2 day meeting at Orsay/LAL with ATLAS domain architects • external reviewers

  9. Current Architecture

  10. Use Cases (scenarios)

  11. LHCb Detector Description Persistency Detector Store Persistency Service DetElement DetElement Detector Data Service DetElement DetElement Converter DetElement Converter Converter DetElement Converter Geant4 Detector description Transient Detector Store ToGeant4 Service • Detector Elements need to be “identified” • Strong hierarchical structure • Versioning Converter Converter Converter Converter

  12. Visualisation Representations Store (graphical, textual) Graph Store Rep. Service Converter Converter Converter Converter Transient Event/ Detector Store Selector User Interface Mark objects in Store

  13. Architecture Review • Benefits • Force preparation for the review - Documentation! • Early detection of problems with the existing architecture • Validation of the requirements • Improvement in Architectures in all experiments • Planned for last week in November • Review team • Experience with software architectures • Domain experts • From other LHC experiments

  14. Development Environment • Development platform: NT • Design tool: Rational Rose • Coding/debugging: Visual C++ • Code Management: Visual SourceSafe • Code repository: \\alnts1\Packages\LHCb\ • Web authoring: Front Page 98 • Participate in SPIDER project

  15. LHCb OO Programming Course • Five day course to be held at CERN Dec 7-11 • Covers OO Analysis and Design, and hands-on programming • Establish use of common methods and notation • 16 people registered to attend • Second course already fixed for Jan 18-22, 1999

  16. Releases • Release 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. • Future 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. Work Breakdown

  18. Project Tracking September October November December January 24/8 31/8 7/9 14/9 21/9 28/9 5/10 12/10 19/10 26/10 2/11 9/11 16/11 23/11 30/11 7/12 14/12 21/12 28/12 4/1 ID Task Name 1 User Requirements 2 Architecture Design 3 SDE preparation 4 Review Preparation 5 Architecture Review 25/11 6 Module Development 7 Module Design 8 Coding 9 Module testing 10 System Testing 11 Documentation 12 Release 1.0 18/12 • Progress can be followed from Web page • http://lhcb.cern.ch/computing/offline/html/TNS_Scrapboard.htm • 1 week delay for the moment

  19. Data Acquisition System

  20. Event Builder Project • Myrinet Equipment received and installed. • First program for interface processor written • First measurements of raw speed done

  21. Myrinet interface-interface bandwidth

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

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

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

More Related