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

2017/10/23 (Monday)

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)
Overnight baked for 5 hours. Base temp is elevated from before the bake at 92.8 mK.
1000 Realize that using the DCRCcontrol flashandflash tool caused 2 things to happen. First, because I only set it to flash on DCRCs 2,3, it left DCRC1's charge bias on. Second, it saves and restores whatever charge bias state it was in before the flash (i.e. DCRCs 2,3 bias settings). So, because I didn't ground the detector manually, it flashed with DCRC1 biased and since then has had all DCRCs biased.
1003 Turn off DCRC biases. Tower temp falls to normal level of ~84 mK. Why did this raise the temp though?
1007 Tower/MC/Coldplate = 84.0/57.8/361 mK, Still = 1.24 K / 0.20 mbar, G1/G2 = 260/252 mbar, 1K Pot = 1.63 K / 28 mbar. MB = 22.8%
1011 Fill LN2 cold trap
1014 Realize there was an error in the charge_bias_scan_R65 sequence I had been using so it never changed DCRCQI bias from 0 V! Not sure how exactly this would have screwed things up. Maybe it was the source of the noise and thus noise triggering I saw at bias >0 V?
1018 Flash detector for 60s
1038 Tower = 84.8 mK
1040 Let's get some high bias data while in lab. Go back to the trigger levels I tuned in on saturday morning before I mucked around with that bias scan sequence.
1041 Start series of data with Vbias(external) = 70.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).
1046 Triggering looks good so far. It's a little strange though, looking at raw traces it seems like it's taking a dozen triggers from each dcrc in turn. DCRC1 will trigger on some pulses, then DCRC2, then DCRC3. Maybe this is how triggerfe handles things? It polls a DCRC for triggers, fetches them, then polls the next DCRC? This could also explain the noise triggering behavior I saw this weekend. If one channel is triggering on noise, then those noise triggers will all come in a burst when its that DCRCs turn.
1123 Triggering still looks good and dump sizes are constant.
1143 File sizes begin to fall in the 58th dump.
1144 Stop the run Ground and flash detector for 60 s.
1200 The above 70V series has clear 60keV lines in it. They were just an order of magnitude lower than I'd been looking before. That series was triggering well and lower than we'd been triggering before.
1215 Tower = 84.4 mK
1217 Start series of data with Vbias(external) = 30.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).
1330 Triggering looks good.
1237 Stop run , ground detector
1238 Start LHe transfer (18.7%)
1244 Flash detector for 60s
1320 Cease LHe transfer (87.3%)
1325 Start series of data with Vbias(external) = 50.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).
1430 Bleh, triggering on noise again for this whole series.
1433 Stop run, ground detector, flash for 60s.
1452 Tower temp = 84.6 mK
1453 Start series of data with Vbias(external) = 50.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).
1459 That low frequency noise in DCRC2 is back, but we seem to be triggering just on pulses again.
1543 Dump sizes start falling around minute 37
1541 Stop run, ground and flash detector for 60 s
1618 Start series of data with Vbias(external) = 90.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).
1718 She's still going strong.
1738 Dump sizes start to fall in 75th minute.
1740 Stop the run, ground detector.
1741 Begin 1 hour mini-bake.
1742 Fill LN2 cold trap full.
1952 Tower = 84.2 mK
1953 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
2058 0V (_1953) triggering looks good, but 3V (_2045) data is triggering on noise…
2059 Stop the sequence
2101 Manually start test series at 0V. Triggering looks fine.
2106 Manually start test series at 3V DCRC bias. Triggering on noise. Disable DCRC1 triggers at beginning of minute 4. Still have noise triggers. Re-enable DCRC1 triggers and disable DCRC3 triggers at beginning of minute 11. Now there are no noise triggers. Re-enable DCRC3 triggers with thresholds raised to 60/60 ADC at beginning of minute 19. Triggering on noise again. Raise DCRC3 thresholds to 100/100 ADC part way through 28th minute. Still triggering on noise. Disable DCRC3QO trigger midway through 33rd minute. Triggers on noise. Enable DCRC3QO, disable DCRC3QI triggers at beginning of minute 38. Triggers on noise. Disable all DCRC3 triggers again at minute 44. No there is no noise triggering.
Summary of above tests: 0V = good triggering, DCRC bias of 3V = bad, turn off DCRC3 triggers=good, turn on either DCRC3 trigger=bad, double DCRC3 thresholds=still bad. This wasn't really a problem during the day with the external bias. Maybe DCRC3's bias line is noisy enough to screw up its triggering.
2200 Ground and flash detector for 60 s.
2225 Tower = 85.1 mK
2224 Modify charge_bias_scan_R65 sequence by removing initial 0V series.
2226 Start charge_bias_scan_R65 sequence with 1000 beginning randoms, and a 40/30/15/-/- 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 3, 6, 9, 12, -3, -6, -9, -12 V
2231 stop the sequence, immediately have rapid triggering on noise. This is dumb.
On Saturday I was able to run at DCRC biases of 5 V, 10 V by manually starting a run. It wasn't till I tried the sequence that things tarted getting screwy. Maybe I'll try that again now.
2232 Manually start a run with 0V DCRC bias, and triggers enabled at thresholds of DCRC1qI/qO/DCRC2qO/DCRC3qI/qO = 40/30/15/40/40 ADC. Well, this was going to be a control series, but now even this 0V series is triggering on noise…
2238 Manually start a run with 10V DCRC bias, and triggers enabled at thresholds of DCRC1qI/qO/DCRC2qO/DCRC3qI/qO = 40/30/15/40/40 ADC. This also has rapid triggers on noise.
2240 Stop run, ground detector, restart DCRC programs.
2243 Manually start a run with 10V DCRC bias, and triggers enabled at thresholds of DCRC1qI/qO/DCRC2qO/DCRC3qI/qO = 40/30/15/40/40 ADC. Now its triggering fine!
Somehow using the sequence puts (one of?) these guys into a noise-triggering state that requires restarting the programs to fix? Purge the sequence of any commands I'm not doing manually here (e.g. remove lines about setting up flash constants etc. Assume the user will have everything set up before the sequence is started)
2250 Stop run, ground and flash detector. Let's try this one last time tonight.
2320 Start barebones 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 3, 6, 9, 12, -3, -6, -9, -12 V
2343 Well now its not copying dumps to midasraw for some reason… Stop the sequence
2348 Even another manually started run does not get copied to midasraw.
0005 Ground detector and start 5 hour bake.

Next Day