Difference between revisions of "Run Planning Meeting Notes, Feb 1-Feb 7, 2018"

Revision as of 08:14, 5 February 2018

<- Back to Run Coordination Meetings:Fall2017 Spring2018 Run

Monday, February 5

1. Notes from the previous 24 hours:
   • South Linac down for ~5 hrs due to CHL issue
   • Beam unstable and position Y position drifting overnight
   • Spreadsheet: number of triggers
   • Low level monitoring
2. Today's access (starting at 7 am):
   • Re-installation of the muon chamber (at least 2 hours with 3+ people)
   • FCAL base maintenance (1-2 hours for base replacement + 1-2 hours for each channel tests)
   • TPOL sector 3 investigation
   • TAGM light leak test for columns 82-84 (2+ hours)
   • CDC bubbler evaluation and re-fill
   • Profiler radiator changed (Pb -> Al?)
   • Walkthrough for Ahmed
3. Issues:
   • Radiator ID in RCDB?
   • Edge drifts with Y position
   • Process for changes to production configuration (discussion):
4. Today's run plan Google Calendar:
   • Hall Access (unknown duration)
   • Production running
5. Reports:
   • PS enhancements after retune and CBSA polarization vs run number
   • Empty target analysis
   • rho asymmetry update
   • DAQ test at 300 nA
6. Standing issues:
   • Rate evolution: Work ongoing to compare rho yields to PS flux before and after "step" in PS rate.
   • TPOL analysis status?

Sunday, February 4

1. Notes from the previous 48 hours:
   • Friday day shift: L1 trigger studies (~2 hrs) for min-bias trigger and high rate DAQ test (~1.5 hrs)
   • Saturday AM: South Linac down for ~4 hrs
   • After South Linac recovers, harp scans show beam convergence at collimator looks good.
   • Spreadsheet: number of triggers: ~4 B triggers in last 2 days.
   • Low level monitoring
2. Tomorrow's potential access (7 am Monday):
   • Re-installation of the muon chamber
   • FCAL base maintenance
   • TPOL sector 3 investigation
   • CDC bubbler evaluation and re-fill
   • Walkthrough for Ahmed
3. Issues:
   • CDC-FDC pressure dip followup
   • AD00 ~4 minute oscillation: appears to be "fixed"
   • 5C11B Y position still wandering at times
   • Approval process for changes to production configuration?:
     • CDC readout thresholds
     • TAGM trigger thresholds
4. Today's run plan Google Calendar:
   • Production running
5. Reports:
   • PS enhancements after retune
   • Empty target analysis
   • rho asymmetry update
   • DAQ test at 300 nA
6. Standing issues:
   • Rate evolution: Work ongoing to compare rho yields to PS flux before and after "step" in PS rate.
   • TPOL analysis status?

Friday, February 2

1. Notes from the previous 24 hours:
   • Harp scans around 2 pm found the beam was significantly over-focused in y. Around the same time MCC decided to retune the beam.
   • After beam tuning in the afternoon, harp scans around 8 pm showed convergence at the collimator is better
   • 12.6 hours of CW beam. ABU: 10.9 hrs (3.2+1.7+6.0), BANU: 1.7 hrs (0.3+0.7+0.7), BNA: 11.3 hrs (4.5+5.6+1.2)
   • Spreadsheet: number of triggers.
   • Low level monitoring
2. Issues:
   • CDC-FDC Pressure dip and Beni's followup -> opportunistic access?
   • 5C11B Y position wandering
   • Coherent edge fitting: New amorphous reference to be taken this morning. ROOTSpy should use 41180 from last night.
   • ROOTSpy Modification
   • New "5 DC" DAQ default configuration
3. Today's run plan Google Calendar:
   • Production running
   • 10 am: Min-bias trigger setup (Sasha)
   • 11:30 am: High intensity test (Sergey)
4. Reports:
   • ρ asymmetry (offline monitoring ver06)
5. Standing issues:
   • Rate evolution: Work ongoing to compare rho yields to PS flux before and after "step" in PS rate.
   • Polarization status?
6. Beam Time Accounting (BTA) discussion:
   • 3 possible conditions:
     • ABU: Available Beam Used
     • BANU: Beam Available [to the Hall] but Not Used [by the Hall]
     • BNA: Beam Not Available [to the Hall]
   • Automated procedure in MCC for populating BTA have not been very reliable
   • Proposal from Mark D:
     • Shift leader should record the integrated time that we request no beam (for example changing the radiator or other experiment downtime). When submitting the BTA form, the shift leader should check that the BANU and BNA numbers are correct (ie. BANU does not exceed the integrated time we request no beam). If they are not correct, the shift leader should move all the time that is listed under BANU into the BNA column unless they specifically requested no beam from MCC.

Thursday, February 1

1. Notes from the previous 24 hours:
   • After empty target run, beam intermittent. Trouble setting up V-wire TAC run, due to lock on Active Collimator not providing consistent TAC rate.
   • 8 PM start production TAC run with lock on Beam Profiler. TAC rate initially at ~200 kHz, but dropped to 100 kHz overnight.
   • 5:30 AM stopped the TAC run and switch to production: target filled, beamline back in production configuration and production run started.
   • 16.1 hours of CW beam. ABU: 14.4 hrs (4.9+3.5+6.0), BANU: 1.7 hrs (0.1+0.8+0.8)
   • Spreadsheet: number of triggers.
   • Low level monitoring
2. Issues:
   • Missing BCAL LED triggers and Random pulser (Run 41172)
   • TAC setup
   • TPOL dead channel.
3. Run plan for this week:
   • Low intensity runs planned for tonight: what is the status of min-bias triggers?
4. Today's run plan:
   • At 9 AM (or after run production run 41172):
     • Harp scans by MCC and Hall D (Hovanes on shift)
   • Production running the rest of the day
5. Reports:
   • Preliminary PS acceptance
   • Statistics from RCDB
6. Standing issues:
   • Rate evolution: Work ongoing to compare rho yields to PS flux before and after "step" in PS rate.
   • Polarization status? Came up at MCC meeting, Eugene suggested to report next week.