Difference between revisions of "June 26, 2022"
From HallCWiki
Jump to navigationJump to searchLine 5: | Line 5: | ||
* Experiment status: | * Experiment status: | ||
** pionLT continues to make progress on run plan, though we are still behind schedule, unless Ops is able to deliver 80 uA at >50% efficiency | ** pionLT continues to make progress on run plan, though we are still behind schedule, unless Ops is able to deliver 80 uA at >50% efficiency | ||
− | ** On page | + | ** On page 95 of run plan. New Setting: Q2=2.45, W=3.20, x=0.21, high ε data taking. |
− | ** On page | + | ** On page 93 of run plan (Q2=3.85, W =3.07, x=0.31, high ε data taking). Finished step 5, on step 6 (Dummy). Next we will move the SHMS to 9.91degress and do steps 3 and 4. We will prorate ABU's by 20/80 and 20/70 |
= Current Run Plan = | = Current Run Plan = |
Latest revision as of 10:04, 26 June 2022
Current Status
- Accelerator status:
- Can't deliver more than 20 uA, probably stuck here till Monday
- Experiment status:
- pionLT continues to make progress on run plan, though we are still behind schedule, unless Ops is able to deliver 80 uA at >50% efficiency
- On page 95 of run plan. New Setting: Q2=2.45, W=3.20, x=0.21, high ε data taking.
- On page 93 of run plan (Q2=3.85, W =3.07, x=0.31, high ε data taking). Finished step 5, on step 6 (Dummy). Next we will move the SHMS to 9.91degress and do steps 3 and 4. We will prorate ABU's by 20/80 and 20/70
Current Run Plan
Notices in Effect for Shift Crew
- Please pro-rate ABU for max current limit in run plan (uA) in beam time accounting. For example, if we receive 15 uA instead of the max_current_limit in the run plan, then the ABU should be: ABU_prorated = 15/(max current limit) * ABU
- Check the HMS/SHMS rates for when production starts, since for Heep coin. production SHMS saw higher rates. Make sure shift crew takes snapshot of scalers at every setting
- When analyzing LD2 or Al dummy or LH2, please leave the target_mass_amu in the standard.kinematics as that of the proton, but when analyzing the data with the pionLT script, specify the target used, as different targets will have different ranges in the cuts when integrating the missing mass peak. Refer to log entry: https://logbooks.jlab.org/entry/4005387 These instructions are given in the pionLT run plan.
- Keep on eye on HMS DC chamber wire maps. See current issues
Current Issues
- shift crew continues to see HMS DC noise outbursts more frequently, see log-entries:
- See log-entries: https://logbooks.jlab.org/entry/4005325 , https://logbooks.jlab.org/entry/4005330
- study noise dependence on HMS DC thresholds, and found that noise temporarily went away @ DC threshold 5.8 V, but re-appeared on the next runs see log-entry --> https://logbooks.jlab.org/entry/4005624 This issue will have to be addressed today during maintenance day
- Hall C BCMs and Accelerator BCMc (i.e., MPS BCMs) mismatch --> https://logbooks.jlab.org/entry/4005801
- I would think this is just a scale factor missing between the two measurements? Usually S. Wood did this in the past. I have notified S. Wood in the log-entry
- Gains and offset need to be update https://logbooks.jlab.org/entry/4006872
Planned Accesses to the Hall
- Need new plan to address HMS DC noise. Check thresholds on cards, low voltages, check grounding, add copper tape, and follow Brad's suggestions. Last resort we can swap nanometrics card.
- Will notify SoLID parasitic group to see if they need access
Planned Accelerator Configuration Changes
- Possibly take down machine Monday to get us to higher currents
Special Requests
- Install telegram on RC Phone (DONE)