You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
PartSeg.load_masked_image -load tiff image and mask (as labels layer) from file {image_path_without_suffix}_mask.tif. It looks like napari selects by random which contribution use to load this image. You could see the film below when multiple open operations ends with a different result for loading (without recording it flickers faster).
napari_open-2023-06-16_10.27.27.mp4
This happens on napari from the repository, and the latest released PartSeg.
@Czaki thanks for raising. If this is at the level of a single plugin with multiple contributions, I think it's quite possible we've got undefined/undesired behaviours in there. From the napari API we don't pass through any information below the plugin level afaik, so I think you're right it'll be in the read logic here. Will look into it 🙏
The PartSeg provides two contributions:
PartSeg.load_image
- load tiff imagePartSeg.load_masked_image
-load tiff image and mask (as labels layer) from file{image_path_without_suffix}_mask.tif
. It looks like napari selects by random which contribution use to load this image. You could see the film below when multiple open operations ends with a different result for loading (without recording it flickers faster).napari_open-2023-06-16_10.27.27.mp4
This happens on napari from the repository, and the latest released PartSeg.
Example files that could be used to reproduce:
stack1_component1.zip
The text was updated successfully, but these errors were encountered: