search

JeffersonLab / japan

Just Another Parity ANalyzer
7 stars 13 forks source link

Feature: BMOD data extractor #108

Closed paulmking closed 4 years ago

paulmking commented 5 years ago

Is your feature request related to a problem? Please describe. We want to be able to routinely extract the BMOD data into an independent event-level ROOT tree, so we don't need to keep the full evt trees, but can accumulate the BMOD responses over multiple runs.

cameronc137 commented 5 years ago

Wouter's work in 92e260f48f73271c78272e3314f75c5fd7483494 begins to resolve this

wdconinc commented 5 years ago

Right, 18 July is about when moving took over... What's the plan/demand for this? I can bring someone up to speed just as fast as I can bring myself up to speed again :-)

cameronc137 commented 5 years ago

It would be nice to have it before we do a full respin of all the data (which is probably the end of next week or beyond). I would like to be caught up on it, as I'm already familiar with the existing downstream analysis scripts for which this pruned tree output would be ideally suited to serve as input.

wdconinc commented 5 years ago

Ok, give me half a day tomorrow to figure out where (or why) I left this. Let's chat on the phone/bluejeans after 2pm Eastern. Works?

cameronc137 commented 5 years ago

What was the progress on this? I believe @wdconinc said that he's gotten a working copy that allows for evt tree extraction based on ErrorFlag cuts?

cameronc137 commented 5 years ago

This was moved into the combiner class and relies on the errorflag.

Wouter's default error flag is 0x5b7e6bff, while the one used by the beam mod analysis script is 0xda7e6bff.

I'm testing a device list now and seeing if the analysis script gets the same results.

cameronc137 commented 4 years ago

This ultimately worked and was used during CREX. Closing.