Skip to content

Reuse ROI region properties and own Java format-probe lifetime - #16

Merged
trissim merged 15 commits into
mainfrom
fix/fragmented-roi-properties-20260929
Oct 1, 2026
Merged

trissim merged 15 commits into
mainfrom
fix/fragmented-roi-properties-20260929

Conversation

@trissim

@trissim trissim commented Sep 29, 2026 •

Copy link
Copy Markdown
Contributor

Paired ROI/context/namespace checkpoint

Parent integration owner. Existing PR16 normally incorporates canonical main
b493c8f and namespace worker20 into production91fd7e854. Existing ROI extractor
reuses region properties with one bbox scan; BioFormatsJavaContext owns reader
probe lifetime. Frozen MetadataConfig owns namespace path behavior and is carried
by the existing virtual backend/FileManager state; no competing store or reader.

Application PR206 source29 controls pass in both import orders; five namespace
controls pass with independent filenames. Child11 namespace controls and original
guard are recorded at this exact production source. Current original application,
benchmark/scripts guards have zero positive deltas. Earlier48/163 controls and
bounded ROI profile remain separately attributed; no full NRA/native proof claim.

Actual paired installed wheels pass MCP health, persisted reopening and bounded
virtual pixel sampling with independent generic/application namespaces. Real
raw ImageXpress initialization/compile succeeds. This is an installed local pair,
not public registry availability, global installation or biological acceptance.
Raw singleton Opera grid initialization, real Java/CZI/native execution and full
R1/ZIP acceptance remain explicit OpenHCS follow-ups; original failures retained.

Current receipt: docs/source/input_preparation_installed_20261001.rst;
paired full receipt: OpenHCS docs/validation/input_preparation_installed_20261001.rst.
The old dependency-first defect is repaired by the typed paired namespace change,
not environment mutation or companion metadata. Merge without hosted CI waiting;
retain all recorded pending acceptance and original failures.

@trissim trissim changed the title Reuse region properties for fragmented 2D ROI extraction Reuse ROI region properties and own Java format-probe lifetime Sep 29, 2026
@trissim

trissim commented Sep 29, 2026

Copy link
Copy Markdown
Contributor Author

Authorized critical cache/progress integration checkpoint is published as OpenHCS228 at bf9aae4620585e98d10e469037ef98237884b4f8, paired with PolyStore17 at c16b8fc99a07f17e92e5fbf46f312d73cc9c46d7. Both remote heads verified; exact child gitlink adopted by228. Base current main213439a04 includes merged218. References224,206 and16; original branches/source/receipts preserved, no force/rebase/reset.

This extracts the already-owned cache/progress implementation, not another runtime/materializer. Source-selection/Java probe/ROI optimization stays in206/16. Their 141-pass/26-failure receipt remains unresolved; after-ROI profile did not run. No claim of broad preservation or installed acceptance from this checkpoint.

Before application/MCP startup set POLYSTORE_IMAGEJ_CACHE_ROOT=/home/ts/.cache/polystore/imagej (bundle parent, not hashed directory) and POLYSTORE_IMAGEJ_ALLOW_DOWNLOAD=false. Both settings belong to existing PolyStore distribution/download-policy owners, projected by existing OpenHCS launch owner. Independent XDG logs/caches remain independent. Existing progress/worker binding stays canonical.

Current-main pair: 36 passed5.14s, peakRSS277712KiB, availableRAM14.4→13.96GiB. Two fresh native processes with production download-forbidden policy, separate XDG roots, actual same existing Fiji/Java paths, zero new cache entries/no downloads/no JVM. Reproducer and durable receipt are in228. No override/copy/archive in native proof, no installed/frozen/scientific change or replay. Parent owns review/merge/install and resource-coordinated real installed stdio inspection + concurrent discovery/heartbeat. No Closes/readiness claim until that live gate.

@trissim
trissim marked this pull request as ready for review October 1, 2026 03:15
Copilot AI balanced review requested due to automatic review settings October 1, 2026 03:15

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

@trissim
trissim merged commit 84f322e into main Oct 1, 2026
0 of 11 checks passed
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