Run Planning Meeting Notes, Jan 25-Jan 31, 2018
From GlueXWiki
<- Back to Run Coordination Meetings:Fall2017 Spring2018 Run
Monday, January 29
- Notes from the previous 24 hours:
- "The machine was rather trippy" (MCC quote), with persistent BLM trips.
- NN hours of actual beam per MCC in the last 24 hours.
- ABU NN hoours, BANU NN hours.
- NN B events collected. Total: Spreadsheet: number of triggers.
- There were 2 minutes of 150nA beam with no radiator to study the chamber currents.
- Issues:
- FDC2 HV tripped without alarm [1]. For an hour, data were taken with FDC2 cell6 off.
- No monitoring plots in logbook during day shift.
- More on TAGM scaler trouble.
- Short term run plan:
- Harp scan then production.
- Hall access for FCAL?
- Empty target: Tue evening after beam studies, or Wed morning before TAC run?
- Run plan chart: Week 3
- Reports:
Sunday, January 28
- Notes from the previous 48 hours:
- Beam ran smoothly for most of the last 2 days. According to MCC calculations, they delivered 37 hours of actual beam in the last 48 hours. They even proudly posted this: A good hour of beam
- Friday ABU 12.9, BANU 4.8. Saturday ABU 14.8, BANU 4.0
- About 3.8 B triggers in the last 2 days. Total: Spreadsheet: number of triggers.
- 2 hours of 300nA AMO run.
- Trigger rate >65kHz, event rate 65kHz, L.T. 96% but with DAQ crashes every 10 minutes.
- Both CDC and FDC were not tripping HV at 300nA. Currents in both chambers scaled well with the beam current but only FDC current scaled with 2 different AMO radiators.
- TOF rate was reaching 2.2 MHz. Impact on signal magnitude is yet to be studied.
- TPOL access for 4 hours. Apparently, the noise issue has been fixed. fADC baselines were recalibrated.
- Fixed TAGM cabling for channels 19 and 21. Translation table was updated [2]
- Issues:
- Low level monitoring.
- TPOL dead channel or not dead?
- TAGM ch.19 is back but ch. 21 is still empty in the latest histos.
- An epic fight with TAGM scalers and CBREM gui overnight [3], [4], [5], [6], [7], [8]
- gluonraid3/gluonraid4 switching [9], [10]
- BTA is still unreliable. Hovanes has fixed a bug. However, occasionally, BNA is still counted as BANU [11].
- Harp scan was forgotten on Saturday.
- Short term Run plan:
- Production, production, production
- Short Hall access for TPOL dead channel and FCAL bases during either Hall C pass change or beam studies.
- Empty target run: before or after beam studies?
- Run plan chart: Week 3
- Reports:
Friday, January 26
- 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 [14].
- Accelerator went down at 5:20am to investigate A -> C bleed-thru. We got beam back at 8am.
- ABU 15.2 hrs (5.6+5.1+4.5), BANU 3.5 hrs (2.3+0.6+0.6) for the last 3 shifts
- About 2.4B triggers collected. Total: Spreadsheet: number of triggers.
- Issues:
- Hall D tagger credited control expires at midnight tonight
- Switched to a different gateway for data transfer from Hall to CC [15].
- 20 minutes have been lost on recovering TAGM after bias voltage incident.
- At 2:15pm the beam went off for 45 minutes [16] but we were charged BANU for 45 minutes [17]?
- RootSpy and HLDetectorTiming plugin [18], [19].
- Plan for today:
- 300nA AMO run together with L1 study from 8am until 10am.
- Controlled access (with TPOL RADCON sweep) at 10am for:
- RADCON test
- TPOL noise
- TAGM cable connection
- Return to production after that.
- Possible Saturday morning access as well.
- Run plan chart: Week 3
- Reports:
- Weekend meeting?
Thursday, January 25
- 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
- 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: [20]
- TAGM voltages
- Any other issues?
- 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 TAGM channels.
- Possible Saturday morning access as well.
- Run plan chart: Week 3
- Reports: