Add stochastic uncertainty surface, robustness fixes, and broader pyfrbus validation gates - #5
Merged
Conversation
… gates - New frbus.uncertainty.stochsim_bands(): seeded residual-bootstrap percentile bands (68/90 default, configurable) around any shock scenario, with honest replication failure accounting (n_failed, failure_rate; raises only when all replications fail). - Robustness: stochsim narrows bare Exception to FrbusError so programming errors propagate; _preconditioner guards all-zero Jacobian rows with a named ComputationError; used_exos matches whole identifiers instead of substrings (verified identical exo set, 81=81, on the real model). - Validation gates extended from one to four pyfrbus like-for-like scenarios (monetary, fiscal egfe, tax trp, non-inertial Taylor) with committed vendor-generated fixtures agreeing to <=2.1e-8; scenario definitions shared verbatim between generator and gates; CI vendor-reference job matrixed over all four. - docs/mce-feasibility.md: concrete plan for model-consistent expectations (stacked-system solve), est. 2-4 days, no rewrite. Co-Authored-By: Claude Fable 5 <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.
percentile bands (68/90 default, configurable) around any shock
scenario, with honest replication failure accounting (n_failed,
failure_rate; raises only when all replications fail).
programming errors propagate; _preconditioner guards all-zero
Jacobian rows with a named ComputationError; used_exos matches
whole identifiers instead of substrings (verified identical exo
set, 81=81, on the real model).
scenarios (monetary, fiscal egfe, tax trp, non-inertial Taylor)
with committed vendor-generated fixtures agreeing to <=2.1e-8;
scenario definitions shared verbatim between generator and gates;
CI vendor-reference job matrixed over all four.
expectations (stacked-system solve), est. 2-4 days, no rewrite.
Co-Authored-By: Claude Fable 5 noreply@anthropic.com