Skip to content
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

Better provenance tracking #64

Open
JoanneBogart opened this issue Sep 27, 2023 · 0 comments
Open

Better provenance tracking #64

JoanneBogart opened this issue Sep 27, 2023 · 0 comments

Comments

@JoanneBogart
Copy link
Collaborator

Currently a single config file, including provenance, is written when one or more output data files are created.
To be sure of what we're getting, provenance information needs to be kept on a per-data-file basis. It should include at a minimum

  • code identification. At least one of release version, git hash
  • run-time options and their values
  • inputs
  • output schema version
    Ideally the information should be stored as metadata in the binary output.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant