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

2021/02/24 (Wednesday)

Previous Day

  • Lab in-person: Derek
  • Virtual partner: Matt
Status Run 74 in progress.
Setup: DIB1/2+acc → SL 41/43 → 3.2 MHz filters → cables 2/3 → nothing/motor_board+HV_board → DCRC50(3)/55(1). No lead/poly shield.
1400 Derek Enters Lab
1403 Tower/MC/Coldplate = 106/31.9/190 mK, Still = 1.49 K / 0.130 mbar / 0 mW, G1/G2= 173/159 mbar, 1K Pot = 1.68 K / 36±2 mbar.
1405 MB = 54.3%
1405 Fill LN2 cold trap bath.
We have been having some trouble with the data. Charge channel baselines are wandering around and occasionally railing, which seems to be screwing up the noise PSD algorithm. Also phonon channels are occasionally showing some non-zero values which may also interfere with the event-selection algorithm for noise. Gonna do some troubleshooting…
1430 Start data and open the Pulse Viewer. Looking at randoms at 0-Volts. Seeing the wandering charge channels, also occasional noise in phonon channels.
Try unplugging and replugging the cable that is grounding the Side2 electrode. Doesn't really do much.
Notice some noise/fluctuations in the phonon channels. Set all SQUID biases to zero. Set all SQUID lockpoints to zero. Set driver offsets to either 2 or -2 to rail the channels (most were set to 2 but some were still showing noise so I set them to -2).
This seems to have improved the charge channels! Then seem to be holding to a constant baseline and not railing!
Try some triggering. DCRC3qI. Need to increase the threshold to 4600 to avoid constant triggering. That's lots higher than Run67, I think… At 0V, seeing very rare pulses. Bias to +5V - now seeing frequent pulses! Looks good. In DCRC3qI they appear to be erect. Should try the other channels too.
Tower Temperature started falling a little after 14:30. Fell from 106→98 mK. This seems to be related to fixing the charge channels. (Seems to have happened too late to have been caused by the LN2 fill.)
1445 Derek Exits Lab
1604 Start 3min series of 0V data, with 1000 beginning randoms, no trigger, 20 Hz in-run randoms, with 1.6384 ms pulses (8192 length) and 400 us prepulse (500 length).
this data seemed to process just fine

Next Day