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).
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).