WAC Notes September 18 2019

Documentation

HOW TOs for shift crew

Expert Tools

All Expert Contacts

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

WAC Notes September 9 2019 << >> WAC Notes September 19 2019

September 18 2019

Daily Meeting BlueJeans

Data

We want to look at all of the data and figure out what changes need to be done to get ready for respin/final results (idealistically)

Issues

• Slug 7 needs to be changed to correctly reflect IHWP setting
• Dithering sensitivity changes/other kinds of changes should not be considered as slug changes

Slug 0 Inclusion

• Slug 0 was marked as suspicious at the time

Slugs 1-3 Inclusion

• Because of different BPM DAQ inclusion we haven't been using these slugs in our aggregation
• An aggregator hack can be done or we can just have the plots be empty

Slug 7 update

• Prior slug 6 was ~50 uA, and OUT
• Slug 7 is basically a parity scan
• Goal is to take the tail of "slug 7" as it was originally taken and make it part of slug 6
  • Take 3444-3446 as IN, slug 7
  • Take 3447-3452 and put them in OUT slug 6 (because slug 8 is basically left arm only... hard to merge in)

Slug 13-18 slugs inclusion

• Devi has included data from some of his slugs into the lists that were previously not there (will show up in respin)

Single/Both arm slugs ???

• Slug 43 has 4 runs with only one arm
• Slug 74 has several runs with only one arm

To resolve these:

• Could make the aggregation scripts check the arm variable in order to make plots correctly
• Could do add + 100 for right only, + 200 for left only

Lets add BMOD Active Data back into our "good" data cut

• We need to identify exactly what the JAPAN decoding -> BMOD-on flagging mechanism is, and maybe pass off this flag to another place
• We need to verify that this is OK with plots and stuff
  • Original data set
  • Only BMOD on data set
  • Both together data set
  • If anythin crazy happens then this needs further investigation
• This requires amending the error flag cuts everywhere to show BMOD in the "good" data

Planned Updates

Pedestals

• 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)

Attendance

Cameron, Tao, Victoria, Devi, Adam, Eric, Weibin, Ryan, Sakib, Robert, Paul King