-
Notifications
You must be signed in to change notification settings - Fork 13
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
Add usage info to README #7
Comments
I again find myself trying to understand how to use this plugin. To reproduce, I created a 9-well plate using
and run like this
I get this output for EACH row in the csv (9 rows)
Followed by stacktrace So, something seems to have changed since I last tried running this script. Working my way through the source code in At this point I have no understanding of what the script is trying to do or how to use it. |
If I print out the
where e.g. 108 is the ID of the Well referred to by Although there are no columns for
|
I think whoever wrote this plugin or knows what the code does, should get back and add at least basic documentation (what a method does, what parameter it expects and what it returns). At least for me, not being a Python guru, it is basically unmaintainable like that. |
@pwalczysko You've had some success running "populate metadata" plugin recently. Can you share what you did to get it working? |
@will-moore https://docs.openmicroscopy.org/internal/testing_scenarios/BulkAnnotations.html is the basics - Testing scenarios :) |
OK, thanks. My bad. Testing locally I had forgotten that I'm now on a laptop that doesn't have pyTables installed! I assumed the problem was related to the |
No problem, same here. But you can play with outreach if you will. |
It's 8½ years old! ome/openmicroscopy@876841f |
PR opened at #28 |
Currently, arriving at https://pypi.org/project/omero-metadata/ (e.g. from the new 'apps' page ome/www.openmicroscopy.org#249) users have no idea what this tool does or how to use it.
Even
$ bin/omero metadata --help
would be a useful starting point.The text was updated successfully, but these errors were encountered: