Repository navigation
Normalize image planes into one owned buffer through shared array operations - #9
Merged
Conversation
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.
Per-plane image normalization currently allocates separate cast and divided planes followed by a final stack. Add the operation to the existing ArrayOperations/MemoryType owners, with a shared mutable-array implementation that allocates one output buffer for NumPy and CuPy. Immutable frameworks retain the original numerical recipe through the base implementation. Inputs remain unchanged and scale cardinality is enforced.
Validation: 252 exact comparisons with the original normalization owner, genuine WoundHealing RGB inputs, three CuPy dtype/device checks, and the complete external suite (242 passed, 17 skipped). Ruff, Black, and mypy passed. A four-fork saved-source replay reduced the normalization critical path from 1.174 s to 0.377 s; this is boundary evidence, not a full pipeline speedup claim. Bump to 0.3.8 so consumers can require the new API.
Addresses OpenHCSDev/openhcs#1106; the corresponding OpenHCS consumer PR will close that issue after production qualification.