-
Notifications
You must be signed in to change notification settings - Fork 16
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
ome 2021 workshop #88
Conversation
Not to block this PR, but I'll re-raise my concern here that as more logic gets added to these scripts, the more useful they become for other, non-training users. I'd really suggest that they get packaged in a re-usable way. |
The most useful functionality here is the type of "move data from one server to another" (e.g. Map Annotations). I know users are interested in moving Images from one server to another, which is really the first step. To get Images from IDR for this workshop prep I'm using a script (just a gist) that I created for users at ome/omero-documentation#2179 (comment). There's other code in the First questions:
|
I guess I would turn the questions back around: Are you ready to version the API with server? (If not, then omero-py probably isn't best) Having an |
204c247
to
b42bbfc
Compare
These changes weren't needed when all of idr0079 was imported on Training server
This is now in omero-guide-figure
Merging, since leaving this open as a PR isn't much of a better situation, but I'll re-iterate that I think we should work against the proliferation of one-off scripts. |
The The functionality that I think of these scripts in the same way as scripts in each IDR repo: specific one-off scripts to perform a particular data preparation step. Some of the changes I first made got reverted. For example, I realised that I could use metadata plugin to set pixel sizes. |
It's not as much about the scripts themselves (or the names) but the amount of code in them. |
Adding setup info for OME2021 figure workshop.
To test:
Follow the steps in idr0079-data-prep.md.