Difference between revisions of "Run Planning Meeting Notes, November 25 - December 1, 2021"
From GlueXWiki
| Line 1: | Line 1: | ||
=Sunday November 28= | =Sunday November 28= | ||
#Last 24h: | #Last 24h: | ||
| − | |||
#* Production has been quite good. | #* Production has been quite good. | ||
| − | |||
#Issues: | #Issues: | ||
| − | |||
#* No major issues to report. | #* No major issues to report. | ||
#* The energy oscillations reported by Alexandre [https://logbooks.jlab.org/entry/3950833 here] and [https://logbooks.jlab.org/entry/3951413 here] were addressed by [https://logbooks.jlab.org/entry/3951960 Jay] this morning. I lack the enough knowledge to arrive at a conclusion, but it is apparent that it is not affecting the quality of the data. | #* The energy oscillations reported by Alexandre [https://logbooks.jlab.org/entry/3950833 here] and [https://logbooks.jlab.org/entry/3951413 here] were addressed by [https://logbooks.jlab.org/entry/3951960 Jay] this morning. I lack the enough knowledge to arrive at a conclusion, but it is apparent that it is not affecting the quality of the data. | ||
| − | |||
# [https://halldweb.jlab.org/wiki/index.php/SRC/CT_Run_Plan Plan:] | # [https://halldweb.jlab.org/wiki/index.php/SRC/CT_Run_Plan Plan:] | ||
#* run on carbon at 150nA´ | #* run on carbon at 150nA´ | ||
| Line 18: | Line 14: | ||
=Saturday November 27= | =Saturday November 27= | ||
#Last 24h: | #Last 24h: | ||
| − | |||
#* Production has been quite good. | #* Production has been quite good. | ||
| − | |||
#Issues: | #Issues: | ||
| − | |||
#* No major issues to report. | #* No major issues to report. | ||
| − | |||
# [https://halldweb.jlab.org/wiki/index.php/SRC/CT_Run_Plan Plan:] | # [https://halldweb.jlab.org/wiki/index.php/SRC/CT_Run_Plan Plan:] | ||
#* run on carbon at 150nA´ | #* run on carbon at 150nA´ | ||
| Line 33: | Line 25: | ||
=Friday November 26= | =Friday November 26= | ||
#Last 24h: | #Last 24h: | ||
| − | |||
#* Production has been quite good. | #* Production has been quite good. | ||
| − | |||
#Issues: | #Issues: | ||
| − | |||
#* ~23:30 VESDA Fire Alarm panel started to beep, but not alarm was present. Sasha explained us how to proceed, and around one hour later it was solved. | #* ~23:30 VESDA Fire Alarm panel started to beep, but not alarm was present. Sasha explained us how to proceed, and around one hour later it was solved. | ||
| − | |||
# [https://halldweb.jlab.org/wiki/index.php/SRC/CT_Run_Plan Plan:] | # [https://halldweb.jlab.org/wiki/index.php/SRC/CT_Run_Plan Plan:] | ||
#* run on carbon at 150nA´ | #* run on carbon at 150nA´ | ||
| Line 48: | Line 36: | ||
=Thursday November 25= | =Thursday November 25= | ||
#Last 24h: | #Last 24h: | ||
| − | |||
#* Solenoid ramped down, cryotarget removed and replaced with the carbon foils (work finished ~12:00) | #* Solenoid ramped down, cryotarget removed and replaced with the carbon foils (work finished ~12:00) | ||
#* Beni started to ramp up the solenoid. ~19:00 tune beam was delivered into the hall. After harp scans and finishing with the solenoid ramp up, DAQ was prepared for production. | #* Beni started to ramp up the solenoid. ~19:00 tune beam was delivered into the hall. After harp scans and finishing with the solenoid ramp up, DAQ was prepared for production. | ||
#* First Carbon run at 150nA started ~11:30 | #* First Carbon run at 150nA started ~11:30 | ||
| − | |||
#Issues: | #Issues: | ||
#* DAQ computer was frozen during the afternoon, so a hot reboot was necessary. That could cause some communications issues with some racks, especially with the Pair Spectrometer. | #* DAQ computer was frozen during the afternoon, so a hot reboot was necessary. That could cause some communications issues with some racks, especially with the Pair Spectrometer. | ||
#* Besides that issue, I suggest limiting the DAQ computer just for CODA. I had the experience that the computer gets freeze or lose the GUI when is used with other apps. | #* Besides that issue, I suggest limiting the DAQ computer just for CODA. I had the experience that the computer gets freeze or lose the GUI when is used with other apps. | ||
#* Not an experimental issue, but important, the mouse from the conference room has disappear. | #* Not an experimental issue, but important, the mouse from the conference room has disappear. | ||
| − | |||
# [https://halldweb.jlab.org/wiki/index.php/SRC/CT_Run_Plan Plan:] | # [https://halldweb.jlab.org/wiki/index.php/SRC/CT_Run_Plan Plan:] | ||
| − | |||
#* run on carbon at 150nA´ | #* run on carbon at 150nA´ | ||
#* Rotate the radiators and use both configurations | #* Rotate the radiators and use both configurations | ||
Revision as of 22:20, 28 November 2021
Sunday November 28
- Last 24h:
- Production has been quite good.
- Issues:
- Plan:
- run on carbon at 150nA´
- Rotate the radiators and use both configurations
- It was suggested to stop the beam ALWAYS before changing the radiator configuration (even with the same radiator). Between radiator change (0/90 <--> 35/145 ALWAYS ask MCC to set the dumplette)
Saturday November 27
- Last 24h:
- Production has been quite good.
- Issues:
- No major issues to report.
- Plan:
- run on carbon at 150nA´
- Rotate the radiators and use both configurations
- It was suggested to stop the beam ALWAYS before changing the radiator configuration (even with the same radiator). Between radiator change (0/90 <--> 35/145 ALWAYS ask MCC to set the dumplette)
Friday November 26
- Last 24h:
- Production has been quite good.
- Issues:
- ~23:30 VESDA Fire Alarm panel started to beep, but not alarm was present. Sasha explained us how to proceed, and around one hour later it was solved.
- Plan:
- run on carbon at 150nA´
- Rotate the radiators and use both configurations
- It was suggested to stop the beam ALWAYS before changing the radiator configuration (even with the same radiator). Between radiator change (0/90 <--> 35/145 ALWAYS ask MCC to set the dumplette)
- Take ONE amorphous run.
Thursday November 25
- Last 24h:
- Solenoid ramped down, cryotarget removed and replaced with the carbon foils (work finished ~12:00)
- Beni started to ramp up the solenoid. ~19:00 tune beam was delivered into the hall. After harp scans and finishing with the solenoid ramp up, DAQ was prepared for production.
- First Carbon run at 150nA started ~11:30
- Issues:
- DAQ computer was frozen during the afternoon, so a hot reboot was necessary. That could cause some communications issues with some racks, especially with the Pair Spectrometer.
- Besides that issue, I suggest limiting the DAQ computer just for CODA. I had the experience that the computer gets freeze or lose the GUI when is used with other apps.
- Not an experimental issue, but important, the mouse from the conference room has disappear.
- Plan:
- run on carbon at 150nA´
- Rotate the radiators and use both configurations
- It was suggested to stop the beam ALWAYS before changing the radiator configuration (even with the same radiator). Between radiator change (0/90 -> 35/145 ALWAYS ask MCC to set the dumplette)
- Take at least two amorphous runs
- Analysis update
