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
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.
The text was updated successfully, but these errors were encountered:
@romainGuiet , @lacan , @NicoKiaru
We have tried to upload, on OMERO, QuPath detections as nested shapes inside ROIs in two different ways
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.The text was updated successfully, but these errors were encountered: