Open
Conversation
josegcpa
reviewed
Feb 28, 2026
Collaborator
josegcpa
left a comment
There was a problem hiding this comment.
Okay, this looks good to me!
I have just one question - is there any circumstance where non-zero bounds would not need to be applied? The grandqc workflows having an option to apply these makes it seem as though this is optional but I am not sure if that is the case; could you please confirm this whenever you can?
Owner
Author
|
Good question! Non-zero bounds are effectively required for correct final exported annotation coordinates (GeoJSON/centroids) whenever outputs are intended in viewer/display i.e. QuPath space. The apply_bounds_offset option is present so internal processing in the WSI prediction entrypoint can remain in raw slide coordinates and so zero-bounds slides are handled cleanly afterwards. |
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.
This PR fixes a coordinate‑offset bug that was causing QuPath‑exported ROIs to be misaligned on slides with non‑zero
openslide.bounds-x/y. The updates read the bounds offsets, shift ROI/tissue/artefact geometries and adjust output GeoJSONs accordingly. The issue and discussion are documented in this Image.sc forum thread.