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

2017/10/21 (Saturday)

Previous Day

Setup: DIB 1/3/4 → 3.2 MHz filters 1/2/3 → cable 1/3/2 → gender changers → rerouting boards 1/3/4 → DCRC55(1)/33(2)/50(3)
Status: Baked overnight.
1026 Tower stayed around 775 mK during bake, began falling around 0500. Now tower = 85.1 mK
1103 Pulse viewing remotely using vnc and SQUIDTuningGui. Playing with triggering at 0V bias. Try just triggering on just DCRC1 QI. The noise is about 15 mVpp, but a threshold of anything less than ~5000 ADC triggers continuously. There are few pulses to trigger on, but the threshold level to get above noise should still be reasonable (~100ADC). What is happening here? Same thing seen using DCRC1QO
1109 Triggering on DCRC2QO or DCRC3QI/QO are reasonable. Baseline noise = 15 mVpp and threshold of 100 ADC gets strong pulses, can turn it down to DCRC2QO/DCRC3QI/QO=15/40/40 ADC and trigger on pulses just above noise at a reasonable rate.
1122 Stop run and restart programs (triggefe, towerfe, dcrcdriver). Now all DCRCs trigger as expected. Set DCRC1QI/QO thresholds to 40/30 ADC to trigger on pulses just above noise. Not sure what sort of bad triggering state DCRC1 got in to. Is it correlated with using the SQUIDtuning GUI?
1127 Start series of data with Vbias(external) = 0.0 V, with 1000 beginning randoms, and a 40/30/15/40/40 ADC bin threshold trigger on DCRC1qI/qO/DCRC2qO/DCRC3qI/qO, with trigger baseline = 32 samples and trigger length = 10 samples (these are 2x the usual values).
1133 Raw traces appear to be triggering on pulses just above noise as desired.
1134 Stop the run
1136 Since I'm doing this remotely, I can't set the contact free electrode bias. Let's try using the DCRC bias.
1137 Start series of data with Vbias(DCRC) = 10.0 V, with 1000 beginning randoms, and a 40/30/15/40/40 ADC bin threshold trigger on DCRC1qI/qO/DCRC2qO/DCRC3qI/qO, with trigger baseline = 32 samples and trigger length = 10 samples (these are 2x the usual values).
1145 Traces look good so far. Later: DCRC2QO(QD) has no events above noise for some reason.
1210 Stop run Ground and flash detector for 60s.
1250 Tower = 85.4 mK
1254 Start series of data with Vbias(DCRC) = 5.0 V, with 1000 beginning randoms, and a 40/30/15/40/40 ADC bin threshold trigger on DCRC1qI/qO/DCRC2qO/DCRC3qI/qO, with trigger baseline = 32 samples and trigger length = 10 samples (these are 2x the usual values).
1314 Stop run Ground and flash detector for 60s.
1453 Start LHe transfer (MB = 16.9%)
1504 Fill LN2 cold trap full.
1535 Remove empty He cylinder and replace with full one. Continue transfer. We'll need to order a new one.
1634 End LHe transfer (MB = 82.3% - pretty sure dewar is empty)
1635 Tower/MC/Coldplate = 85.7/60.6/365 mK, Still = 1.22 K / 0.20 mbar, G1/G2 = 244/242 mbar, 1K Pot = 1.63 K / 38 mbar. MB = 82.3%
1722 Start charge_bias_scan_R65 sequence with 1000 beginning randoms, and a 40/30/15/40/40 ADC bin threshold trigger on DCRC1qI/qO/DCRC2qO/DCRC3qI/qO, with trigger baseline = 32 samples and trigger length = 10 samples (these are 2x the usual values). This will scan through DCRC biases of 0, 3, 6, 9, 12, -3, -6, -9, -12 V Later: All biased series have rapid noise triggering. Realized there was an error in the sequence so DCRC3QI was stuck at 0 V bias.
1753 Pulses seen in all traces, but DCRC2 has low frequency (10-100Hz?) noise on the baseline. It still seems to be triggering fine, but reconstruction will be screwy.

Next Day