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

Write out a software_versions file #185

Closed
silviamorins opened this issue Mar 29, 2019 · 3 comments
Closed

Write out a software_versions file #185

silviamorins opened this issue Mar 29, 2019 · 3 comments

Comments

@silviamorins
Copy link
Contributor

silviamorins commented Mar 29, 2019

Hi,

I see that a file containing information about all the versions of all the tools used by the pipeline is also generated:

rnaseq/main.nf

Line 306 in 37f260d

file 'software_versions_mqc.yaml' into software_versions_yaml
Can this information also be made part of nextflow's (MultiQC's) output? I need these numbers as well often for reporting and copying them down from the MultiQC report is doable but requires a little time.

Best,
Silvia

@ewels
Copy link
Member

ewels commented Mar 30, 2019

Yup, that's what the file is already used for 😉 See later on in the MultiQC process:

rnaseq/main.nf

Line 1092 in 37f260d

file ('software_versions/*') from software_versions_yaml

It should show up as a section right at the bottom of the report. Is this not the case?

Phil

@silviamorins
Copy link
Contributor Author

Yes it is the case, I see this session at the bottom of the MultiQC report - the question was if it can be written out as stand alone file in the rnaseq's pipeline results.

But I just chatted about it with @apeltzer and found out that a software_versions.yaml file already exists in the work directory, so I am just going to take it from there. Thank you for your answer :)

@ewels
Copy link
Member

ewels commented Apr 2, 2019

Ah I see, I misunderstood the question sorry. It would be pretty trivial to also output a csv / similar from that process and save it to the results folder if you think it would be useful. Just add to this file at the end, to print the dictionary to a csv file too. Then pick up that output from the process and use a conditional publishdir directive to only save this output file to the results.

Feel free to make a pull-request if you fancy it :)

Phil

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

2 participants