WAC Notes April 1 2020

From PREX Wiki
Revision as of 11:32, 1 April 2020 by Cameronc (Talk | contribs) (Finalize Run List and prepare JAPAN analysis for Respin)

Jump to: navigation, search
HOW TOs for shift crew
Expert Tools
All Expert Contacts

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

WAC Notes March 24 2020 << >> WAC Notes April 3 2020

April 1 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 :/ )


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, and that all cuts are applied as needed. We should also decide which run ranges should receive which pedestals, as well as dithering slopes (mostly done). There are also some additional items to add into regression and dithering corrections for AT and SAM analyses.

  • Tools:
    • Full Experiment Aggregator chained file: ~/PREX/prompt/aggRootfiles/slugRootfiles/grandRootfile/CREX-full-miniruns.root
    • Run List spreadsheet
    • List of calibration runs -> Needs to be completed with AT and Main detector moves/HV changes for pedestal applicability
  • 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
    3. Verify all needed cuts
    4. Apply pedestals to accurate run ranges
      • Update the spreadsheet with Detector moves and HV changes
    5. Finalize dithering slopes
  2. Go back over pedestal analyses again, triple check the list of calibrations and incidents
  3. 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
  4. Add more SAM combos?

Make a run range map files list, for safety

  • 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

1X BPM bad wire questions

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/