LHCb Core Software Meeting

Date and Location

May, 14 2008
10:30 - 12:00
CERN (2-R-030)


Dirk Duellmann, Hubert, Marco Ca., Marco Cl. (minutes), Markus, Olivier, Patrick (EVO), Witek Pokorski


Specific Topics

POOL review

Witek and Dirk came to the LHCb Core Software Meeting to check with us the way LHCb uses the components in POOL (see the slides).

The aim of the review is to define what can be done in terms of clean up of the code. In the process, a new CVS or SVN repository will be created (which will host CORAL and COOL too).

The first thing that we pointed out is that we are not using the POOL XMLFileCatalog anymore, but we have our own implementation. Thus the only components of POOL that we are using are:

  • StorageSvs
  • RootStorageSvc

Markus said that we had some internal discussion (without any decision yet) about the possibility of use directly ROOT for our persistency (with a format compatible with POOL).
For sure we are not going to change this year and it is hard to tell if we will ever change.

Marco Ca. mentioned that, in the second half of the year (as soon as ROOT 5.20 is released), we want to test the new ROOT schema evolution framework. We need that POOL allows us to do it (either with direct access to the underlying ROOT or with some API).

Marco Ca. also expressed interest in a packaging of POOL that allows better control of which releases we need (i.e. only those affecting the 2 services we are using).


Software Releases

Gaudi (Marco Cl.)

  • Started to apply the pending patches aiming for the release at the end of the month.

LHCb, Boole, Brunel (Marco Ca.)

  • LHCb v23r6 is ready in DEV, waiting for news from IT/TT (long standing problems with detector description).
  • Would like to start using the nightlies to validate Gaudi HEAD version (built in LCG nightlies).
    Hubert said that there are still few pending stability problems, but should be sorted out soon.

HLT (Patrick)

  • Slowly evolving.

OnLine (Markus)

  • Things are breaking in initialization since the changes to avoid cyclic dependencies in services initialization (patch #1757).
    Markus said that it should not be needed because services should not use other services during initialize (only get pointer to them), but Marco Cl. proposed the counter-example of a service that needs to be registered as IncidentListener (the service must get and use the IncidentSvc during initialize).
    Marco Cl. proposed to extend the API of ISvcLocator to allow clients to get services even if not yet initialized (avoid the check).

Release and Deployment (Hubert)

  • Gauss is being released. Hubert had to apply quick fixes.
  • Preparing the second version of the project LbScripts, to allow the deployment of the versions database by Marco Cl..
  • Working on a new setup script for LHCb login and local installation. The script will be one (per shell flavor), and will be able to set up the environment for AFS (CERN) and local installation. Later on it will be extended to support a shared area (for GRID).

Round Table

Marco Ca.
  • Architects Forum tomorrow. Discussion about next LCG configuration on the agenda. Atlas is asking to have HepMC2, but we cannot accept it.
  • Software Week in June: we should start thinking about it (tutorials?, etc)
It has been observed recently that the size of a ROOT file containing histograms grows a lot if we just add a directory level. Marco Ca. suggested to report the problem directly to the ROOT team (see post by Chris).

-- MarcoClemencic - 14 May 2008

Edit | Attach | Watch | Print version | History: r3 < r2 < r1 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r3 - 2010-06-11 - PeterJones
    • Cern Search Icon Cern Search
    • TWiki Search Icon TWiki Search
    • Google Search Icon Google Search

    LHCb All webs login

This site is powered by the TWiki collaboration platform Powered by PerlCopyright & 2008-2021 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
or Ideas, requests, problems regarding TWiki? use Discourse or Send feedback