Page updated: April 13, 2002

Run II Reconstruction Program Status - Version p10

Status:
Certified
Latest version:
p10.15.01
Next release:
p11
Not yet scheduled
Version processing data:
p10.15.01
Version processing MC:
p10.15.01


Performance  Upcoming Features  Known Problems    History


Overview

Version p10.15.01 is the final p10 version and is currently being used to process collider and Monte Carlo data.

Details on official Run II DØ data sets is available from the farm production group.


Performance

The Object ID groups have studied the performance of p10 reconstruction, and have certified versions of physics object identification (electrons, muons, jets, missing Et, jet energy scale). Some overall statistics (speed, memory usage, etc.) for the reconstruction program are also available. Also, some standardized plots are available.


Upcoming patches, etc.


Known Problems

red dot Major error, yellow dot Annoying feature, blue dot Functionality to be added
green ball Scheduled for next release, blue dot Problem fixed.
(common = occurs within 100 events, rare = occurs within 1000 events)

Status Description Fixed in version
yellow dot RECO: Requires a large amount of memory to link - under investigation.  
yellow dot RECO: Additional memory leaks - under investigation.  
yellow dot RECO: Contents of chunks is poorly documented.  
blue dot RECO: If a run is missing from the run configuration database, reco will abort. This is by design, since reco needs to know the solenoid polarity to get the correct SMT Lorentz corrections and to reconstruct the correct charges. However, there is supposed to be a useful error message generated. A bug prevents the error message from appearing in the .out file. You can look at the run configuration database here. p10.15.00
blue dot RECO: Crashs when processing MC if no network connection to databases is available. p10.15.00
blue dot RECO: Can't read DSPACK files on Red Hat 7.1 systems using optimized build. p10.15.00
blue dot RECO: Crashs when processing files that contain events from many runs. p10.15.00
blue dot RECO: Errors in CFT and CPS electronics maps p10.15.00
blue dot RECO: Not every SMT ladder has a pedestal. Pedestal is required to use hits in tracking p10.15.00
blue dot RECO: Memory leak in cal_nada. p10.15.00
blue dot RECO_ANALYZE: vertex_analyze takes a lot of CPU time. p10.15.00
blue dot RECO_ANALYZE: Crashes on data containing more than 128 L3 bits. p10.14.01
blue dot RECO: Incorrect solenoid field polarity used for SMT Lorentz corrections p10.14.00
blue dot RECO: SMT Lorentz corrections not enabled p10.14.00
blue dot RECO: Nada not in dynamic killing mode. p10.14.00
blue dot RECO: Uses incorrect nominal beam position for post-shutdown data. p10.13.00
blue dot RECO_ANALYZE: Assertion failed: pqold->is_valid() p10.11.00
blue dot RECO_ANALYZE: crashes occur (creating a core file) at a moderate rate at the end of the job, after processing all events. The reco_analyze root tuple appears to be OK. ???
blue dot GTR assumes beam centered at (0,0) p10.08.00
blue dot Bug in d0omCORBA requires connection to network for RECO to run properly p10.08.00
blue dot RECO_ANALYZE: It is difficult to connect from an entry in the CH block to track information in the reco_analyze root tuple. p10.07.00
blue dot RECO: In p10.06.00, a parameter was incorrectly set in d0_prop.obs, resulting in a large loss in tracking efficiency. This problem is fixed in p10.07.00. p10.06.01
blue dot RECO_ANALYZE: It is very difficult to get information for all types of found tracks in the reco_analyze root tuple. p10.05.00
blue dot RECO_ANALYZE: GTRACK block only includes GTracks from the "230" chunk (SMT only) for real data. The MuoGTR block does contain some information about all found tracks (with PT > 1.5 GeV). p10.05.00 (use gtr_analyze blocks)
blue dot RECO: FPE in kinem:y at line return 0.5 * log ((E+pz+EPSILON)/(E-pz+EPSILON)); Error occurs in CalData when processing real data. (rare) p10.04.00
blue dot RECO: Problem processing data when PDT wire lengths were not downloaded to the front end. Requires new muon_rawdata. p10.04.00
blue dot RECO: Output event size very large. p10.04.00
blue dot RECO: topological vertexing algorithm uses incorrect GTracks p10.04.00
blue dot RECO_ANALYZE: crash in CPSanal::analyzeEvent at line slcmult[_cl3Dptr->at(i).vCluster()]++; (rare) p10.04.00
blue dot RECO_ANALYZE: crash in vertex_analyze when processing single particle MC files p10.04.00
blue dot RECO_ANALYZE: bcjet_analyze crashes in getLikeTags (common) p10.04.00
blue dot RECO: SimEventInfoChunk dropped - needed for history of magnetic field used in Geant generation p10.04.00
blue dot RECO_ANALYZE: bcjet_analyze likelihood block turned off due to problems - may be fixed in p10.01.00; under investigation. p10.04.00
blue dot RECO: Segment violation in EMClusFinder::make_EMCluster at line if(emiso && sem>-1) _matchedECL[_nmatch]=-(11+iofset)*charge; (rare) p10.03.00
blue dot RECO: memory leak in MuoSegmentChunk p10.03.00
blue dot RECO: cps_unpdata/rcp/mcm_unpdata.rcp flag PED_LO_GAIN should be 30 p10.03.00
blue dot RECO: Latest version of vkalman_util not installed in p10.02.00 p10.03.00
blue dot RECO: crash in vertexing for tracks with qoverpt = 0 (vertex_selalg, vkalman_util) (rare) p10.02.00
blue dot RECO: crash in MuoTrackReco at line for (int i=0; i < trackVector->size(); i++) delete (*trackVector)[i]; observed when processing p10 MC samples (rare) p10.02.00
blue dot RECO_ANALYZE: bcjet_analyze turned off due to bugs p10.02.00
blue dot RECO_ANALYZE: bcjet_analyze crashes in mutagUtilities::setJets - Linux only? (common) p10.02.00
blue dot RECO_ANALYZE: bcjet_analyze crashes in BlockMuon::accumulate (common) p10.02.00
blue dot RECO: Does not correctly handle CAL weights for events generated with p09.08.00. This causes all calorimeter-related objects (jets, electrons, etc.) to have very incorrect energies. p10.01.00
blue dot RECO: Incorrect calculation of ICD/MG fractions in jetreco. p10.01.00
blue dot RECO: bcjet reco turned off due to bugs. p10.01.00
blue dot RECO: ELoss correction overestimated in Muon::Track. p10.01.00
blue dot RECO: Kalman primary vertexing turned off inadvertently. p10.01.00
blue dot RECO: Farm scripts pick up incorrect rcp for p09 MC processing. p10.01.00
blue dot RECO: CPS unpacking was turned off (historical?). p10.01.00
blue dot RECO: Support for L3 trigger selection p10.01.00
blue dot RECO_ANALYZE: has incorrect vertex_analysis rcp for SAM version. p10.01.00
blue dot RECO_ANALYZE: bcjet_analyze crashes for real data p10.01.00
blue dot RECO_ANALYZE: jetanalyze min Et wrong. p10.01.00
blue dot RECO_ANALYZE: Include cps_analyze p10.01.00


History of Major New Features


Detailed history of changes in p10


This page maintained by Harry Melanson