2015/12/15 (Tuesday)

Previous Day

	Setup: iZIP mode, DIB1/2/3 → cables → 3.2 MHz filters → DCRC55/33/50
	Taking background data overnight with MIDAS. Last flash at 00:10, apparently. Some unexplained temperature excursions between flashes seen.
	Looks like only 8 series of data were taken out of the 15 planned. MIDAS says “Logger not running” so apparently the logger script crashed again. However it is different this time because the flashes did not continue after the last recorded series, so maybe something different happened.
0850	Tower/MC(H35)/MC sensor/Cold Plate = 32.4/27.7/42.3/178 mK, Still = 1.37 K / 0.10 mbar, G1/G2 = 120/115 mbar, 1K Pot = 1.59 K / 5.5 mbar, Main bath = 66.4%
0900	Fill LN2 cold trap Dewar
0915	Set charge biases back to 0/0 V.
1010	Restart mlogger process from a terminal on jiajin

Switch to user cdmssoft:

> sudo -u cdmssoft -s
> whoami

Go to home directory then

> cd scdmsDAQ/MidasDAQ/online/bin/

See what's running

> ps -u cdmssoft
  PID TTY          TIME CMD
13259 pts/8    00:00:00 bash
13789 ?        1-08:52:58 mhttpd
13791 ?        00:01:54 mserver
13795 ?        00:40:27 lazylogger
241594 ?        00:06:12 dcrc_driver.exe
241596 ?        1-11:01:08 towerfe3.exe
241598 ?        1-09:17:02 triggerfe2.exe
385840 pts/18   00:00:00 bash
457635 pts/19   00:00:00 bash
460806 pts/21   00:00:00 bash
461106 ?        00:00:00 mlogger
462800 pts/21   00:00:00 ps

mlogger is running in example above. If it isn't, look in start_daq_umn.sh to get the line to start mlogger properly:

mlogger -D -e cdms_UMN

After doing this, “Logger not running” should no longer appear on MIDAS front page. If you wanted to do a complete restart of the DAQ you can run kill_daq_umn.sh then start_daq_umn.sh

1025	Flash for 1 minute (0.015 hours) using MIDAS flash-and-flash tool.
1130	Had trouble with the pulse viewing gui/MIDAS getting stuck in a transition state. Learned the fix: go to ODB→Runinfo and set three things to zero:

Transition in progress	0 (0x0)
Start abort	0 (0x0)
Requested transition	0 (0x0)

1140	On ODB / Equipment /Triggerfe2 / Settings try setting PileupCut (s) to 0.0001. This should reject triggers that are within 100 μs of the previous trigger, maybe. Another attempt to remove retriggers from data.
1150	Pulse viewing gui so sluggish as to be pretty much unusable.
1206	Start 3 30min series of +/-4V MIDAS background data; FG=5/2/5, OG=3; with 30s flash and 25min cooldown in between series. Trigger on DIB1pA only (Side1pB) with trigger threshold = 30. Set Pileup Cut threshold to 100 μs.
1610	Fill LN2 cold trap Dewar
1613	Start 16 19 30min series of +/-4V MIDAS background data; FG=5/2/5, OG=3; with 30s flash and 20min cooldown in between series. Trigger on DIB1pA only (Side1pB) with trigger threshold = 30 and Pileup Cut threshold to 100 μs. (It was set to 16 hours of data taking but this is 19 series. A full cycle takes 51.3 minutes on average. We have cooldown set at only 20 minutes - it's probably sufficient but maybe should be increased.)
1615	Main bath = 53.0%

Next Day