Outline:
LHCb and LCG-AAPh.Charpentier
011010011101
1010100010101010110100
B00le
QuickTime™ et undécompresseur TIFF (LZW)
sont requis pour visionner cette image.
PhC LCG-AA Internal review 2
LHCb Applications
Simul.Gauss
AnalysisDaVinci
MCHits
DST
Raw Data (r)DSTMCParts
GenParts
Event model / Physics event model
AOD
ConditionsDatabase
Gaudi
Digit.Boole
TriggerMoore
Recons.Brunel
PhC LCG-AA Internal review 3
LHCb packages dependencies
LHCb
Online
SEALPOOL
Root Ext.Libs
Ga
uss
Bo
ole
Bru
nel
Pa
nora
mix
Mo
ore
Gaudi
LCG
Framework
Ap
plic
atio
ns
PhysRecLbcom
Event ModelD
aV
inci
Componentprojects
COOL
CORAL
Geant4
GENSER
: depends
: uses
PhC LCG-AA Internal review 4
LCG-AA dependencies
LHCb applications depend on LCG-AA through Gaudi Persistency: POOL Conditions DB: COOL Event model: physics vectors, SVectors, SMatrix from ROOT
No more CLHEP dependency (new event model) except through Geant4, HepMC
Simulation: Geant4 (Giga), generators from GENSER, HepMC No direct dependency on CORAL nor on SEAL (but need all libraries…) Minimum of PI needed integrated in Gaudi
SPI dependencies Externals: direct dependency (GSL, Boost, Python, Xerces…), plugins
(gfal, lfc, castor, dcache…) LCGCMT for build (LHCb uses CMT) Savannah for bug and feature tracing
Gaudi, applications, but also DIRAC, GANGA Platforms used
slc3_gcc323, moving to slc4_gcc34. Windows VC debug version Interest in MacOS
PhC LCG-AA Internal review 5
SPI
LHCb build relies on LCGCMT Acknowledge CMT interfaces for external projects
Should separate build and runtime dependencies LHCb script used for setting run time environment for plugins
LHCb would like to be able to rebuild from source (for non-supported platforms)
Might be facilitated by AA using CMT LCG externals
Very positive, AA flexible for adding new packages Releases
Tarfiles should be built automatically and systematically doxytag files should be produced automatically (our doc
relies on it)
PhC LCG-AA Internal review 6
SPI (cont’d)
Middleware client libraries (part of lcg/externals) Good (necessary) to have full control of versions
Impossible to rely on Grid-installed versions Better liaison needed with developers Why not deploy client libraries only through lcg/externals?
Libraries (gfal, lfc, castor, dcache_client) Setting the UI environment breaks AA dependencies … thus release most common LCG commands (already there)
lcg_utils, grid-proxy-init… need for repackaging (globus comes through globusrls ;-))
PhC LCG-AA Internal review 7
Persistency
POOL No need for File Catalog support besides XML (gfal ROOT
plugin) Stable and reliable LHCb contributes to storage manager (M.Frank)
CORAL No direct dependency
COOL Basis for our Conditions DB LHCb contributes to COOL Core development (M.Clemencic) Framework completed for seamless update of calibrations
and alignment from Conditions Migration from XML files to CondDB to take place in coming
months SQLite slice used for simulation ORACLE DB used at Tier1s & CERN for reconstruction / analysis Replication through 3D (ORACLE streaming)
PhC LCG-AA Internal review 8
ROOT
REFLEX, RELAX used by persistency (+ ROOT IO) and GaudiPython (through PyROOT)
Event model moved from CLHEP to ROOT new vector and matrix classes
Contribution to packages evaluation and SMatrix (symmetric matrices)
Used successfully for DC06 software releases File access: support for all file access protocols needed
rfio, rootd, dcap, gsidcap Use gfal for file access and/or file staging (Gaudi event
access service) - from LFN, SURL or tURL Plugins need testing and version control
Problems of server version compatibility? Client libraries should all be backward compatible How to back port bug fix releases of plugins (cf rfio recently)
PhC LCG-AA Internal review 9
ROOT (cont’d)
LHCb still has legacy data and hence software…. Uses ROOT 3! Ported Castor2 plugin to ROOT 3 Not clear how long this support can go (LHCb would need it
until end 2006) PROOF
LHCb watching developments Currently considering more batch analysis using Ganga /
DIRAC / LCG grid (job splitting, result merging) Plugin and component model
Convergence needed between SEAL and ROOT. Gaudi could use it instead of its own (see review 2005)
General remark Beware to concentrate on LHC top priorities….
PhC LCG-AA Internal review 10
Simulation
Simulation production performed on the GRID all software distributed to the sites ship only necessary libraries
and input data Almost all generator libraries from GENSER area
HepMC for event record schema evolution
Generators integrated in Gauss simulation framework Pythia 6.325.2, LHAPDF 4.2, Photos 215.2 for DC06 production
(PDFLIB in DC04 no longer used) libraries cannot be removed from LCG area without agreement
Herwig 6.510.2, Hijing 1.383bs not yet used for central productions work in progress for integration of Sherpa
Private LHCb version of EvtGen (adapted from BaBar) and of BcVegPy
EvtGenLHC in GENSER based on LHCb version Initial problems with granularity of libraries
better now for remote distributions, could be improved further at CERN link directly with GENSER areas
PhC LCG-AA Internal review 11
Simulation (cont’d)
GEANT4 used in Gauss for production of data for physics studies since DC04
Version 7.1.p01a used in DC06 Due to DC06 production Gauss has not yet been ported to
version 8.1 Stable production ongoing
Source taken from GEANT4 area and global libraries built in LHCb with CMT
allow fast bug fixes to be introduced for example for problems identified in production
good communication with GEANT4 team
FLUKA used for radiation studies at CERN library downloaded from web site
PhC LCG-AA Internal review 12
Management and release cycles
Management Very effective Architects Forum biweekly meetings Easy to reach consensus for next steps Need for closer integration of Grid client libraries
LCG developers’ and deployment representative in AF
Release cycles Improvement with the policy used since spring Still could be faster for rebuild releases Tarfiles and doc to be built automatically with releases Useful to have a preview (LCGCMT_HEAD) LHCb cannot pick up all releases, but easy to make plans if
LCG-AA follows the agreed schedule
PhC LCG-AA Internal review 13
Conclusions
LHCb is fully using LCG-AA All projects, directly or indirectly
LHCb is generally satisfied with the service provided Efficient organisation Improved release cycle
Looking forward to better integration of external Grid / fabric software
Ready to face the challenge of real data… when they come