Project

General

Profile

Data Quality in our Productions

We are revising out approach to Data Quality Bits in R005. Instead of setting bits to 1 for "Good" or "Test Passed", we are switching it to 0. This has the added benefit that analyzers that don't need to know too much about the individual bits meanings can just query for dataQuality = 0.

When In Doubt, add "WHERE dataQuality = 0"!

Spill

Nth bit Category Description Roadset 57 & 59 Roadset 61 Roadset 62 Roadset 67 Roadset 70
0 Beam Duty Factor [15,60] [15,60] [10, 60] [10, 60] [10, 60]
1 Beam G2SEM [2e12, 1e13] [2e12, 1e13] [2e12, 1e13] [2e12, 1e13] [2e12, 1e13]
2 Beam QIEsum [4e10, 1e12] [4e10, 1e12] [4e10, 1e12] [4e10, 1e12] [4e10, 1e12]
3 Beam FMAG < 1000A
4 Beam KMAG < 1000A
5 Beam
6 Beam
7 Beam
8 Target Spill.TargetPos !=
Target.TargetPos
9 Target TargetPos between
1 and 7
10 Target
11 Target
12 Target
13 Target
14 Target
15 Target
16 DAQ / Trigger Inhibit [4e9, 1e11] [4e9, 1e11] [4e9, 2e11] [4e9, 2e11] [4e9, 2e11]
17 DAQ / Trigger Busy [4e9, 1e11] [4e9, 1e11] [4e9, 1e11] [4e9, 1e11] [4e9, 1e11]
18 DAQ / Trigger AcceptedFPGA1 [1e3, 8e3] [1e3, 12e3] [1e2, 6e3] [1e2, 6e3] [1e2, 6e3]
19 DAQ / Trigger AfterInhFPGA1 [1e3, 3e4] [1e3, 1e6] [1e2, 1e4] [1e2, 1e4] [1e2, 1e4]
20 DAQ / Trigger Accepted/AfterInh [0.2, 0.9] [0.0, 0.9] [0.2, 1.05] [0.2, 1.05] [0.2, 1.05]
21 DAQ / Trigger TSGo [1e3, 8e3] [1e3, 12e3] [1e2, 6e3] [1e2, 6e3] [1e2, 6e3]
22 DAQ / Trigger BOS and EOS exist
23 DAQ / Trigger MATRIX1 Settings
24 Decoding Duplicate values
25 Decoding Missing values
26 Decoding Problematic spills ([303215, 3109547],
[371870, 3765331],
[378366, 3793331])
([394308, 4095403],
[394287, 4145556],
[416207, 4241802])
[526201,5263644],
[581369,5824605]
27 Decoding
28 Decoding
29 Decoding
30 Decoding
31 Decoding

Please do note that spill range [482574, 484924] corresponds to part of Roadset 62 with the FMag/KMag polarity flipped, but will not be marked in any way as 'bad' in the spill dataQuality. This needs to be treated specially in physics analysis.

Event

Nth bit Description Comment
0 High Occupancy Check Not Implemented
1 v1495 Readout Problem 0xD1AD issue
2 QIE Readout Problem
3 No in-time RF TriggerHit No possible RF-based timing

Hit

Nth bit Description Comment
0 In-time Check
1 Hodoscope Masked Taiwan and v1495 hodos used for masking prior to runID 11795, only v1495 hodos used from runID 11795 on.
2 Trigger Road Masked Trigger roads reconstructed from in-time v1495 hodo hits only.
3 After-Pulse Check Only the first in-time hit per element per event passes this check.

1 Trigger timing shift ranges

2 Manual target rotation. Can be set to 0 after 'fixing' it.

3 Trigger timing not final, target rotation not even, G2SEM & duty factor low

4 Bad QIE inhibit timing

5 KMag off

6 LD2 flask filled with LH2. See SeaQuest-DocDB !#1499

7 QIE problems in 8% of events and the QIESum See SeaQuest-DocDB !#1378