Difference between revisions of "WAC Notes January 7 2021"

From PREX Wiki
Jump to: navigation, search
m
m (General)
Line 74: Line 74:
 
Concerns:
 
Concerns:
 
* Any run which had special cuts applied to segment BPM 12X regions will need to be checked on after respin 1 to retune those cuts  
 
* Any run which had special cuts applied to segment BPM 12X regions will need to be checked on after respin 1 to retune those cuts  
*  
+
* BCM analog difference value doesn't compute correctly in the aggregator ... is .hw_sum an invalid leaf? Is there an assumed /ppm in the grand plots script for yield_.._mean?
 +
* All BCM Aqs have a much larger difference between wien states and away from 0.0 for respin1 vs. prompt. Is the pedestal wildly off during prompt or during respin1? More pedestal studies should be done to decide what is going on.
 +
* The main detector's regressed RMS has a drop from prompt->respin, especially around the slug 140 region.
 +
* The Chi2 values are all pretty small, and got smaller with respin1 vs prompt.
 +
* Detector asymmetry "answer" did not change value or error bar very much between prompt and respin1.
  
 
=== Runs for checking later ===
 
=== Runs for checking later ===
*  
+
*
 
+
  
 
== December 10th notes, updates from Dec 3 ==
 
== December 10th notes, updates from Dec 3 ==

Revision as of 12:06, 7 January 2021

RCDB HALOG HAPLOG DocDB Online Prompt BlueJeans Link Runlist spreadsheet, respin 1 spreadsheet

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

WAC Notes December 10 2020 << >> WAC Notes January 14 2021

Organization

Date and time: January 7, 2021, 11:00am
Bluejeans ID: 454783784
Meeting link: https://bluejeans.com/454783784
Runlist spreadsheet

January 7th notes, updates from the respin 1

Analyses that need to be done with respin 1 data:

  • Determine changes to the data as a result of changes in map files and cuts between prompt and respin 1
  • Determine efficacy and quality of BCM, target and energy BPM cuts across all runs (and develop changes to cuts if necessary)
  • Cyclewise, runwise, and run-range-wise BMOD data quality determinations need to be solidified (AT data from respin 1 can be a ifarm script testing ground)
  • BMOD slopes calculation and map files, and Lagrange+eigenvector BPM analysis set up
  • Second pass pedestal studies, including looking at RF injected runs and beam off pedestals across all of CREX for all monitors and detectors
    • Look at charge-normalized and regression corrected detectors vs. another BCM (not bcm_target) to check for non-zero pedestals or correlations.
    • Should be consistent at < 1 or 2 % level.
    • Beam off pedestals should also not be deviated from.
  • Reclassify and update all NeedCut, Suspicious, and non-production (but "good") runs based on respin 1 data quality and known needed changes
  • Develop tools with respin 1 to evaluate beam correction, Aq, and pedestal systematics across the run
  • Generate more useful and specific slug plots, etc.
  • Pitt and Wien level plots, systematics, etc.
  • Carefully check on various time scale pull plots (multiplet wise, miniruns, slugs, pitts, wiens, etc.)
  • Null asymmetry check
  • Sub-block analysis consistency check
  • SAMs analysis (especially during AT running)

To Do:

  • Comparison of number of events/patterns per slug between Respin 1 and Prompt
    • Also check on the size of regressed error bar
    • Will be done by Robert
  • Devi can look at BPM and BCM fluctuations away from comfort ranges
  • Each WAC should scan their weeks' data to see if anything looks bad
    • Runlist verification etc. will be done by WACs
  • BMOD analysis is being done by Cameron + bmod subgroup
  • Cameron and Weibin will look over pedestal checking, etc.
  • Weibin and Sakib can help will Null asymmetry analysis
  • Looking at cuts (especially burp cuts) should happen after Devi looks at BPM ranges, etc.

Suggested Changes after respin1

  • Cuts size, extent, holdoffs?
  • Regression BPM selection?
  • Manual cuts for target and 12X BPMs need another look?
  • Pedestals need a more detailed look
  • Special runs with known tune change that get special cuts to segment miniruns properly

General

Tracking events and calibrations:

Respin 1 outputs

Concerns:

  • Any run which had special cuts applied to segment BPM 12X regions will need to be checked on after respin 1 to retune those cuts
  • BCM analog difference value doesn't compute correctly in the aggregator ... is .hw_sum an invalid leaf? Is there an assumed /ppm in the grand plots script for yield_.._mean?
  • All BCM Aqs have a much larger difference between wien states and away from 0.0 for respin1 vs. prompt. Is the pedestal wildly off during prompt or during respin1? More pedestal studies should be done to decide what is going on.
  • The main detector's regressed RMS has a drop from prompt->respin, especially around the slug 140 region.
  • The Chi2 values are all pretty small, and got smaller with respin1 vs prompt.
  • Detector asymmetry "answer" did not change value or error bar very much between prompt and respin1.

Runs for checking later

December 10th notes, updates from Dec 3

  • Pedestal update (a temporary placeholder) summarized in HAPLOG 4417
  • Prompt data set summarized in HAPLOG 4418
  • Cuts and other Respin updates summarized in HAPLOG 4419
    • Added bcm_an_diff device to all CREX runs, resolving issue that was especially bad in runs 8350-8370: https://logbooks.jlab.org/entry/3845576
      • Added bcm_an_diff cut to all CREX runs already having reasonable current cuts
combinedbcm, bcm_an_diff,       -10,     +10,    g,      0,   0.15
  • Weibin added a bcm_an_diff plot to ifarm install of prompt plots
    • He'll update the cut to only do can events when (bcm_an_diff.Device_ErrorCode&0x40001c00)!=0 && (ErrorFlag&0x8000000)==0
    • If possible edit the asyms to diffs in their plots
  • Cameron updated the Error Counter macro on the ifarm install
    • Will change the general cut information to show Beam Trip and All Else separately -> (ErrorFlag&0x8000000)==0 cuts out beam trip data
    • And change percentages to N events
  • The target BPMs are not easily diagnosable from minirun plots (thanks Weibin), but will be analyzed similarly to the BPM12X data after respin1
    • Note that at run 6500 we have a major change in our optics and beam delivery, which produces similar beam instability as we saw at the beginning of the experiment in slug 100 or so
    • Some documentation of pedestal investigations during that time here: https://logbooks.jlab.org/entry/3787428
  • Some commits of changes on adaq computer may conflict with committed or uncommitted changes on the ifarm (due to push pull privileges and edits testing)
  • Weibin created a run list of runs included in prompt runlist text files but disagreeing in the RCDB: https://docs.google.com/spreadsheets/d/1l5qA0u9KhLIFA-MbcEpI3ezUD9saq6g1kzB_eTJD_po/edit#gid=214727289
  • Robert made a run list for respin 1 with generous filters: respin 1 spreadsheet

How to use Aggregator

Now updated to include "rcdb_[run_condition]" branches (converted to doubles, string entries have a lookup table given in the camDataFrame.hh source code).

  • 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

Attendence

Cameron, Paul, Weibin, Adam Zec, Robert Radloff, Ryan, Sakib, Victoria, Juliette, Devi