Skip to content

Preserve typed numerical failures in native tree evaluation - #21

Open
huashengshao wants to merge 1 commit into
codex/native-hermitian-tree-normfrom
codex/native-numerical-errors
Open

huashengshao wants to merge 1 commit into
codex/native-hermitian-tree-normfrom
codex/native-numerical-errors

Conversation

@huashengshao

Copy link
Copy Markdown

Finite physical inputs can overflow during native wavefunction construction, coefficient evaluation or the coherent norm. Those failures previously became generic evaluation messages, preventing consumers from requesting reconstruction in a wider scalar.

This change adds RusticolErrorKind::NonFiniteResult and preserves it through the native runtime's ExecutionError, including FeynKit's typed wavefunction failure and lane context. Nonfinite computed outputs use that category; malformed supplied components and physical-domain errors stay separate. No error-message matching, value clipping or precision promotion is introduced.

The regression exercises finite-input wavefunction overflow, coefficient and norm overflow, fresh 113-bit reconstruction from original decimal inputs, malformed supplied components and reuse after failure. All 84 native unit tests pass on both the standalone pinned dependency family (9cdc2949) and the ROULETTE consumer family (e93c3c73), with Python and external compilers absent from PATH. The consumer adapter passes 11 checks, including double overflow followed by reconstruction from the original exact parameter at 113 bits, direct input/output range failures and continued evaluation after failure. Independent source review approved the category propagation and input/output distinction.

Stacked on codex/native-hermitian-tree-norm at 34e9c6d (PR20).

This branch has not been deployed

No deployments
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.

2 participants