Repository navigation
Declare native output defaults through existing typed dtype policy (#213) - #2
Merged
trissim merged 3 commits intoSep 30, 2026
Conversation
…0260929 Keep runtime GPU context handles out of retained callable history
Contributor
Author
|
Parent integrated PR2 normally with current main409b1e0, published d6d92a7 without editing the original worktree. All four real callable dtype tests passed as part of the paired15-test OpenHCS/BaSiCPy source run: native fractions/negative/large output, explicit runtime override, unchanged undeclared preserve-input behavior, untyped default rejection. Actual source paths asserted, existing Python3.12 environment, no install/download. Original receipts in the persistent issue-batch/basicpy-parent-numeric-20260930 ledger. Parent owns the paired PR217 integration and installed/MCP acceptance separately; this is not a live activation claim. |
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.
Refs OpenHCSDev/openhcs#213; paired OpenHCS draft
OpenHCSDev/openhcs#217. Linnaeus owns this backend/dtype
integration. Stacked on PR1 (retained history/runtime-handle ownership), base
fix/durable-decorator-context-20260929; do not merge/install either withoutcoordinator acceptance. The PR diff adds only the dtype default and regressions.
Concrete defect / reproducer
ArrayBridge direct decorators default to PRESERVE_INPUT even when a callable
naturally produces floating measurements. Removing a BaSiC wrapper's own
astype(input.dtype)is insufficient: the outer dtype wrapper rescales/castsits first output. Input uint16 plus output
[-1.25, 12.5, 70000.5]loses valuesunless an explicit native runtime config is passed. OpenHCS pipelines already
default to native via DtypeConfig, but direct calls are a distinct real entrypoint.
Existing owner extension
dtype_config_defaultaccepts the existing DtypeConversionConfig owner. Itsruntime default and reflected signature use the same object; explicit
runtime dtype_config still overrides it through existing conversion runners.
No extra policy registry, special BaSiC name dispatch, wrapper bypass, module
global config mutation, fallback or new config schema. Framework/GPU wrapping
and undeclared preserve-input behavior are retained. OpenHCS declares its own
existing DtypeConfig native default on the BaSiC callable.
Evidence / scope
range; explicit override with float sidecar retained; existing undeclared
preserve behavior; untyped default rejected. Not executed yet under the
serialized runtime schedule. This is a source checkpoint, not live readiness.
Lovelace currently owns finite heavy slot, Confucius prepare-only next.
Focused catalog review: BOUND-2 existing typed config owns policy; IMPL-13 one
existing conversion mechanism handles both defaults and overrides; TIME-7 no
copied framework policy. New conversion modes still extend their existing runner
family, not new consumer branches. Source/AST/catalog only, no global NRA proof.
Remaining: focused regressions, exact paired OpenHCS direct and compiled/MCP fit
journey, retained history compatibility, current installed entrypoint acceptance
after reviewed integration. Keep draft and no issue-closing claim.