- surrow's home page
- Posts
- 2024
- May (1)
- 2018
- 2017
- 2016
- 2015
- 2014
- October (3)
- September (1)
- August (1)
- July (1)
- June (3)
- May (4)
- April (6)
- March (4)
- February (5)
- January (2)
- 2013
- December (2)
- November (1)
- October (1)
- September (4)
- August (6)
- July (11)
- June (8)
- May (5)
- April (5)
- March (11)
- February (4)
- 2012
- December (3)
- November (3)
- October (3)
- September (3)
- August (3)
- July (10)
- June (9)
- May (5)
- April (4)
- March (4)
- February (7)
- January (4)
- 2011
- 2010
- December (2)
- November (4)
- August (2)
- July (3)
- June (6)
- May (4)
- April (4)
- March (8)
- February (6)
- January (4)
- 2009
- My blog
- Post new blog entry
- All blogs
FGT QA
Procedure: Look through various FGT specific QA histograms / slow control info. and report on a
regular basis in a standard format (Drupal)
When? QA will start with beginning of shift-crew operation of FGT
Who? Anybody from the FGT group
How? Sign up on doodle link / Report findings in standard format:
a) Morning: Owl data taking
b) Afternoon: Day data taking
c) Evening: Evening data taking
Write a daily summary and alert experts immediately once something unusual has been found!
Sources for now:
1) For the beginning: Are all channels alive which are supposed to be alive / More details will be added : J-Plots
2) Check online gas level : DB plots
3) Look through HV history and check if any channel was at one point zero or any abnormal HV ramping different from default ramp procedure: DB plots
4) Look through current history for any abnormal behavior : DB plots
- surrow's blog
- Login or register to post comments