Difference between revisions of "Run Coordinator report: winter 2023 w2"

From GlueXWiki
Jump to: navigation, search
Line 78: Line 78:
  
  
The main task during the RC week from 01/18-01/25/2023 was to align the diamond and start then production with linearly polarized photons. The diamond was aligned on Sunday (01/22/2023) and production started right after. The reason why alignment could not be done sooner is because of multiple issues with the accelerator. Wednesday, the beam was not available during the day for beam and RF study and a long recovery from these study: acceptable beam came back only Thursday at 1:10am. Hovanes, the expert aligning the diamond waited until 1am and left as the beam was still not there and it was getting too late to do the long work efficiently. We therefore took amorphous data in production configuration when the beam. Thursday, the beam was again taken way for RF study. The reason was that the accelerator could not reach the high currents required by the Hall A and C experiments. The beam came back around 17:30. Hovanes tried to see if he could align the 0/90 directions of the diamond, which he hoped would be quick to align since they were already aligned for the CPP/NPP experiments, but it turned out not the be the case and he realized he will have to redo the alignment from scratch. By the time, it was getting too late for such task. During Thursday night, we ran again on amorphous radiator, choosing to do one run on each of the 4 available Al. foils in order to check the dependence of the rates with radiator thickness. This was due to the rate appearing to be 30% larger than expected for our nominal current. (This was ultimately traced back to a BCM calibration problems, see below in the list of issues). Friday, the beam became unavailable again starting around 7:30am due to a vacuum issue in south linac.  
+
The main task during the RC week from 01/18-01/25/2023 was to align the diamond and start then production with linearly polarized photons. The diamond was aligned on Sunday (01/22/2023) and production started right after. The reason why alignment could not be done sooner is because of multiple issues with the accelerator. Wednesday, the beam was not available during the day for beam and RF study and a long recovery from these study: acceptable beam came back only Thursday at 1:10am. Hovanes, the expert aligning the diamond waited until 1am and left as the beam was still not there and it was getting too late to do the long work efficiently. We therefore took amorphous data in production configuration when the beam. Thursday, the beam was again taken way for RF study. The reason was that the accelerator could not reach the high currents required by the Hall A and C experiments. The beam came back around 17:30. Hovanes tried to see if he could align the 0/90 directions of the diamond, which he hoped would be quick to align since they were already aligned for the CPP/NPP experiments, but it turned out not the be the case and he realized he will have to redo the alignment from scratch. By the time, it was getting too late for such task. During Thursday night, we ran again on amorphous radiator, choosing to do one run on each of the 4 available Al. foils in order to check the dependence of the rates with radiator thickness. This was due to the rate appearing to be 30% larger than expected for our nominal current. (This was ultimately traced back to a BCM calibration problems, see below in the list of issues). Friday, the beam became unavailable again starting around 7:30am due to a vacuum issue in south linac. It came back Saturday at 2am. Hovanes was not available for Diamond alignment on Saturday, so it was postponed to Sunday and we did production on the amorphous radiator of the goniometer until Sunday 9am. Then Hovanes started diamond alignment. It was relatively quick, finishing by Sunday 17:30. Then we started production cycling over 0/90/45/135/amorphous and continued until the end of my RC tenure Wednesday, Jan. 25th.
  
  
= Monday January 23 =
+
Beside diamond alignement, the other special task done during the week (waiting for the aligned diamond to become available) was a long empty target run done during the Tuesday-Wednesday night. Its analysis shows the expected vertex distribution.  
=== Past 72 hours ===
+
* Beam was off from Friday 7:30am to Saturday 2am due to vacuum issue in south linac. Friday ABU: 4.0h
+
* Saturday: Ran on amorphous (goni), 300 nA. Until Sunday 9am when Hovanes started diamond alignment. Saturday ABU: 18.6h
+
* Sunday 9am-5:30pm: diamond alignment. '''Sunday 8:30pm - Monday 7:30am: First production 0/90/45/135/amo cycle''' (see [https://logbooks.jlab.org/entry/4115218 CBrem peak]). Then did Harp scans. Sunday ABU: 14.3h
+
  
=== Shift Reports ===
+
In all, the useful beam time (ABU) for the week was ***, and we lost about *** due to problem on our side (BANU).
* Day shift summary [https://logbooks.jlab.org/entry/4113703 Friday], [https://logbooks.jlab.org/entry/4114358 Saturday], [https://logbooks.jlab.org/entry/4114927 Sunday]
+
* Swing shift summary [https://logbooks.jlab.org/entry/4113892 Friday], [https://logbooks.jlab.org/entry/4114507 Saturday], [https://logbooks.jlab.org/entry/4115112 Sunday]
+
* Owl shift summary [https://logbooks.jlab.org/entry/4114007 Saturday], [https://logbooks.jlab.org/entry/4114730 Sunday], [https://logbooks.jlab.org/entry/4115243 Monday]
+
* Early Riser shift summary [https://logbooks.jlab.org/entry/4114137 Saturday], [https://logbooks.jlab.org/entry/4114774 Sunday], [https://logbooks.jlab.org/entry/4115380 Monday]
+
 
+
=== Reports ===
+
* [https://logbooks.jlab.org/entry/4114903 Diamond alignment (Hovanes)]. See also [https://logbooks.jlab.org/entry/4114981 here] and [https://logbooks.jlab.org/entry/4114995 here] and [https://logbooks.jlab.org/entry/4115071 here]
+
* [https://logbooks.jlab.org/entry/4113672 Empty target vertex reconstruction (Simon Taylor)]
+
* [https://logbooks.jlab.org/entry/4113681 TAGM check] and also [https://logbooks.jlab.org/entry/4114603 here] (Richard Jones)
+
* [https://logbooks.jlab.org/entry/4113756 DIRC LED performance (Bill)]
+
* [https://logbooks.jlab.org/entry/4114222 FCAL occupancy plots (Churaman)]
+
* [https://logbooks.jlab.org/files/2023/01/4114183/HarpScanResultsExtraPolation_01212023_churamani.pdf Harp scan Saturday morning]. Convergence does not look very good, but we decided to run this way for now (amorphous runs).
+
* [https://logbooks.jlab.org/entry/4114336 cdc currents (Beni)]
+
* [https://logbooks.jlab.org/entry/4114884 TOF timing resolution  (Beni)]
+
* [https://logbooks.jlab.org/entry/4115456 tagger field after power glicth (Alexandre Deur)]
+
 
+
=== Issues ===
+
* Numerous pressure alarms. [https://logbooks.jlab.org/entry/4114307 Sensor problem? Since Saturday morning, instruction from Lubomir are that we should only acknowledge the alarms. No need for stoping the ongoing run.] [https://logbooks.jlab.org/entry/4114263 See also here.] [https://logbooks.jlab.org/entry/4114344 The suspicious sensor has been removed from the alarm (Hovanes)]
+
* Beam energy oscillation investigation: Several accelerator experts are looking at it. No consensus whether it is real or not. Since it is at the MeV level, it should not be an issue for GlueX (but it is for accelerator).
+
* 30% increase in rates compared to Summer 2020 run period.
+
**[https://logbooks.jlab.org/entry/4113855 Yields after BCM recalibration (A. Deur)]
+
** Edy (Hall D Accelerator contact) has been asked to follow up on the issue.
+
* Target control issue.
+
**[https://logbooks.jlab.org/entry/4113961 Target communication lost around 1pm Friday]. [https://logbooks.jlab.org/entry/4113908 Alarm acknowledged by shift crew without action or calling expert. New shift noticed this and called Hovanes.] Hovanes informed Alexandre who checked what was the issue and call then Chris Carlin. Chris C. could not come (catching a flight at the airport) but instructed the crew to switch the the back-up IOC, which apparently fixed the issue. However, the controlled came back in a confused state (Full but with heater on, an incompatible situation) so Alexandre informed Chris Keith [https://logbooks.jlab.org/entry/4113972 who went in (beam was off for repair during the whole event) with the shift leader (Dene) and partly fixed the issue by switching the target to local control.]
+
**We can monitor the target, but not control it remotely (switch empty <=> full). For the moment, this is not a crucial problem.
+
* Numerous DIRC alarms Saturday, see [https://logbooks.jlab.org/entry/4114519 this entry], [https://logbooks.jlab.org/entry/4114518 this one], and the comments in the [https://logbooks.jlab.org/entry/4114358 day] and [https://logbooks.jlab.org/entry/4114507 swing] shift summaries.
+
 
+
=== Plans ===
+
* Production on amorphous (Goni, 300 nA) until the diamond is aligned.
+
* Diamond alignment: Sunday morning, ~9am. (Hovanes)
+
* Then production on diamond radiator, 4 orientations + amo. 300 nA. Presently, we do each orientation once (not twice) and each run is nominally 2h, including the amo run.
+
* Tomorrow (Tuesday, 24th: 4h of beam studies + 2h beam restoration):
+
** ?Safety Walkthrough (M. Dalton + trainee(s))?
+
** Scot to access to take out Vlad's chiller
+
** ?Investigate the faulty pressure sensor?
+
** ?Chris Carlin to fix the target controls?
+
* [https://halldweb.jlab.org/wiki/index.php/Run_Coordination_Meetings:Spring2023#Runplan Link to runplan]
+
 
+
 
+
 
+
Beside diamond alignement, the other special task done during the week (waiting for the aligned diamond to become available) was a long empty target run done during the Tueaday-Wednesday night. Its analysis shows the expected vertex distribution.
+
 
+
In all, ABU***
+
  
 
Significant issues discovered during the week were:
 
Significant issues discovered during the week were:
 
* The calibration of our BCM differed by 30% compared to the run in 2020. Discussions with Ops revealed that the BCM calibration (called BLA calibration) is not done systematically before each run period and the last one was done in 2021. We discussed with Ops to ensure that it should now be done at each start of new run period. We did the BLA calibration on Thursday, 01/24/2023;
 
* The calibration of our BCM differed by 30% compared to the run in 2020. Discussions with Ops revealed that the BCM calibration (called BLA calibration) is not done systematically before each run period and the last one was done in 2021. We discussed with Ops to ensure that it should now be done at each start of new run period. We did the BLA calibration on Thursday, 01/24/2023;
 
*The Start Counter was effectively (but not physically) rotated by about 90 degree;
 
*The Start Counter was effectively (but not physically) rotated by about 90 degree;
*Loss of communication with the target: for a few days, it could be only locally controlled;  
+
*Loss of communication with the target: for a few days, it could be only locally controlled: we could monitor the target, but not control it remotely (switch empty <=> full).This is not a crucial problem since there was no need to empty the target during that week;  
 
*Loss of communication with the TAGH high voltage crate.
 
*Loss of communication with the TAGH high voltage crate.
 +
*DIRC issues.
  
 
Smaller issues beside the usual running woes such as DAQ or FADC troubles, included  discovering beam energy modulations of a few MeV due to artifacts in BPMs, the pressure sensor for the CDC producing unphysical spikes and triggering alarms (the sensor information was temporarily removed from the alarm). When it was inspected during an access, found hanging. After being put back and shielded from winds, the spikes disappeared.
 
Smaller issues beside the usual running woes such as DAQ or FADC troubles, included  discovering beam energy modulations of a few MeV due to artifacts in BPMs, the pressure sensor for the CDC producing unphysical spikes and triggering alarms (the sensor information was temporarily removed from the alarm). When it was inspected during an access, found hanging. After being put back and shielded from winds, the spikes disappeared.

Revision as of 10:09, 29 January 2023

Wednesday January 24

Past 24 hours

  • Beam study, with Hall D access. Then, production on diamond. ABU= 12.2 h for the day.

Shift Reports

Reports

Issues

Plans

  • Production (300 nA, 2h runs) with cycle:
    • 2 runs para(0/90)
    • 2 runs perp(0/90)
    • 2 runs para(45/135)
    • 2 runs perp(45/135)
    • 1 run amo (use it to rejuvenate amo reference in CBREM GUI)
  • Trigger fine tuning Thursday? (A. Somov)

Tuesday January 24

Past 24 hours

  • Production on diamond. Trippy beam, but good availability. ABU=16.2h for the day

Shift Reports

Reports

Issues

Plans

  • 4h of beam studies + 2h beam restoration). Tagger and Hall to be surveyed around 9pm:
    • Safety Walkthrough (M. Dalton + trainee(s))?
    • Scot to access to take out Vlad's chiller
    • Tagger access for HV communication issue?
    • Investigate the faulty pressure sensor?
    • Chris Carlin to fix the target controls
  • Production (300 nA, 2h runs) with cycle:
    • 2 runs para(0/90)
    • 2 runs perp(0/90)
    • 2 runs para(45/135)
    • 2 runs perp(45/135)
    • 1 run amo



The main task during the RC week from 01/18-01/25/2023 was to align the diamond and start then production with linearly polarized photons. The diamond was aligned on Sunday (01/22/2023) and production started right after. The reason why alignment could not be done sooner is because of multiple issues with the accelerator. Wednesday, the beam was not available during the day for beam and RF study and a long recovery from these study: acceptable beam came back only Thursday at 1:10am. Hovanes, the expert aligning the diamond waited until 1am and left as the beam was still not there and it was getting too late to do the long work efficiently. We therefore took amorphous data in production configuration when the beam. Thursday, the beam was again taken way for RF study. The reason was that the accelerator could not reach the high currents required by the Hall A and C experiments. The beam came back around 17:30. Hovanes tried to see if he could align the 0/90 directions of the diamond, which he hoped would be quick to align since they were already aligned for the CPP/NPP experiments, but it turned out not the be the case and he realized he will have to redo the alignment from scratch. By the time, it was getting too late for such task. During Thursday night, we ran again on amorphous radiator, choosing to do one run on each of the 4 available Al. foils in order to check the dependence of the rates with radiator thickness. This was due to the rate appearing to be 30% larger than expected for our nominal current. (This was ultimately traced back to a BCM calibration problems, see below in the list of issues). Friday, the beam became unavailable again starting around 7:30am due to a vacuum issue in south linac. It came back Saturday at 2am. Hovanes was not available for Diamond alignment on Saturday, so it was postponed to Sunday and we did production on the amorphous radiator of the goniometer until Sunday 9am. Then Hovanes started diamond alignment. It was relatively quick, finishing by Sunday 17:30. Then we started production cycling over 0/90/45/135/amorphous and continued until the end of my RC tenure Wednesday, Jan. 25th.


Beside diamond alignement, the other special task done during the week (waiting for the aligned diamond to become available) was a long empty target run done during the Tuesday-Wednesday night. Its analysis shows the expected vertex distribution.

In all, the useful beam time (ABU) for the week was ***, and we lost about *** due to problem on our side (BANU).

Significant issues discovered during the week were:

  • The calibration of our BCM differed by 30% compared to the run in 2020. Discussions with Ops revealed that the BCM calibration (called BLA calibration) is not done systematically before each run period and the last one was done in 2021. We discussed with Ops to ensure that it should now be done at each start of new run period. We did the BLA calibration on Thursday, 01/24/2023;
  • The Start Counter was effectively (but not physically) rotated by about 90 degree;
  • Loss of communication with the target: for a few days, it could be only locally controlled: we could monitor the target, but not control it remotely (switch empty <=> full).This is not a crucial problem since there was no need to empty the target during that week;
  • Loss of communication with the TAGH high voltage crate.
  • DIRC issues.

Smaller issues beside the usual running woes such as DAQ or FADC troubles, included discovering beam energy modulations of a few MeV due to artifacts in BPMs, the pressure sensor for the CDC producing unphysical spikes and triggering alarms (the sensor information was temporarily removed from the alarm). When it was inspected during an access, found hanging. After being put back and shielded from winds, the spikes disappeared.