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.
|
|
Conflicting PR. Removed from build OMERO-plugins-push#31. See the console output for more details.
|
|
Conflicting PR. Removed from build OMERO-plugins-push#48. See the console output for more details.
|
|
Conflicting PR. Removed from build OMERO-plugins-push#65. See the console output for more details.
--conflicts |
|
I agree with #174 (comment) - Let's simply add support for e.g: I'm not sure whether we need to add support for: since that doesn't feel like Also, the export of Well KVPs to csv (included in this PR) is also handled by https://github.com/ome/omero-scripts/blob/develop/omero/annotation_scripts/Export_to_csv.py. Once you have a whole plate of KVPs in a CSV, it's pretty trivial (for a developer) to remove rows based on KVP values etc, and to generate a cc @jburel |
|
Conflicting PR. Removed from build OMERO-plugins-push#41. See the console output for more details.
--conflicts |
|
Conflicting PR. Removed from build OMERO-plugins-push#42. See the console output for more details.
--conflicts |
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