Skip to content

Create a "SciJava ops philosophy" document #143

@elevans

Description

@elevans

ImageJ ops and SciJava ops clearly have distinct design philosophies that they abide by. While I know some of the reasons for why SciJava ops works the way it does, new users may be really mystified by it. Especially if they have any experience with ImageJ ops. For example when I was first interacting with SciJava ops, I thought the ops.binary() was a special namespace for binary images. So this call: ops.binary("filter.gauss").input(inImage, 2.0).output(outImage).computer() had me a little confused for a moment.

I think it would be a great starting point for new and existing users (i.e. I'd probably would refer to it myself and share it).

Metadata

Metadata

Assignees

Labels

docsIssues relating to documentation of the Ops frameworkenhancement

Type

No type
No fields configured for issues without a type.

Projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions