20190812-Analyzer-Mtg

From PREX Wiki
Jump to navigationJump to search
The printable version is no longer supported and may have rendering errors. Please update your browser bookmarks and please use the default browser print function instead.

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
    • Do we want the aggregator to be aware of file splits?
      • We probably should change the options for the engine to combine file splits. This would produce a single set of outputs. The rootfiles could end up getting split, if we take very long runs.
    • The prompt summary class initially had a bunch of hardcoded things, such as the pattern size
      • I would suggest having the prompt summary class directly request those values from the internal data objects, rather than having another parameter file which could become mismatched.
      • Cameron had made a series of log entries about what was needed to be done when we switched to 240Hz, so we can refer to them: Changing to 240 Hz summary notes
    • There have been some issues with doing widcarded "rm" operations of png files within the prompt scripts, and having this bogging down.
      • Maybe we should change the prompt script to produce the pngs into a temporary directory that we could just do a "rm -r <tempdirname>"
      • Cameron raises a question about using the ROOT "dataframes" mechanic.
      • Maybe we can use the engine's histogramming functionality for some things?
    • Analysis-minder is hanging sometimes
      • I'll try to look into it with Robert this week
  2. New feature plans
    • Continuing development of minirun functionality
    • Data-handlers which can process results from other data-handlers
      • Robert had been working on getting the "prompt" analysis chain working on the farm machines
      • Robert and I will pick up the data-handler-handler this week
    • BMW first pass extractor
      • Hooks are in place for an event-level data handler.
      • Wouter was going to set up a prototype general-purpose data extractor (selector), then hand off to Cameron: it just requests either specific variables or looks at the ErrorFlag and writes to a tree based on the values.
    • Issue #207: Cameron will follow up

Prompt analysis toolchain

    • Robert was having issues with file system permissions in getting the tootlchain working on the farm machines
      • I will follow up with him and Cameron later today.

Other issues

Changing to 240 Hz summary notes

Present

Phone: Paul K., Cameron, Devaki, Devi, Robert R., Sakib, Yufan

Excused