Difference between revisions of "WAC Notes July 27 2019"
From PREX Wiki
Jump to navigationJump to search| Line 38: | Line 38: | ||
** Q1 tripped during the run | ** Q1 tripped during the run | ||
** Used bad_evt_cut.3675.map and now good | ** Used bad_evt_cut.3675.map and now good | ||
| − | * | + | * Good - [https://hallaweb.jlab.org/parity/prex/onlinePlots/index.php?run=summary/all/run3676_000 run3676] |
** Mini-run 1 has large width for regressed detectors | ** Mini-run 1 has large width for regressed detectors | ||
** Can see a spike in bpm plots, may need to cut the events in that region | ** Can see a spike in bpm plots, may need to cut the events in that region | ||
Revision as of 09:00, 28 July 2019
| Documentation |
| HOW TOs for shift crew |
| Expert Tools |
| All Expert Contacts |
PREX Main << Weekly Analysis Coordinator << WAC Notes << Instructions
WAC Notes July 26 2019 << >> WAC Notes July 28 2019
July 27 2019
Daily Meeting BlueJeans
Production Run List
- Since we are using bcm_dg_ds, the width in the bcm asymmetry is 2X of what we had with bcm_an_ds
- Should we think about changing saturation limit for this SAM?
- If we compare with 70uA good run from previous slug, yield of SAMs on Right Hand Side has increased while on the other side decreased
- Lower SAM3 HV?
Start Slug 15, IHWP OUT, FFB on always
- Good - run3670
- Good - run3671
- Good - run3672
- Aq width is too large
- Good - run3673
- Aq width is too large
- Good - run3674
- Good - run3675
- Q1 tripped during the run
- Used bad_evt_cut.3675.map and now good
- Good - run3676
- Mini-run 1 has large width for regressed detectors
- Can see a spike in bpm plots, may need to cut the events in that region
- Fixed with bad_evt_cut
Start Slug 16, IHWP IN, FFB on always
- Good - run3678
- Good - run3679
- Good - run3680
- Suspicious - run3681
- MCC fighting to get beam in hall B
- Big fluctuation (noise) in second half OFF the run
- MCC called to inform they are going to turn hall A FFB of temporarily
- Good - run3683
- Mini-run 6 had big RMS in regressed detectors
- bpm11 (energy monitors) saturated during that time
- applied bad_evt_cut and fixed it
- Good - run3684
- Good - run3685
Start Slug 17, IHWP OUT, FFB on always
- Good - run3686
- Good - run3687
- asym_bcm double peaks?
- Good - run3688
- Good - run3689
- Q1L tripped
- Applied bad_evt_cut->fixed it
- Good - run3690
- Good - run3691
Start Slug 18, IHWP IN, FFB on always
- Good - run3692
