Skip to content

reco2: do not run blipana by default - #983

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

jzennamo wants to merge 1 commit into
developfrom
feature/jaz_reco2_no_blipana

Conversation

@jzennamo

Copy link
Copy Markdown
Contributor

blipana re-runs the whole blip reconstruction just to fill an analysis ntuple. This turns it off by default; add it back to the path when the ntuple is needed.

Measured effect: 6.3 s per event saved in reco2.

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

blipana re-runs the whole blip reconstruction to fill an ntuple (6.3 s/event). Off by default; add it back for blip ntuples.

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