Difference between revisions of "WAC Notes July 26 2019"

From PREX Wiki
Jump to: navigation, search
(Non-Production Runs and Bad Runs)
(Non-Production Runs and Bad Runs)
Line 54: Line 54:
 
** Target Trouble Shooting
 
** Target Trouble Shooting
 
* Test [https://hallaweb.jlab.org/parity/prex/onlinePlots/index.php?run=summary/all/run3647_000 run3647]
 
* Test [https://hallaweb.jlab.org/parity/prex/onlinePlots/index.php?run=summary/all/run3647_000 run3647]
* Attempting to production but some Feedback issue [https://hallaweb.jlab.org/parity/prex/onlinePlots/index.php?run=summary/all/run3648_000 run3648]
+
** Beam current ~20uA. No event passed event cuts.
 +
* Bad [https://hallaweb.jlab.org/parity/prex/onlinePlots/index.php?run=summary/all/run3648_000 run3648]
 +
** Attempting to production but some Feedback issue
 +
** Quite big Aq mean, very short run ~11k events
 
* Suspicious - [https://hallaweb.jlab.org/parity/prex/onlinePlots/index.php?run=summary/all/run3649_000 run3649]
 
* Suspicious - [https://hallaweb.jlab.org/parity/prex/onlinePlots/index.php?run=summary/all/run3649_000 run3649]
 
** Short run with many beam trips  
 
** Short run with many beam trips  

Revision as of 19:25, 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 25 2019 << >> WAC Notes July 27 2019

July 26 2019

Daily Meeting BlueJeans

Production Run List

Start Slug 14, IHWP In, FFB on always

    • Since we are using bcm_dg_ds, the width in the bcm asymmetry is 2X of what we had with bcm_an_ds
    • We used the same, bcm_dg_ds, bcm in slug13 also, where the Aq width was ~1.5X of what we had with bcm_an_ds
    • SAM3 started saturating since run3640
    • 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
  • Good - run3652
  • Good - run3653
  • Good - run3654
  • Good - run3655
  • Good - run3656
  • Good - run3657
  • Good - run3658
  • Good - run3659
  • Good - run3664
    • Regressed detector widths are ~5ppm higher than previous runs->might be due to the jump in current from 70uA to 60uA
  • Good - run3666
    • mini-run 8 had too large widths in regressed detector asymmetry
    • Quad problem, applied cut->Looks good

Non-Production Runs and Bad Runs

  • Test run3637
  • Test run3638
  • Test run3639
  • Test run3642
  • Test run3643
    • Musson injects 10uA fake signal into digital system after new chassis added
    • All the runs upto here were under slug13 conditions
  • Test run3644
    • Target Trouble Shooting
  • Test run3647
    • Beam current ~20uA. No event passed event cuts.
  • Bad run3648
    • Attempting to production but some Feedback issue
    • Quite big Aq mean, very short run ~11k events
  • Suspicious - run3649
    • Short run with many beam trips
    • Caryn says "attempting to go to production but having some FFB issues"
  • Suspicious - run3650
    • BPM11 saturated
  • Suspicious - run3651
    • BPM11 saturated
  • No Beam - run3665
  • Test - run3667
  • Test - run3668

Pedestal/Calibrations Updates

Issues

Other Status Updates