Skip to content

Construct a mechanism for data provenance #53

@gselzer

Description

@gselzer

As Ops grows, we aspire to wrap the algorithms of other libraries into callable ops. This can result in numerous implementations of many algorithms, and it is of interest to determine which implementation was used for a particular Op call.

There are a few ways that we could try to implement this (note that this is an incomplete list):

  • @ctrueden suggested baking provenance data into "simplified" types (these types would arise as a part of the simplification work being done to solve Implement Type Conversion #4)
  • We might be able to bake this work in to the Op wrappers. This has the added benefit of recording data when no simplified types are used, but might extend past the intended purpose of the wrappers.

see scijava/scijava-common#227

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions