RECO Status Report - November, 2002
| |
Page updated November 8,
2002 |
Status of releases
Recent progress:
- p13.02.00 began processing data on Tuesday, November 5, 2002.
- p13.02.00 RECO Monte Carlo certification samples have been
generated.
Major outstanding problems /
issues:
- There are a few production related problems with p13.02.00 RECO:
- Data farms report approximately 10% of files crash. Two sources
have been found, and fixes are scheduled for p13.03.00 (November 12,
2002).
- MC farms and data farms report occasional "infinite loops". One
source has been found, and a fix is scheduled for p13.03.00.
- The Monte Carlo muon geometry installed in p12 (and also in p13) was
changed with the intent to be the surveyed geometry. p13 RECO was
modified to support this geometry. Unfortunately, an error was made in the
d0gstar geometry such that it is not correct. Corrections to both d0gstar and
RECO geometries are required.
- The solenoid field is shifted in RECO by 1cm from it's nominal
position. Additional evidence supports that the field is in the wrong place for
data reconstruction. A
proposal
to fix this in p13.04.00 is under consideration.
- We have not yet deployed access to the detector calibration
databases.
- Issues needing testing:
- Memory requirements.
- Server reliability.
- There is a critical need to develop an Event based Error
chunk, that can keep track of things like fatal unpacking errors. This
information also needs to be propogated to the TMB. This is one of the projects
previously advertised.
Ongoing projects:
- Calorimeter - A task force is studying
the issue of the calorimeter zero-suppression threshold (online, Level 3 and
offline).
- Investigation into physical dependences of packages has started, with
the goal of reducing the memory required to link an analysis executable.
- Discussions to make more direct connection between TMB and TMB Tree
objects is underway. Proposal to ID / Physics groups has been sent.
- RECO Monitoring
tasks - Currently nine people have volunteered and are working on the two
advertised
RECO monitoring projects, however the level of effort has to date been rather
low. There are many additional aspects of these projects that need
volunteers.
- Chunk documentation -
Currently three people have volunteered and others are participating, however
the convergence rate is rather slow. More people are needed.
- An effort is underway to reduce the memory required for RCP (by about
80 MB) and the time required to load (from several minutes to tens of seconds).
Version one deployed in t02.38.00.
This page maintained by
Harry Melanson