Adopt G4BNB v1.1.0 Flux Files

[marcodeltutto]

Description

This PR changes the default flux files used for the main workflow to use the new G4BNB v1.1.0 production flux files.

Update flux files wiki: https://sbnsoftware.github.io/sbndcode_wiki/The_SBND_flux_files.html

Note that, since G4BNB files are in dk2nu format, GDK2NUFLUXXML must point to the following file that containes the flux window specification for SBND:

export GDK2NUFLUXXML=/cvmfs/sbnd.osgstorage.org/pnfs/fnal.gov/usr/sbnd/persistent/stash/fluxFiles/bnb/G4BNB/v1.1.0/GNuMIFlux.xml

Addittionally:

• For some genie fhicl files, a "legacy" version is available that runs the with the old flux files:
  • GENIE only: sbndcode/JobConfigurations/standard/gen/genie/other_flux_config/flux_configk/
  • GENIE+CORSIKA rockbox: sbndcode/JobConfigurations/standard/gen/genie_corsika/other_flux_config/flux_configl/
• This PR also include fhicls to run in RHC mode and beamdump mode (flux files were made with a previous version of G4BNB, v1.0.0)
• This PR includes a CAFMaker fhicl that runs on gen-level files

$${\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? NO If so, please assign a CAF maintainer (PetrilloAtWork or JosiePaton) as additional reviewer.
• Does this affect the standard workflow? YES
• 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?