add a new config file to save gn2 flip outputs and mSV
Merge request reports
Activity
added 1 commit
- e0956e67 - Extend MultifoldTagger.py to use the flip tag option (already in athena)
- Resolved by Nicole Michelle Hartman
- Resolved by Nicole Michelle Hartman
- Resolved by Nicole Michelle Hartman
- Resolved by Nicole Michelle Hartman
- Resolved by Nicole Michelle Hartman
added 5 commits
-
c96e7c44...c0c2ac6d - 4 commits from branch
atlas-flavor-tagging-tools:main
- 4dac61ba - Merge branch training-dataset-dumper:main into main
-
c96e7c44...c0c2ac6d - 4 commits from branch
Hello! Thank you for the feedback @afroch and @npond
I didn't know before we could start from the GN3_dev.json config, so doing that now as Nikita suggested
I think I had f***ed smth up earlier this afternoon blindly accepting the gitlab suggestions, but in the meantime, Alex had saved an intermediate
GN2Flip.json
file, so I started from that tonightWhat I learned:
- Our
MultifoldTagger
CA decorates the btagging object instead of the jet object (so needed to switch out that) - Now since starting from the
GN3_dev.json
config, I made a new config file:fragments/pflow-sv1-jf.json
that just adds the extra sv1, jf variables.
OK, it's now clear the extra code I added on top of
GN3_dev.json
it much more minimal :) (altho, it does look a bit like config file spaghetti )- Our
Good news: The extra variables I wanted are all there now
And... I also have the SV1 mass so @neal can compare to for investigating swapping the mSV1 var to fit the flavor fractions w/ the reco GN2 mass .
^ Demonstration test dump has these new vars
enabled an automatic merge when all merge checks for 76a8efd3 pass