Revision as of 13:48, 9 February 2013

GlueX Offline Software Meeting
Wednesday, February 6, 2013
1:30 pm EST
JLab: CEBAF Center F326/327

Agenda

1. Announcements
   1. CCDB now the default
   2. New release of HDDS
   3. New release of sim-recon
2. Review of minutes from the last meeting: all
3. Collaboration Meeting
   1. Friday February 22, 2013
   2. 14:45 Session IVb (100) --- Offline Reconstruction - (Organizer: M. Ito)
4. Data Challenge Status
5. The Transition to GEANT4 (discussion).
6. Closer review of b1pi/single-track jobs
   1. Prototype custom email list
7. Action Item Review
   • Recently Resolved
   • Outstanding Items
8. Review of recent repository activity: all

Communication Information

Video Conferencing

• ESNet: 8542553
• SeeVogh:
  • Direct Meeting Link
  • Phone Bridge ID: 15 3270

Slides

Talks can be deposited in the directory /group/halld/www/halldweb1/html/talks/2013-1Q on the JLab CUE. This directory is accessible from the web at https://halldweb1.jlab.org/talks/2013-1Q/ .

Minutes

Present:

• CMU: Paul Mattione, Curtis Meyer
• FSU: Nathan Sparks
• IU: Matt Shepherd
• JLab: Mark Ito (chair), David Lawrence, Yi Qiang, Sascha Somov, Simon Taylor, Elliott Wolin, Beni Zihlmann

Announcements

1. CCDB is now required to build sim-recon.
2. There is a new release of HDDS, 1.5. This fixes some geometry issues and is needed to go along with the corresponding changes in the tracking code.
3. The new release of sim-recon, sim-recon-2013-01-11, uses CCDB 0.06 and HDDS 1.5. Note that as of this writing, the recent bug fix from David for the REST format is not part of the release.

There was some discussion about the meaning of the date in the sim-recon releases. Note that the date corresponds to the date when the tag was first made from the trunk and not the date that the release is announced. In general, not all of the code in a release will correspond to the date in the tag name. Changes may have to be introduced to fix bugs.

Collaboration Meeting

The schedule for the offline session has been added to the agenda on the wiki.

Friday February 22, 2013

• 14:45 Session IVb (150) --- Offline Reconstruction - (Organizer: M. Ito) Chair:
  • 14:45 (20) --- Overview and Data Challenge -- Mark Ito
  • 15:05 (20) --- CCDB -- Dmitry Romanov
  • 15:25 (20) --- Tracking -- Simon Taylor
  • 15:45 (20) --- TBD -- David Lawrence
• 16:05 Coffee (30)
  • 16:35 (20) --- Physics Analysis Tools -- Paul Mattione

Data Challenge Status

Not a lot has moved on analysis of data challenge data lately. Justin Stevens of MIT has been looking at them however. He expressed an interest in generating skims, to reduce processing time for selected channels. Paul is working on reconfiguring code in the REST plugin to facilitate skim creation.

The Transition to GEANT4 (discussion)

We reviewed the recent email discussion on the transition from GEANT3 to Geant4. In that discussion it was not unamimous that this is high priority. Points not raised in the emails:

• It should be possible to freeze G3 development for a time to allow Richard to work on a stable code base.
• Alternately, Richard could work on a branch, and changes to the trunk could be ported piecemeal, in a controlled fashion, to the branch if they occur.
• Richard has stated that there will be a lot of code re-use in the transition, so work done validating G3 code will not go completely to waste when validating G4 code.
• Discussion of this issue needs to involve Richard. Plans:
  1. Raise the issue informally with Richard at the collaboration meeting.
  2. Ask for a presentation on what is involved from Richard at a future offline meeting.

Closer review of b1pi/single-track jobs

At Beni's request, we discussed the problem of lack of monitoring of the results from the bi-weekly tests of the b1pi and single-track analyses. Recently there have been failures that have gone ignored.

• Beni suggested that we show recent results at this meeting as a standing agenda item.
• Mark showed a prototype system for a light-weight email list system that interested collaborators could subscribe to on an opt-in basis. The idea is to have multiple result-nofication email lists.

We will try both approaches.

Prototype custom email list

Review of recent repository activity