Difference between revisions of "WAC Notes July 26 2019"

From PREX Wiki
Jump to: navigation, search
(Non-Production Runs and Bad Runs)
(Production Run List)
 
(39 intermediate revisions by the same user not shown)
Line 23: Line 23:
 
=== Production Run List ===
 
=== Production Run List ===
  
Start [https://hallaweb.jlab.org/parity/prex/onlinePlots/slug/slug_list/slug14-Left/y_postPanPlots_slug14-Left.pdf Slug 14, IHWP In, FFB on always]  
+
Start [https://hallaweb.jlab.org/parity/prex/onlinePlots/slug/slug_list/slug14/y_postPanPlots_slug14.pdf Slug 14, IHWP In, FFB on always]  
*** Since we are using bcm_dg_ds, the width in the bcm asymmetry is 1.5X 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'''
* Suspicious - [https://hallaweb.jlab.org/parity/prex/onlinePlots/index.php?run=summary/all/run3640_000 run3640]
+
** '''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'''
** This run was taken during collimator scan
+
** '''SAM3 started saturating since run3640'''
** Aq widths are too large
+
** '''Should we think about changing saturation limit for this SAM?'''
* Suspicious - [https://hallaweb.jlab.org/parity/prex/onlinePlots/index.php?run=summary/all/run3641_000 run3641]
+
** '''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'''
** Aq widths are too large (>200ppm)
+
* Good - [https://hallaweb.jlab.org/parity/prex/onlinePlots/index.php?run=summary/all/run3649_000 run3649]'''ADDED from suspicious list'''
** Started with 1uA checking position then go to 70uA
+
** Short run with many beam trips
 +
** Caryn says "attempting to go to production but having some FFB issues"
 +
* Good - [https://hallaweb.jlab.org/parity/prex/onlinePlots/index.php?run=summary/all/run3650_000 run3650]'''ADDED from suspicious list'''
 +
** BPM11 saturated for a long time
 +
* Good - [https://hallaweb.jlab.org/parity/prex/onlinePlots/index.php?run=summary/all/run3651_000 run3651]'''ADDED from suspicious list'''
 +
** BPM11 has saturated couple of times
 +
* Good - [https://hallaweb.jlab.org/parity/prex/onlinePlots/index.php?run=summary/all/run3652_000 run3652]
 +
* Good - [https://hallaweb.jlab.org/parity/prex/onlinePlots/index.php?run=summary/all/run3653_000 run3653]
 +
* Good - [https://hallaweb.jlab.org/parity/prex/onlinePlots/index.php?run=summary/all/run3654_000 run3654]
 +
* Good - [https://hallaweb.jlab.org/parity/prex/onlinePlots/index.php?run=summary/all/run3655_000 run3655]
 +
* Good - [https://hallaweb.jlab.org/parity/prex/onlinePlots/index.php?run=summary/all/run3656_000 run3656]
 +
* Good - [https://hallaweb.jlab.org/parity/prex/onlinePlots/index.php?run=summary/all/run3657_000 run3657]
 +
* Good - [https://hallaweb.jlab.org/parity/prex/onlinePlots/index.php?run=summary/all/run3657_000 run3658]
 +
* Good - [https://hallaweb.jlab.org/parity/prex/onlinePlots/index.php?run=summary/all/run3659_000 run3659]
 +
* Good - [https://hallaweb.jlab.org/parity/prex/onlinePlots/index.php?run=summary/all/run3664_000 run3664]
 +
** Regressed detector widths are ~5ppm higher than previous runs->might be due to the jump in current from 70uA to 60uA
 +
* Good - [https://hallaweb.jlab.org/parity/prex/onlinePlots/index.php?run=summary/all/run3666_000 run3666]
 +
** mini-run 8 had too large widths in regressed detector asymmetry
 +
** Quad problem, applied cut->Looks good
  
 
== Non-Production Runs and Bad Runs ==
 
== Non-Production Runs and Bad Runs ==
Line 38: Line 56:
 
* Test [https://hallaweb.jlab.org/parity/prex/onlinePlots/index.php?run=summary/all/run3642_000 run3642]
 
* Test [https://hallaweb.jlab.org/parity/prex/onlinePlots/index.php?run=summary/all/run3642_000 run3642]
 
* Test [https://hallaweb.jlab.org/parity/prex/onlinePlots/index.php?run=summary/all/run3643_000 run3643]
 
* Test [https://hallaweb.jlab.org/parity/prex/onlinePlots/index.php?run=summary/all/run3643_000 run3643]
 +
** Musson injects 10uA fake signal into digital system after new chassis added
 +
** '''All the runs upto here were under slug13 conditions'''
 +
* Test [https://hallaweb.jlab.org/parity/prex/onlinePlots/index.php?run=summary/all/run3644_000 run3644]
 +
** Target Trouble Shooting
 +
* Test [https://hallaweb.jlab.org/parity/prex/onlinePlots/index.php?run=summary/all/run3647_000 run3647]
 +
** 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
 +
** Only 4k events have passed event cuts
 +
* No Beam - [https://hallaweb.jlab.org/parity/prex/onlinePlots/index.php?run=summary/all/run3665_000 run3665]
 +
* Test - run3667
 +
* Test - run3668
  
 
== Pedestal/Calibrations Updates ==
 
== Pedestal/Calibrations Updates ==
 +
*Current Calibration [https://hallaweb.jlab.org/parity/prex/onlinePlots/index.php?run=summary/all/run3645_000 run3645]
 +
** New target (D9PbD10)
 +
* PITA Scan [https://hallaweb.jlab.org/parity/prex/onlinePlots/index.php?run=summary/all/run3646_000 run3646]
  
 
== Issues ==
 
== Issues ==
Line 45: Line 79:
 
== Other Status Updates ==
 
== Other Status Updates ==
 
* [https://hallaweb.jlab.org/parity/prex/onlinePlots/slug/slug_list/Charge_Monitor-2019-07-25.pdf Accumulated charge] =  
 
* [https://hallaweb.jlab.org/parity/prex/onlinePlots/slug/slug_list/Charge_Monitor-2019-07-25.pdf Accumulated charge] =  
 
+
* bcm_dg_ds pedestal map has been updated [https://logbooks.jlab.org/entry/3710499 HAPLOG]
 
+
* started burpcut since '''slug13'''
 
[[Category:WAC]]
 
[[Category:WAC]]

Latest revision as of 20:48, 6 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 - run3649ADDED from suspicious list
    • Short run with many beam trips
    • Caryn says "attempting to go to production but having some FFB issues"
  • Good - run3650ADDED from suspicious list
    • BPM11 saturated for a long time
  • Good - run3651ADDED from suspicious list
    • BPM11 has saturated couple of times
  • 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
    • Only 4k events have passed event cuts
  • No Beam - run3665
  • Test - run3667
  • Test - run3668

Pedestal/Calibrations Updates

Issues

Other Status Updates