jean-marie burel
jean-marie burel
I have updated the readme with the various informations and how to retrieve the ports Also it is no longer necessary to go to infrastructure to run the playbooks
https://merge-ci.openmicroscopy.org/jenkins/job/OMERO-test-integration/1306/testngreports/integration.gateway/RawDataFacilityTest/testGetTileResolutions/ is green
https://merge-ci.openmicroscopy.org/jenkins/job/OMERO-test-integration/1306/testngreports/integration.gateway/MetadataFacilityTest/testGetPlaneInfo/ is green
We should unify with other repositories and use bump2version for version bump. Pushing the tag will trigger the GitHub action workflow pushing to pypi
* Fix selection bug when tracking an object i.e. select a shape in the table (right) when we move to the new plane. The selected shape is no longer selected...
It seems a small diff in time for diff in size. It will be good to check with remote server
> If we can just say "Over 1000 ROIs, everything is read-only" and then we can avoid loading permissions? Running tools like trackmate or ilastik on the type of data...
> So, we're not saving a huge amount of JSON data and marshalling, but we're saving quite a bit of time loading Points coordinates via projections instead of loading full...
I can see us deleting the ROIs that are false positive for example. IDR is a read-only server. Let's not confuse the two.
Agree we need to discuss the evolution of the ROI section(s) I have other use cases I want to discuss too.