Skip to content

g4: drop energy deposits that only this job consumes - #985

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

jzennamo wants to merge 1 commit into
developfrom
feature/jaz_g4_output_drops

Conversation

@jzennamo

Copy link
Copy Markdown
Contributor

Drops the largeant and ionandscintout SimEnergyDeposits from the g4 output. They are consumed inside the g4 job and detsim drops them anyway.

Measured effect: g4 file from 61.4 MB to 33.8 MB per event.

Validation: Downstream truth and reconstruction agree with the release within its own run-to-run variation.

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

largeant and ionandscintout SimEnergyDeposits are consumed inside the g4 job and dropped by detsim anyway: 61.4 to 33.8 MB/event.

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