Difference between revisions of "Run Coordinator report: Fall 2021 w18"

From GlueXWiki
Jump to: navigation, search
(Created page with "=Tuesday December 21= #Last 24h: #*~6h of production on <sup>4</sup>He (150 nA, 0/90 perp only: para was too degraded.) #*3h35 (3:40am-7:15am) empty target data taking. #*[htt...")
 
Line 1: Line 1:
=Tuesday December 21=
 
#Last 24h:
 
#*~6h of production on <sup>4</sup>He (150 nA, 0/90 perp only: para was too degraded.)
 
#*3h35 (3:40am-7:15am) empty target data taking.
 
#*[https://logbooks.jlab.org/entry/3966712 trigger tests in raw data mode and CPP trigger test.]
 
#Issues
 
#* Target OVC vacuum.
 
#* [https://logbooks.jlab.org/entry/3966702 Target temperature increases]
 
#* [https://logbooks.jlab.org/entry/3966864 Transmission rate decreased by 5%]
 
#Summaries
 
#*[https://logbooks.jlab.org/entry/3966910 Electron beam energy during the SRC-CT run.]
 
#*[https://logbooks.jlab.org/entry/3966912 Normalized rates for SCR-CT Fall 2021 run]
 
#Plans
 
#*End of Fall 2021 run. Hall shut down tasks:
 
#**Secure beam line:
 
#***All radiators retracted.
 
#***Collimator in blocking position.
 
#***PS and sweeping magnets off.
 
#**Solenoid ramp down.
 
#**Target will already be empty. Keep PTR on since the target group might do some investigation of the vacuum event.
 
#**High and low Voltages off.
 
#**Crates will be kept on.
 
 
=Monday December 20=
 
#Last 24h:
 
#* ~4h of production on <sup>4</sup>He (150 nA, 0/90 para and perp).
 
#* 2 long down times: ~5h between Sunday 9am-13:45 (multiple causes. Mains ones: Bulk power supply and 1L04 RF). Monday: 1am-ongoing (IL05 RF).
 
#* 2h on Amorphous radiator (runs 90631, 90632).
 
#* [https://logbooks.jlab.org/entry/3966194 CPP trigger tests (~5h)]
 
#Issues
 
#*[https://logbooks.jlab.org/entry/3965971 Target pressure event] due to large [https://logbooks.jlab.org/files/2021/12/3965971/screen.jpg vacuum spike] in the Outer Vacuum Can (OVC). [https://logbooks.jlab.org/entry/3966001 No incidence on data taking.] (Most of the event unfolded during beam down time in any case.)
 
#* [https://logbooks.jlab.org/entry/3966112 Target status and comments from Chris C. and Hovanes]
 
#* [https://logbooks.jlab.org/entry/3966302 Target status (7pm)]
 
#* [https://logbooks.jlab.org/entry/3966090 Diamond degradation]
 
#Plans
 
#*Production on <sup>4</sup>He (150 nA, 0/90 para and perp) until Tuesday 7am.
 
#*3h trigger tests in raw data mode.
 
#*1h CPP trigger test.
 
#* Finish run period with ~3h Empty target run, from 3:30am (12/21/2021) to shutdown around 7am. (This will permit to check if the target event above has made ice to accumulate on the target cell).
 
#*No analysis meeting today
 
 
=Sunday December 19=
 
#Last 24h:
 
#* Smooth data collection on <sup>4</sup>He (150 nA, 0/90 para and perp).
 
#Issues
 
#*Nothing special.
 
#Plans
 
#*Production on <sup>4</sup>He (150 nA, 0/90 para and perp).
 
#*Amorphous run Sunday morning.
 
#*CPP trigger tests (During A. Somov shift in the afternoon.)
 
 
 
 
 
 
 
=RC summary, December 15-21 2021=
 
=RC summary, December 15-21 2021=
  
 
This RC tenure is the last of the SRC-CT (E12-19-003) run period. It started with the target filled with LD<sub>2</sub>.  
 
This RC tenure is the last of the SRC-CT (E12-19-003) run period. It started with the target filled with LD<sub>2</sub>.  
 
Wednesday 12/15/2021 saw smooth production on LD<sub>2</sub> at 140 nA, 0/90 para and perp. It was interrupted only by ~1h of RF-related beam down time and a search for better spot on diamond JD70-105 since it had degraded due to beam damage. [https://logbooks.jlab.org/entry/3963658 H. Egiyan tried to find a new location that improved the 0/90 para and 45/135 para/perp coherent peaks, but to no avail.]  
 
Wednesday 12/15/2021 saw smooth production on LD<sub>2</sub> at 140 nA, 0/90 para and perp. It was interrupted only by ~1h of RF-related beam down time and a search for better spot on diamond JD70-105 since it had degraded due to beam damage. [https://logbooks.jlab.org/entry/3963658 H. Egiyan tried to find a new location that improved the 0/90 para and 45/135 para/perp coherent peaks, but to no avail.]  
Untrouble data taking continued on Thursday, 12/16/2021, with about 6h of beam-related interruption. After the RC morning meeting, SRC-CT leadership decided that the experiment would benefit from changing the target from LD<sub>2</sub> to <sup>4</sup>He the next day (Friday, 12/17/2021. This was a long discussion because none of the Target Group persons who knew how to do the change (C. Keith, J. Maxwell) were available. Eventually, C. Carlin agreed to do it with C. Keith, who was out of town, writing a detailed procedure and supporting by phone.   
+
Good data taking continued on Thursday, 12/16/2021, with about 6h of beam-related interruption. The only (small) trouble was that the target control computer needed to be rebooted. This did not caused time loss, but [https://logbooks.jlab.org/entry/3964773 the target LD2 nominal temperature after reboot was 1.3K lowerer than before the reboot.]
 +
After the Thursday morning run meeting, SRC-CT leadership decided that the experiment would benefit from changing the target from LD<sub>2</sub> to <sup>4</sup>He the next day (Friday, 12/17/2021. This was a long discussion because none of the Target Group persons who knew how to do the change (C. Keith, J. Maxwell) were available. Eventually, C. Carlin agreed to do it with C. Keith, who was out of town, writing a detailed procedure and supporting by phone.   
 
On Friday, 12/17/2021, LD<sub>2</sub> (140 nA, 0/90 para and perp) data taking continued until 14:10, followed by a 1h empty target run since such data were needed and the target had to be first emptied. (This failed at first because [https://logbooks.jlab.org/comment/36529#comment-36529 the target cell boiler used to evacuate the cell] would not respond. C. Carlin asked for Rapid Access and fixed the issue. This problem reduced the empty target run from the planned 2h to 1h). The target gas change [https://logbooks.jlab.org/entry/3965061 went relatively smoothly] and was done within the expected time. A planned Rapid Access was done for switching gas.  
 
On Friday, 12/17/2021, LD<sub>2</sub> (140 nA, 0/90 para and perp) data taking continued until 14:10, followed by a 1h empty target run since such data were needed and the target had to be first emptied. (This failed at first because [https://logbooks.jlab.org/comment/36529#comment-36529 the target cell boiler used to evacuate the cell] would not respond. C. Carlin asked for Rapid Access and fixed the issue. This problem reduced the empty target run from the planned 2h to 1h). The target gas change [https://logbooks.jlab.org/entry/3965061 went relatively smoothly] and was done within the expected time. A planned Rapid Access was done for switching gas.  
 
A. Somov, L. Penchev, S. Botarinov and V. Berdnikov took advantage of that access to [https://logbooks.jlab.org/entry/3965001 re-position the calorimeter prototype] in the Pair Spectrometer test area.
 
A. Somov, L. Penchev, S. Botarinov and V. Berdnikov took advantage of that access to [https://logbooks.jlab.org/entry/3965001 re-position the calorimeter prototype] in the Pair Spectrometer test area.
 
while the target <sup>4</sup>He gas cooled down (a process taking about 3h), the Hall was closes and A. Somov requested the beam for opportunistic Pair Spectrometer background data taking.
 
while the target <sup>4</sup>He gas cooled down (a process taking about 3h), the Hall was closes and A. Somov requested the beam for opportunistic Pair Spectrometer background data taking.
Around 23:00 (12/17/2021) the <sup>4</sup>He reached its nominal temperature and SRC-CT was ready for production but the beam was unavailable. [https://logbooks.jlab.org/entry/3965138 the beam was unavailable.] It came back at about 1:50am (Saturday 12/18/2021) and we started production on <sup>4</sup>He (150 nA, 0/90 para and perp).
+
Around 23:00 (12/17/2021) the <sup>4</sup>He reached its nominal temperature and SRC-CT was ready for production but the beam was unavailable. [https://logbooks.jlab.org/entry/3965138 the beam was unavailable.] It came back at about 1:50am (Saturday 12/18/2021) and we started production on <sup>4</sup>He (150 nA, 0/90 para and perp). The rest of Saturday went very smoothly, with data collection on <sup>4</sup>He (150 nA, 0/90 para and perp).
 
+
However, Sunday and Monday were less efficient. We got, out of 48h, only about 15h of production on <sup>4</sup>He (150 nA, 0/90 para, perp, and amorphous).
 
+
There were 2 long down times: ~5h between Sunday 9am-13:45 (multiple causes. Mains ones: Bulk power supply and 1L04 zone RF issue) and Monday (1am-10:30am due to IL05 zone RF issue).
 
+
In addition, to <sup>4</sup>He production data, about 6h was used for [https://logbooks.jlab.org/entry/3966194 CPP trigger tests] and [https://logbooks.jlab.org/entry/3966712 3h trigger tests in raw data mode]. (Both tests were conducted by A. Somov).
 
+
On Monday (12/20/2021) a [https://logbooks.jlab.org/entry/3965971 target pressure event occured] due to large [https://logbooks.jlab.org/files/2021/12/3965971/screen.jpg vacuum spike] in the Outer Vacuum Can (OVC) of the target. This had [https://logbooks.jlab.org/entry/3966001 no incidence on data taking.] (Most of the event unfolded during beam down time in any case.) Eventually, the cause of the events was trace back to [https://logbooks.jlab.org/entry/3966798 a faulty turbo pump].
 
+
The vacuum degradation caused the [https://logbooks.jlab.org/entry/3966702 target temperature to slightly increase].
 
+
We continued production on <sup>4</sup>He (150 nA, 0/90 perp only because para was too degraded) until Tuesday (12/21/2021) ~3:30am, gathering a final ~6h of data on <sup>4</sup>He. Then we finished the SRC-CT run period with ~3h Empty target run. This was done because more empty target data were needed but also to check if the target vacuum degradation had caused ice to accumulate on the target cell. (This would have happened if the OVC vacuum degradation were caused by a leak. It is only later that the faulty turbo pump was identified as the cause.).
For the whole SCR-CT run:
+
On Tuesday, 12/21/2021, at 7:15am, the beam was terminated and the Hall put in restricted access. We started the hall shut down procedure:
 
+
The beam line was secured by retracting all radiators, putting the collimator in blocking position and turning off the pair spectrometer and sweeping magnets.
There were 41.3 days scheduled for SRC-CT (43.3 days on the ENP schedule, but 48h were spent in beam studies).  
+
[https://logbooks.jlab.org/entry/3966993 M. Stevens ramped down the Solenoid, put on the beamline windows and completed the rest of the technical shut-down checklist].
 
+
[https://logbooks.jlab.org/entry/3966989 C. Keith secured the target] will already be empty.  
The ABU+BANU was 71.6% (708.5h)
+
[https://logbooks.jlab.org/entry/3966962 L. Penchev and A. Somov turned High and low Voltages off as well as the wire chamber gas] [https://logbooks.jlab.org/entry/3966981 and chiller].
The ABU was 60.7% (601.2h)
+
Crates were be kept on.
 
+
If we want to assess the time for SRC-CT itself, we need to remove about 6h of dedicated to CPP trigger test. I think there was nothing else unrelated to SRC-CT (all overheads like target change etc. should be included the PAC request).
+
 
+
In that case, ABU+BANU=70.9%  (702.5h)
+
ABU=60.1% (595.2h)
+
Assuming the usual 50% run efficiency and using the 21 pac days allocated to the experiment (not the 41.3 days actually scheduled), SRC-CT should have gathered 118% of the expected data.  
+
  
As usual, this does not account for details, like data taking overhead higher than expected (e.g. due to radiator swaps, reducing the data taking efficiency), or the fact the SRC-CT run used a coherent enhancement that effectively favored better kinematics (increasing the data taking efficiency).
+
For this week of RC tenure, we got 84h of Accceptable Beam in Use (ABU) out of the scheduled 136h, therefore  a 62% overall efficiency.
  
Noticeable events were  
+
For the whole SCR-CT run, there were 41.3 days scheduled (43.3 days total, but 48h were spent in beam studies).
#* On 12/17/2021: [https://logbooks.jlab.org/entry/3964773 Target LD2 nominal temperature before reboot was 1.3K higher than nominal temperature after reboot.]
+
Therefore, the overall ABU was 60.7% (601h), or 60.1% (595h) if we account for the 6h of CPP trigger test (not part of the SRC-CT run).  
 +
Assuming the usual 50% run efficiency and using the 21 pac days allocated to the experiment, SRC-CT gathered 118% of the expected data.
 +
As usual, this number is for accounting only and does not account for details, like data taking overhead higher than expected (e.g. due to radiator swaps, reducing the data taking efficiency), or the fact the SRC-CT run used a coherent enhancement that effectively favored better kinematics (increasing the data taking efficiency).

Revision as of 09:22, 22 December 2021

RC summary, December 15-21 2021

This RC tenure is the last of the SRC-CT (E12-19-003) run period. It started with the target filled with LD2. Wednesday 12/15/2021 saw smooth production on LD2 at 140 nA, 0/90 para and perp. It was interrupted only by ~1h of RF-related beam down time and a search for better spot on diamond JD70-105 since it had degraded due to beam damage. H. Egiyan tried to find a new location that improved the 0/90 para and 45/135 para/perp coherent peaks, but to no avail. Good data taking continued on Thursday, 12/16/2021, with about 6h of beam-related interruption. The only (small) trouble was that the target control computer needed to be rebooted. This did not caused time loss, but the target LD2 nominal temperature after reboot was 1.3K lowerer than before the reboot. After the Thursday morning run meeting, SRC-CT leadership decided that the experiment would benefit from changing the target from LD2 to 4He the next day (Friday, 12/17/2021. This was a long discussion because none of the Target Group persons who knew how to do the change (C. Keith, J. Maxwell) were available. Eventually, C. Carlin agreed to do it with C. Keith, who was out of town, writing a detailed procedure and supporting by phone. On Friday, 12/17/2021, LD2 (140 nA, 0/90 para and perp) data taking continued until 14:10, followed by a 1h empty target run since such data were needed and the target had to be first emptied. (This failed at first because the target cell boiler used to evacuate the cell would not respond. C. Carlin asked for Rapid Access and fixed the issue. This problem reduced the empty target run from the planned 2h to 1h). The target gas change went relatively smoothly and was done within the expected time. A planned Rapid Access was done for switching gas. A. Somov, L. Penchev, S. Botarinov and V. Berdnikov took advantage of that access to re-position the calorimeter prototype in the Pair Spectrometer test area. while the target 4He gas cooled down (a process taking about 3h), the Hall was closes and A. Somov requested the beam for opportunistic Pair Spectrometer background data taking. Around 23:00 (12/17/2021) the 4He reached its nominal temperature and SRC-CT was ready for production but the beam was unavailable. the beam was unavailable. It came back at about 1:50am (Saturday 12/18/2021) and we started production on 4He (150 nA, 0/90 para and perp). The rest of Saturday went very smoothly, with data collection on 4He (150 nA, 0/90 para and perp). However, Sunday and Monday were less efficient. We got, out of 48h, only about 15h of production on 4He (150 nA, 0/90 para, perp, and amorphous). There were 2 long down times: ~5h between Sunday 9am-13:45 (multiple causes. Mains ones: Bulk power supply and 1L04 zone RF issue) and Monday (1am-10:30am due to IL05 zone RF issue). In addition, to 4He production data, about 6h was used for CPP trigger tests and 3h trigger tests in raw data mode. (Both tests were conducted by A. Somov). On Monday (12/20/2021) a target pressure event occured due to large vacuum spike in the Outer Vacuum Can (OVC) of the target. This had no incidence on data taking. (Most of the event unfolded during beam down time in any case.) Eventually, the cause of the events was trace back to a faulty turbo pump. The vacuum degradation caused the target temperature to slightly increase. We continued production on 4He (150 nA, 0/90 perp only because para was too degraded) until Tuesday (12/21/2021) ~3:30am, gathering a final ~6h of data on 4He. Then we finished the SRC-CT run period with ~3h Empty target run. This was done because more empty target data were needed but also to check if the target vacuum degradation had caused ice to accumulate on the target cell. (This would have happened if the OVC vacuum degradation were caused by a leak. It is only later that the faulty turbo pump was identified as the cause.). On Tuesday, 12/21/2021, at 7:15am, the beam was terminated and the Hall put in restricted access. We started the hall shut down procedure: The beam line was secured by retracting all radiators, putting the collimator in blocking position and turning off the pair spectrometer and sweeping magnets. M. Stevens ramped down the Solenoid, put on the beamline windows and completed the rest of the technical shut-down checklist. C. Keith secured the target will already be empty. L. Penchev and A. Somov turned High and low Voltages off as well as the wire chamber gas and chiller. Crates were be kept on.

For this week of RC tenure, we got 84h of Accceptable Beam in Use (ABU) out of the scheduled 136h, therefore a 62% overall efficiency.

For the whole SCR-CT run, there were 41.3 days scheduled (43.3 days total, but 48h were spent in beam studies). Therefore, the overall ABU was 60.7% (601h), or 60.1% (595h) if we account for the 6h of CPP trigger test (not part of the SRC-CT run). Assuming the usual 50% run efficiency and using the 21 pac days allocated to the experiment, SRC-CT gathered 118% of the expected data. As usual, this number is for accounting only and does not account for details, like data taking overhead higher than expected (e.g. due to radiator swaps, reducing the data taking efficiency), or the fact the SRC-CT run used a coherent enhancement that effectively favored better kinematics (increasing the data taking efficiency).