Difference between revisions of "WAC Notes January 11 2020"
From PREX Wiki
Jump to navigationJump to search(2 intermediate revisions by the same user not shown) | |||
Line 15: | Line 15: | ||
[[Main_Page|<B>PREX Main</B>]] << [[Weekly Analysis Coordinator]] << [[WAC Notes CREX]] << [[WAC|Instructions]] | [[Main_Page|<B>PREX Main</B>]] << [[Weekly Analysis Coordinator]] << [[WAC Notes CREX]] << [[WAC|Instructions]] | ||
<br><br> | <br><br> | ||
− | [[WAC Notes December 15 2019]] << >> [[WAC Notes January | + | [[WAC Notes December 15 2019]] << >> [[WAC Notes January 16 2020]] |
== January 11 2020 == | == January 11 2020 == | ||
Line 40: | Line 40: | ||
* 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/run5650_000 Run 5650] | ||
* Good - [https://prex.jlab.org/analysis/crex/index.php?run=summary/all/run5651_000 Run 5651] - Large Aq... OK | * Good - [https://prex.jlab.org/analysis/crex/index.php?run=summary/all/run5651_000 Run 5651] - Large Aq... OK | ||
+ | ** Later: adding cuts at bad Aq sections: 70k-100k and 270k-320k events | ||
* 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/run5652_000 Run 5652] | ||
* Good - [https://prex.jlab.org/analysis/crex/index.php?run=summary/all/run5653_000 Run 5653] - Current ramp, useful as data | * Good - [https://prex.jlab.org/analysis/crex/index.php?run=summary/all/run5653_000 Run 5653] - Current ramp, useful as data | ||
+ | ** '''Questionable Aq issues''' | ||
=== Production Run List - Slug 109 - IHWP OUT - Flip-RIGHT - Production === | === Production Run List - Slug 109 - IHWP OUT - Flip-RIGHT - Production === | ||
− | * | + | * Continued in like a week -> [[WAC Notes January 16 2020]] |
− | |||
== Non-Production Runs and Bad Runs == | == Non-Production Runs and Bad Runs == |
Latest revision as of 11:53, 31 March 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 16 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
- Good - Run 5645 - beam excursion trip cut out 130k-180k, otherwise everything is back to normal :) Slug 108 begins now
- Good - Run 5646 - Cameron: LQ1 trip from 200k onward. Beam motion at 0-25k. Otherwise Good
- Good - Run 5648 - The y position has some noisy tails
- Good - Run 5649 - looks good, cut out 80-150k due to excursion
- Good - Run 5650
- Good - Run 5651 - Large Aq... OK
- Later: adding cuts at bad Aq sections: 70k-100k and 270k-320k events
- Good - Run 5652
- Good - Run 5653 - Current ramp, useful as data
- Questionable Aq issues
Production Run List - Slug 109 - IHWP OUT - Flip-RIGHT - Production
- Continued in like a week -> WAC Notes January 16 2020
Non-Production Runs and Bad Runs
- Good - Run 5647 - LQ1 cycling now - bad
Pedestal/Calibrations Updates
- https://docs.google.com/spreadsheets/d/1mt39fCuIW3Pr8TO7fzhtFjmMFt4Op30jMm5wMQke6Xo/edit?usp=sharing
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