| Setup | DIB1/2 → cables → Dsub filters → DCRC55/50. DCRCs powered. |
| | taking 2-hour data series overnight. Last flash at 06:00 |
| 0855 | Fill LN2 cold trap full. |
| 0900 | MC/Tower/Cold Plate: 35.5/50.8/183 mK. Still: 1.11 K / 40 μbar. G1/G2: 115/110mbar. 1K Pot: 1.41K / 1.4 mbar. Main bath = 77.8% |
| 0905 | Open 1K Pot needle valve additional 10 degrees. |
| 0925 | MC/Tower: 32.8/48.9 mK. Still: 70 μbar. G1/G2: 165/155mbar. 1K Pot: 1.61K / 10 mbar |
| 1320 | Turned off random triggers, began charge breakdown study. |
| | Trouble finding pulses. Tried flashing to no avail. |
| 1349 | Tried zapping squids, cause why not?! |
| 1352 | 1K Pot pressure was at 2.2mbar, opened needle valve 1/16 of a turn. P2 pressure rises initially, then oscillating while steadily decreasing. |
| 1400 | After allowing fridge to cool reset timing link. Either timing link or zapping fixed the issue, as pulses can now be see. Commence charge breakdown study. |
| | During charge breakdown study no breakdown was seen on any of the channels from +/-4V up to +/-14 V, in intervals of 2.0 V. During the test some low noise was seen, believed to be causes by Taconis oscillations. |
| 1532 | After studying midas sequencer and .mls files, write a test file to “take” 2 minutes of +1.0 V data followed by +2.0 V data, with one minute flashing, two minute cooldown proceeding each series (logger turned off). Everything appears to be working correctly, with run starting and stopping, biases changing, and flashing/cooldown occuring as expected. |
| 1540 | After successful test, make sequencer file to take bias sweep from +1.0 V to +13.0 V, and -1.0 V to -9.0 V. This should end before next helium transfer is needed. He level currently at 69%. |
| 1554 | Turn on logger. Check that pulses are still present on all channels. Set trigger to 40 ADC bins on DCRC1 Qo. Turn on before and after randoms. |
| 1600 | Start 22 hours of 30 min background series bias sweeps at +/+1 V to +/+13 V and -/-1 V to -/-9 V in increments of 1 V with 2min flash and 28min cooldown in between. Triggering on DIB1 Qo at 40ADC bins. 1000 randoms before and after. |
| 1601 | 1K Pot pressure/temperature was at 4.5mbar/1.53 K, opened needle valve 1/16 of a turn. P2 pressure/temperature rises initially, maxing out at 1bar/1.83 K, then oscillating while steadily decreasing. |
| 1620 | Fill LN2 cold trap full. |
| 1625 | 1K Pot has stabilized around 1.65K and 19mbar. Will steadily drop overnight. |
| 1626 | First data series started. We have confirmed that the Qbias voltages have been correctly set, and that data files are being written properly to /home/hep/cdmssoft/scdmsDAQ/MidasDAQ/online/data/byseries/. |
| 1650 | During the 1.0V data series, mserver appears to have crashed. Restarted it by running start_daq_umn.sh in the /home/hep/cdmssoft/scdmsDAQ/MidasDAQ/online/bin directory. The crash should be unrelated to our custom sequencer script. When the server was restarted, all the frontend programs were still running as was our sequence. The sequence was still set to be taking 1.0V bias data, and checking the ODB, the QBias is set to 1.0V. The data series has ~6 minutes left, which is what it should have if nothing had gone wrong, so perhaps we just lost a few minutes of data during this series. |
| | We won't be sure if we've lost data during this series because we have 29 data dumps in the /home/hep/cdmssoft/scdmsDAQ/MidasDAQ/online/data/byseries/07160607_1626 directory for this run, whereas during a 30min series yesterday, there were also 29 data dumps, which you can find in the /home/hep/cdmssoft/scdmsDAQ/MidasDAQ/online/data/byseries/07160606_1434 directory. So we won't know if we lost some of the data until we determine if some of our dumps from today's series are empty. Looking at the file sizes, some appear to be ~10MB instead of the ~100MB of dumps from yesterday's run, so perhaps we did lose some data? |
| 1703 | mhttpd appears to have crashed again, prompting another restart by running start_daq_umn.sh as done above. This was during a cooldown, so nothing should have caused this. Maybe something is going on with the network. MIDAS messages tab provides no insight other than the following two messages that occurred before the crash: |