-
Notifications
You must be signed in to change notification settings - Fork 7
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
Example of TableWrapper with ROI #57
Comments
The ROIs need a "ROI_ID" property set with their ID on OMERO (which is done automatically when retrieving ROIs). updatedRois = ROIWrapper.toImageJ(image_wpr.getROIs(user_client), "ROI")
TableWrapper table_wpr = new TableWrapper(user_client, rt, image_wpr.getId(), updatedRois, "ROI") However, you'll retrieve all the ROIs, so if you have more than what you want, you may have to filter them. Or use Folders. |
I'll try to improve the documentation... |
Hi, simple-omero-client/src/main/java/fr/igred/omero/annotations/TableWrapper.java Lines 408 to 435 in 9442f4a
Only one of those 2 is sufficient:
|
Well, it's also about what you want do display on OMERO:
I try to match against any of those properties when ROIs are passed to a TableWrapper (but you can't mix them though). |
Thanks for the answer, I am not familiar with 3D/4D ROI on OMERO. |
Oh, yes. Any string can be used to group 2D shapes, but, by default, I just return a local index (the string has to be parsed). At one point, I also merged "ROI" and "ROI_NAME" too, but there was actually no guarantee that ROI names should be unique. |
Hi,
Sorry, I already have a question.
I would like to create a Table in omero with a column with ROIs.
I have a ResultTable (obtained with Analyze particle) and the corresponding ImageJ ROIs (in the overlay).
I tried to use
setProperty
on the ImageJ ROIs then add a column in my ResultTable.But in omero there is no link between my table entries and my ROIs.
I am quite sure something is missing but I don't know what.
Would you mind to give an example?
Thank you.
My attempt was:
The text was updated successfully, but these errors were encountered: