Project

General

Profile

PMT - Troubleshooting » History » Version 3

Taritree Wongjirad, 05/11/2016 02:23 PM

1 1 Taritree Wongjirad
h1. PMT - Troubleshooting
2 1 Taritree Wongjirad
3 2 Taritree Wongjirad
We list here problems that come up during operations and the steps used to solve them.
4 1 Taritree Wongjirad
5 3 Taritree Wongjirad
High Rates:
6 3 Taritree Wongjirad
7 3 Taritree Wongjirad
The shifters are asked to monitor the following Monitor Lizard Plot:
8 3 Taritree Wongjirad
9 3 Taritree Wongjirad
(pic here)
10 3 Taritree Wongjirad
11 3 Taritree Wongjirad
12 3 Taritree Wongjirad
If one of the values goes above 256, the shifter should note which PMT it is in the e-log and then call the PMT expert.
13 3 Taritree Wongjirad
14 3 Taritree Wongjirad
PMT experts should have some tools ready to quickly swizzle the data  (To experts, if you don't have this code ready to go, please talk to Taritree about setting it up)
15 3 Taritree Wongjirad
16 3 Taritree Wongjirad
-- ratecheck fcl file that runs specalib analyzer (for pulse height and rates), the swtrigger (for both online and offline info), and the raw waveforms (for analysis and viewing)
17 3 Taritree Wongjirad
-- pylard can be used to look at the waveforms
18 3 Taritree Wongjirad
19 3 Taritree Wongjirad
Known issues (section to be updated):
20 3 Taritree Wongjirad
21 3 Taritree Wongjirad
-- high frequency noise info goes here. Solution was to switch HV channels
22 3 Taritree Wongjirad
23 3 Taritree Wongjirad
-- Long, bright bursts of PMT activity.  Source still under investigation.