- genevb's home page
- Posts
- 2024
- 2023
- 2022
- September (1)
- 2021
- 2020
- 2019
- December (1)
- October (4)
- September (2)
- August (6)
- July (1)
- June (2)
- May (4)
- April (2)
- March (3)
- February (3)
- 2018
- 2017
- December (1)
- October (3)
- September (1)
- August (1)
- July (2)
- June (2)
- April (2)
- March (2)
- February (1)
- 2016
- November (2)
- September (1)
- August (2)
- July (1)
- June (2)
- May (2)
- April (1)
- March (5)
- February (2)
- January (1)
- 2015
- December (1)
- October (1)
- September (2)
- June (1)
- May (2)
- April (2)
- March (3)
- February (1)
- January (3)
- 2014
- December (2)
- October (2)
- September (2)
- August (3)
- July (2)
- June (2)
- May (2)
- April (9)
- March (2)
- February (2)
- January (1)
- 2013
- December (5)
- October (3)
- September (3)
- August (1)
- July (1)
- May (4)
- April (4)
- March (7)
- February (1)
- January (2)
- 2012
- December (2)
- November (6)
- October (2)
- September (3)
- August (7)
- July (2)
- June (1)
- May (3)
- April (1)
- March (2)
- February (1)
- 2011
- November (1)
- October (1)
- September (4)
- August (2)
- July (4)
- June (3)
- May (4)
- April (9)
- March (5)
- February (6)
- January (3)
- 2010
- December (3)
- November (6)
- October (3)
- September (1)
- August (5)
- July (1)
- June (4)
- May (1)
- April (2)
- March (2)
- February (4)
- January (2)
- 2009
- November (1)
- October (2)
- September (6)
- August (4)
- July (4)
- June (3)
- May (5)
- April (5)
- March (3)
- February (1)
- 2008
- 2005
- October (1)
- My blog
- Post new blog entry
- All blogs
Anomalous Run 18 AuAu27 data
Updated on Thu, 2019-05-02 01:29. Originally created by genevb on 2019-05-01 14:00.
Following up on this post: Big abort gap cleaning charge
A reminder that this is the anomaly seen in run 19132076 that Ben found during his calibration work of sDCA vs time [sec]:
There are plots of DCA vs. event number within the file (not exactly the same as time, but a reasonable proxy) from various runs during the first half of Run 18 AuAu27 data-taking:
More to come.
-Gene
A reminder that this is the anomaly seen in run 19132076 that Ben found during his calibration work of sDCA vs time [sec]:
There are plots of DCA vs. event number within the file (not exactly the same as time, but a reasonable proxy) from various runs during the first half of Run 18 AuAu27 data-taking:
run | Example of anomaly sDCA vs. event in file |
DAQ metadata event size vs. time [sec] |
---|---|---|
Category I: reasonable correlation with DAQ metadata | ||
19130071 | ||
19131046 | ||
19133056 | ||
19134030 | ||
19135004 | ||
19141049 | ||
Category II: spikes not seen in DAQ metadata | ||
19130078 | ||
19130085 | ||
19131004 | ||
19131007 | ||
19131015 | ||
19131020 | ||
19131026 | ||
19131027 | ||
19132013 | ||
19132026 | ||
19132044 | ||
19132075 | ||
19132076 | ||
19132079 | ||
19132082 | ||
19133028 | ||
19133043 | ||
19133055 | ||
19134046 | ||
19135003 | ||
19135017 | ||
19135022 | ||
19139038 | ||
19140015 | ||
Category III: other anomalies not seen in DAQ metadata | ||
19135029 | ||
19136046 | ||
19142007 | ||
19142008 |
More to come.
-Gene
»
- genevb's blog
- Login or register to post comments