- heppel's home page
- Posts
- 2021
- July (3)
- 2020
- February (1)
- 2019
- 2018
- 2017
- 2016
- December (2)
- November (2)
- October (3)
- September (2)
- August (1)
- July (3)
- June (5)
- May (8)
- April (4)
- March (1)
- February (2)
- January (2)
- 2015
- December (1)
- November (4)
- October (8)
- September (4)
- August (3)
- July (2)
- June (7)
- May (8)
- April (5)
- March (13)
- February (5)
- January (2)
- 2014
- December (1)
- November (2)
- September (1)
- June (3)
- May (2)
- April (1)
- March (3)
- February (2)
- January (1)
- 2013
- 2012
- 2011
- December (2)
- November (1)
- September (2)
- August (3)
- July (2)
- June (6)
- May (2)
- April (2)
- March (3)
- February (3)
- January (3)
- 2010
- December (1)
- November (2)
- September (2)
- August (1)
- July (4)
- June (3)
- May (2)
- April (1)
- March (1)
- February (2)
- January (1)
- 2009
- 2008
- My blog
- Post new blog entry
- All blogs
Run 12 Recalibration Update
Updated on Tue, 2016-05-31 23:15. Originally created by heppel on 2016-05-19 10:02.
The attached figures show from the plots
set078Bb_callpt.pdf, set095Ba_callpt.pdf, set108Bb_callpt.pdf, UpdateRun12.pdf
This showed that the prescaled lower threshold triggers, as tagged with the low 64 bits of the trigger, seem to make sense. The high threshold triggers, tagged with the upper 64 bits do not. However, the dsm outputs (lastdsm[5] mask do seem to make sense)
Triggers are plotted using the low 64 bits (low threshold triggers) as before but the high threshold triggers (take all) are selected with the lastdsm[5]) bits. These plots are attached, corresponding to runs around day 94 and day 108 of run 12.
»
- heppel's blog
- Login or register to post comments