RECO Status Report - October, 2002

Status of releases

• p13
  • p13 is a part of the "Overall Goals for the Experiment"
  • p13.00.00 was built on schedule.
  • p13.01.00 is built and being tested.
  • p13.02.00 will start on October 29, 2002.
  • Status.
    • A status report was given to the CPB on October 30, 2002 (ppt, pdf).
  • Current performance.
  • Known problems.
  • New features coming.
• p12
  • RECO not certified for production use in this version.
  • Intended for development of TMB.
  • DO NOT use this version of RECO for any official studies.
• p11
  • Currently installed on farms: p11.13.00

Recent progress:

• p13.01.00 being installed on MC and data farms for testing.
• Successfully tested shifted calorimeter geometry in p13.

Major outstanding problems / issues:

• We have not yet deployed access to the detector calibration databases.
  • Issues:
    • Memory requirements - d0omCORBA is being improved.
    • Server reliability - not yet tested.
• 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