-
Notifications
You must be signed in to change notification settings - Fork 2
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
Update provenance format #27
Conversation
This is looking great. Could you add a section to the README that describes the format of the provenance file? See the kma-cgmlst README for an example. Please be sure not to include any real sample IDs in the example (just replace with https://github.com/BCCDC-PHL/kma-cgmlst?tab=readme-ov-file#provenance |
…f into update-provenance update remote
modules/tbprofiler.nf
Outdated
printf -- "- process_name: tbprofiler\\n" > ${sample_id}_tbprofiler_provenance.yml | ||
printf -- " tools:\\n" >> ${sample_id}_tbprofiler_provenance.yml | ||
printf -- " - tool_name: tb-profiler\\n" >> ${sample_id}_tbprofiler_provenance.yml | ||
printf -- " database_version: \$(grep 'Database version' ${sample_id}_tbprofiler_full_report.csv | cut -d',' -f2)\\n" >> ${sample_id}_tbprofiler_provenance.yml |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we remove this database_version
attribute here? That's important provenance info but I think we may need to find another place to put it. It doesn't fit there in the schema.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
...nevermind, I've done it myself.
Fixes #20
Adding provenance in the same format as BCCDC-PHL/kma-cgmlst
Format may still be adjusted to add name and and flag and optional description variable.
TBD: BCCDC-PHL/pipeline-provenance-schema