Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Random selection of contributtions used to load file #299

Open
Czaki opened this issue Jun 16, 2023 · 1 comment
Open

Random selection of contributtions used to load file #299

Czaki opened this issue Jun 16, 2023 · 1 comment

Comments

@Czaki
Copy link
Collaborator

Czaki commented Jun 16, 2023

  • npe2 version: 0.7.0
  • Python version: 3.9
  • Operating System: Ubuntu 22.04

The PartSeg provides two contributions:

  1. PartSeg.load_image - load tiff image

  2. 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.

Example files that could be used to reproduce:

stack1_component1.zip

@DragaDoncila
Copy link
Contributor

@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 🙏

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

No branches or pull requests

2 participants