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

From GlueXWiki
Jump to: navigation, search
Line 73: Line 73:
 
**2 runs perp(45/135)
 
**2 runs perp(45/135)
 
**1 run amo
 
**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.
 +
  
 
= Monday January 23 =
 
= Monday January 23 =
Line 119: Line 126:
 
* [https://halldweb.jlab.org/wiki/index.php/Run_Coordination_Meetings:Spring2023#Runplan Link to runplan]
 
* [https://halldweb.jlab.org/wiki/index.php/Run_Coordination_Meetings:Spring2023#Runplan Link to runplan]
  
−
= Friday January 20 =
 
−
=== Past 24 hours ===
 
−
* Ran on amorphous radiator (250 nA) until 10am. Then, beam was taken away for [https://logbooks.jlab.org/entry/4113138 RF work (high current push for Halls A and C)]. Beam came back around 5:30pm. We did harp scans, a BCM/FCup calibration, and then [https://logbooks.jlab.org/entry/4113378 ran on various amorphous radiators during the night] and [https://logbooks.jlab.org/entry/4113552 early morning]. ABU= 11.5h for the day
 
−
* Several accesses done during the day:
 
−
** Sasha (FADC replacement for TOF)
 
−
** Sergey
 
  
−
=== Shift Reports ===
 
−
* [https://logbooks.jlab.org/entry/4112998 Day shift summary]
 
−
* [https://logbooks.jlab.org/entry/4113173 Swing shift summary]
 
−
* [https://logbooks.jlab.org/entry/4113378 Owl shift summary]
 
−
* [https://logbooks.jlab.org/entry/4113552 Early Riser shift summary]
 
  
−
=== Reports ===
+
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.  
−
* [https://logbooks.jlab.org/files/2023/01/4113248/harpscan20230119-1815.pdf Harp scans.] Sigma_y is too wide=> too wide photon beam spot (magenta). Okay for now (unpolarized beam)?
+
−
* [https://logbooks.jlab.org/entry/4112963 TOF calibration (Beni)], [https://logbooks.jlab.org/entry/4113076 FADC replacement for TOF (A. Somov)]
+
−
*[https://logbooks.jlab.org/entry/4113630 Difference in Shape of Reconstructed photon beam energy with different AMO radiators (Churamani Paudel)]
+
  
 +
In all, ABU***
  
 +
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;
 +
*Loss of communication with the TAGH high voltage crate.
  
−
 
+
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.
−
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. 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 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***
+
−
 
+
−
A significant issue discovered during the week was that 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. It was also discovered that the Start Counter was effectively (but not physically) rotated by about 90 degree. 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:02, 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.


Monday January 23

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 CBrem peak). Then did Harp scans. Sunday ABU: 14.3h

Shift Reports

Reports

Issues

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?
  • 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:

  • 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;
  • Loss of communication with the TAGH high voltage crate.

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.

Retrieved from "https://halldweb.jlab.org/wiki/index.php?title=Run_Coordinator_report:_winter_2023_w2&oldid=118684"