transport-regression-keeper

To document transport regression drift, you map affected modules and consolidate numerical impact assessments into validated evidence. This process identifies output changes and justifies baseline updates with traceable drift data.

Selecting the right test layer for transport changes requires enforcing testing scope rules to pick the narrowest sufficient layer. You progress from unit to integration to regression to validation for focused verification.

The best way to manage baseline updates for scattering rates and relaxation times is generating summarized drift evidence. This maps numerical impacts and provides the required traceability for baseline changes.

Yes, this regression framework works for smoke, core, and full transport workflows. It applies cross-section, scattering rate, and relaxation time verification rules across all regression layers to enforce testing scope.

You need to enforce testing scope rules for numerical impact assessments to ensure focused verification and prevent error-prone manual governance. Selecting the minimal sufficient test layer validates transport changes accurately.