Skip to content

reco2: do not run cvn and cvnSCE - #982

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

jzennamo wants to merge 1 commit into
developfrom
feature/jaz_reco2_no_cvn

Conversation

@jzennamo

Copy link
Copy Markdown
Contributor

Takes cvn and cvnSCE out of the reco2 workflow. This is a proposal to stop running CVN in production; the producers stay in the fcl, so restoring them is one line.

Measured effect: reco2 from 11.0 s to 4.1 s per event, peak memory from 1.82 GB to 1.24 GB.

Validation: Only the four rec.slc.cvn scores change (left at their defaults); every other flat CAF branch is identical.

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

Proposal: drop CVN from production. reco2 11.0 to 4.1 s/event and 1.82 to 1.24 GB peak. Only the 4 rec.slc.cvn CAF leaves change (left at defaults).

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