Difference between revisions of "WAC Notes January 11 2020"

From PREX Wiki
Jump to navigationJump to search
m
m
Line 21: Line 21:
 
'''Daily Meeting [https://bluejeans.com/454783784 BlueJeans]'''
 
'''Daily Meeting [https://bluejeans.com/454783784 BlueJeans]'''
  
=== Production Run List - Slug 106 (b) - Production ===
+
=== Production Run List - Slug 107 - IHWP OUT - Flip-RIGHT - Production ===
  
* Good - [https://prex.jlab.org/analysis/crex/index.php?run=summary/all/run5636_000 Run 5636] - Ca48 150uA - very messy beam, otherwise OK small amount of data
+
* Good - [https://prex.jlab.org/analysis/crex/index.php?run=summary/all/run5636_000 Run 5636] - Ca48 150uA - very messy beam, otherwise OK small amount of data - Looks good, even with low quality beam - low avg current, so large RMS, but it's real
* The magnet setting splits this slug to 107
+
* Good - [https://prex.jlab.org/analysis/crex/index.php?run=summary/all/run5637_000 Run 5637] - Added a > 0.3 4eX cut
 +
* Good - [https://prex.jlab.org/analysis/crex/index.php?run=summary/all/run5639_000 Run 5639] - Cut out beam excursions at 0-50k and 225k-370k, otherwise OK
 +
* Good - [https://prex.jlab.org/analysis/crex/index.php?run=summary/all/run5640_000 Run 5640] - The y position has some noisy tails, but not so far away from the center to be a concern (only 0.4 mm)
 +
* Good - [https://prex.jlab.org/analysis/crex/index.php?run=summary/all/run5641_000 Run 5641] - beam excursions, cut out 60k-80k, and 300k-325k. The y position has some noisy tails
 +
* Good - [https://prex.jlab.org/analysis/crex/index.php?run=summary/all/run5642_000 Run 5642] - The y position has some noisy tails
 +
* Good - [https://prex.jlab.org/analysis/crex/index.php?run=summary/all/run5643_000 Run 5643]
 +
* Good - [https://prex.jlab.org/analysis/crex/index.php?run=summary/all/run5644_000 Run 5644]
 +
 
 +
=== Production Run List - Slug 108 - IHWP IN - Flip-RIGHT - Production ===
 +
 
 +
* Good - [https://prex.jlab.org/analysis/crex/index.php?run=summary/all/run5645_000 Run 5645] -
 +
* Good - [https://prex.jlab.org/analysis/crex/index.php?run=summary/all/run5646_000 Run 5646] -
 +
* Good - [https://prex.jlab.org/analysis/crex/index.php?run=summary/all/run5647_000 Run 5647] -
 +
* Good - [https://prex.jlab.org/analysis/crex/index.php?run=summary/all/run5648_000 Run 5648] -
 +
* Good - [https://prex.jlab.org/analysis/crex/index.php?run=summary/all/run5649_000 Run 5649] -
 +
* Good - [https://prex.jlab.org/analysis/crex/index.php?run=summary/all/run5650_000 Run 5650] -
 +
* Good - [https://prex.jlab.org/analysis/crex/index.php?run=summary/all/run5651_000 Run 5651] -
 +
* Good - [https://prex.jlab.org/analysis/crex/index.php?run=summary/all/run5652_000 Run 5652] -
 +
* Good - [https://prex.jlab.org/analysis/crex/index.php?run=summary/all/run5653_000 Run 5653] -
  
 
== Non-Production Runs and Bad Runs ==
 
== Non-Production Runs and Bad Runs ==
 
  
 
== Pedestal/Calibrations Updates ==
 
== Pedestal/Calibrations Updates ==
Line 33: Line 50:
  
 
== Issues ==
 
== Issues ==
 
+
* The magnet setting splits this slug to 107/108
 
* Adjustment in LHRS dipole current messed up the detector alignment - gets its own separate slug 107 - WAC diagnostic on widths here: https://logbooks.jlab.org/entry/3761778
 
* Adjustment in LHRS dipole current messed up the detector alignment - gets its own separate slug 107 - WAC diagnostic on widths here: https://logbooks.jlab.org/entry/3761778
 
* FFB was saturating all night, killing lots of our data with BPM cuts - this was due to improper limits on auto-gaining BPMs set by OPS - this made some strange noise upon FFB restoration after BMW cycles: https://logbooks.jlab.org/entry/3761789
 
* FFB was saturating all night, killing lots of our data with BPM cuts - this was due to improper limits on auto-gaining BPMs set by OPS - this made some strange noise upon FFB restoration after BMW cycles: https://logbooks.jlab.org/entry/3761789
 
* Run 5646 had a LQ1 trip, cutting out events 200k and onward in that run only
 
* Run 5646 had a LQ1 trip, cutting out events 200k and onward in that run only
 
=== BMOD Ana ===
 
'''note regarding beammod analysis:'''
 
 
Running the BeamMod analysis for a single run.
 
 
From ~/PREX/prompt/bmodAna/
 
create a new beammod root file from the already prompted run (####) using command
 
root -l -b -q bmodAna.C'(####,"some_input.list")'
 
 
then, to plot all combinations of alphas, deltas,and alpha/delta use the common
 
root -l -b -q plotAD.C'("path/to/rootfile/created/by/the/previous/command.root")
 
  
 
=== Counting Mode Downstream Detectors ===
 
=== Counting Mode Downstream Detectors ===

Revision as of 13:29, 15 January 2020

Documentation
HOW TOs for shift crew
Expert Tools
All Expert Contacts



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

WAC Notes December 15 2019 << >> WAC Notes January 12 2020

January 11 2020

Daily Meeting BlueJeans

Production Run List - Slug 107 - IHWP OUT - Flip-RIGHT - Production

  • Good - Run 5636 - Ca48 150uA - very messy beam, otherwise OK small amount of data - Looks good, even with low quality beam - low avg current, so large RMS, but it's real
  • Good - Run 5637 - Added a > 0.3 4eX cut
  • Good - Run 5639 - Cut out beam excursions at 0-50k and 225k-370k, otherwise OK
  • Good - Run 5640 - The y position has some noisy tails, but not so far away from the center to be a concern (only 0.4 mm)
  • Good - Run 5641 - beam excursions, cut out 60k-80k, and 300k-325k. The y position has some noisy tails
  • Good - Run 5642 - The y position has some noisy tails
  • Good - Run 5643
  • Good - Run 5644

Production Run List - Slug 108 - IHWP IN - Flip-RIGHT - Production

Non-Production Runs and Bad Runs

Pedestal/Calibrations Updates

Issues

  • The magnet setting splits this slug to 107/108
  • Adjustment in LHRS dipole current messed up the detector alignment - gets its own separate slug 107 - WAC diagnostic on widths here: https://logbooks.jlab.org/entry/3761778
  • FFB was saturating all night, killing lots of our data with BPM cuts - this was due to improper limits on auto-gaining BPMs set by OPS - this made some strange noise upon FFB restoration after BMW cycles: https://logbooks.jlab.org/entry/3761789
  • Run 5646 had a LQ1 trip, cutting out events 200k and onward in that run only

Counting Mode Downstream Detectors

  • Removed from cuts and correlator channel maps for safety