Difference between revisions of "Run Planning Meeting Notes, Jan 25-Jan 31, 2018"
From GlueXWiki
m |
m |
||
Line 8: | Line 8: | ||
#* We switched to production running at 7pm and has been taking production data since then. | #* We switched to production running at 7pm and has been taking production data since then. | ||
#* ABU (0.7+3.5+), BANU (0+0.3) for the last 3 shifts | #* ABU (0.7+3.5+), BANU (0+0.3) for the last 3 shifts | ||
− | #* About xxxN triggers collected. | + | #* About xxxN triggers collected. Total: [https://docs.google.com/spreadsheets/d/1NffTc4-S5PbTMSuH_pp7ZYsGRH4JC_WSVo770_iJYt0/edit#gid=1635471172 Spreadsheet: number of triggers] |
# Issues: | # 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.) | #* 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.) | ||
Line 14: | Line 14: | ||
#* Once, a coherent edge had to be nudged by more than 50 MeV. | #* 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: [https://logbooks.jlab.org/files/2018/01/3520512/BCAL_Timing.png] | #* BCAL ADC/TDC timing offsets jumped by 32 ns for some modules: [https://logbooks.jlab.org/files/2018/01/3520512/BCAL_Timing.png] | ||
+ | #* Low level monitoring | ||
+ | #* Any other issues? | ||
+ | # Short term run plan: | ||
+ | #* 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 restricted access to fix TPOL noise issue. | ||
+ | #* Simultaneous tagger hall access to fix bad TAGH channels. | ||
+ | #* Possible Saturday morning access as well. | ||
+ | #* TAC run will happen either next Monday (if no pass changes on this day), or next Wednesday (more likely). |
Revision as of 08:30, 25 January 2018
<- Back to Run Coordination Meetings:Fall2017 Spring2018 Run
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 (0.7+3.5+), BANU (0+0.3) for the last 3 shifts
- About xxxN 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: [1]
- Low level monitoring
- Any other issues?
- Short term run plan:
- 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 restricted access to fix TPOL noise issue.
- Simultaneous tagger hall access to fix bad TAGH channels.
- Possible Saturday morning access as well.
- TAC run will happen either next Monday (if no pass changes on this day), or next Wednesday (more likely).
- 2 hours of AMO 300nA running tomorrow morning.