Difference between revisions of "20191216-Analyzer-Mtg"

From PREX Wiki
Jump to navigationJump to search
Line 16: Line 16:
 
#  Operations was remade and installed last week; new issues?
 
#  Operations was remade and installed last week; new issues?
 
##  Issue [https://github.com/JeffersonLab/japan/issues/269 269]:  diff* variables are missing in burst and muls trees
 
##  Issue [https://github.com/JeffersonLab/japan/issues/269 269]:  diff* variables are missing in burst and muls trees
 +
##*  This is probably just a labelling issue
 
##  Pushing the last minirun into the previous if it is "too short"
 
##  Pushing the last minirun into the previous if it is "too short"
 +
##*  Maybe do one runthough just to get the total events, then have the burst advancement only if we have at least a full burst remaining (or maybe more, to account for bad events)
 +
##*  Alternately, do a pass1 without making the trees, and only create the trees on second pass.  Combine the slopes from the short minirun with the previous, and we need another label to tell the system when to do the burst advancement on the second pass
  
 
=== Prompt analysis toolchain ===
 
=== Prompt analysis toolchain ===

Revision as of 11:14, 16 December 2019

Back to Main Page >> Analyzer_Meeting

previous meeting << >> following meeting

Logistic information

Meeting room at JLab: Counting House Conference Room

 BlueJeans calling instructions:
 Toll-Free Number (U.S.&  Canada):  888-240-2560
 International toll number:         408-740-7256
 Bluejeans CODE:                  385 600 867
 Bluejeans link: https://bluejeans.com/385600867

Agenda

Analyzer code updates

  1. Operations was remade and installed last week; new issues?
    1. Issue 269: diff* variables are missing in burst and muls trees
      • This is probably just a labelling issue
    2. Pushing the last minirun into the previous if it is "too short"
      • Maybe do one runthough just to get the total events, then have the burst advancement only if we have at least a full burst remaining (or maybe more, to account for bad events)
      • Alternately, do a pass1 without making the trees, and only create the trees on second pass. Combine the slopes from the short minirun with the previous, and we need another label to tell the system when to do the burst advancement on the second pass

Prompt analysis toolchain

  1. Respin1
    1. I'll merge operations into develop, then into master, and make a new branch for the respin
    2. Still waiting on getting bmod slopes; can someone help Victoria in running through these? (Cameron? Robert?)
  2. Dithering & Lagrange toolchain
    • Status of the toolchains for CREX

New modification ideas

  1. Basing summary plots on JAPAN ouptuts directy
    • Summary and prompt plots
    • Can we consolidate the prompt summary outputs to be builtin to JAPAN now?
    • Aggregation can/should be changed to use the burst trees

Other issues

Present

Tao, Devi, Weibin

Phone: Cameron, Sakib, Paul

Excused