Bump analysis release to 25.2.32

It's been a while since 25.2.27. We should update.

Looks like I have to disable some stuff that isn't supported in the new onnx version. I'm also taking this as an opportunity to clean up:

• VMFv1 is crashing when I try to run the EMPFlow config. Removing that everywhere. Attention @npond
• Removed the small-R UFO jets (they were also running some models that had similar issues). Attention @wlai
• The JVT tool got very noisy¹, so I replaced it with JetVertexNNTagger
• The retag-lite configuration was crashing on zero track jets, had to flip a switch to return default values. Attention @vhomsak, but I don't think he's using the lite version anyway.

Closes #160 (closed)

1. I was getting a lot of warnings like VarHandle(StoreGateSvc...ts_NNJvtCopy[1244316195])WARNING StoreGate/src/VarHandleBase.cxx:838 (void*SG::VarHandleBase::typeless_dataPointer_impl(bool)): could not get proxy for key AntiKt4EMPFlowJets_NNJvtCopy

Digging into where this annoying warning is coming from, it seems that the function which is printing it has a quiet option, which is set to true everywhere except one place. I guess I could make a MR to silence it there too and ask Scott what is going on.

Seems like we might have picked the wrong JVT tool, maybe we should use JetVertexNNTagger instead.

mentioned in issue #160 (closed)

added 3 commits

• 423d72fd - swap out NN JVT tool for simpler one
• 623f4841 - fixes in truth config
• 7fc6c85b - fixes for softe

Compare with previous version

added 1 commit

• aeb0da7d - remove small-r UFO configs

Compare with previous version

changed the description

added 1 commit

• fc423995 - fix for retag_lite

Compare with previous version

changed the description

@svanstro and @hartman, the main issue this might cause is the removal of VMFv1, i.e. the maskformer outputs.

But the release I'm moving away from is now 2 months old: we can't hold the main branch back for that long. If you need the maskformer outputs for some ongoing work I think the options are:

• Just use the commit before this one, if no more development is needed, or
• make a branch in the dumpster (ugly but better than holding main back), or
• update the models, or find some other workaround

I hope to get this merged in any case, we can always figure out which strategy to follow later.

mentioned in issue #162

resolved all threads

approved this merge request

changed the description

marked this merge request as ready

merged