Difference between revisions of "WAC Notes July 27 2019"

From PREX Wiki
Jump to: navigation, search
(Production Run List)
(Non-Production Runs and Bad Runs)
Line 59: Line 59:
 
== Non-Production Runs and Bad Runs ==
 
== Non-Production Runs and Bad Runs ==
 
* 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]
 +
* Test - [https://hallaweb.jlab.org/parity/prex/onlinePlots/index.php?run=summary/all/run3682_000 run3682]
 +
** MCC was trying to fix the problem in hall B
  
 
== Pedestal/Calibrations Updates ==
 
== Pedestal/Calibrations Updates ==

Revision as of 08:34, 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
  • NeedCut - 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


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 of the run
    • MCC called to inform they are going to turn hall A FFB of temporarily
  • Good - run3683
    • Mini-run 6 has big RMS in regressed detectors
    • bpm11 (energy monitors) saturated during that time
    • applied bad_evt_cut and fixed it
  • Good - run3684

Non-Production Runs and Bad Runs

  • Test - run3677
  • Test - run3682
    • MCC was trying to fix the problem in hall B

Pedestal/Calibrations Updates

Issues

Other Status Updates