Difference between revisions of "WAC Notes November 19 2020"

From PREX Wiki
Jump to: navigation, search
m (→‎General)
m (→‎Cameron)
 
Line 56: Line 56:
 
Beginning of the second run period. It is in identical conditions to how we left in March.
 
Beginning of the second run period. It is in identical conditions to how we left in March.
  
−
See full notes from last week '''[[WAC_Notes_November_19_2020#Cameron|here]]'''.
+
See full notes from last week '''[[WAC_Notes_November_12_2020#Cameron|here]]'''.
 
* Main takeaway from that discussion is the questionable cuts runs will be addressed after respin 1 when checking how the burp cut changes do for removing 12X jumps.   
 
* Main takeaway from that discussion is the questionable cuts runs will be addressed after respin 1 when checking how the burp cut changes do for removing 12X jumps.   
 
* Otherwise there were some notes about potential BMOD slope segmentations that should be checked out (usually denoted in italics or bold).
 
* Otherwise there were some notes about potential BMOD slope segmentations that should be checked out (usually denoted in italics or bold).

Latest revision as of 12:30, 3 December 2020

RCDB HALOG HAPLOG DocDB Online Prompt BlueJeans Link Runlist spreadsheet

PREX Main << Weekly Analysis Coordinator << WAC Notes CREX << WAC Post-Run_Meeting Notes

WAC Notes November 12 2020 << >> WAC Notes December 3 2020

Organization

Date and time: November 19, 2020, 11:00am
Bluejeans ID: 454783784
Meeting link: https://bluejeans.com/454783784
Runlist spreadsheet

Updates on action items from 12 November

  • Paul: Event-level BCM difference combination
    • New variable bcm_an_diff defined as (bcm_an_us-bcm_an_ds)/2, initial commit just has it starting at run 7502 to test it. This should be pushed back to all CREX runs.
      • Weibin will add a plot to the ifarm prompt plots scripts (and show Cameron where these live)
    • Event cut on this channel (initially defined in prexCH_beamline_eventcuts.8301-.map to test it): must be in -10 to +10 range (so up to 20 uA difference possible; could be tighter if desired); no stability cut; burp cut level of 0.15 (so a change in the disagreement by 0.3 uA triggers the burp). This was initially tested using run 8354.
    • Victoria has done further testing.
    • Robert will propagate this variable to all map files and do spot checks
    • Need to add this variable to our monitoring plots
    • Do we have a way to keep track of how many event are cut due to this reason?
  • Back-propagating pedestals to start of run2 period
  • Cuts monitoring
    • Can be tracked with the error counter macro
    • Needs to be uncommented
    • Add a text file printing for this info
    • Track which devices are triggers for non-beam trip cuts
    • Include BPM 12X and BCM difference (above definition)

November 5th notes

  • Weibin: stability cuts map files
  • Robert and Paul: burp cuts
  • Special cuts for runs 6852, 7860, 8321, 8507, and more? Coming from injector conditions, etc. These should be verified. Also run 7402 needs an individual file due to IHWP change. Make sure we have a list of any runs that need "chainfiles" set since submission script needs to be special too.
    • 6852 - /adaqfs/home/apar/PREX/japan_WAC_only/Parity/prminput/eventNumberCut.6852.conf # Cuts to keep only evnts with Ca-48 target in position - cut out event=20000:
    • 7402 - /adaqfs/home/apar/PREX/japan_WAC_only/Parity/prminput/prex_bad_events.7402.map #HWP changed after starting the run - cut out 0:2000
    • 7842 - split two 12X domains, needs revisiting
    • 7860 (blinder.force-target-blindable=1)
    • 8321 (chainfiles=1)
    • 8507 - /adaqfs/home/apar/PREX/japan_WAC_only/Parity/prminput/eventNumberCut.8507.conf # Cuts to keep only events with Ca-40 target in position - cut out event=20000:, blinder.force-target-out=1
    • and more? Coming from injector conditions, etc.
  • Cameron and Amali: new pedestals
  • Other updates

Suggested Changes

Each WAC will suggest changes for their run period, which will be discussed at this meeting:

Cameron

Beginning of the second run period. It is in identical conditions to how we left in March.

See full notes from last week here.

  • Main takeaway from that discussion is the questionable cuts runs will be addressed after respin 1 when checking how the burp cut changes do for removing 12X jumps.
  • Otherwise there were some notes about potential BMOD slope segmentations that should be checked out (usually denoted in italics or bold).
  • Runs 7626 and 7657 and 7798 should get marked as good, or at least get included in the respin to check again with ideal pedestals and cuts.

Sakib

Slug 195- 7865 and 7866 is flagged as need cut. Slightly higher asym_us_avg rms. WAC comment indicates dp/p fluctuation. No other obvious issues. Ok to reclassify or needs a closer look?

Slug 196- 7867 and 7869 has the same issue of dp/p fluctuations.

Some runs from August 21 onwards might need bpm12X cuts. Still sorting through them.

Weibin

Victoria

Robert

General

Tracking events and calibrations:

Concerns:

  • Need global cuts on ATs (probably also including at the end when they get blinded)
  • Run 8107 is likely a "good" production run, but was labelled as a pedestal run


Weibin's stability/burp cuts info:

  • Weibin harvested the cut levels from map files and sees that there is a only one BCM with stability and no burp cuts: HAPLOG
  • And the BPMs burp cut changes from 2000 to 0 only at some point (around run 7600), but it needs to be clarified.
  • Victoria says this has to do with BMOD having some data get cut that shouldn't have.
  • Paul says he and Robert were working on getting the stability/burp cut map files to work correctly, which will require some spot checking to see if anything changes severely
  • Recall why changes in cuts took place during running.
  • We should, before respin 1, spot check a consistent set of burp cuts, scan over current good-events statistics, count how many 12X events we expect to get cut out, and then see if that is matched by a respin 1.
    • Checking the runs in slug 186 to see if it works there would be a good testing grounds
    • Also 7701 and 7718

Runs for checking later

Get pedestals set properly for initial part of the run - decide after respin whether to keep 7626

  • 7626 - decide after respin
  • 7627 - good
  • 7701, 7718 need burp cut checks for sure
  • 8157 looks to have a hardware issue in BPM 11
  • Burp cuts and 12X cuts will be further scrutinized after the respin 1 data is made available (though we should make a systematic scan of current ErrorFlag statistics and 12X suspicious spikes).


Respin needs to consider specially:

  • 6852 - /adaqfs/home/apar/PREX/japan_WAC_only/Parity/prminput/eventNumberCut.6852.conf # Cuts to keep only evnts with Ca-48 target in position - cut out event=20000:
  • 7402 - /adaqfs/home/apar/PREX/japan_WAC_only/Parity/prminput/prex_bad_events.7402.map #HWP changed after starting the run - cut out 0:2000
  • 7842 - split two 12X domains, needs revisiting
  • 7860 (blinder.force-target-blindable=1)
  • 8321 (chainfiles=1)
  • 8507 - /adaqfs/home/apar/PREX/japan_WAC_only/Parity/prminput/eventNumberCut.8507.conf # Cuts to keep only events with Ca-40 target in position - cut out event=20000:, blinder.force-target-out=1

Attendence

Cameron, Adam, Devi, Paul King, Ryan, Sakib, Victoria, Weibin

Retrieved from "https://prex.jlab.org/wiki/index.php?title=WAC_Notes_November_19_2020&oldid=12218"