-
Notifications
You must be signed in to change notification settings - Fork 68
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
Investigate "dots" image vocabulary #220
Comments
maybe max-proj-{axes-list, sorted} |
I like it, except I'd be verbose: maximum-projection-{axes-list, sorted} |
Now that we use xarray, we can store arbitrary metadata on the DataArray object. I also opened #449 because I think max projection should generate a new ImageStack. It could be possible to store such information on the provenance of the new imagestacks in the attrs field. That would be really neat, as users would be able to see how their data was processed. |
@shanaxel42 how hard would it be for max_proj to be recorded in the log? I think that's all that is left to close out this issue. |
Remove ImageStack.max_proj. Steer users towards using ImageStack.reduce. Test plan: travis Addresses comment in https://github.com/spacetx/starfish/pull/1342/files#r288261378 Fixes #220
Remove ImageStack.max_proj. Steer users towards using ImageStack.reduce. Test plan: travis Addresses comment in https://github.com/spacetx/starfish/pull/1342/files#r288261378 Fixes #220
We generate a bunch of "dots" images that represent bright spots in the image. These are typically max projections over some subset of the data. Brian long suggested we might want to store some information on how such projections were created (e.g. max projection over z? z, h, and c?
Determine how to store this data in starfish and the starfish spec.
The text was updated successfully, but these errors were encountered: