Skip to content

BlipReco: build the per-track deposit map once per event - #981

Open
jzennamo wants to merge 1 commit into
developfrom
feature/jaz_blip_track_deposit_map
Open

jzennamo wants to merge 1 commit into
developfrom
feature/jaz_blip_track_deposit_map

Conversation

@jzennamo

Copy link
Copy Markdown
Contributor

FillParticleInfo looped over every energy deposit for every particle. This builds a map of track ID to (energy, electrons) once per event and looks it up.

Measured effect: blipreco from 6.5 s to 0.2 s per event.

Validation: Flat CAF identical to the release.

Context: one item of a menu of time, memory, and disk savings for the Gen3 MC production. Each change is its own PR with one commit on develop, so they can be taken (or not) independently. Profiling and validation are in the slides "Gen3 MC Production: Where the Time and Disk Go" (Nov 2026). The validation is a fixed-seed comparison of the full gen-to-CAF chain against v10_26_00 (124 events, release run twice to measure its own run-to-run variation), plus each change applied alone on the release's own inputs and compared in the flat CAF (2895 branches).

🤖 Generated with Claude Code

FillParticleInfo looped over every energy deposit for every particle. Build an unordered_map of track id to (energy, electrons) once and look it up. blipreco 6.5 to 0.2 s/event; CAF output identical (2597 leaves).

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant