Present: Heather, Ian, Joanne, Leon, Karl, Riccardo, Richard, Thomas, Toby, Traudl
Core status: (Toby) See the Core status page with an updated diagram and comments/updates on several issues. Follow the Demonstration link to see the job options file and some output (event display, n-tuples, histogram) from a working simulation/recon chain which could be used for the PDR run. However this chain uses AoRecon rather than CalRecon/TkrRecon. There was some discussion of what it would take to get the latter chain working. It hinges on getting some form of the geometry to the right place. detModel won' t be ready in time for the PDR, but there are other possibilities. These needs to be discussed with Cal and Tracker people.
The executive decision on container class naming has been made: we'll be using a suffix of Col. typedefs will be used where helpful and appropriate.
Balloon issues:
Heather raised the issue of common geometry input for the various balloon projects engaging various people. The best we can expect (and it should be doable) is to get everyone except balloon G4 simulation folk to use a common input, probably a file of the form of instrument.xml.
Leon mentioned that the current G4 geometry for the Tracker does not include the glue thickness, resulting in an incorrect offset for other parts of the detector. This should be resolved by discussions between the two groups (G4 balloon simulation and Tracker).
Richard mentioned that Eduardo is taking part in the definition of analysis tools for the balloon flight, a very positive development.
Data formats: Heather is still awaiting a quasi-real event data file from JJ, who is in turn held up by lack of access to various electronics components. It would also be good to pin down the housekeeping data format.
Root versions: Should we be moving to Root 3? Traudl believes that Atlas is using it, and they're also using Gaudi, which implies it should be feasible.
Generic XML geometry status: (Joanne, Riccardo) See this week's geoStatus page. Riccardo and Dario have a test program which implements a good percentage of the model. See their description of this work and some output. Other topics mentioned were ACD geometry for flight.xml (at least half done) and identifiers/identifier dictionary.
PDR requirements documents: (Richard) They are beginning to trickle in. We need to learn how to make distinctions between hard requirements ("must"), and goals, desired properties, etc. Comments are solicited on this (Powerpoint) dependency graph among the various components with requirements documents.
PDR software schedule: When do we need to freeze the software? Toby pointed out that reconstruction need not be ready at the same time as simulation; Richard believes it can't lag by much, though.
Mini-core meeting: (Richard) Traditionally they have been held between Software weeks. Next Software Week will probably be in June. Points of information: Ian goes back to Canada in 3 weeks; Thomas leaves in April ([ed: eek!]. How about a mini-core meeting the second week in April?
J. Bogart Last Modified: 06/01/2010 15:47