Skip to content
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

Pass Image_ID from selected image in OMERO.web #24

Open
ctrueden opened this issue Mar 13, 2014 · 2 comments
Open

Pass Image_ID from selected image in OMERO.web #24

ctrueden opened this issue Mar 13, 2014 · 2 comments
Milestone

Comments

@ctrueden
Copy link
Member

The currently selected image in OMERO.web is supposed to be automatically populated as the script's Image_ID if that field exists. But for some reason it isn't. This means you have to manually type the image ID when running ImageJ commands through OMERO.web, which is too bad. Figure out what the problem is.

@ctrueden ctrueden added this to the 0.3.0 milestone Mar 13, 2014
@ctrueden ctrueden modified the milestones: 0.1.1, 0.3.0 May 16, 2014
@ctrueden
Copy link
Member Author

The issue is that the field on the OMERO side needs to be called Image_IDs (IIRC), not Image_ID, and it needs to be a list, not a single long. That way, scripts can support a list of images for situations such as multiple thumbnails selected in OMERO.web.

The tricky part is that handling multiple selected images across the ImageJ boundary is non-trivial. Suppose you have a common ImageJ command that operates on an input image. Just one, not multiple. This is the typical scenario. Now in OMERO.web, you select three images and say "Find Edges"!

  • As a first cut fix for this bug, we could pass that list of Image IDs as the value of the Image_IDs parameter, which then gets culled to the first image ID which gets passed over the wire to ImageJ, and then Find Edges works... but only on the first selected image. Not all three.
  • But better would be for the ImageJ script runner to be smarter, and realize that its Image_IDs parameter maps to a single image, so we must sequentially execute Find Edges on each ID in the list, returning the results as an output list of processed images. Making this work as expected is more involved, and perhaps should be filed as a separate issue for a later milestone.

@ctrueden
Copy link
Member Author

Very related (duplicate-ish, actually) to #29.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant