Difference: CoreSoftwareMeetingMinutes20080903 ( vs. 1)

Revision 12008-09-04 - MarcoClemencic

Line: 1 to 1
Added:
>
>
META TOPICPARENT name="CoreSoftwareMeetingMinutes"

LHCb Core Software Meeting

Date and Location

03 Sep 2008
14:00 - 15:30
CERN (2-R-030)

Attendees

Gloria, Hubert, Joel, Karol, Marco Ca., Marco Cl. (minutes), Morten, Patrick, Stefan
<!--

Apologies

-->

Subjects

Specific Topics

LCG-AA nighty build configuration

Morten, SPI summer student, created a web based configuration tool for the LCG nightly build system. Since we are using the same system for our nightly builds and contributing to it, we can use the configuration tool too.

In his presentation, Morten didn't spend time on the technical implementation details (described in the slides) focusing on a live demonstration.

The configuration tool looks very good. It features only some minor bugs observed during the demo. The main comments raised during the presentation are:

  • the version of a project relies on CVS tags or a list of customizable strings (regular expressions) for the validation, we think it would be better to have a "smarter" validation where we specify the version number instead of strings like "LHCB_v25r0"
    Morten designed the system such the the validation is done in plugins (currently cvs and svn are supported), so we can extend the cvs plugin to understand our policy for the version numbers.
  • the way permissions are granted to users doesn't look optimal (permission on projects or on slots with the project inside). The best would be to have permission with granularity on projects, slots and combination of both (e.g. user A can modify all the occurrences of Boole in any slot, user B can modify anything in the slot lhcb1 but not in the others, user C can only modify the configuration of Hlt in the slot lhcb2). Such a system of permissions will require quite some work, which Morten cannot do because he is going to leave soon. Anyway the code is available and somebody else can change it.

Round Table

Marco Ca.
Some problems with the conditions database
  • we need urgently the changes by Jan Amoraal, needed by the new code (see bug #40313)
  • the default configuration using ONLINE snapshots is guessing the latest one from the current date, and the initial event time (used during initialization) is the current time. This creates problems on the first day of the month, when the snapshot is not yet produced. Moreover, the snapshots become available only with new releases of SQLDDDB. We agreed to fix the set of available ONLINE snapshots in the options released with SQLDDDB.
Hubert
Modified SetupProject to be able to find externals when using the local+shared areas with install_project.py
Patrick
  • SetupProject modifies CMTPROJECTPATH and all the subsequent calls will rely on the new value (i.e. if you ask once for DEV, you will always get it unless you unset CMTPROJECTPATH yourself).
    Marco Cl. says that the behavior was defined before the inclusion of the options --dev and --dev-dir, when the only way to get a special CMTPROJECTPATH was to set it by hand. We agreed to modify the default behavior of SetupProject to reset CMTPROJECTPATH unless a specific command line option is used (it will also fix some ordering issue between user release area and DEV). Another suggestion is to have a shortcut for the path for the nightlies (e.g. --nightly lhcb1 Mon, a la --dev).
  • Released Hlt/Moore without re-releasing LHCb (to quickly fix something for the PIT).
  • During the next software week, we are going to advertise to use uDST for user analysis. This will bound the user analysis to the version of ROOT used by Gaudi...

-- MarcoClemencic - 04 Sep 2008

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