-
Notifications
You must be signed in to change notification settings - Fork 32
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
Batch export ROIs from screen #156
Conversation
Travis failed with
Re-running... |
@@ -247,15 +247,36 @@ def link_annotation(objects, file_ann): | |||
o.linkAnnotation(file_ann) | |||
|
|||
|
|||
def get_images_from_plate(plate): |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Note for self
This is the kind of method to add to "omero-py-toolbox"
message = "Exported %s shapes" % len(export_data) | ||
return file_ann, message | ||
|
||
|
||
def run_script(): | ||
"""The main entry point of the script, as called by the client.""" | ||
data_types = [rstring('Dataset'), rstring('Image')] | ||
data_types = [rstring(s) for s in |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is much more than Screen as indicated in the PR title.
All types of containers need to be reviewed
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, that is in the description. Not space in the title for all testing instructions.
RFEs:
|
RFE #172 |
I found this useful recently, exporting big CSV from many images in a Screen or Plate.
To test: