Difference between revisions of "20190819-Analyzer-Mtg"
From PREX Wiki
(→Present) |
(→Agenda) |
||
| Line 15: | Line 15: | ||
=== Analyzer code updates === | === Analyzer code updates === | ||
# General discussion | # General discussion | ||
| + | #* Wouter is looking into being able to run regression on different events for different channels (i.e. when one DV has lots of event failures) | ||
| + | #** Among the questions on how to do this would be to how to treat the IV covariance matrix: should we just use the "global" IV matrix, or do we need to have separate IV covar matrices for each DV? | ||
| + | #* A set of runs had a mismatch between the BCM used in normalization and what was used for event cuts; that BCM had some strange behavior. Probably should have the burp cut applied in the map files. | ||
# New feature plans | # New feature plans | ||
#* Update on dataframes | #* Update on dataframes | ||
| + | #** It's in and working, starting with slug 49. This is only a change in the aggregator. | ||
#* Continuing development of minirun functionality | #* Continuing development of minirun functionality | ||
#* Data-handlers which can process results from other data-handlers | #* Data-handlers which can process results from other data-handlers | ||
| + | #** I was distracted on it last week nor has Robert, but both should get back to it this week | ||
#* BMW first pass extractor | #* BMW first pass extractor | ||
#* Issue #207: Cameron will follow up | #* Issue #207: Cameron will follow up | ||
| Line 24: | Line 29: | ||
=== Prompt analysis toolchain === | === Prompt analysis toolchain === | ||
# Robert was having issues with file system permissions in getting the tootlchain working on the farm machines | # Robert was having issues with file system permissions in getting the tootlchain working on the farm machines | ||
| − | #* As of last week, still having issues craeting and saving the plots. Transition to the dataframe stuff? | + | #* As of last week, still having issues craeting and saving the plots. Transition to the dataframe stuff? Also, we should look to see if there are new changes in the repo that we hadn't picked up, but right now the major problem is still that the plots are not actually created. |
=== Other issues === | === Other issues === | ||
| − | |||
== Present == | == Present == | ||
Latest revision as of 10:40, 19 August 2019
Back to Main Page >> Analyzer_Meeting
previous meeting << >> following meeting
Contents
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
- General discussion
- Wouter is looking into being able to run regression on different events for different channels (i.e. when one DV has lots of event failures)
- Among the questions on how to do this would be to how to treat the IV covariance matrix: should we just use the "global" IV matrix, or do we need to have separate IV covar matrices for each DV?
- A set of runs had a mismatch between the BCM used in normalization and what was used for event cuts; that BCM had some strange behavior. Probably should have the burp cut applied in the map files.
- Wouter is looking into being able to run regression on different events for different channels (i.e. when one DV has lots of event failures)
- New feature plans
- Update on dataframes
- It's in and working, starting with slug 49. This is only a change in the aggregator.
- Continuing development of minirun functionality
- Data-handlers which can process results from other data-handlers
- I was distracted on it last week nor has Robert, but both should get back to it this week
- BMW first pass extractor
- Issue #207: Cameron will follow up
- Update on dataframes
Prompt analysis toolchain
- Robert was having issues with file system permissions in getting the tootlchain working on the farm machines
- As of last week, still having issues craeting and saving the plots. Transition to the dataframe stuff? Also, we should look to see if there are new changes in the repo that we hadn't picked up, but right now the major problem is still that the plots are not actually created.
Other issues
Present
Phone: Paul, Cameron, Sakib, Robert, Wouter
