| |
All partitions corresponding to this run have been processed completely, without any error. DST, ROOT tuples, filtered DST and the corresponding ROOT tuples have been generated and no inconsistency was found in the number of events. There was no error in the process or merging files |
| |
All partitions corresponding to this run have been processed completely, but there are some problems with the ROOT tuples corresponding to the filtered DST sample (either they haven't been generated or there are inconsistencies in the number of events or errors in the process of merging ROOT files.. The DST, ROOT tuples and the filtered DST are fine and no inconsistency was found in the number of events. |
| |
This run hasn't been processed with the current version of the D0 software and there is no job in the D0 farm queue. |
| |
Jobs for this run have been submitted to the D0 farm. |
| |
This run was processed only partially. The fraction of events processed at each step (DST: D0reco, ROOT: RecoAnalyze, recoS: filtered DST) is indicated in the respective column of the table. |
| |
The run appears to have been processed completely. However there are some inconsistencies in the number of events. Check the Consistency check column. |
| |
Used to signal a processing error. Click on the run number to see more details. |
| Consistency check |
PASS: The number of events in the output of each program of the reconstruction chain is consistent with the number of input events. FAIL: An inconsistency has been found between the number of input and output events (generally this indicates that one partition hasn't been completely processed). |
| Merging errors |
NONE: No errors found while merging ROOT tuples or filtered DST. YES: Errors founds in the merging of ROOT tuples or filtered DST. Usually this involves merging the ROOT tuple for an incomplete partition or assigning a file name which spans a non-processed partition. Click on the run number or on YES: to see more details. |