Skip to article frontmatterSkip to article content
Site not loading correctly?

This may be due to an incorrect BASE_URL configuration. See the MyST Documentation for reference.

ColliderML hits

ColliderML Release 1 hit datasets use raw tracker and calorimeter hits with one target row per input hit. Both builders use schema version 1.0.0. Pileup membership is carried in the target particle’s ispu feature.

Physics samples

Physics samplePileupTFDS datasetModel recipe
Top-quark pairsNonecolliderml_ttbar_hitspyg-colliderml-hits-v1, pyg-colliderml-hits-set-v1
Top-quark pairsApproximately 200 interactionscolliderml_ttbar_pu200_hitsBuilder exists; no named training recipe

The TFDS mappings configure partitions 1--10. These samples are not included in the verified public selection; check publication availability before downloading. A custom pileup-200 training recipe requires its own validation.

Event view

These views show the same simulated no-pileup ttbar event (index 0) in the transverse plane. The particle panel shows visible primary-leaf truth; the hit dataset defines its training targets through postprocessing.

Raw detector hitsPrimary-leaf truth proxy
ColliderML: raw detector hits for event 0.ColliderML: primary-leaf truth proxy for the same event.

All-component overlay, vector input view and vector particle view are available for reuse. See event-view conventions for particle sources, sampling and scale.

productions.colliderml.tfds_hit_mapping in particleflow_spec.yaml selects the hit builders under mlpf/heptfds/colliderml_hits/. Use the ColliderML converter and source/workspace configuration with dataset generation; the CLD/CLIC Key4HEP commands do not define ColliderML conversion.

Inspect input sizes and measure memory with a short dedicated hit-model run before scaling. For the clustered representation and its weighted two-group recipe, see ColliderML tracks and clusters.