Difference between revisions of "WAC Notes April 8 2020"

From PREX Wiki
Jump to: navigation, search
m (Issues)
Line 59: Line 59:
##** Some of the EPICS and slopes and such have _slope and maybe _slope_error or _mean and are what you would expect
##** Some of the EPICS and slopes and such have _slope and maybe _slope_error or _mean and are what you would expect
## Verify all needed cuts
## Verify all needed cuts
##* 12X +- 0.8mm shifts -> Corresponds to 2e-4 dpp shift. Devi is investigating and will update next week.
##* Burp cuts
##* Burp cuts
##* Time scale of beam trip cut
##* Time scale of beam trip cut

Revision as of 13:09, 11 April 2020

HOW TOs for shift crew
Expert Tools
All Expert Contacts

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

WAC Notes April 1 2020 << >> WAC Notes April 15 2020

April 8 2020

Weekly Meeting BlueJeans

  • Run List spreadsheet
  • List of calibration runs
  • Full Experiment Aggregator chained file: ~/PREX/prompt/aggRootfiles/slugRootfiles/grandRootfile/CREX-full-miniruns.root
  • PREX version: ~/PREX/prompt/aggRootfiles/PREXII_slugRootfiles/grandRootfile/PREX-full-miniruns.root (maybe 20% of the data got messed up somehow :/ )
  • Kent's collab meeting list of tasks


Finalize Run List and prepare JAPAN analysis for Respin

  • We meed to go through all of our notes and make sure any loose ends are tied off
  • Make sure that all cuts are applied as needed (i.e. burp cuts have the right scale)
  • We should also decide which run ranges should receive which pedestals
  • Decide on runranged dithering slopes
  • There are also some additional items to add into regression and dithering corrections for AT and SAM analyses

  • To Do List
  1. Finalize Run List (spreadsheet)
    1. Go through all WAC Notes
    2. Go through runs with curious behavior from full-CREX aggregated file (~/PREX/prompt/aggRootfiles/slugRootfiles/grandRootfile/CREX-full-miniruns.root)
      • n_runs == Slug number branch. Was originally intended to denote how many runs had been TChained to derive a given file's outputs, but we just do miniruns and such these days instead.
      • run_number == Run number branch
      • minirun_n == Minirun ID branch (starts at 0 for first minirun of each run)
      • split_n == Nothing for now. Was originally intended to denote split runs in JAPAN analysis, but other scripts never fully supported it and it rarely comes up
      • All of the data in these aggregator files is exactly ErrorFlag==0 passing data, meaning it cuts out BMOD ON data and also fails to properly consider AT and SAM error flags (in prompt outputs, see respins for proper global error flag on those).
      • The individual data fields for a given device are as follows:
        • _mean == mean value for a given minirun
        • _mean_error == the error on the mean
        • _rms == the RMS from the histogram for a given minirun
        • _rms_error == the error on RMS calculation (probably not really useful)
        • _nentries == the number of Multiplet entries used in the minirun for the histogram to obtain the above numbers
        • Some of the EPICS and slopes and such have _slope and maybe _slope_error or _mean and are what you would expect
    3. Verify all needed cuts
      • 12X +- 0.8mm shifts -> Corresponds to 2e-4 dpp shift. Devi is investigating and will update next week.
      • Burp cuts
      • Time scale of beam trip cut
      • Stability cut on BCM over noisy time frames
    4. Go back over pedestal analyses again, triple check the list of calibrations and incidents
      • Update the spreadsheet with Detector moves and HV changes
      • Note when pedestals were used and when they should be used
      • Update on unser scans and more detailed pedestal analyses
      • SAMs pedestals for AT purposes
    5. Update all dithering slopes and properly run-range as well
  2. Update AT combos
    • Add Combos sensitive to A_{PV}. atl_avg_atr_avg_avg (exists) and at1_avg_at2_avg_avg
    • Vertical
      • asym_atl_avg_atr_avg_dd (exists) DD of (Left AT_in L A_T out avg ) and (R AT_in ,R AT_out avg)
      • asym_at1_dd_at2_dd_avg Avg of ( Left AT_in - Right AT_in ) and (Left AT_out , Right AT_out DD)
      • asym_atl1r2dd_atl2r1dd_avg Avg of (Left A_Tin , Right AT_out DD) and (Left AT_out - R AT_in DD)
    • Horizontal
      • asym_atl_dd_atr_dd_avg (exists) Avg of (Left AT_in L A_T out DD ) and (R AT_in ,R AT_out DD)
      • asym_at1_avg_at2_avg_dd DD of ( Left AT_in, Right AT_in avg) and (Left AT_out , Right AT_out Avg)
      • asym_atl1r2dd_atl2r1dd_dd DD of (Left A_Tin , Right AT_out DD) and (Left AT_out - R AT_in DD)
    • Combinations of Main + ATs (see PREX)
    • Add global cuts for AT detectors
  3. Add more SAM combos?

Map files: make a text file with the run ranged map files list

  • Look at pedestals actually used, vs map file implementation
  • Apply pedestals onto the times for which they actually apply
  • Verify the quality of pedestals, and systematic impacts too
  • Make sure everything is properly committed

1X BPM bad wire questions

  • We should analyze how dangerous the flaky 1X cable was for Parity Analysis. We clearly saw mm scale shifts in the calculated X/Y positions, but this may have just been a pedestal change due to some signal pickup. Is it bad for diff calculations?

PVDB and Aggregator replacement on ifarm

  • Sakib and Cameron are planning to just use the aggregation tools that Tao has already put together for the ifarm respins. Most of the scripts already in use can be modified to work on the JAPAN and postpan summary trees without much hassle. This is ongoing
  • The PVDB is up and running on the ifarm. It requires python2 and ROOT 5.34, but it at least allows read privileges from the PVDB

Tying Compton Electron and Photon detector runs to Parity Data (for convenience and such)

RCDB is good for this. The time stamps are a bit hard to use, but they are there -> https://hallaweb.jlab.org/rcdb/

State of Updates

Run list

  • Cameron has gone through BCM Aq and DD problematic runs:
    • 6201 - Added 10k events to Weibin's cut
    • 6212 - Laser issues abound. Lots of BCM noise, and the Aq mean is >3 ppm, so this run may need to be put on the suspicious list. Otherwise it looks great. I don't know what the real problem is here. Ironically, once the beam noise hair goes away is when the charge asymmetry jumps off by 10 sigma... should we just trash the whole run for laser/clipping suspicions?
    • 6585 - has some trippy beam, but I'm leaving it alone for now.
    • Generally we decided to not cut on Aq, especially if the cause is understood and it isn't a BCM hardware issue (i.e. PITA wrong, Aq feedback wrong, or Laser noise all pass cuts).


Cameron has gone through the slugs for CREX and made what quick slug splitting and supercycle pruning decisions I could with the data on hand. All slugs are basically fine now with a few exceptions:

  • 109: Has lots of actual changes, hard to catch with slug averaging and splitting
  • 121: Missing some entries maybe... need to decide how to split this slug
  • 124: It's a weird slug, but probably OK as it stands
  • 128: Misses the entry for run 6176 (This isn't really an issue, but for now the way I have the scripts doing splits I assume that all runs including and after the run for a specific supercycle entry in the dithering slopes rootfile will be the members of a slug "split", meaning that if a split starts at a certain run, but there is no supercycle for that run, then the split in the dithering slopes rootfile won't know to affect that missing entry and it will accidentally be lumped in with whichever split number applies to the runs before that missing entry - the missing entry in the slopes rootfile can be manually run-ranged later if we use the same text-file method as in PREX respin, but this note here serves as our warning about it)
  • 130: unneccessary split?
  • 136: unneccessary split?
  • 139: Misses a needed split entry for run 6563
  • 145: Misses a needed split entry for run 6684
  • 165: unneccessary split?
  • 166: unneccessary split?
  • 168: unneccessary split?

So there are at least 3 slugs (that Cameron noticed) that need to be carefully looked at to get the splitting right (on top of what I've already noted inside of the rootfiles and scripts).


Work has been assigned to look at specific calibration runs and make sure error bars are being utilized correctly for pedestals

  • Cameron and Caryn have updated the unser pedestal analysis to have RMS error bars and output in a root file. See http://ace.phys.virginia.edu/HAPPEX/4062, https://logbooks.jlab.org/entry/3809639
  • Robert has extracted which pedestals were used from CREX data
  • Weibin has denoted the applicability of various pedestal runs (in a new tab on the google sheet)
  • Amali has finished the pedestal analysis scripts for most runs