Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

AFIT-107: new RCT bad flags for FT0 #13698

Open
wants to merge 2 commits into
base: dev
Choose a base branch
from
+11 −0
Open

AFIT-107: new RCT bad flags for FT0 #13698

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
aaee758
AFIT-107: new RCT bad flags for FT0
afurs Nov 15, 2024
43099b7
AFIT-107: review
afurs Nov 18, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions DataFormats/QualityControl/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -76,6 +76,12 @@ This section details the currently available Flag Types and provides a brief exp
* **Bad Electron PID:** analyses relying on correct electron identification should not use this data.
* **Bad Photon Calorimetry:** analyses relying on correct photon calorimetry should not use this data.
* **Bad EMCalorimetry:** analyses relying on correct electromagnetic calorimetry should not use this data.
* **Bad Data Consistency:** data is inconsistent. FT0's example: some modules haven't sent data, BC async among modules(modules sent data with shifted BC), etc.
* **Bad HW Settings:** Bad hardware settings, which corrupted data. FT0's example: phase time shift at some channels, time peak is close to gate borders, or even out of gate.
* **Bad Reco Settings:** Bad reconstruction settings. FT0's example: bad DeadChannelMap(healthy channels ignored for reco, or vice versa); incorrectly configured time filtering logic
* **Bad FT0 Time Offset Calibration:** Bad FT0 time offset calibration, collected during online. Can be fixed. Causes bad accuracy in FT0's timeA and timeC at AOD
* **Bad FT0 Time Slewing Calibration:** Bad FT0 time slewing calibration, collected during offline. Can be fixed. Causes the same as for FT0's bad time offset calibration.

* **Unknown:** the exact impact of an issue on the data is unclear, but it's likely bad.
Treat data with this flag with caution until further investigation.
* **Unknown Quality:** the quality of data could not be determined definitively.
Expand Down
5 changes: 5 additions & 0 deletions DataFormats/QualityControl/etc/flagTypes.csv
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -12,3 +12,8 @@
12,"BadEMCalorimetry","Bad EM Calorimetry",1,0
13,"BadPhotonCalorimetry","Bad Photon Calorimetry",1,0
14,"Unknown","Unknown",1,0
15,"BadDataConsistency","Bad data consistency",1,0
16,"BadHWSettings","Bad hardware settings",1,0
17,"BadRecoSettings","Bad reconstruction settings",1,0
18,"BadFT0TimeOffsetCalibration","Bad FT0 time offset calibration",1,0
19,"BadFT0TimeSlewingCalibration","Bad FT0 time slewing calibration",1,0
Loading