Difference between revisions of "WAC Notes October 23 2019"
From PREX Wiki
Jump to navigationJump to searchLine 39: | Line 39: | ||
** We should check all "bad" run comments to see if they were marked as bad due to Aq failure and re-consider them | ** We should check all "bad" run comments to see if they were marked as bad due to Aq failure and re-consider them | ||
** Weibin will go and look at Aq feedback logs to get this information at first order -> run list | ** Weibin will go and look at Aq feedback logs to get this information at first order -> run list | ||
+ | * '''Paul''' will make a special setup script on adaq machiens to analyze prex2 runs after tha data directory move | ||
== Planned Updates == | == Planned Updates == |
Revision as of 13:18, 23 October 2019
Documentation |
HOW TOs for shift crew |
Expert Tools |
All Expert Contacts |
PREX Main << Weekly Analysis Coordinator << WAC Notes << Instructions
WAC Notes October 16 2019 << >> WAC Notes October 30 2019
October 23th 2019
Daily Meeting BlueJeans
Agenda
Lets follow up on Tao's summarized spreadsheet https://docs.google.com/spreadsheets/u/1/d/1Y6qR_h4oW4qNmbtdpo2TIX2u_TI5qjRUZIDyEroMfl0/edit#gid=0
Issues Done
- A bunch of runs from the spreadsheet have been investigated
- Some tools for investigating runs have been developed by Tao and others (in various repositories, should be joined into JAPAN soon)
Issues Pending
- Update slugs with accurate RCDB/disagreements - https://docs.google.com/spreadsheets/u/1/d/1Y6qR_h4oW4qNmbtdpo2TIX2u_TI5qjRUZIDyEroMfl0/edit#gid=0
- Some mis-labelled runs
- Some runs with NeedsCuts should be addressed at next week's meeting - put your suggestions into the spreadsheet
- Some runs have disagreeing RCDB/slow tree EPICs data - this needs to be checked carefully and have the Blinder state forced in a separate map
- Aq failure/large charge asymmetry solution:
- We should check the pockels cell voltages to see if Aq was trying to be on/when it turns on
- We should look at the feedback log during these runs to see if it was updating
- If no Aq feedback running then probably ignore the run
- Otherwise check when Aq feedback turns back on and see in a prof plot once it converges (by eye) in order to begin accepting data
- We should check all "bad" run comments to see if they were marked as bad due to Aq failure and re-consider them
- Weibin will go and look at Aq feedback logs to get this information at first order -> run list
- Paul will make a special setup script on adaq machiens to analyze prex2 runs after tha data directory move
Planned Updates
Pedestals
- Devi has made log entries on this:
- We should look at all of the calibration runs/condition changes and make sure that the pedestals calculated accurately reflect the conditions during that time
- We should make sure that all pedestal changes are well motivated and no calibration runs were neglected
- We should make sure that early runs aren't missing pedestals that may currently have later run ranges (Due to late application)
- Robert has made a log entry on identifying pedestal changes across runs http://ace.phys.virginia.edu/HAPPEX/3917
BCM normalizer, systematic control, etc.
- Cameron has reproduced Catherine's BCM systematics vs. normalizer/Aq BCM, but now with DDs in it too - this lives in a parallel folder to the main slug plots (called PQB)
- Victoria and W&M students are running with this and making diagnostics about systematic control on Aq
- Devaki has revisited up-to-date JAPAN operations map files, made summary list of normalizing BCM in run list and compared conclusion from different sources. http://ace.phys.virginia.edu/HAPPEX/3915
Including Dithering as Production Data
- Victoria will use cuts to investigate how it looks to include the dithering data (that was cut before) as production data
Attendance
Tao, Weibin, Ryan, Cameron, Adam Phone: Paul K., Caryn, Devi, Dmitrii, Robert R., Sakib, Cip, Kent