This section contains a table of the different runs, which identifies what type each run is, when it started and ended.

The type column describes the run as either

• 'd' == data runs
• 'c' == calibration run
• 'x' == experimental, related to development, problems etc

This section covers the data runs, which took place.

The runs, unless otherwise stated, are using the FSR files as in the Septem H calibration Git repo in the folder fsr_inuse. These are the THL values, which were obtained during calibration, but have THL+50 for chips 1, 2, 5 and 6. The HV values are the ones documented in the detector documentation ./Doc/Detector/CastDetectorDocumentation.html (as of <2017-11-09 Thu 19:05>).

.//ssh:tpc@tpc00:/volume1/cast/data/2017_CAST-Run/DataRuns/Run_76_171030-18-39.tar.gz

.//ssh:tpc@tpc00:/volume1/cast/data/2017_CAST-Run/DataRuns/Run_77_171102-05-24.tar.gz

.//ssh:tpc@tpc00:/volume1/cast/data/2017_CAST-Run/DataRuns/Run_78_171103-05-28.tar.gz

.//ssh:tpc@tpc00:/volume1/cast/data/2017_CAST-Run/DataRuns/Run_79_171103-20-46.tar.gz

.//ssh:tpc@tpc00:/volume1/cast/data/2017_CAST-Run/DataRuns/Run_80_171105-00-09.tar.gz

.//ssh:tpc@tpc00:/volume1/cast/data/2017_CAST-Run/DataRuns/Run_81_171105-23-54.tar.gz

.//ssh:tpc@tpc00:/volume1/cast/data/2017_CAST-Run/DataRuns/Run_82_171107-00-01.tar.gz

NOTE: this was the first run with the correct SiPM HV setting of \(\SI{65.6}{\volt}\) .//ssh:tpc@tpc00:/volume1/cast/data/2017_CAST-Run/DataRuns/Run_84_171108-17-49.tar.gz

NOTE: this run was stopped early to fix the src/waitconditions.cpp bug, mentioned in the note below. .//ssh:tpc@tpc00:/volume1/cast/data/2017_CAST-Run/DataRuns/Run_85_171109-19-01.tar.gz

NOTE: VERY IMPORTANT In all runs above, there was a bug in src/waitconditions.cpp, which cause the FADC and scintillator values to be written the all subsequent files, from an event in which the FADC triggered until the next (in case of non-subsequent FADC events). Therefore: for analysis, we need to take into account

• fadcReadout == 1.

Otherwise we read random scintillator trigger values as well as FADC trigger clock cycles.

All runs below are without the aforementioned error.

.//ssh:tpc@tpc00:/volume1/cast/data/2017_CAST-Run/DataRuns/Run_86_171109-21-47.tar.gz

.//ssh:tpc@tpc00:/volume1/cast/data/2017_CAST-Run/DataRuns/Run_87_171111-02-17.tar.gz

NOTE: During Run 89 the byobu buffer containing TOS got stuck on <2017-11-12 Sun 19:35> due to <F7> being pressed (which eventually pauses the thread). Was called by Cristian at <2017-11-13 Mon 05:55> roughly. I fixed the issue. Therefore the length given in the table is misleading, as it does not show the actual time of data taking of that run.

.//ssh:tpc@tpc00:/volume1/cast/data/2017_CAST-Run/DataRuns/Run_89_171112-15-30.tar.gz

.//ssh:tpc@tpc00:/volume1/cast/data/2017_CAST-Run/DataRuns/Run_90_171113-19-14.tar.gz

.//ssh:tpc@tpc00:/volume1/cast/data/2017_CAST-Run/DataRuns/Run_91_171114-20-24.tar.gz

.//ssh:tpc@tpc00:/volume1/cast/data/2017_CAST-Run/DataRuns/Run_92_171115-21-45.tar.gz

.//ssh:tpc@tpc00:/volume1/cast/data/2017_CAST-Run/DataRuns/Run_94_171117-20-48.tar.gz

NOTE: The following run contains the beginning (and most of it) of the GRID measurement. It only contains a single tracking, that's why the run is so long.

.//ssh:tpc@tpc00:/volume1/cast/data/2017_CAST-Run/DataRuns/Run_95_171119-02-35.tar.gz

NOTE: Regarding Run 97, morning shift on 25/11/17, from the elog:

Remarks: At approx. 7:02 there was an error message in the Slow
Control program indicating that some file could not be saved because
there was not enough memory. After about a minute, the Slow Control PC
restarted by itself. At about the same time, an error message appeared
in the Tracking program, probably related to the fact that it could
not communicate with the Slow Control program in order to read
proximity sensor data. After the restart of the Slow control PC and
Slow control program, things went back to normal. Because of all that,
we lost first 3-4 minutes of tracking

NOTE: Still need to add links to previous runs (97, 98, 99)

NOTE: Regarding Run 101: Because of pretty bad noise during the run, I decided to play around with the main amplifier of the analogue signal. I changed the settings as followed:

• Diff: 50 ns -> 20 ns (one to left)
• Coarse gain: 6x -> 10x (one to right)

this got rid of (almost ?) all of the noise. However, obviously this changes the FADC data completely. The shapes are slightly altered (a little steeper)

NOTE: Regarding Run 109: CRAZY amounts of noise during that run. Interestingly, the only difference between the previous runs from what I can tell (although I wasn't present in the shift), was that the main light in the LHCb part of the hall was turned on. Maybe this causes the electricity circuit to be working under high load, producing a lot more noise? Will keep an eye on this.

NOTE: Regarding Run 111: Was stopped early, because I tried to debug the noise and in doing so burned a fuse in the gas interlock box by connecting the NIM crate to a wrong power cable. -> no shift on 6/12/17, background data being taken again since <2017-12-06 Wed 14:55>.

NOTE: Regarding Run 112: Another change of FADC settings due to crazy amounts of noise. Changed integration time from:

• 50ns -> 100ns

gets rid of all noise for now. However, shapes are much smoother than before, might make differentiation much harder later. This was done at around <2017-12-07 Thu 08:00> Also: The power cable from the main amplifier to the pre amplifier was not properly inserted. Did that before changing the settings, seeemed to help, but noise eventually returned.

NOTE: Regarding Run 112 and previous note: Turned down integration time from 100ns to 50ns again at around <2017-12-08 Fri 17:50>.

NOTE: Regarding Run 112: Run is so long, because after problems with fuse, had quench on <2017-12-07 Thu 18:31>.

NOTE: Regarding Run 121: Jochen set the FADC main amplifier integration time from 50 to 100 ns again. Happened at around <2017-12-15 Fri 10:20>. Maybe 5 min later.

This scetion covers the calibration runs, which took place.

.//ssh:tpc@tpc00:/volume1/cast/data/2017_CAST-Run/CalibrationRuns/Run_83_171108-16-27.tar.gz

.//ssh:tpc@tpc00:/volume1/cast/data/2017_CAST-Run/CalibrationRuns/Run_88_171112-14-30.tar.gz

.//ssh:tpc@tpc00:/volume1/cast/data/2017_CAST-Run/CalibrationRuns/Run_93_171117-19-18.tar.gz

.//ssh:tpc@tpc00:/volume1/cast/data/2017_CAST-Run/CalibrationRuns/Run_96_171123-10-42.tar.gz

The following run list is created by the writeRunList tool: ./../CastData/ExternCode/TimepixAnalysis/Tools/writeRunList/writeRunList.nim based on the tracking logs.

Run period 2 (= 2017/18):

Type: rtBackground
         trackingDuration: 4 days, 10 hours, and 20 seconds
         nonTrackingDuration: 14 weeks, 2 days, 1 hour, 23 minutes, and 18 seconds
Type: rtCalibration
         trackingDuration: 0 nanoseconds
         nonTrackingDuration: 4 days, 11 hours, 25 minutes, and 20 seconds

Which amounts to: Calibration data: 107.42 h Background data: 2401.40 h Tracking data: 106 h

Run period 3 (= Oct-Dec 2018):

Type: rtBackground
         trackingDuration: 3 days, 2 hours, 17 minutes, and 53 seconds
         nonTrackingDuration: 6 weeks, 4 days, 20 hours, 54 minutes, and 29 seconds
Type: rtCalibration
         trackingDuration: 0 nanoseconds
         nonTrackingDuration: 3 days, 15 hours, 3 minutes, and 45 seconds

Which amounts to: Calibration data: 87.05 h Background data: 1124.9 h Tracking data: 74.29 h

So in total: Calibration data: 194.47 h Background data: 3526.3 h Tracking data: 180.29 h

Due to the bug in TOS that caused the temperature log files to be placed in ./TOS/log/ instead of the respective run folders, the files were overwritten periodically it seems.

The only temperature information we still have from it thus is the shift forms.

There are also pictures of every shift form in my googlo photos.