Difference between revisions of "WAC Notes July 27 2019"
From PREX Wiki
Jump to navigationJump to search(23 intermediate revisions by the same user not shown) | |||
Line 23: | Line 23: | ||
=== Production Run List === | === 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''' | ** '''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?''' | ** '''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''' | ** '''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 [https://hallaweb.jlab.org/parity/prex/onlinePlots/slug/slug_list/slug15/y_postPanPlots_slug15.pdf Slug 15, IHWP OUT, FFB on always]''' | ||
* Good - [https://hallaweb.jlab.org/parity/prex/onlinePlots/index.php?run=summary/all/run3670_000 run3670] | * Good - [https://hallaweb.jlab.org/parity/prex/onlinePlots/index.php?run=summary/all/run3670_000 run3670] | ||
* Good - [https://hallaweb.jlab.org/parity/prex/onlinePlots/index.php?run=summary/all/run3671_000 run3671] | * Good - [https://hallaweb.jlab.org/parity/prex/onlinePlots/index.php?run=summary/all/run3671_000 run3671] | ||
Line 37: | 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 | ||
+ | ** '''Fixed with bad_evt_cut''' | ||
+ | |||
+ | '''Start [https://hallaweb.jlab.org/parity/prex/onlinePlots/slug/slug_list/slug16/y_postPanPlots_slug16.pdf Slug 16, IHWP IN, FFB on always]''' | ||
+ | * Good - [https://hallaweb.jlab.org/parity/prex/onlinePlots/index.php?run=summary/all/run3678_000 run3678] | ||
+ | * Good - [https://hallaweb.jlab.org/parity/prex/onlinePlots/index.php?run=summary/all/run3679_000 run3679] | ||
+ | * Good - [https://hallaweb.jlab.org/parity/prex/onlinePlots/index.php?run=summary/all/run3680_000 run3680] | ||
+ | * Good - [https://hallaweb.jlab.org/parity/prex/onlinePlots/index.php?run=summary/all/run3681_000 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 | ||
+ | ** The second half has huge BPM excursion, decided to keep it as it is for now as suggested in WAC meeting 09/25/2019. | ||
+ | * Good - [https://hallaweb.jlab.org/parity/prex/onlinePlots/index.php?run=summary/all/run3682_000 run3682]'''ADDED from suspicious list''' | ||
+ | ** MCC was trying to fix the problem in hall B | ||
+ | * Good - [https://hallaweb.jlab.org/parity/prex/onlinePlots/index.php?run=summary/all/run3683_000 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 - [https://hallaweb.jlab.org/parity/prex/onlinePlots/index.php?run=summary/all/run3684_000 run3684] | ||
+ | * Good - [https://hallaweb.jlab.org/parity/prex/onlinePlots/index.php?run=summary/all/run3685_000 run3685] | ||
+ | |||
+ | '''Start [https://hallaweb.jlab.org/parity/prex/onlinePlots/slug/slug_list/slug17/y_postPanPlots_slug17.pdf Slug 17, IHWP OUT, FFB on always]''' | ||
+ | * Good - [https://hallaweb.jlab.org/parity/prex/onlinePlots/index.php?run=summary/all/run3686_000 run3686] | ||
+ | * Good - [https://hallaweb.jlab.org/parity/prex/onlinePlots/index.php?run=summary/all/run3687_000 run3687] | ||
+ | ** asym_bcm double peaks? | ||
+ | * Good - [https://hallaweb.jlab.org/parity/prex/onlinePlots/index.php?run=summary/all/run3688_000 run3688] | ||
+ | * Good - [https://hallaweb.jlab.org/parity/prex/onlinePlots/index.php?run=summary/all/run3689_000 run3689] | ||
+ | ** Q1L tripped | ||
+ | ** Applied bad_evt_cut->'''fixed it''' | ||
+ | * Good - [https://hallaweb.jlab.org/parity/prex/onlinePlots/index.php?run=summary/all/run3690_000 run3690] | ||
+ | * Good - [https://hallaweb.jlab.org/parity/prex/onlinePlots/index.php?run=summary/all/run3691_000 run3691] | ||
== Non-Production Runs and Bad Runs == | == Non-Production Runs and Bad Runs == | ||
+ | * Bad - [https://hallaweb.jlab.org/parity/prex/onlinePlots/index.php?run=summary/all/run3669_000 run3669] | ||
+ | ** Very short run. BPM11 saturated for the whole run | ||
* Test - [https://hallaweb.jlab.org/parity/prex/onlinePlots/index.php?run=summary/all/run3677_000 run3677] | * Test - [https://hallaweb.jlab.org/parity/prex/onlinePlots/index.php?run=summary/all/run3677_000 run3677] | ||
+ | ** Short run for Aq test | ||
== Pedestal/Calibrations Updates == | == Pedestal/Calibrations Updates == |
Latest revision as of 15:06, 25 September 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
- Good - 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
- The second half has huge BPM excursion, decided to keep it as it is for now as suggested in WAC meeting 09/25/2019.
- Good - run3682ADDED from suspicious list
- MCC was trying to fix the problem in hall B
- 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
Non-Production Runs and Bad Runs
- Bad - run3669
- Very short run. BPM11 saturated for the whole run
- Test - run3677
- Short run for Aq test