-
Notifications
You must be signed in to change notification settings - Fork 10
Skip wells #174
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
base: master
Are you sure you want to change the base?
Skip wells #174
Conversation
|
@jrswedlow You can install from this branch with Probably best to |
|
Testing against merge-ci looking good: Delete |
|
@jrswedlow I've added support for I don't know if you've been using the |
Have tested --skip_wells_map on Plates from Glencoe OMERO Plus and all seems to work. Great work! I have not tested --name_by |
|
A quick thought: though for this workflow having the explicit method is more straight-forward, I think there could be sufficiently many workflows that we wouldn't want individual command-line arguments. An alternative would be to have one command that generates a list of Wells (or any object) and then to take that list of identifiers as a skip list: |
|
Thanks @joshmoore - that makes sense. I'm not even sure at this point that we want to release any of this |
|
Conflicting PR. Removed from build OMERO-plugins-push#552. See the console output for more details.
|
This adds support for excluding Wells from Plate export, based on Key-Value pairs.
E.g. if we have
"my_key": "my_value"on a Well, we can exclude that with an exact match or with wildcards:This PR also adds a
--metadata_onlyoption, which skips all the pixel data (no chunks) but still includesarray metadata
.zarrayetc. This allows a fast export of a Plate, e.g. to quickly test the--skip_wells_mapabove.cc @jrswedlow