Adding a fcl wth 0.1 MeV threshold for dirt

[sungbinoh]

Description

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

Adding a new fcl file with lower dirt threshold 0.1 MeV for a validation study in 2025 Fall production.

Filer efficiency is ~ 29% based on lar -c prodgenie_corsika_proton_rockbox0p1_sbnd.fcl -n 100.
Bellow is a table from Macro's PR 792.

FHiCL	Cut on Deposited Energy	Pass Rate
prodgenie_corsika_proton_rockbox_sbnd.fcl	E_dep>1 MeV	TPD
prodgenie_corsika_proton_rockbox100_sbnd.fcl	E_dep>100 MeV	17.9%
prodgenie_corsika_proton_rockbox_lowenergydirt_sbnd.fcl	1<E_dep<100 MeV	6.2% (Dirt only)
N/A	E_dep>1MeV	23.5%

So, there would be about 25% increase in the filtering efficiency compared to 1 MeV threshold.

For the record, in this version of sbndcode (v10_11_01_01), -n 100 gives filtering efficiencies for various thresholds

• 0.1 MeV: 29/100
• 0.5 MeV: 24/100
• 1 MeV: 22/100

So, 0.5 MeV will increase the filtering efficiency about 10% compared to 1 MeV.

$${\color{red}!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!}$$

$${\color{red}\bf{\textrm{IMPORTANT UPDATE June 22nd 2025:}}}$$ If you are making a PR which is intended as a patch for the CURRENT production (which started in Spring 2025), you must make two PRs: one for develop and one for the production/v10_06_00 branch.

$${\color{red}!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!}$$

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.)?

Link(s) to docdb describing changes (optional)

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