Repository navigation
Conversation
Drop SimPhotonsLites and the blip Pandora copies from the reco2 output: 28.3 to 25.7 MB/event, CAF unchanged. priorSCE energy deposits are kept (CAFMaker fills rec.mc.dep from them). Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
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.
Drops
SimPhotonsLiteand the blip Pandora copies from the reco2 output; nothing downstream reads them. The prior-SCE energy deposits are kept because CAFMaker fillsrec.mc.depfrom them.Measured effect: reco2 file from 28.3 MB to 25.7 MB per event.
Validation: Flat CAF unchanged except one opt0 slice (0.7% in measured PE). The release shows the same kind of opt0 shift with no configuration change at all when run with
MALLOC_PERTURB_=85, so it comes from uninitialized memory in the existing reco2 opt0 step, not from this change.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