Difference between revisions of "Run Planning Meeting Notes, February 23 - February 28, 2023"

From GlueXWiki
Jump to: navigation, search
(Created page with "[https://jlab-org.zoomgov.com/j/1601990060?pwd=TUtwTGszMFg5bjhwdC9nU0IvREUzZz09 Zoom connect] Meeting ID: 160 199 0060 / Passcode 8394 [https://cebaf.jlab.org/files/ops/accbo...")
 
 
(74 intermediate revisions by the same user not shown)
Line 9: Line 9:
 
[https://halldweb.jlab.org/data_monitoring/run_statistics/RunPeriod-2023-01/index.html Integrated Trigger Count]
 
[https://halldweb.jlab.org/data_monitoring/run_statistics/RunPeriod-2023-01/index.html Integrated Trigger Count]
  
−
= Thursday February 23 =
+
 
 +
= Wednesday March 1 =
  
 
=== Past 24 hours ===
 
=== Past 24 hours ===
 
* Production runs
 
* Production runs
 +
* TAGM row-by-row scan
  
 
=== Shift Reports ===
 
=== Shift Reports ===
 +
[https://logbooks.jlab.org/entry/4140667 Early riser]
 +
[https://logbooks.jlab.org/entry/4140782 Day]
 +
[https://logbooks.jlab.org/entry/4140934 Swing]
 +
[https://logbooks.jlab.org/entry/4140988 Owl]
  
 
=== Reports ===
 
=== Reports ===
 +
*[https://logbooks.jlab.org/entry/4140983 CCAL check] (Sasha)
  
 +
=== Issues ===
 +
*[https://logbooks.jlab.org/entry/4140883 diagnosing problems in the TAGM readout] (Richard)
 +
** [https://logbooks.jlab.org/entry/4140969 TAGM row-by-row scan] (Richard)
 +
** [https://logbooks.jlab.org/entry/4140991 TAGM scalers using only row 4]
 +
** [https://logbooks.jlab.org/entry/4141000 turning off Vbias on rows 1-3 in TAGM] (Richard)
 +
** [https://logbooks.jlab.org/entry/4141052  Coherent peak after TAGM Vbias change]
 +
 +
=== 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 EPICS GUI)
 +
 +
 +
 +
= Tuesday February 28 =
 +
 +
=== Past 24 hours ===
 +
* Production runs
 +
* Down during day shift due to SL dropping to restricted access twice
 +
 +
=== Shift Reports ===
 +
[https://logbooks.jlab.org/entry/4139854 Early riser]
 +
[https://logbooks.jlab.org/entry/4140089 Day]
 +
[https://logbooks.jlab.org/entry/4140280 Swing]
 +
[https://logbooks.jlab.org/entry/4140504 Owl]
 +
 +
=== Reports ===
 +
*[https://logbooks.jlab.org/entry/4139919 NMR Probe Swap Out]
 +
*[https://logbooks.jlab.org/entry/4140160 CCAL chiller]
  
 
=== Issues ===
 
=== Issues ===
−
Pending:
+
* A couple of instances of the DAQ not stopping properly, requiring a reset/restart of the DAQ, after shift crew responding to DIRC tile alarms.
−
* [https://logbooks.jlab.org/entry/4117764 Start Counter (Beni)] - We do not understand why there is a mismatch in the software between start counter and tracking.
+
* Some runs missing from rcdb, corresponding in time to extended down time
−
* [https://logbooks.jlab.org/entry/4133378 TAGH hot channels w/ no beam]
+
* [https://logbooks.jlab.org/entry/4140732 FDCHit Wiretime- hot channel]
−
* [https://logbooks.jlab.org/entry/4133666 Noise in FDC2] (Lubomir)
+
* [https://logbooks.jlab.org/entry/4139902 Higher than normal TAGM baseline level] (Beni)
−
* [https://logbooks.jlab.org/entry/4133998 FCAL11 crate problems] (Sergey)
+
* [https://logbooks.jlab.org/comment/43723#comment-43723 Hot pixels in DIRC], [https://logbooks.jlab.org/entry/4140200 Update] (Justin)
−
** Network port on the fan tray for FCAL11 crate is not working. When we have an expected long downtime, this tray should be replaced (Chris Stanislav).
+
* [https://logbooks.jlab.org/entry/4140088 FCAL reset left base off briefly] (Mark D.)
 +
 
 +
=== 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 EPICS GUI)
 +
 
 +
= Monday February 27 =
 +
 
 +
=== Past 24 hours ===
 +
* Production runs
 +
 
 +
=== Shift Reports ===
 +
[https://logbooks.jlab.org/entry/4139267 Early riser]
 +
[https://logbooks.jlab.org/entry/4139451 Day]
 +
[https://logbooks.jlab.org/entry/4139629 Swing]
 +
[https://logbooks.jlab.org/entry/4139756 Owl]
 +
 
 +
=== Issues ===
 +
* There were multiple FCAL base lockups
 +
*[https://logbooks.jlab.org/entry/4139171 More on TAGM distribution]
 +
*[https://logbooks.jlab.org/entry/4139766 Tagger NMR probe not working again] (Hovanes)
 +
 
 +
= Sunday February 26 =
 +
 
 +
=== Past 24 hours ===
 +
* Production runs
 +
 
 +
=== Shift Reports ===
 +
[https://logbooks.jlab.org/entry/4138502 Early riser]
 +
[https://logbooks.jlab.org/entry/4138728 Day]
 +
[https://logbooks.jlab.org/entry/4138889 Swing]
 +
[https://logbooks.jlab.org/entry/4139072 Owl]
 +
 
 +
=== Reports ===
 +
* After coming back from the downtime due to the Hall-D dipole trip, the diamond needed to be realigned (thanks Hovanes for coming in to take care of this)
 +
** [https://logbooks.jlab.org/entry/4138755 Checking alignment of JD70-103 50um diamond]
 +
** [https://logbooks.jlab.org/entry/4138788 PARA and PERP for 0/90 after realignment]
 +
** [https://logbooks.jlab.org/entry/4138800 PARA and PERP for 45/135 after realignment]
 +
** [https://logbooks.jlab.org/entry/4138819 Scan result for TAGM:A:scaler_r1_wf_total_vs_ HD:GONI:Y.RBV_vs_ HD:GONI:X.RBV]
 +
** [https://logbooks.jlab.org/entry/4138821 Snapshot from XY goni scan]
 +
* [https://logbooks.jlab.org/entry/4139056 Initial checkout of newly installed CCAL] (Sasha)
 +
 
 +
=== Issues ===
 +
* CDC HV AI needed to be disabled
 +
* [https://logbooks.jlab.org/entry/4139001 Ratty TAGM distribution]
 +
* Same pending issues as before...
 +
 
 +
=== 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 EPICS GUI)
 +
 
 +
= Saturday February 25 =
 +
 
 +
=== Past 24 hours ===
 +
* Beam came back at about 5:40 am Saturday morning after long downtime due to Hall-D dipole over-temperature trip.
 +
 
 +
=== Shift Reports ===
 +
[https://logbooks.jlab.org/entry/4137977 Early riser]
 +
[https://logbooks.jlab.org/entry/4138174 Day]
 +
[https://logbooks.jlab.org/entry/4138323 Swing]
 +
[https://logbooks.jlab.org/entry/4138410 Owl]
 +
 
 +
=== Reports ===
 +
*[https://logbooks.jlab.org/entry/4138135 Further rho decay polarization results] (Alex A.)
 +
*[https://logbooks.jlab.org/entry/4138297 CCAL installed in hall]
 +
 
 +
=== Issues ===
 +
* Same pending issues as before...
 +
 
 +
=== 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 EPICS GUI)
 +
 
 +
= Friday February 24 =
 +
 
 +
=== Past 24 hours ===
 +
* Production runs
 +
* [https://logbooks.jlab.org/entry/4137815 Hall D dipole (ramp to tagger hall) trip due to over-temperature at about 21:47]
 +
 
 +
=== Shift Reports ===
 +
[https://logbooks.jlab.org/entry/4137188 Early riser]
 +
[https://logbooks.jlab.org/entry/4137394 Day]
 +
[https://logbooks.jlab.org/entry/4137664 Swing]
 +
[https://logbooks.jlab.org/entry/4137835 Owl]
 +
 
 +
=== Reports ===
 +
 
 +
* [https://logbooks.jlab.org/entry/4137324 Two FCAL bases replaced] (Mark D.)
 +
* [https://logbooks.jlab.org/entry/4137710 First look at 2023 beam polarization from rho decays] (Alex A.)
 +
 
 +
=== Issues ===
 +
 
 +
 
 +
*Pending:
 +
** [https://logbooks.jlab.org/entry/4117764 Start Counter (Beni)] - We do not understand why there is a mismatch in the software between start counter and tracking.
 +
** [https://logbooks.jlab.org/entry/4133378 TAGH hot channels w/ no beam]
 +
** [https://logbooks.jlab.org/entry/4133666 Noise in FDC2] (Lubomir)
 +
** [https://logbooks.jlab.org/entry/4133998 FCAL11 crate problems] (Sergey)
 +
 
 +
=== Plans ===
 +
* Completion of CCAL installation
 +
*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 EPICS GUI)
 +
 
 +
= Thursday February 23 =
 +
 
 +
=== Past 24 hours ===
 +
* Production runs
 +
* Cosmic run in raw mode when beam was down: Run 120800
 +
 
 +
=== Shift Reports ===
 +
[https://logbooks.jlab.org/entry/4136448 Early riser]
 +
[https://logbooks.jlab.org/entry/4136624 Day]
 +
[https://logbooks.jlab.org/entry/4136858 Swing]
 +
[https://logbooks.jlab.org/entry/4137001 Owl]
 +
 
 +
=== Reports ===
 +
* New prototype in PS test stand: [https://logbooks.jlab.org/entry/4136933] (Sasha)
 +
* CCAL ready for installation: [https://logbooks.jlab.org/entry/4136944] (Sasha)
 +
* [https://halldweb.jlab.org/data_monitoring/run_statistics/RunPeriod-2023-01/index.html Accumulated statistics]
 +
 
 +
=== Issues ===
 +
* gluon04 spontaneously rebooted itself...  which killed process providing main trigger rate to epics.
 +
* [https://logbooks.jlab.org/entry/4136974  DIRC LED Pulsers different from reference?] -- midway through run.
 +
* [https://logbooks.jlab.org/entry/4136669 TAGM waveforms] (Beni)
 +
* Quality of coherent peak?  Compare [https://logbooks.jlab.org/entry/4131776] from 2/15 and [https://logbooks.jlab.org/entry/4136910] from 2/22 and another for 45/135 perp: [https://logbooks.jlab.org/entry/4136947]
 +
 
 +
*Pending:
 +
** [https://logbooks.jlab.org/entry/4117764 Start Counter (Beni)] - We do not understand why there is a mismatch in the software between start counter and tracking.
 +
** [https://logbooks.jlab.org/entry/4133378 TAGH hot channels w/ no beam]
 +
** [https://logbooks.jlab.org/entry/4133666 Noise in FDC2] (Lubomir)
 +
** [https://logbooks.jlab.org/entry/4133998 FCAL11 crate problems] (Sergey)
  
−
=== Plans ===
+
=== Plans ===  
 +
* Completion of CCAL installation:  possible during MCC work in NL tomorrow morning ~8:30 for about an hour.
 +
*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 EPICS GUI)

Latest revision as of 07:50, 1 March 2023

Zoom connect Meeting ID: 160 199 0060 / Passcode 8394

MCC whiteboard

Hall D counting room white board

Spreadsheet with list of runs

Integrated Trigger Count


Wednesday March 1

Past 24 hours

  • Production runs
  • TAGM row-by-row scan

Shift Reports

Early riser Day Swing Owl

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 EPICS GUI)


Tuesday February 28

Past 24 hours

  • Production runs
  • Down during day shift due to SL dropping to restricted access twice

Shift Reports

Early riser Day Swing Owl

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 EPICS GUI)

Monday February 27

Past 24 hours

  • Production runs

Shift Reports

Early riser Day Swing Owl

Issues

Sunday February 26

Past 24 hours

  • Production runs

Shift Reports

Early riser Day Swing Owl

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 EPICS GUI)

Saturday February 25

Past 24 hours

  • Beam came back at about 5:40 am Saturday morning after long downtime due to Hall-D dipole over-temperature trip.

Shift Reports

Early riser Day Swing Owl

Reports

Issues

  • Same pending issues as before...

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 EPICS GUI)

Friday February 24

Past 24 hours

Shift Reports

Early riser Day Swing Owl

Reports

Issues

Plans

  • Completion of CCAL installation
  • 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 EPICS GUI)

Thursday February 23

Past 24 hours

  • Production runs
  • Cosmic run in raw mode when beam was down: Run 120800

Shift Reports

Early riser Day Swing Owl

Reports

Issues

Plans

  • Completion of CCAL installation: possible during MCC work in NL tomorrow morning ~8:30 for about an hour.
  • 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 EPICS GUI)
Retrieved from "https://halldweb.jlab.org/wiki/index.php?title=Run_Planning_Meeting_Notes,_February_23_-_February_28,_2023&oldid=119453"