| 1130 | Attempting to take randoms with QETs in superconducting state, but strange problem with DAQ - at around 830 events, computer bogs down: event rate ~ 1 Hz, CPU usage ~ 100%. Set to 100 randoms, it bogs down sooner, at ~60 events. Set to 5000 randoms, it goes past 1000 but then hits a “not enough memory error” some time later, and then you need to kill LabView with the task manager. |
| note | Initially we thought we might want to take data only on DIB3, to test just the 3.2MHz filter, so we tried MultiDAQ with only one DCRC. There was some problem so we tried changing the timing master to DCRC50 (previously DCRC84). But then we realized three-DCRC data would be useful for noise in the superconducting or normal states. |
| note | One symptom of the problem was that in MultiDAQ_EventBuilder the indicators “# of events in queue” and “triggers lost” would go up to largeish values, 50 or a few hundred. |
| 1200 | We tried clearing up disk space, restarting LabView, rebooting the computer, going back to biased QETs, going back to the original timing master… the problem persists. |
| 1511 | Start data in superconducting state, ⇐1000 randoms. |
| 1516 | Start data in superconducting state, ⇐1000 randoms. |
| 1528 | Set all QET biases to +/- 250 μA for RevC.1/RevC to get them all into normal resistance. Note: high frequency noise in DIB2pD - it disappears if Frontend Gain reduced to 6 but I'm leaving it at 7 for consistency. |
| 1533 | Start data in normal state, ⇐1000 randoms. Low frequency noise in DIB1pB. |
| 1553 | Start data in normal state, ⇐1000 randoms. |
| 1630 | Fill LN2 coldtrap full. |
| 1634 | Start data in normal state, ⇐1000 randoms. |
| 1738 | Powercycle DCRCs. Had to change the switch port for DCRC50/DIB1 because I couldn't establish connection or even see the LED on the switch turn on. Tried MultiDAQ - the problem seems to have disappeared. “# of events in queue” and “triggers lost” now stay near 0. |
| 1750 | Zap SQUIDs. |