Apply min-max normalisation of SigmaNet features
Modifies the SigmaNet implementation to include optional min-max normalisation (division of values by the difference between the clamping minima and maxima) of features, required for the latest topo. trigger tuning.
To-do:
-
Add min-max functionality -
Make behaviour optional, so as to not affect other SigmaNet MVAs
Required for Moore!4724 (merged)
Edited by Jamie Gooding
Merge request reports
Activity
assigned to @jagoodin
added 1 commit
- 9b3f82d4 - Make min-max normalisation optional (disabled by default)
mentioned in merge request Moore!4724 (merged)
added 1 commit
- b9b7befe - Make min-max normalisation optional (disabled by default)
added 1 commit
- a8c29587 - Make min-max normalisation optional (disabled by default)
requested review from @bldelane
Hi @bldelane, this should be ready now so I'd appreciate if you could take a look over this! I'll leave this in draft until Moore!4724 (merged) is ready, in case we discover we need to make any more changes in Rec.
- [2025-04-11 14:29] Validation started with lhcb-master-mr#13339
- [2025-04-16 17:06] Validation started with lhcb-master-mr#13418
- [2025-04-17 05:26] Validation started with lhcb-master-mr#13420
Edited by Software for LHCbadded 2 commits
added 1 commit
- f1467467 - Store values for final NN inference in SigmaNet
added 1 commit
- 6f57a106 - Store values for final NN inference in SigmaNet
- Resolved by Miroslav Saur
- Resolved by Miroslav Saur
Please register or sign in to reply