Difference between revisions of "Run Planning Meeting Notes, Jan 25-Jan 31, 2018"
From GlueXWiki
m |
m |
||
(19 intermediate revisions by the same user not shown) | |||
Line 1: | Line 1: | ||
<- Back to [[Run Coordination Meetings:Fall2017 Spring2018 Run]] | <- Back to [[Run Coordination Meetings:Fall2017 Spring2018 Run]] | ||
+ | |||
+ | == Wednesday, January 31 == | ||
+ | # Notes from the previous 24 hours: | ||
+ | #* After pass change, we got beam at 12:30 pm. It was reasonably stable except for 2 hours downtime at midnight. We were running production until 6am. | ||
+ | #* MCC kept tuning beam for Hall C until 8pm when they achieved 5/5.5 pass CW beam to all 4 halls [https://logbooks.jlab.org/entry/3524206]. | ||
+ | #* 14.7 hours of CW beam. BAU: 13.8 hrs (3.7+5.6+4.5), BANU: 0.9 hrs (0.5+0.1+0.3) | ||
+ | #* Richard did TAGM HV scan and some other TAGM work. | ||
+ | #* Started empty target set of runs at 6am. Rate is ~15kHz. | ||
+ | #* ~1.9 B triggers collected. | ||
+ | #* Total: [https://docs.google.com/spreadsheets/d/1NffTc4-S5PbTMSuH_pp7ZYsGRH4JC_WSVo770_iJYt0/edit#gid=1635471172 Spreadsheet: number of triggers]. | ||
+ | #* We have first entries in [https://logbooks.jlab.org/book/hddirc HDDIRC] logbook! | ||
+ | # Issues: | ||
+ | #* [https://logbooks.jlab.org/entry/3524119 Low CO2] | ||
+ | #* [https://logbooks.jlab.org/entry/3524483 Low level monitoring] | ||
+ | #* TPOL dead channel [https://logbooks.jlab.org/files/2018/01/3524384/rs_page13.png is back]. | ||
+ | #* TAGM seems to be [https://logbooks.jlab.org/files/2018/01/3524384/rs_page15.png heading back] to its state a few days ago. | ||
+ | #* [https://logbooks.jlab.org/entry/3523981 Beam convergence] still needs improvement [https://logbooks.jlab.org/entry/3524063]. | ||
+ | # Short term run plan: | ||
+ | #* At 6 AM: | ||
+ | #** Stop current run. Change DAQ config to raw mode and start a new run. | ||
+ | #** Start emptying the target. | ||
+ | #** When the target is empty, stop the run (~20 minutes). | ||
+ | #** Take beam away. Put goniometer in blank. Ask for 150nA beam. After 2 minutes of beam, take it away. | ||
+ | #** Close a collimator. Ask for 150nA beam. After 2 minutes of beam, take it away. | ||
+ | #** Put collimator back to 5mm. Set goniometer back to the previous diamond. Ask for 150 nA beam. | ||
+ | #** Reconfigure DAQ for a normal (not raw) mode. Start an empty target run for 2 hours. | ||
+ | #* At about 9am, we'll proceed to TAC run. | ||
+ | #* After TAC, another raw mode run when the target is being filled. BTA 5nA threshold? | ||
+ | #* A Harp scan after empty target run. | ||
+ | #* Then back to production. | ||
+ | #* [https://halldweb.jlab.org/wiki/images/3/31/Spring18_week3.jpg Run plan chart: Week 3] | ||
+ | # Reports: | ||
+ | #* [https://logbooks.jlab.org/entry/3524060 Rate evolution] | ||
+ | |||
+ | |||
== Tuesday, January 30 == | == Tuesday, January 30 == | ||
Line 20: | Line 55: | ||
#* Do we need the (extended) harp scan after pass change (previous one was 12 hours ago)? | #* Do we need the (extended) harp scan after pass change (previous one was 12 hours ago)? | ||
#* Production all day long until 6am tomorrow. | #* Production all day long until 6am tomorrow. | ||
− | #* Start emptying target at 6am on Wednesday (separate run). | + | #* Start emptying target at 6am on Wednesday (separate run in raw mode). |
+ | #* Blank goniometer for a couple of minutes | ||
+ | #* Same with collimator blocked | ||
#* 2 hours of empty target run (what radiator and current?) | #* 2 hours of empty target run (what radiator and current?) | ||
#* 10-12 hours of TAC running starting at ~9am Wednesday. | #* 10-12 hours of TAC running starting at ~9am Wednesday. |
Latest revision as of 12:14, 31 January 2018
<- Back to Run Coordination Meetings:Fall2017 Spring2018 Run
Contents
Wednesday, January 31
- Notes from the previous 24 hours:
- After pass change, we got beam at 12:30 pm. It was reasonably stable except for 2 hours downtime at midnight. We were running production until 6am.
- MCC kept tuning beam for Hall C until 8pm when they achieved 5/5.5 pass CW beam to all 4 halls [1].
- 14.7 hours of CW beam. BAU: 13.8 hrs (3.7+5.6+4.5), BANU: 0.9 hrs (0.5+0.1+0.3)
- Richard did TAGM HV scan and some other TAGM work.
- Started empty target set of runs at 6am. Rate is ~15kHz.
- ~1.9 B triggers collected.
- Total: Spreadsheet: number of triggers.
- We have first entries in HDDIRC logbook!
- Issues:
- Low CO2
- Low level monitoring
- TPOL dead channel is back.
- TAGM seems to be heading back to its state a few days ago.
- Beam convergence still needs improvement [2].
- Short term run plan:
- At 6 AM:
- Stop current run. Change DAQ config to raw mode and start a new run.
- Start emptying the target.
- When the target is empty, stop the run (~20 minutes).
- Take beam away. Put goniometer in blank. Ask for 150nA beam. After 2 minutes of beam, take it away.
- Close a collimator. Ask for 150nA beam. After 2 minutes of beam, take it away.
- Put collimator back to 5mm. Set goniometer back to the previous diamond. Ask for 150 nA beam.
- Reconfigure DAQ for a normal (not raw) mode. Start an empty target run for 2 hours.
- At about 9am, we'll proceed to TAC run.
- After TAC, another raw mode run when the target is being filled. BTA 5nA threshold?
- A Harp scan after empty target run.
- Then back to production.
- Run plan chart: Week 3
- At 6 AM:
- Reports:
Tuesday, January 30
- Notes from the previous 24 hours:
- Machine maintenance day - work on FCAL, TPOL, TAGM, TRD (wow! secret "Beni's material").
- Beam was back at around 8pm.
- Spent 1h40m on "Our - MCC - Our" harp scans due to beam trips, HV trips and "operator in training".
- Running production since ~10pm.
- 10.0 hours of "MCC beam". BAU: 8.4 hrs (1.4+1.0+6.0), BANU: 1.7 hrs (0.0+1.4+0.3)
- 1.4B events collected.
- For now, PARA runs only 100M events to allow PERP to catch up.
- Total: Spreadsheet: number of triggers.
- GlueX Data Statistics from RCDB.
- Issues:
- Low level monitoring
- Previously dead TAGM ch.21 is now too active in fADC [3]. Channels 82-84 are now alive.
- 5 or 6 FCAL channels are still empty despite of maintenance yesterday [4].
- BTA was discussed with Ryan Slominski [5]. There is something different between MCC and our BTAs but we haven't seen BNA=0 recently.
- Short term run plan:
- Do we need the (extended) harp scan after pass change (previous one was 12 hours ago)?
- Production all day long until 6am tomorrow.
- Start emptying target at 6am on Wednesday (separate run in raw mode).
- Blank goniometer for a couple of minutes
- Same with collimator blocked
- 2 hours of empty target run (what radiator and current?)
- 10-12 hours of TAC running starting at ~9am Wednesday.
- Run plan chart: Week 3
- Reports:
- CDC currents during no radiator.
- Trigger rate comparison for 2017 and 2018.
- New harp fits from Richard [6], [7] and Hovanes [8]
Monday, January 29
- Notes from the previous 24 hours:
- "The machine was rather trippy" (MCC quote), with persistent RF and BLM trips.
- 14.9 hours of actual beam per MCC in the last 24 hours.
- ABU 14.5 hours, BANU 0.4 hours.
- 2.1 B events collected. Total: Spreadsheet: number of triggers.
- There were 2 minutes of 150nA beam with no radiator to study the chamber currents.
- Beam will be off today from 9am until 1pm for RF recovery
- Hall C pass change tomorrow morning for about 1 hour, and no beam studies.
- Issues:
- Low level monitoring
- FDC2 HV tripped without alarm [9]. For an hour, data were taken with FDC2 cell6 off.
- No monitoring plots in logbook during day shift.
- More on TAGM scaler trouble.
- BTA periodic unreliability continues forcing people to do manual BANU->BNA transfers.
- TPOL ch.3 is still alive
- Update sqlite file from ccdb to bring TAGM ch.21 back from oblivion.
- Switch to gluonraid4.
- Short term run plan:
- Harp scan then production.
- Hall access for FCAL?
- Empty target: today after RF recovery, tomorrow after pass change, or Wed morning before TAC run?
- Run plan chart: Week 3
- Reports:
- Imaging the detector
- Different harp fits: Hovanes [10], Richard [11]
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 [12]
- 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 [13], [14], [15], [16], [17], [18]
- gluonraid3/gluonraid4 switching [19], [20]
- BTA is still unreliable. Hovanes has fixed a bug. However, occasionally, BNA is still counted as BANU [21].
- 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 [24].
- 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 [25].
- 20 minutes have been lost on recovering TAGM after bias voltage incident.
- At 2:15pm the beam went off for 45 minutes [26] but we were charged BANU for 45 minutes [27]?
- RootSpy and HLDetectorTiming plugin [28], [29].
- 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: [30]
- 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: