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

From GlueXWiki
Jump to: navigation, search
(Created page with "= 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 === * [https://logboo...")
 
Line 98: Line 98:
  
 
=== Issues ===
 
=== Issues ===
−
* 2 RC volunteers were needed (one for Beni's RC week because of his surgery, and another for Susan S's week because she had to cancel her trip to the US). Hovanes and Simon volunteered to cover the two weeks.
 
 
* 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)]
 
* 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).  
 
* 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).  
Line 138: Line 137:
 
*[https://logbooks.jlab.org/entry/4113630 Difference in Shape of Reconstructed photon beam energy with different AMO radiators (Churamani Paudel)]
 
*[https://logbooks.jlab.org/entry/4113630 Difference in Shape of Reconstructed photon beam energy with different AMO radiators (Churamani Paudel)]
  
−
=== Issues ===
 
−
* [https://logbooks.jlab.org/entry/4113047 Beam energy oscillation investigation (M. Tiefenback)]. Summary: Mike T. suspects the oscilations are not real but he is asking confirmation/advice from the system experts.
 
−
*[https://logbooks.jlab.org/entry/4113408 Tim W. reminder on acknowledging alarms]
 
−
* [https://logbooks.jlab.org/entry/4113027 HVB currents look high] and [https://logbooks.jlab.org/entry/4113590 follow-up] (Naomi)
 
−
* 30% increase in rates compared to Summer 2020 run period.
 
−
**[https://logbooks.jlab.org/entry/4111933 Original finding by A. Somov]
 
−
**[https://logbooks.jlab.org/entry/4113029 Comparison of 2020 and 2023 for TAGH rates (A. Deur)]
 
−
**[https://logbooks.jlab.org/entry/4113193 Check that TAGH counters scale with (A. Deur)]
 
−
**[https://logbooks.jlab.org/entry/4113098 rho and pi0 yields (A. Austregesilo)]
 
−
**[https://logbooks.jlab.org/entry/4113253 BCM/FCup calibration suggested by the PD], [https://logbooks.jlab.org/entry/4113276 its results] and [https://logbooks.jlab.org/entry/4113408 follow-up].
 
−
**[https://logbooks.jlab.org/entry/4113656 the rate discrepancy after BCM/FCup calibration has been reduced by half (A. Deur)]
 
−
**[https://logbooks.jlab.org/entry/4113580 Ran overnight on different amo radiators]
 
  
−
=== Plans ===
 
−
* Thursday evening and Friday night:
 
−
**Once beam come back, do Harp scans.
 
−
**FCup test of our beam dump BCM.
 
−
**Run 1h on the amo radiator of the goni (baseline for next runs below). 250 nA
 
−
**Run 2h on 0.19E-4 RL amo radiator on radiator ladder (250 nA).
 
−
**Run 2h on 1.12E-4 RL amo radiator on radiator ladder (250 nA).
 
−
**Run (until the beam is taken away in the morning) on 3.4E-4 RL amo radiator on radiator ladder (250 nA).
 
−
* Beam off starting Friday morning around 7:30am [https://logbooks.jlab.org/entry/4113148 to fix vacuum issue in south linac], until 4pm(?).
 
−
*When the beam comes back:
 
−
**Harp scans
 
−
<!--**BCM comparison (~15min, invasive to other halls). PD (Joe Grames) recommends comparing (not calibrating) the Hall D MPS BCM against the injector Faraday Cup #2:  To do this:
 
−
***Turn off beam to other halls
 
−
***Close chopping aperture to other halls
 
−
***Send beam to FC#2, use an upstream corrector to convince oneself it is centered (max current)
 
−
***Send current to FC#2 (record it), then pull cup and go to Hall D (record it). Repeat for several current values: 0, 50, 100, 150, 200, 250, 300, 350, 400 and 450 nA.
 
−
***Restore the upstream corrector -->
 
−
**Production on goni amo radiator at 300 nA until Sunday morning.
 
−
* Hall access:
 
−
**Sergey F.
 
−
* Diamond alignment: Sunday morning, ~9am.
 
−
* Until then production on amorphous.
 
−
* [https://halldweb.jlab.org/wiki/index.php/Run_Coordination_Meetings:Spring2023#Runplan Link to runplan]
 
  
  
−
 
+
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 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  
+
−
 
+
−
and Friday.
+
  
 
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.  
 
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.  
  
−
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.
+
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.
−
=== Plans ===
+
−
* Beam off starting around 10am for RF study, nominally until 4pm+/-4h.
+
−
* Hall in controlled access?
+
−
* Diamond alignment: Friday day ? (Hovanes unavailable today)
+
−
* Until Friday day, production on amorphous?
+
−
* [https://halldweb.jlab.org/wiki/index.php/Run_Coordination_Meetings:Spring2023#Runplan Link to runplan]
+

Revision as of 09:50, 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

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

Friday January 20

Past 24 hours

Shift Reports

Reports



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.

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