LHCb Computing Programme of Work

1. LHCb Computing Programme of Work John Harvey LHCb Software Week, July 5-7, 2000

2. GAUDI v6 planning

3. BRUNEL Work Programme 1. SICBDST retirement • End July: Release BRUNEL v1r2 • Built with SICBDST v234r1 + Gaudi release 5 • Verify RICH, CALO, pile-up • End August: Release BRUNEL v1r3 • Built with SICBDST v235 (MUON TDR test version) • Production test: • 50-100k events DST2, to duplicate corresponding SICBDST test • End September (Milano): Retire SICBDST • Productions in October to use Brunel v1r3 • This is safe if above tests successful: algorithms entirely FORTRAN based, only steering is in C++

4. BRUNEL Work Programme 2. C++ Migration • Integration of C++ tracking in BRUNEL • Start with track-fit (~August) • And create AXTK from C++, switch off FORTRAN track fit • Add digitisation + pattern recognition (~September) • And switch off complete FORTRAN tracking • Comparisons with BRUNEL v1r3 (October) • Release as BRUNEL v2 (End October, for software week) • Use in production from November, together with SICBMC with improved tracker simulation • Common issues • Event Model conventions (Navigation to MC truth, naming, etc.) • end July: proposal on web • mid September: agreed recommendation documented • Milano: guidelines become mandatory • Alignment + Calibration • Coordinator to be appointed and workshop organised (September?) • Review progress in Milano.

5. Background to POW meeting • Brainstorming • Look at longer term • Define new projects • Specify them • Review • Implement

6. Project Planning • Produce one project plan for LHCb Computing • Maintained using MSProject • one person in charge of preparation and tracking – task • Essential ingredients • Work Breakdown Structure (WBS) • High-level milestones (medium, long term) • Low-level milestones (short-term) • Status reports from project leaders every 4 months • Used to track progress

7. Quality Control • Perfect QC is manpower intensive, but QC is indispensible • Different QC criteria applied to different parts • Crucial parts (e.g. framework) need stricter control • Apply procedures to core software first • adapt and use elsewhere according to experience • Some procedures already exist (code guidelines, software releases) but not documented and applied formally • We need to study further procedures used by ATLAS and CMS • Some tools need to be evaluated and adopted • E.g. Insure++ for memory leaks, …. • Test plan and checklists for developers to follow - write template • Need someone to take responsibility for organisation of test procedures, reviews, choosing tools, checklists etc. • QC and Test manager needed

8. Event Model – language independent spec • Use a DDL to describe the data – high priority • Ease maintenance - avoid hand made converters • DDL allows for automatic code generation, schema evolution, interactivity, different languages • Different approaches : IDL/ODL, C++ (CINT), XML, UML/Rose + graphical tool • Study options and build prototype • Need manpower

9. Event Storage • Scope covers bookkeeping, data management, event tags • Issues are size, I/O rates, remote access, data replication, schema evolution, connection to mass storage • GAUDI permits use of different persistency technologies • Use ROOT now – proven to work • To be used by BRUNEL at end of year • Start project to study database approach – in context of LHC-wide activities • Joint IT/LHCb project using ORACLE is a possibility • Envisage a Mock Data Challenge 1H2002 • Need manpower • Doctoral student starting in September

10. Conditions Database • IT developing Conditions Database (alignment, calibration) • Expect a prototype in a few months • Need a CondDBSVc to synchronise detector store to the conditions data • Collect use cases and requirements starting in August • Prototype Svc October-December • Manpower • Andrea Valassi

11. Bookkeeping/TAG database • EventSelector selects data via queries to Tag and Event Data DBs • Current solution (hybrid) : SICb files and ORACLE • Other hybrid possible ROOT and ORACLE • Another attractive Solution : store both in same Database • Full navigability, integrity, single technology • E.g. ORACLE • Study both approaches – compare performance • Need manpower

12. Use of GAUDI online • Interface to data is via the ECS (parameters) and the DAQ (event data) rather than persistent storage • Study data format generated by FE electronics • Banks with converters to fill transient event store • Study performance issues (data copying vs pointers) • First project – make a service that will interface to ECS system (like JobOptions or MessageSvc) • Manpower?

13. Grid testbed plans • Installation of the GLOBUS software at CERN, RAL and Liverpool. • Run SICBMC production using the GLOBUS software on all three sites. • Verify that shipping data back to CERN is possible. • Measure sustained data transfer rates between the three sites. • Extend grid activity to other institutes • Progress report in Milano • Full status report in November Software week • Manpower • Eric and Frank have set up a grid testbed WG

14. Simulation • Event generators (Paolo) • used generators and interface in FORTRAN • C++ versions coming – Pythia 7, STDHEP++, HEPMC, QQport • Detector geometry (Gonzalo) • Techniques and tools to check geometry • Need XML editor and display to facilitate work to be done • Manpower for beampipe, magnet to be defined • Integration with GAUDI (Vanya) • G4 implemented as a GAUDI service (GiGa) • Isolate generators, extract geometry, convert hits into Gaudi objects • Support for interactivity essential • Vanya preparing a complete workplan

15. Simulation - steps • 2000 • prepare framework - single particle generator, check geometry.. • 2001 • Introduce subdetector geometry • Interface magnetic field map • Tune physics parameters • Use SICBMC generator files, get experience with Pythia 7 etc • 2002 • Tune and redesign • Implement digitisation • Compare results with testbeam data etc • Retire SICbMC • Program Name : how about GAUSS ?

16. User interaction • Guy working on an event display • Aims to have program for November software week • Scripting • Several options : CINT, Perl, PYTHON • Proof of concept for one scripting interface • High priority • Manpower? • Interactive Analysis • ROOT,LIZARD, IGUANA(CMS), OpenScientist, JAS • What do we want to do?