20190909-Analyzer-Mtg

Back to Main Page >> Analyzer_Meeting

previous meeting << >> following meeting

Logistic information

Meeting room at JLab: CH Conference room (on the accelerator side).

 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. General discussion
   • Wrapup from the run. Do we have all the parameter files up to date on the repo? Storage choice for the "original" pedestal files created by Caryn.
     • Maybe we should store them in git, maybe as a subdirectory or with a prefix
2. New feature plans
   • Continuing development of minirun functionality
   • Data-handlers which can process results from other data-handlers
     • I should get back to it this week
   • BMW first pass extractor
     • Cameron will try to look at the selector extractor feature branch and follow-up with Wouter about his ideas in it
   • Issue #207: Cameron will follow up

Prompt analysis toolchain

1. Status on the farm
   • Robert is just about done. He's committed the prommpt toolchain changes into a branch on github
   • What are the steps we want to take before a respin?
2. Path to migration to japan
   • Dithering analysis should be better intergrated into the overall chain (not directly in the engine thouhg)
     • Tao suggests his work on the Lagrange analysis may be useful approach

Other issues

1. How do we want to keep using the aggregator, and what changes do we want to make?
   • The JAPAN "summary trees" may be a good mechanism, once we have them complete
   • We have been a little behind in getting the dithering corrected outputs aggregated.
     • For a respin of PREX-II, we should use Combiner object and use our current best determinations of the dither slopes to creates the run ranged mapfiles.
     • Maybe Tao or Victoria could work through our dither slope lists?
   • Discussing aggregation when we change variables
     • When we change instrumentation channels, how to aggregate
2. Maybe change the grand aggregator tools to look at the variables available in the slugfiles it is trying to aggregate, and take the union of all variables as the variable list.

Present

Paul, Cameron, Adam, Devi, Weibin, Tao

Phone: Robert R.