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

2017/11/18 (Saturday)

Previous Day

Setup: DIB1/3/4 → SL 27/19/20 → 3.2 MHz filters → cables 2,1,3 → HV board inputs 1,3,2 → HV board outputs 1,2 → DCRC55(1)/50(3).
0701 Begin IbIs data sequence on DCRC1pC with HV=0V from 750 to 400 uA in -0.5 uA steps, 3 seconds of data per step
The sequence got stuck apparently - at 08:27 files stopped being produced, the last one at 526.5 uA.
1020 As far as I can tell (using the Opera browser through x-forwarding at home) the MIDAS website is unresponsive. I'll restart it again.
1035 Kill MIDAS, restart MIDAS and programs. As with the last hangup, had to go to ODB:RunInfo and set Transition In Progress to 0 because it was stuck in transition. Deleted the data files from /livedata from this partially-completed sequence, will restart it.
1040 Begin IbIs data sequence on DCRC1pC with HV=0V from 750 to 400 uA in -0.5 uA steps, 3 seconds of data per step
1320 Begin IbIs data sequence on DCRC3pB with HV=0V from 750 to 400 uA in -0.5 uA steps, 3 seconds of data per step
1450 Again, it looks like the sequence got stuck. Each time I've been able to run one IbIs sequence, but the second one gets stuck. This one stopped producing data at 14:42 at 526.5 uA - that's the same as the last time it got stuck! Something's up.
1500 Kill MIDAS, restart MIDAS and programs. Another detail with these hangups is that the kill_daq shell script does not kill mhttp, dcrcdriver, towerfe, triggerfe - these have to be killed individually with kill -KILL.

From the messages above looks like after the sequence starts a run, all the trace lengths are “updated” for some reason, certainly nothing explicit in the sequence. The QET bias gets updated as normal. Nothing in the messages indicates why it got stuck, it just got stuck.

1521 Begin IbIs data sequence on DCRC3pB with HV=0V from 750 to 400 uA in -0.5 uA steps, 3 seconds of data per step
1715 Fill LN2 cold trap full.
1945 The last sequence ran fine. I'm going to preemptively restart MIDAS before starting the next one.
Actually I forgot to start the DCRC driver and the Tower and Trigger front-ends before starting the last sequence. The dumps are all very small so they're probably empty. Delete these.
1955 Restart MIDAS and start DAQ programs.
1956 Begin IbIs data sequence on DCRC3pB with HV=0V from 750 to 400 uA in -0.5 uA steps, 3 seconds of data per step
2215 Sequence seems to have worked. Turn off DAQ programs, restart MIDAS, restart DAQ programs.
2218 Begin IbIs data sequence on DCRC3pC with HV=0V from 750 to 400 uA in -0.5 uA steps, 3 seconds of data per step
Looks like this sequence got stuck, too. Although it went farther than the last couple of times. Last data file was 459.0 uA at 00:13. That may or may not be low enough to span the transition. So I'll go on to the next channel, but maybe redo this one later.
Moved today's IbIs data files to /rawdata/07171118_2500.

Next Day