| | Setup: DIB 1/3/4 → 3.2 MHz filters 1/2/3 → cable 1/2/3 → gender changer 1/3/4 → DCRC55(1)/33(2)/X(4) |
| 0930 | Tower = 25.3 mK, Still = 0.060 mbar, G1/G2 = 172/162 mbar, 1K Pot = 1.708 K / 36 mbar. MB = 67.5% |
| 0932 | Fill LN2 cold trap full. |
| 0940 | Begin 2/-2V DCRC4PA IbIs remotely. |
| 1045 | Complete DCRC4PA IbIs |
| 1610 | Fill LN2 cold trap the fullest. |
| 1632 | Try test signal scan script with file naming, not writing as cdmsseries. Starting with series 7894, but files will be named e.g. Fscan_10.mid.gz for 10Hz test signal. |
| | Took 27 series, each 5 sec long, with 3 sec wait after each freq change. Whole sequence took ~8 min to run. |
| | Data looks good in Batviewer. Making a new “series” in /data/chocula/k100/midasraw/byseries/07170721_2500 and placing the raw files there. |
| 1648 | Flash for 30 sec, monitor temp via logfile on vuk-01 |
| 1707 | Tower temp is 28.1 mK |
| 1715 | Start sequence 12 60-minute data series of charge-bias-scan data with Frontend Gain = (15/2)/(4/4)/(5/5/5/5), OG = 4/2/4, QET biases = 2017/07/17, with 1000 beginning randoms, 30 sec flash with 25 min wait, and a 100ADC bin threshold trigger on DCRC1 q[0]. Charge biases are DCRC1/2 = -/+ = Side1/2 = +/-. Side 1 biases in order are 0, 0.25, 0.5, 0.75, 1, 1.5, 2, 2.5, 3, 3.5, 4, 5 |
| 1724 | Triggering on noise, raise DCRC1 q[0] trigger to 150. Strange, threshold of 100 looked good in pulse viewer before starting run. |
| 1728 | Geez, still triggering on noise, raise DCRC1 q[0] trigger to 200 |
| 1732 | Raise raise DCRC1 q[0] trigger to 250 [image not archived: doubt.svg] |
| 1737 | Abort the run Not sure what's going on here. |
| | Things still look good in pulse viewer. Can turn down trigger level to 100 and every event is still clearly a pulse. Why does it take crap data when I run the sequencer??? |
| 1746 | If I start a run (logging off, watching pulse viewer) with no initial randoms, DCRC1 q[0] trigger = 100, it goes through randoms fine, but then starts triggering like mad even if I take the trigger up to 1500. Stop the run, disable initial randoms, start a new run, triggering works fine with DCRC1 q[0] trigger=100. Go to start a new run, but SQUID tuning gui crashed, restart it. Start a new run with 100 initial randoms, now triggering works fine?!?! |
| 1752 | Change back to 1000 initial randoms and start a new run. Triggering is working fine now… DCRC1 or the DAQ was throwing a tantrum of some sort, but seems to have gotten over it somehow. Gonna chalk this one up to ghosts because I have no idea. |
| 1755 | Start sequence 12 60-minute data series of charge-bias-scan data with Frontend Gain = (15/2)/(4/4)/(5/5/5/5), OG = 4/2/4, QET biases = 2017/07/17, with 1000 beginning randoms, 30 sec flash with 25 min wait, and a 100ADC bin threshold trigger on DCRC1 q[0]. Charge biases are DCRC1/2 = -/+ = Side1/2 = +/-. Side 1 biases in order are 0, 0.25, 0.5, 0.75, 1, 1.5, 2, 2.5, 3, 3.5, 4, 5 |
| 1756 | Tower = 25.6 mK |
| 1759 | Abort the run Again, triggering is not working. After 1000 initial randoms, data is being recorded every few us. |
| 1800 | Turn off logger, start run manually and watch pulse viewer. After initial randoms, triggering works fine. Whaaat?!? |
| 1802 | Stop run. Turn on logger. Start run manually. Triggering looks good in Batviewer. Let's try that charge_bias_scan.msl script once more. |
| 1806 | Start sequence 12 60-minute data series of charge-bias-scan data with Frontend Gain = (15/2)/(4/4)/(5/5/5/5), OG = 4/2/4, QET biases = 2017/07/17, with 1000 beginning randoms, 30 sec flash with 25 min wait, and a 100ADC bin threshold trigger on DCRC1 q[0]. Charge biases are DCRC1/2 = -/+ = Side1/2 = +/-. Side 1 biases in order are 0, 0.25, 0.5, 0.75, 1, 1.5, 2, 2.5, 3, 3.5, 4, 5 |
| 1811 | Abort the run Again, triggering is still not working. It must be something funky this charge_bias_scan script is doing, but I can't figure what… |
| 1813 | Just start a run manually without changing anything else. Of course triggering works now. End the run. This is stupid. |
| 1824 | Restart triggerfe2, towerfe3_01, dcrc_driver01 programs. Start the sequence. Charge triggering is bananas. |
| 1828 | Restart triggerfe2, towerfe3_01, dcrc_driver01, and SQUIDtuning programs. Start the sequence. It worked! |
| | Start sequence 12 60-minute data series of charge-bias-scan data with Frontend Gain = (15/2)/(4/4)/(5/5/5/5), OG = 4/2/4, QET biases = 2017/07/17, with 1000 beginning randoms, 30 sec flash with 25 min wait, and a 100ADC bin threshold trigger on DCRC1 q[0]. Charge biases are DCRC1/2 = -/+ = Side1/2 = +/-. Side 1 biases in order are 0, 0.25, 0.5, 0.75, 1, 1.5, 2, 2.5, 3, 3.5, 4, 5 |
| 1831 | It seems like restarting the SQUIDtuning program is what did it. I'm doing this remotely, so I had a SQUIDtuning instance running on denali in addition to the normal one which was open on cdms2. Restarting that program via the ODB killed both. Maybe they were interfering somehow? Not sure, but I'm glad it seems to be working now! |