Core Minutes 4/20/2004
Present: Pol d'Avezac, Joanne Bogart, Toby Burnett,
Jim Chiang, Seth Digel, Richard Dubois, Dan Flath, Berrie Giebels, Navid
Golpayegani, Traudl Hansl-Kozanecka, Heather Kelly, Michael Kuss, Matt Langston,
Julie McEnery, Pat Nolan, James Peachey, Dirk Petry, Sean Robinson, Bob
Schaefer,
Alex Schlessinger, Tom Stephens,
Tracy Usher
-
Manager's meeting: (Richard) One piece
of news to come out of it is probable additional one month delay before first
calorimeter module appears, making it late September rather than August.
However there still is some sentiment within the Cal group that some way must
be found to stick with August.
-
Core issues and status: (Toby) See
Toby's
run-down of issues of interest
here.
They were discussed at length.
- JIRA (bug-tracking): (Richard) After
generally favorable reactions to Tony Johnson's demo last week, we have
decided to go with JIRA.The SLAC Computer Center has agreed to by the
Enterprise edition, to be used not only by us but also by FreeHep (Tony
Johnson and associates) and LCD. Tony will probably act as chief admin. It is
likely that Flight Software will also be interested.Once it has been obtained
and installed, we'll have to do some configuration before it is usable, but as
soon as it is, we should start using it!
- VCC 7.0: There were no objections to
dumping it in favor of 7.1, but some institutions (Goddard? SSC?) may
need a little time to make the switch. We hope a month grace period will be
enough.
- New technology: (Richard) Matt has
been investigating various options. The hope is that several candidates,
including System Tests, Pipeline, and Release Manager, will be able to share
various components. Matt will be doing a walk-through of what he's found on
Thursday afternoon.
- Release Manager: Given that
Release Manager as it stands now may be largely thrown away (see previous
item), it is hard to know how much work to put into, e.g., the Windows build
or multiple Linux builds. However Alex is willing to entertain requests.
Julie asked about a gcc 3.3 build (3.3 is used by Fedora but not Enterprise).
The purpose of these builds would be only to make visible to developers
compile errors with the more stringent 3.3. If disk space is an issue, all but
the most recent such build could be deleted. Traudl would like to see
optimized builds. See Joanne's
old proposal (slightly amended in light of experience) on the subject.
- Install area: (Traudl) This is now
well-enough understood that we can get started on the migration. For the
bottom line, see her
migration page; for explanations and other background material, see this
overview page.
Most steps listed in the table can be done in parallel. In particular,
the cleanup of requirements files can start immediately. The first step will be to install the latest CMT (v1r16) for use at SLAC; Alex
agreed to take care of this. Would it be possible to do for now LATEST builds,
and only LATEST builds with v1r16? Alex believes so.CMT v1r16 shoudlbe
backward compatible; Traudl had no problems using it with GlastRelease. Two
small adaptions for Glast are needed, related to the NFS disk problem.
In order
to make full use of multiple install areas (not so exotic as it might sound,
since each entry in a CMTPATH corresponds to a separate install area), we'll
need to upgrade to Gaudi v14r0 or later. Earlier Gaudi versions will not
search in more than one location for job options.
Traudl suggests we make a separate job options-only package, rather than
keeping standard options files in the Gleam package. (Heather) Why? And
what about EngineeringModel? Should it also have a parallel job options
package? (Traudl) There are two reasons for the separate job options
package: it will simplify the install area migration, and it will aid in
avoiding circular dependencies, such as we now have when a test program refers
to Gleam job options.
At least one other issue remains to be resolved: what to do about the xml
file hierarchy in xmlGeoDbs. The normal install area expectation is that data
files are stored in a single level.
Richard pointed out that potentially destablizing changes, like upgrading
CMT and Gaudi, should be well behind us before the end of May, the Flight
Integration deadline.
- GlastRelease: The new tag, v4r2, looks
OK. all_gamma runs are about ready to go.
- Science Tools: (Jim, James) Just about
everything (Likelihood, observationSim,...) has now been tipified;
meanwhile tip
itself has picked up a lot of functionality;
more is on the way.
- InstallAnywhere: (Pat) He's been investigating
this product for packaging and installing
our software. It works on Windows and Linux platforms, among others.
-
Flight Integration: The
weekly run-down:
- EBF/LDF news: (Heather) She's finishing off ACD data handling.
- OPUS: (Dan) He's rewriting some stored procedures, adding some
new ones. Student is working on the Web front-end. On schedule.
- Calibration database interface: (Joanne, Marco, Riccardo)
Believed to be on track for end of May or earlier release.
- Diagnostic access to calibration data: (Joanne) Something which
should meet Xin's requirements has been committed and tagged; no news yet on
whether he's tried it.
- ICQ central: (Pat) He's maintaining a
list of
collaborator ICQ numbers. It's in the Stanford protected area; you need a
password to view it. Your number will be automatically added to the list if
you enter it into the Stanford GLAST personal information database.
- Document effect of MC pruning options (Riccardo) (8/5/2003) It's
documented in the code; Tracy will look into putting the information in a
more accessible place. (9/2/2003)
- Write up, and perhaps present at a future meeting, hints on debugging.
(02/18/03) Some combination of Toby and Tracy will provide
something for Windows.(7/22/03)
- Overhaul documentation altogether by about November (Heather and ??) (9/2/2003)
In progress; not yet done (01/13/04)
- Resolve calibration/timestamp issue. (11/20/02) Online folk have not yet thought about
putting timestamp information into EM data, but, thanks to Richard's
inquiry, may now do so. (2/25/03) We can probably live without a realistic
system for EM, but we will put it on the agenda for the DC1
workshop.(5/6/03) At the DC1 Workshop Steve Ritz promised to find an
authoritative reference for timestamp format and pass it on. (7/17/03) Now
that events have "real" timestamps, Joanne needs to reassess
situation with Calibration (9/2/2003) Timestamp exists in EM data. Needs to
be fetched by Calibration (1/13/04)
Put on hold until formats settle down. (3/16/04)
J. Bogart Last Modified:
01-Jun-2010 15:45:03 -0700