Difference between revisions of "WAC Notes February 3 2020"

From PREX Wiki
Jump to: navigation, search
(Production Run List - Slug 128 - IHWP IN - Flip-RIGHT - Production)
(February 3 2020)
Line 43: Line 43:
 
* Good - [https://prex.jlab.org/analysis/crex/index.php?run=summary/all/run6178_000 Run 6178]
 
* Good - [https://prex.jlab.org/analysis/crex/index.php?run=summary/all/run6178_000 Run 6178]
 
* Good - [https://prex.jlab.org/analysis/crex/index.php?run=summary/all/run6179_000 Run 6179]
 
* Good - [https://prex.jlab.org/analysis/crex/index.php?run=summary/all/run6179_000 Run 6179]
 +
continue slug 128 on [https://prex.jlab.org/wiki/index.php?title=WAC_Notes_February_4_2020 February 4]:
  
 
== Non-Production Runs and Bad Runs ==
 
== Non-Production Runs and Bad Runs ==

Revision as of 16:07, 4 February 2020

Documentation
HOW TOs for shift crew
Expert Tools
All Expert Contacts



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

WAC Notes February 2 2020 << >> WAC Notes February 4 2020

February 3 2020

Daily Meeting BlueJeans


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

continue slug 127 from February 1:

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

this slug at about 6 am

continue slug 128 on February 4:

Non-Production Runs and Bad Runs

Pedestal/Calibrations Updates

Issues

  • double peak in bpm X appears since run 6161, continues to most recent run
  • raw asym of url goes up to huge value
  • 3 (12:00 - 15:00) hours of hall C spin dance
  • LQ2 tripped off at 19:07
  • it looks like the bpm X double peak just gone after we return to production run 6176, though we still don't know why there comes the double peak and how it goes away?

Updates