Difference between revisions of "Run Planning Meeting Notes, Mar 14 - Mar 20, 2019"
From GlueXWiki
| Line 8: | Line 8: | ||
* [https://halldweb.jlab.org/data_monitoring/run_statistics/RunPeriod-2019-01/index.html Trigger counter] | * [https://halldweb.jlab.org/data_monitoring/run_statistics/RunPeriod-2019-01/index.html Trigger counter] | ||
* To join via a Web Browser, go to the page [https://bluejeans.com/660743227 https://bluejeans.com/660743227] | * To join via a Web Browser, go to the page [https://bluejeans.com/660743227 https://bluejeans.com/660743227] | ||
| + | |||
| + | == Friday, Mar. 15 at 08:45 == | ||
| + | # Past 24 hours: | ||
| + | #* Short access after meeting | ||
| + | ##* [https://logbooks.jlab.org/entry/3667744 Beni/Tim: adjust rotometer flow to 1 L/hr] | ||
| + | ##* Sergey and Hovanes: DAQ | ||
| + | ##* [https://logbooks.jlab.org/entry/3667703 logbook entry Chris, Colin, Nick, Sasha: FCAL VME crate 11 power supply/ fan issue] | ||
| + | #* gluon01 is back with a new kernel and graphics driver | ||
| + | #* Production running | ||
| + | # Issues | ||
| + | #* Problematic FCAL channels near beamline | ||
| + | ##* One base lost connection and was recovered by power cycling the power supply. This happens 1-2 times per week. Right now I (Colin) am the only one capable of doing this. Need to train more people how to spot and fix these errors. It is a relatively simple process, but one that should not be left to the shift crew. | ||
| + | ##* [https://logbooks.jlab.org/entry/3667944 One base lost HV near beam line. Access needed? Need to discuss offline how to best HV failures near beamline.] | ||
| + | # Reports | ||
| + | #* [] | ||
| + | # Today: | ||
| + | #* Production: 200nA, Al 10<sup>-4</sup> | ||
| + | #Run Plan | ||
| + | #* Production running | ||
| + | #* TAC run | ||
== Thursday, Mar. 14 at 08:45 == | == Thursday, Mar. 14 at 08:45 == | ||
Revision as of 01:05, 15 March 2019
- Run_Coordination_Meetings:Spring2019_Run
- PrimEx daily meeting
- PrimEx-η run plan
- Production runs, number of triggers
- Trigger counter
- To join via a Web Browser, go to the page https://bluejeans.com/660743227
Friday, Mar. 15 at 08:45
- Past 24 hours:
- Short access after meeting
- gluon01 is back with a new kernel and graphics driver
- Production running
- Issues
- Problematic FCAL channels near beamline
- One base lost connection and was recovered by power cycling the power supply. This happens 1-2 times per week. Right now I (Colin) am the only one capable of doing this. Need to train more people how to spot and fix these errors. It is a relatively simple process, but one that should not be left to the shift crew.
- One base lost HV near beam line. Access needed? Need to discuss offline how to best HV failures near beamline.
- Reports
- []
- Today:
- Production: 200nA, Al 10-4
- Run Plan
- Production running
- TAC run
Thursday, Mar. 14 at 08:45
- Past 24 hours:
- Production running
- Issues
- RootSpy Problem with CCAL Pedestal Histograms
- Hall D y position variation from Jay. Beam position variation not related to dispersion.12
- Console 1 frozen. Who knows how to reboot?
- Reports
- Rate monitoring (Alexandre)
- FCAL shift in simulation (Liping)
- Beni really wanted to conitune our discussion yesterday on histogram binning (Beni)
- Today:
- Production: 200nA, Al 10-4
- Run Plan
- Production running
- Hall C goes down Sunday at 4pm. Postpone TAC run until Monday unless there are objections.
- There are parity quality beam testes (PQB) scheduled for Hall A Monday and Tuesday, but this should not affect the beam delivered to us.
- RF Recovery scheduled for Wednesday
