Adding hyperon filter for Gen2 production

[tjones79]

Description

Please provide a detailed description of the changes this pull request introduces.

Adds the sbnd_hyperon_filter block to signal_filters_sbnd.fcl and wires it up in run_sbnd_gen2_rare_signal_filter.fcl to enable Gen2 exclusive hyperon filtering.

$${\color{blue}!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!}$$

$${\color{blue}\bf{\textrm{IMPORTANT UPDATE Feb 2nd 2026:}}}$$ If you are making a PR which is intended as a patch for the CURRENT production for gen 2 SBND analyses, you must make two PRs: one for develop and one for the production/sbnd-gen2 branch.

$${\color{blue}!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!}$$

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?
• Is this PR a patch for the ongoing production? If so, separate PR must also be made for production/v10_06_00 branch!

Relevant PR links (optional)

Does this PR require merging another PR in a different repository (such as sbnanobj/sbnobj etc.)?
No

Link(s) to docdb describing changes (optional)

Is there a docdb describing the issue this solves or the feature added?
N/A

Assigning as draft as I am still extracting neccesary filter info

I have confirmed that after the running the filter on a generated sample of beam + corsika + rockbox, that there are events in my output file. Below are the relevant metrics. I have also attached a file that shows the end of the art log file wth the summaries. -> filter_end_log.txt

Filter Performance Metrics (Based on 11,794 generated events):

• Filter Efficiency: 14 / 11,794 events (~0.12% retention for the hyperon stream)
• Average CPU Time (hyperon filter module): ~0.026 seconds / event
• Output File Size: 525 MB total (~37.5 MB / saved event)

[linyan-w]

Looks good to me. Pending other reviewers.
@tjones79 could you confirm you see your desired events in your test?
@tbwester could you please review?

[tjones79]

Hi @linyan-w

I can confirm that the 14 events filtered were indeed events that contain hyperons, as desired :)