Detect VisiumHD full-res image when path is relative #230
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.
There is a minor bug in the Visium HD reader. When we provide a relative path to the data, e.g.
"data/Visium_HD_Mouse_Small_Intestine"
, then it will search for the microscopy image inside"data/Visium_HD_Mouse_Small_Intestine/data/Visium_HD_Mouse_Small_Intestine/microscope_image"
.This is because it was using
path / fullres_image_file
instead of simplyfullres_image_file
.I also did some minor updates to use
pathlib
everywhere instead of a combination ofpathlib
andos
(it makes the code more readable I think).