Filter to reject events with very high hit multiplicity (ported from ProtoDUNE)

[absolution1]

Description

Include a port of the ProtoDUNE hit filter to reject events with a very high hit multiplicity. In data, some events have a very large number of hits: these events demand a lot of memory/processing time and are unusable. The filter is connected up to the data workflow to reject such events after gaushit, saving on memory and processing time.

I have set the minimum number of hits per TPC to be 50,000. This can obviously be iterated on as the filter is deployed.

I've included an extra data processing fcl (reco1_data_storefilteredevents.fcl) that keeps the filtered events (but in a separate output file)

Checklist

• Added at least 1 label from available labels.
• Assigned at least 1 reviewer under Reviewers,
• Assigned all contributers including yourself under Assignees
• Linked any relevant issues under Developement
• Does this PR affect CAF data format? If so, please assign a CAF maintainer (PetrilloAtWork or JosiePaton) as additional reviewer.
• Does this affect the standard workflow?

[bear-is-asleep]

trigger build LArSoft/lar*@LARSOFT_SUITE_v09_93_01 SBNSoftware/sbnanaobj@bug/coackley_ciCafv09_91_02

[bear-is-asleep]

Looks good! Do we want to do this for MC?

[FNALbuild]

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

[FNALbuild]

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

[absolution1]

Looks good! Do we want to do this for MC?

Sorry @bear-is-asleep I completely missed this.
I don't think we do, for now at least. The filter is to reduce the number of times we get stuck in a long processing with data. The filter is quite generous in terms of letting events through, so I think the data/MC bias should be small.

[FNALbuild]

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

🚨 For more details about the failed phase, check the build SBND phase logs

parent CI build details are available through the CI dashboard

[FNALbuild]

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

🚨 For more details about the failed phase, check the build SBND phase logs

parent CI build details are available through the CI dashboard

[bear-is-asleep]

trigger build LArSoft/lar*@LARSOFT_SUITE_v09_93_01 SBNSoftware/sbnanaobj@bug/coackley_ciCafv09_91_02

[FNALbuild]

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

[FNALbuild]

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

[FNALbuild]

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

🚨 For more details about the failed phase, check the build SBND phase logs

parent CI build details are available through the CI dashboard

[FNALbuild]

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

🚨 For more details about the failed phase, check the build SBND phase logs

parent CI build details are available through the CI dashboard

[bear-is-asleep]

@absolution1 , can you resolve conflicts and update the branch to develop? There are some build errors which I think are attributed to not being on the develop branch.

[absolution1]

@bear-is-asleep this is done.
@henrylay97 can you check that the CRT bits in reco1_data.fcl are still OK?

[henrylay97]

YAY! 🥳 (CRT stuff is all good (services & producer))

[bear-is-asleep]

trigger build LArSoft/lar*@LARSOFT_SUITE_v09_93_01 SBNSoftware/sbnanaobj@bug/coackley_ciCafv09_91_02

[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 SBND Failed at phase build SBND on slf7 for c14:prof -- details available through the CI dashboard

🚨 For more details about the failed phase, check the build SBND phase logs

parent CI build details are available through the CI dashboard

[FNALbuild]

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

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

parent CI build details are available through the CI dashboard

[bear-is-asleep]

Ready to merge