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

Sending detections as nested shapes in OMERO ROIs #10

Open
Rdornier opened this issue Dec 8, 2022 · 0 comments
Open

Sending detections as nested shapes in OMERO ROIs #10

Rdornier opened this issue Dec 8, 2022 · 0 comments
Labels
documentation Improvements or additions to documentation wontfix This will not be worked on

Comments

@Rdornier
Copy link

Rdornier commented Dec 8, 2022

@romainGuiet , @lacan , @NicoKiaru

We have tried to upload, on OMERO, QuPath detections as nested shapes inside ROIs in two different ways

  1. all detections are nested into one single ROI
  2. a maximum of 5'000 nested shapes per ROIs is set and multiple ROIs are sent to OMERO.

Here is a report of those tests : QuPath-OMERO_Nested_Shapes_Tests.pdf.

Judging from low performances of the OMERO server to deal with a large number of ROIs/shapes, we decided to not send detections to OMERO. There will be no command in the extension that send detections to OMERO. However, there is still the possibility to use a public method from OmeroRawScripting API in scripts to send any pathObject to OMERO. In that case, all pathObjects will be considered as one single ROI. Therefore, if the number of pathObjects is large, OMERO limits the display to 500 ROIs per page but server performances are not guaranted in such cases.

@Rdornier Rdornier added bug Something isn't working documentation Improvements or additions to documentation labels Dec 8, 2022
@romainGuiet romainGuiet added wontfix This will not be worked on and removed bug Something isn't working labels Dec 8, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation wontfix This will not be worked on
Projects
None yet
Development

No branches or pull requests

2 participants