Difference between revisions of "WAC Notes July 25 2019"

From PREX Wiki
Jump to: navigation, search
(Production Run List)
(Production Run List)
Line 60: Line 60:
 
** Normalized detector yield is decreasing again
 
** Normalized detector yield is decreasing again
 
** Regressed detector widths are larger
 
** Regressed detector widths are larger
 +
* '''Test''' - [https://hallaweb.jlab.org/parity/prex/onlinePlots/index.php?run=summary/all/run3640_000 run3640]
 +
** This run was taken during collimator scan
 +
** Aq widths are too large
 +
* '''Test''' - [https://hallaweb.jlab.org/parity/prex/onlinePlots/index.php?run=summary/all/run3641_000 run3641]
 +
** Aq widths are too large (>200ppm)
 +
** Started with 1uA checking position then go to 70uA
 +
** Really a test run
  
 
== Non-Production Runs and Bad Runs ==
 
== Non-Production Runs and Bad Runs ==

Revision as of 19:03, 3 August 2019

Documentation
HOW TOs for shift crew
Expert Tools
All Expert Contacts



PREX Main << Weekly Analysis Coordinator << WAC Notes << Instructions

WAC Notes July 24 2019 << >> WAC Notes July 26 2019

July 25 2019

Production Run List

Start Slug 13, IHWP OUT Flip Right, FFB on always

      • Since we are using bcm_dg_ds, the width in the bcm is ~1.5X of what we used to have with bcm_an_ds3
  • Good - run3622
  • Good - run3623
  • Good - run3624
  • Good - run3625
    • Mini-run 0 had too large detector widths->Fixed after bad_event_cut
  • Good - run3626
  • NeedCut - run3629
    • Couldn't find any obvious cut region
    • Aq mean is large
  • Good - run3630
    • Detector widths are fluctuating between mini-runs.
    • First run with detector width started increasing
  • Good - run3631
    • Detector widths become worse
    • Beam position change
    • Beam current fluctuating
    • Normalized detector yield is decreasing over time
  • Good - run3632
    • Regressed detector widths are even higher
    • Normalized detector yield is decreasing over time
    • Regressed detectors are correlated
  • Good - run3633
    • Normalized detector yield is increasing over time (opposite to run3632)
    • Regressed detectors are correlated
    • Regressed detector widths are larger
  • Good - run3634
    • Normalized detector yield is increasing over time (opposite to run3632)
    • Regressed detectors are correlated
    • Regressed detector widths are larger
  • Good - run3635
    • Normalized detector yield is increasing over time (opposite to run3632)
    • Regressed detectors are correlated
    • Regressed detector widths are larger
  • Good - run3636
    • Long beam trip during the run
    • Normalized detector yield is decreasing again
    • Regressed detector widths are larger
  • Test - run3640
    • This run was taken during collimator scan
    • Aq widths are too large
  • Test - run3641
    • Aq widths are too large (>200ppm)
    • Started with 1uA checking position then go to 70uA
    • Really a test run

Non-Production Runs and Bad Runs

Pedestal/Calibrations Updates

Issues

  • There were many pedestal and event cut problems. From now on, when an event cut isn't absolutely necessary it should be removed - see japan source code for reference of cuts here
  • The BCM appears to be falling apart. We are fixing it and running slug 12 on BCM DG DS in the meantime.
  • BPM 4ec had intermittant problems (iocse10 has issues) and so we are regressing with 4e again. BPM 11X is ok and stays in regression.


  • Increase in Detector widths and Collimator temperature HALOG COLLIMATOR HALOG
  • Increase in collimator temperature and raising neutron dose HALOG
  • The increase in detector widths started from late Swing Shift HALOG
  • Cavity BPM lock change HALOG

Other Status Updates