Add IDEA simulation and MLPF pipeline integration - #495
Merged
Conversation
This was referenced Sep 4, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds end-to-end FCC-ee IDEA support to MLPF:
The PR also adds CLD particle-gun validation samples and updates shared pipeline configuration used by CLD and IDEA.
Current limitations
This pipeline is intended for engineering validation, not physics-performance studies. Tracks are truth-seeded and baseline candidates use target information, so the resulting metrics are not yet suitable for physics claims.
IDEA calorimeter energies are currently uncalibrated. Validation therefore focuses on data representation, truth relations, and energy closure.
GGTF tracking is disabled by default because the MLPF workflow uses truth-seeded tracks and GGTF significantly increases runtime and memory use. It can be enabled with
ENABLE_GGTF=1.Key4HEP dependencies
The reproducible workflow targets Key4HEP
2026-04-08:key4hep-2026-04-08-mlpfb313130key4hep-2026-04-08-mlpf25016a3key4hep-2026-04-08-mlpfcdc8b78key4hep-2026-04-08-mlpfc09ebd3key4hep-sim@c09ebd3pins the other three commits and was verified from a fresh recursive clone.Upstream staging PRs
Validation
tests/test_postprocessing_idea.py,tests/test_idea_pipeline.py, andtests/test_interleaved_shard_sampler.py)2026-04-08bash -nkey4hep-sim@c09ebd3resolves to the pinned commitsInitial training results
Attention versus HEPTv2 on the initial dataset: