In SciJava Ops, ops are supposed to be deterministic. In scikit-ops, because they are often built on DL-based approaches, it's not always possible for them to be deterministic. But some/many of them can be, in which case they'd still produce cacheable outputs. Maybe we should let the @op decorator declare cacheable=True for those cases, as a hint?
In SciJava Ops, ops are supposed to be deterministic. In scikit-ops, because they are often built on DL-based approaches, it's not always possible for them to be deterministic. But some/many of them can be, in which case they'd still produce cacheable outputs. Maybe we should let the
@opdecorator declarecacheable=Truefor those cases, as a hint?