GENIE Reweight systematics fcl updates

[sjgardiner]

Updates the list of GENIE Reweight systematics dials to be compatible with GENIE v3.4.0 with the AR23_20i_00_000 model set

[jedori0228]

I wonder if we want to have v1 along with v2, with a directory structure like below...

[/SystTools]$ tree
.
|-- CMakeLists.txt
|-- configs
|   |-- CMakeLists.txt
|   |-- icarus_v1
|   |   |-- CMakeLists.txt
|   |   |-- config_All_icarus_v1.fcl
|   |   |-- config_GENIEReWeightMultisigma_icarus_v1.fcl
|   |   |-- config_GENIEReWeightMultisim_icarus_v1.fcl
|   |   |-- config_MINERvA_E2p2h_icarus_v1.fcl
|   |   |-- config_MINERvAq0q3Tune_icarus_v1.fcl
|   |   |-- config_MiscInteractionSysts_icarus_v1.fcl
|   |   `-- config_NOvAStyleNonResPion_icarus_v1.fcl
|   `-- icarus_v2
|       |-- CMakeLists.txt
|       |-- config_All_icarus_v2.fcl
|       |-- config_GENIEReWeightMultisigma_icarus_v2.fcl
|       |-- config_GENIEReWeightMultisim_icarus_v2.fcl
|       |-- config_MINERvA_E2p2h_icarus_v2.fcl
|       |-- config_MINERvAq0q3Tune_icarus_v2.fcl
|       |-- config_MiscInteractionSysts_icarus_v2.fcl
|       `-- config_NOvAStyleNonResPion_icarus_v2.fcl
|-- eventweight_genie_systtools.fcl
|-- syst_params_icarus_v1.fcl
`-- syst_params_icarus_v2.fcl

[sjgardiner]

I guess we could. However, I don't foresee a scenario in which we would want to use the deprecated systematics for anything. They're not really compatible with any of the samples we will use going forward.

[jedori0228]

Five GSysts (RPA_CCQE, CoulombCCQE, ThetaDelta2NRad, NormCCCOH and NormNCCOH) were not recognized by nusystematics, so are missing from icaruscode/fcl/caf/SystTools/syst_params_icarus_v2.fcl. This is fixed in LArSoft/nusystematics#4, and we have to rerun GenerateSystProviderConfig after this is merged.

[mmrosenberg]

trigger build LArSoft/lar*@LARSOFT_SUITE_v09_78_00

[FNALbuild]

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

[FNALbuild]

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

[FNALbuild]

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

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

parent CI build details are available through the CI dashboard

[FNALbuild]

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

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

parent CI build details are available through the CI dashboard

[etworcester]

Where are we on this and the related SBNCode PR? It would be awesome to update sensitivities for the collaboration meeting coming up. But even if we can't get it done in time for that, it's important to try to move forward with this. Lmk if there's anything I can do to help unstick it

[jedori0228]

@etworcester I made a PR to @sjgardiner 's repo (sjgardiner#1), so once it's merged, this PR will be also updated with that.

[mmrosenberg]

trigger build LArSoft/lar*@LARSOFT_SUITE_v09_79_00 SBNSoftware/sbncode@v09_79_00 SBNSoftware/sbnanaobj@v09_21_05 SBNSoftware/sbndaq-artdaq-core@v1_08_00of1 SBNSoftware/sbnobj@v09_17_09

[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 ICARUS Warning at phase ci_tests ICARUS on slf7 for e26:prof - ignored failure for unit_test -- details available through the CI dashboard

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

parent CI build details are available through the CI dashboard

[FNALbuild]

❌ CI build for ICARUS Failed at phase ci_tests ICARUS on slf7 for c14:prof - ignored failure for unit_test -- details available through the CI dashboard

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

parent CI build details are available through the CI dashboard