RECO Status Report - Feb. 2002

The current production version of RECO that is certified for processing real data is p10.14.01. It was installed on the farms on Feb. 12, 2002 and is currently being used to reconstruct incoming data and to reprocess the "Winter, 2002" data set. The previously used version was p10.11.00.

Official Monte Carlo production is currently using p10.11.00. Later versions contain a bug that prevents RECO from being used on farm nodes that do not have an external network connection. This bug will be fixed in p10.15.00 (see below).

p10.14.xx contains several major steps forward for processing real data as compared to p10.11.00 (see below). Probably the most significant are related to track reconstruction. For the first time, we have a chance of finding "believable" CFT tracks in post-shutdown data. In addition, the quality of SMT tracks has improved. Having said that, it must be stressed that there are still many issues to study / resolve. As an example, p10.15.00 will contain another fix to the CFT electronics readout map, which results in 2 more CFT tracks per event (and more global tracks) (!). Also, a complete default set of SMT thresholds will be included, yielding 2 more SMT tracks per event (!). (!!!) Upcoming studies will include looking at CFT stereo layers, SMT internal alignment, CFT internal alignment, SMT calibration, CFT calibration, etc. etc. etc. Users of tracks (everyone?) must understand that we have only begun to explore our new tracking system. All are encouraged to participate directly (and with dedicated effort) in the detector groups, the tracking group, the vertexing group and/or the Tracking Task Force. There is still a lot of fundamental work to be done before we have a chance for believable physics results.

Other important features of p10.14.00 as compared to p10.11.00 include emreco H-matrices tuned using plate MC (and no preshower, as currently required for real data), a fix for hardwired PDT resolutions resulting in improved central muon reconstruction, and the enabling of the dynamic mode in NADA resulting in significantly improved hot cell killing. The previous comment about "a lot of fundamental work" should be understood to apply to all of the components of OUR reconstruction program. All algorithms and object id groups are still understaffed and desperately need collaboration involvement.

We plan to build p10.15.00 during the week of Feb. 18. The list of changes is included below. It will have yet more significant improvements for both data and Monte Carlo production.

At this time, reco developers are (should be) working on making the p11 release ready for use by the collaboration. There are several steps involved. All improvements that were developed for p10 must be included and integrated with any new p11 features. These must be tested, and the results certified before p11 can be used. One important new functionality in p11 will be access to the detector calibration databases for real data processing. This will require new coordination between detector groups, shifters, database experts, software developers and farm groups. Another major new feature in p11 will be the first version of the thumbnail. Since this is the ultimate "physics analysis" interface to the data, it is very important.

A note to users: Although there are p11 releases currently being built, users should understand that neither reco nor reco_analyze have been certified for use. An announcement will be made when p11 is generally useful for "reco".

Because of the huge amount of effort expended to make p10 useful for real data, we are significantly behind our p11 schedule. I hope to have a revised, realistic schedule within two weeks. It is obvious that we must converge as quickly as possible on p11, in order to get back on track with our strategy for quarterly releases. I plan on developing a p12 reco schedule in the next two weeks as well. As an aside, I would like to use this opportunity to explicitly thank ALL of the members of the Tracking Task Force (TTF), who have worked extremely hard to understand the data coming out of our new tracking detectors. We have had several groups that have expended heroic effort to give OUR experiment the chance to succeed (ones that come to my mind are the people who actually BUILT the silicon or fiber tracker detectors, or the crew trying to get all of the AFE boards installed, or the DAQ "guys" giving us REAL rate - others are probably obvious to you so please include them in "my" list). But let me make two distinctions. First, I believe the TTF is the first group that had to cross over all "organizational boundaries" in the experiment. Problems related to hardware, electronics, DAQ, online, calibration, software, etc. etc. etc. were not allowed to be "blamed" on someone else. They simply had to be solved (and in some significant cases, WERE SOLVED). Secondly, the members of the TTF had to watch as others of the collaboration worked on "first physics results for Moriond", and listen to complaints such as "NO ONE understands how to match tracks with the calorimeter" or some other comment that reflected relatively little understanding of the "current" understanding of the "detector". I admire the devotion of these individuals, and I'm extremely proud to be their collaborators. When all is said and done, we stand on the shoulders of these people.

Additional current reco related activities include:

1) The latest version of reco has a significant number of memory leaks. Although they do not appear to significantly impact current production, an effort is underway to understand and fix them. Some of the leaks are straight forward to solve, and will be fixed in p10. Others will require substantial rework of existing code, and will be fixed in p11 or p12. The FNAL CD C++ experts are being consulted on a case-by-case basis.

2) Linking the reconstruction executable requires a significant amount of memory. The CD C++ experts are being consulted to see if this can be reduced. Improvements may be generally applicable to all D0 executables.

More details about the following are available on the reco status page.

Changes to be included in p10.15.00

• Yet another fix to the CFT / CPS electronics map (2 more CFT tracks per event + more global tracks).
• Default SMT pedestals for all channels (2 more SMT tracks per event).
• Fix d0omCORBA allowing reco to process MC on a node with no external network connection
• Fix DSPACK allowing reading files on RH 7.1 (i.e. clued0)
• Fix DSPACK to allowing processing files with events from many runs
• Fix memory leak in cal_nada
• Fix bug in cal weights related to mass-less gaps (goes along with a d0gstar patch)
• Fix CFT clustering code to automatically select thresholds for MC or data (fix cures a problem with d0sim)

Major p10.14.xx upgrades since p10.11.00

• For the first time, we have a CFT electronics map that is "more or less" correct.
• In addition, fiber by fiber CFT thresholds taken from online calibration runs are being used (via flat files). These reduce the occupancy to reasonable values, reducing the number of fake CFT tracks.
• The SMT geometry uses the survey alignment constants, and has a correction for the relative SMT N/S barrel alignment.
• The SMT Lorentz corrections are enabled, and use the run configuration database to get the correct field polarity.
• Post-shutdown SMT pedestals are being used.
• The tracking group has supplied new paths which extrapolate SMT tracks into the CFT, allowing for misses.
• The correct nominal beam position for post-shutdown data has been included in track reconstruction.
• Remove hardwired PDT hit resolution, increasing number of central muons with matched A and BC segments
• New H-matrices tuned with plate MC (no preshower).