-
Notifications
You must be signed in to change notification settings - Fork 420
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
Add nf-prov #1259
Add nf-prov #1259
Conversation
|
should we test it a bit first before adding to the patch release? |
@@ -328,6 +329,10 @@ dag { | |||
enabled = true | |||
file = "${params.outdir}/pipeline_info/pipeline_dag_${trace_timestamp}.html" | |||
} | |||
prov { | |||
enabled = true | |||
file = "${params.outdir}/pipeline_info/manifest_${trace_timestamp}.bco.json" |
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.
Why manifest_${trace_timestamp}.bco.json
? What does that mean?
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.
.bco
because BCO format
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.
Bitstream Compressed Outline Font file?
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.
Ah biocompute object. That's not obvious, let's add some documentation.
I'm not a fan of generic names like manifest_*_bco.json, I'd prefer it to be ${workflow.sessionId}.bco.json
but that feels like a separate issue.
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.
comment on nf-core/tools#2455
@@ -328,6 +329,10 @@ dag { | |||
enabled = true | |||
file = "${params.outdir}/pipeline_info/pipeline_dag_${trace_timestamp}.html" | |||
} | |||
prov { | |||
enabled = true |
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.
Could add a parameter for disabling it here? params.provenance
?
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.
That's what I said to @ewels and he said, you'd just need to add
prov.enabled = false in a config file to disable, so no need for a params.
And I kind of agreed because that's what we do with the other reports
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.
that's fair enough. I believe --prov.enabled false
might work as well?
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.
I'd say no, prov is a nextflow thingy, so -prov false
maybe?
It's been tested already ;-) |
@jfy133 reports that it works in taxprofiler: nf-core/tools#2455 (comment) |
ok fine. Just didn't want to break the patch :D |
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.
although feels like it should then be 3.4
We can discuss that in the prepare release PR |
PR checklist
nf-core lint
).nextflow run . -profile test,docker --outdir <OUTDIR>
).docs/usage.md
is updated.docs/output.md
is updated.CHANGELOG.md
is updated.README.md
is updated (including new tool citations and authors/contributors).