UMN CDMS Wiki archive
start › cdms › k100 › run_diary › 20171228

2017/12/28 (Thursday)

Previous Day

Setup: DIB1/3/4 → SL 27/19/20 → 3.2 MHz filters → cables 2,1,3 → HV board inputs 1,3,2 → HV board outputs 1,2 → DCRC55(1)/50(3). DCRC4 → HV power supply.
0930 Tower/MC/Coldplate = 21.5/25.0/150 mK, Still = 1.4 K / 0.100 mbar, G1/G2 = 208/178 mbar, 1K Pot = 1.63 K / 28 mbar, MB = 40.0%
0935 Fill LN2 cold trap bath
1247 Start LHe transfer (MB = 35.1%)
1326 End LHe transfer (MB = 91.6%)
We'll try triggering on multiple channels. For this test we'll trigger on two channels in the same DCRC.
oops - looks like I actually set two triggering channels on DCRC1 and one on DCRC3. So this is actually a test of triggering on multiple channels across DCRCs.
1530 Start sequence of 12 30-minute background data series at HV = 70V, Driver Gains = 2x, QET biases = 480/360/440/480/380/490 uA, Front-End Gains = 10/5 on DCRC1/3, 1000 initial randoms, trigger on DCRC1pA/DCRC1pB/DCRC3pC thresholds 8/11/11, flashing then waiting 30min after each series, using modified triggerfe, using sequencer script DataLoop_70V_30min_groundflash_30min
Looking at that data it seems that we get retriggering, but it's not consecutive events in the read data stream. We kinda know this from the 5Q device we tested recently - triggers from one DCRC come in clumps in the data stream. We should try triggering on two channels in the same DCRC and verify that we don't get retriggering.
1619 Fill LN2 cold trap full.
1805 Raise D.O. on DCRC3pB from -0.4 to -0.2

Next Day