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

2016/12/14 (Wednesday)

Previous Day

Setup: DIB1/3/4 → 3.2 MHz filters → cables 1,2,3 → HV board inputs 1,3,2 → HV board outputs 1,2 → DCRC55(1)/50(3)
NaI-coincident data taken overnight, HV=60V. The last series in the sequence ended at 7:25 (10 hours of data starting at 21:25 last night). BatViewer shows that all 5 channels are still good, nothing railed, reasonable pulse shapes.
1026 Do a 30 minute bake 30s on / 5s off, prepare for another 3 hours of data by pre-biasing to 75V for 5 min, this will end just after the PuBe source arrives
1140 Tower/MC/Coldplate = 33.3/34.5/203 mK, Still = 1.03 K / 110 μbar, G1/G2 = 192/171 mbar, 1K Pot = 1.68 K / 22 mbar. MB = 66.3%. Boil off rate: faster than slow mode.
1345 Fill LN2 cold trap full
1250 do a 6 minute bake
1354 PuBe source in parafin container next to fridge, outside of shielding, will return at 16:15
1400 overbias to 115V wait 5 minutes
1415 see pulses, modify source position to decrease rate in ZIP do ZAP
1423 source rate still a bit high – 130Hz
1425 moved it back about a meter and got to 90Hz
1615 removed PuBe source, Andy gave us the key (on Matt's desk) we can use it anytime between now and Dec 31st 8am-4pm, no weekends, in the paraffin case only
1627 ramp voltage down and do a flash, follow with bkgnd running in same conditions as above
1659 the rate post-PuBe source seems to be around 36 Hz, so we didn't pick up a lot of activation from this
1702 note DCRC1 triggering is enabled in all the data from today and yesterday, I was worried about this because in the past DCRC1 has produced spurious triggers, but I just checked with the “rt” command to the telnet session and it is apparently not issuing spurious triggers, maybe it's OK now. DCRC3 is also not producing spurious triggers

Next Day