Difference between revisions of "WAC Notes April 1 2020"

Revision as of 13:56, 7 April 2020

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

Issues

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 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
   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 all dithering slopes and properly run-range as well
4. 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
5. 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

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

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/

Updates

Run list

• From Cameron's runlist:
  • Run 5452 - Comment: 6x6 raster - ablation/heating burn in test - production, but suspicious - Decision: only 10 minutes... probably not worth including in the data if it just makes extraction more suspect, marking as Suspicious again
  • Run 5939 - Comment: 60 uA, ignore for now - Decision: Aq way off, don't include this low impact data
  • Run 5940 - Comment: 60 uA, ignore for now - Decision: Aq way off, mostly, also don't include
  • Run 6032 - Comment: 10 minutes of 100 uA data, probably good - Decision: Keep it (Yay, new data)

• Cameron has gone through BCM Aq and DD problematic runs and added cuts/questions for the next meeting

BMOD

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

Pedestals

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