Difference between revisions of "Run Planning Meeting Notes, Feb. 14-Fev 21, 2019"
From GlueXWiki
(→Friday, Feb. 15 at 08:45) |
(→Friday, Feb. 15 at 08:45) |
||
| (5 intermediate revisions by the same user not shown) | |||
| Line 21: | Line 21: | ||
== Friday, Feb. 15 at 08:45 == | == Friday, Feb. 15 at 08:45 == | ||
# Past 24 hours: | # Past 24 hours: | ||
| − | #* Nominal DIRC setting collected 1B triggers | + | #* Nominal DIRC setting collected 1B triggers |
| + | #** Switched to the higher MOROC threshold (200) | ||
#* Smooth overnight running at 180nA, coming back to the desired 225nA this morning. | #* Smooth overnight running at 180nA, coming back to the desired 225nA this morning. | ||
#* Both opportunistic accesses happened during the accelerator down time due to the bulk power supply failure. | #* Both opportunistic accesses happened during the accelerator down time due to the bulk power supply failure. | ||
| − | |||
# Issues: | # Issues: | ||
#* Beam steered to the wrong BCM, therefore constrained the maximum beam delivered to 180nA | #* Beam steered to the wrong BCM, therefore constrained the maximum beam delivered to 180nA | ||
| − | #* Goni camera, wrong angle, did something move? | + | #**Detailed log: https://logbooks.jlab.org/entry/3653554 |
| − | #* root spy crash | + | #* Goni camera, wrong angle, did something move? https://logbooks.jlab.org/entry/3653437 |
| − | #* DIRC SSP out of sync over night (after switching the MOROC threshold). | + | #* root spy crash: https://logbooks.jlab.org/entry/3653678 |
| − | + | #* DIRC SSP | |
| + | #** Runs at MOROC threshold of 50 not possible due to the out of sync issue, need to be looked into | ||
| + | #** Out of sync over night (after switching the MOROC threshold). | ||
| + | #* hdview2 and monitoring email working? | ||
# Plan for today: | # Plan for today: | ||
#* keep collecting higher MOROC threshold data (up to 1B triggers). | #* keep collecting higher MOROC threshold data (up to 1B triggers). | ||
#* When beam is not available, 15 min LED runs with different pulsing and trigger conditions. | #* When beam is not available, 15 min LED runs with different pulsing and trigger conditions. | ||
| + | #* No planned and opportunistic access | ||
Latest revision as of 10:09, 15 February 2019
Thursday, Feb. 14 at 08:45
- Past 24 hours:
- Acceptable quality beam established early morning around 11:00 am.
- Beam profile and convergence by Jay:https://logbooks.jlab.org/entry/3652506
- DIRC data taking.
- DIRC analysis is on-going.
- Acceptable quality beam established early morning around 11:00 am.
- Issues
- Cryo Water Temperature jump to 72F (limit 70F).
- Due to pump switch: https://logbooks.jlab.org/entry/3652512
- IOC lost communication
- IOCHDCOL failed at 21:30. Reported to us by MCC at 0:00. Reset at 1:50 am. Hovanes verified things are ok at 3am. https://logbooks.jlab.org/entry/3652920
- DIRC SSP problem:
- DAQ stopped twice due to the out of sync issue.
- Tagger RF time: https://logbooks.jlab.org/entry/3652533
- hdview2 is work working
- Cryo Water Temperature jump to 72F (limit 70F).
- Today:
- No planned access
- Opportunistic access requested by Kenoe to work on GEM.
- DIRC nominal running (MOROC threshold scan?)
Friday, Feb. 15 at 08:45
- Past 24 hours:
- Nominal DIRC setting collected 1B triggers
- Switched to the higher MOROC threshold (200)
- Smooth overnight running at 180nA, coming back to the desired 225nA this morning.
- Both opportunistic accesses happened during the accelerator down time due to the bulk power supply failure.
- Nominal DIRC setting collected 1B triggers
- Issues:
- Beam steered to the wrong BCM, therefore constrained the maximum beam delivered to 180nA
- Detailed log: https://logbooks.jlab.org/entry/3653554
- Goni camera, wrong angle, did something move? https://logbooks.jlab.org/entry/3653437
- root spy crash: https://logbooks.jlab.org/entry/3653678
- DIRC SSP
- Runs at MOROC threshold of 50 not possible due to the out of sync issue, need to be looked into
- Out of sync over night (after switching the MOROC threshold).
- hdview2 and monitoring email working?
- Beam steered to the wrong BCM, therefore constrained the maximum beam delivered to 180nA
- Plan for today:
- keep collecting higher MOROC threshold data (up to 1B triggers).
- When beam is not available, 15 min LED runs with different pulsing and trigger conditions.
- No planned and opportunistic access
