2D ROI

[matthew-man-457]

2D Region of Interest filter for data reduction and low energy optimization, through zero-suppression of 'empty' channels.
Includes tools to run the ROI (as an Ana or Prod module) on Larsoft simulations and analyze its performance.

The workflow is as follows:
detsim_dune10kt_1x2x6_notpcsigproc.fcl
roiprod_job.fcl
solar_reco_dune10kt_1x2x6_tpcsigproc.fcl

[aolivier23]

trigger build

[FNALbuild]

✔️ CI build for LArSoft Succeeded on slf7 for c14:prof -- details available through the CI dashboard

[FNALbuild]

✔️ CI build for LArSoft Succeeded on slf7 for e26:prof -- details available through the CI dashboard

[FNALbuild]

❌ CI build for DUNE Failed at phase ci_tests DUNE on slf7 for c14:prof -- details available through the CI dashboard

🚨 For more details about the failed phase, check the ci_tests DUNE phase logs

parent CI build details are available through the CI dashboard

[FNALbuild]

❌ CI build for DUNE Failed at phase ci_tests DUNE on slf7 for e26:prof -- details available through the CI dashboard

🚨 For more details about the failed phase, check the ci_tests DUNE phase logs

parent CI build details are available through the CI dashboard

[aolivier23]

trigger build

[FNALbuild]

✔️ CI build for LArSoft Succeeded on slf7 for c14:prof -- details available through the CI dashboard

[FNALbuild]

✔️ CI build for LArSoft Succeeded on slf7 for e26:prof -- details available through the CI dashboard

[FNALbuild]

❌ CI build for DUNE Failed at phase ci_tests DUNE on slf7 for c14:prof -- details available through the CI dashboard

🚨 For more details about the failed phase, check the ci_tests DUNE phase logs

parent CI build details are available through the CI dashboard

[FNALbuild]

⚠️ CI build for DUNE Warning at phase ci_tests DUNE on slf7 for e26:prof -- details available through the CI dashboard

🚨 For more details about the warning phase, check the ci_tests DUNE phase logs

parent CI build details are available through the CI dashboard

[aolivier23]

Is this file necessary to running a module? If you can remove it without breaking your new feature, I can just approve this. We usually try to put .root and other binary files in StashCache so we don't use up our finite github space and don't cause git to slow down when it tries to compare binary files.

[matthew-man-457]

Yes, it can be removed. I used it for generating a solar sample, but it's not necessary for running the ROI.

[matthew-man-457]

I deleted the file from my branch

[aolivier23]

Please see comment about binary file B8_spectrum.root. Can we just remove it? If not, it probably needs to go in StashCache.