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

2012/11/18

0125 We incurred some minor problems with data acquisition. Overall though, data quality should be fine. There are, however, a few things to bear in mind when performing the analysis.
Rather confusingly, 23 data files were collected yesterday. It appears as though 12 files were taken at -/+2 V and 11 files at +/-3 V. A quick look at the pulses with BatViewer should confirm this.
Additionally, it appears as though there was no detector flash before data series 07121117_1754. It's likely this was the first +/-3 V data series. We've seen this before, and restarting the DAQDAQ2 vi seems to clear up whatever is causing the problem. The rest of the data is probably fine, and the fact there was no flash before this data series means it should probably not be included in the analysis. We shall reduce it anyway just in case we can do something with it.
Finally, times between data series are rather erratic, ranging from 14 to 33 minutes. Restarting the DAQDAQ2 vi may clear up whatever is causing this problem.
Restart all LabVIEW vis.
0145 Place Ba-133 source back in safe. Take Cf-252 source out of safe and install 3“ below top of mu-metal shield. Email to be sent to laboratory users to warn them of the source's presence.
Start data acquistion with Cf-252 source 3” below top of mu-metal shield, triggering on phonon channels with 0.4 ms trigger delay and 3.2768 ms trace length. OR phonon trigger threshold 25 ADC bins for all phonon channels, and coincidence time set to 10 μs. Flash for 6 seconds, followed by cool down for 20 minutes. Then take twenty-four 5-minute data series at -/+2 V bias. Flash all LEDs for 6 seconds between data series with usual settings, and wait 20 minutes for cryostat to cool. Finish with a 20 minute flash and 2-hour cool down.
Phonon pulses in test data series look good. Trigger rate lies between 13-14 Hz.
0155 Take advantage of detector flash to fill N2 cold trap full.
0240 A look at the pulses in BatViewer indicates that 07121117_1740 appears to be the last -/+2 V data series, and 07121117_1754 seems to be the first +/-3 V data series.
A quick look at acquisition time for each data series in Table 1 is revealing. For some reason, the last -/+2 V data series had a short data acquisition time of 3 minutes. This was followed by a 10-minute series at +/-3 V, then a flash preceding a 13-minute +/-3 V data series. Not sure what to make of it, except that we should just use whatever data we have without imposing an event time cut. With such erratic behaviour, such a cut becomes difficult to impose in the analysis. There will be some degradation in neutralisation, but as long as the 356 keV line is visible, the data is good enough.
Table 1: Acquisition time for data series taken on 2012/11/17.
Series Acquisition Time [minutes] Size [MB] Bias [V]
07121117_1251 6 912 -/+2
07121117_1318 8 1200 -/+2
07121117_1346 5 757 -/+2
07121117_1411 6 899 -/+2
07121117_1437 6 814 -/+2
07121117_1503 5 731 -/+2
07121117_1528 6 850 -/+2
07121117_1554 7 1100 -/+2
07121117_1621 6 793 -/+2
07121117_1647 8 1200 -/+2
07121117_1715 5 751 -/+2
07121117_1740 3 414 -/+2
07121117_1754 10 1600 +/-3
07121117_1824 13 1900 +/-3
07121117_1857 6 909 +/-3
07121117_1923 9 1300 +/-3
07121117_1952 7 1100 +/-3
07121117_2019 5 752 +/-3
07121117_2044 6 915 +/-3
07121117_2111 5 782 +/-3
07121117_2136 8 1200 +/-3
07121117_2204 8 1200 +/-3
07121117_2232 5 865 +/-3
1500 Cf-252 source placed back in safe.
1520 Started LHe transfer at 28%
1605 Cease helium transfer. Helium liquid level 95.0%.
1620 Historical record of mixing chamber temperature indicates that detector was flashed before every data series taken last night. However, a quick look at the acquisition times and file sizes in Table 2 indicates that the problem with erratic behaviour has not disappeared. Additionally, although 24 data series were requested, only twenty were actually taken.
The DAQ may not like writing just one file per data series. This is pure speculation with no evidence to back it up except for the fact that the DAQ had no trouble stopping the run at the correct time and taking the correct number of data series when taking charge-only data. Charge-only data with a shorter trace length could handle a higher trigger rate, had less dead time and hence produced more than one 10k file, even in a 5-minute run. If we reduce the number of events in each data series to 2k, we may have more success. This is worth trying.
Table 2: Acquisition time for -/+2 V data series taken on 2012/11/18.
Series Acquisition Time [minutes] Size [MB]
07121118_0210 7 1100
07121118_0237 5 744
07121118_0303 13 1900
07121118_0335 6 824
07121118_0401 13 1900
07121118_0434 13 1900
07121118_0507 6 833
07121118_0533 13 1900
07121118_0606 12 1700
07121118_0638 12 1900
07121118_0711 12 1900
07121118_0743 13 1900
07121118_0816 13 1900
07121118_0849 14 1900
07121118_0922 10 1500
07121118_0952 10 1400
07121118_1022 12 1900
07121118_1055 5 743
07121118_1120 7 1100
07121118_1147 8 1100
2145 Fill N2 cold trap full.