Difference between revisions of "Run Planning Meeting Notes, Jan 25-Jan 31, 2018"

Revision as of 07:25, 26 January 2018

<- Back to Run Coordination Meetings:Fall2017 Spring2018 Run

Friday, January 26

1. Notes from the previous 24 hours:
   • Beam was mostly up and we were taking production data.
   • From 6pm till 7:30pm, the beam was off to switch Hall B to 5-pass run.
   • At about the same time, 22.5uA were turned on for Hall A.
   • The beam was acceptable but not as good as before [1].

1. • ABU 10.5 hrs (0.7+3.5+6.3), BANU 0.8 hrs (0+0.3+0.5) for the last 3 shifts
   • About 1.2 B triggers collected. Total: [https://docs.google.com/spreadsheets/d/1NffTc4-S5PbTMSuH_pp7ZYsGRH4JC_WSVo770_iJYt0/edit#gid=1635471172 Spreadsheet: number of

1. Issues:
   • 20 minutes have been lost on recovering TAGM after bias voltage incident.
   • 45 minutes have been lost on starting the run too late after the beam came back [2], [3].

Thursday, January 25

1. Notes from the previous 24 hrs:
   • Beam was off from 9am till 5:20 pm. At the end, Hall A was able to get their 22.5 uA current. Since then, beam was relatively stable.
   • Upon return of the beam, a harp scan was performed: MCC and Our harp. Beam seems to be acceptable.
   • After harp scan, about an hour has been spent on trigger and DAQ studies by Sasha and Sergei.
   • We switched to production running at 7pm and has been taking production data since then.
   • ABU 10.5 hrs (0.7+3.5+6.3), BANU 0.8 hrs (0+0.3+0.5) for the last 3 shifts
   • About 1.2 B triggers collected. Total: Spreadsheet: number of triggers
2. Issues:
   • A couple of hours of beam time has been lost on fighting with DAQ while starting the next run (java out of memory, rebooting rocks, etc.)
   • Sometime, a histogram or two would disappear in rootspy and reappear after monitoring restart.
   • Once, a coherent edge had to be nudged by more than 50 MeV.
   • BCAL ADC/TDC timing offsets jumped by 32 ns for some modules: [4]
   • TAGM voltages
   • Any other issues?
3. Short term run plan:
   • TAC run: should we do it today (Halls A and C are down)?
   • 2 hours of AMO 300nA running tomorrow morning.
     • Would it be better to start it at 7am or 8am?
     • Are any configuration changes necessary (HV, etc.)?
     • Who needs to be here for such run?
     • RADCON will follow this run with their Fast access study.
   • Consequent Hall controlled access to fix TPOL noise issue.
   • Simultaneous tagger hall access to fix bad TAGH channels.
   • Possible Saturday morning access as well.
   • Run plan chart: Week 3
4. Reports:
   • Low level monitoring
   • Polarization check