-
Notifications
You must be signed in to change notification settings - Fork 678
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
Comments
Yup, that's what the file is already used for 😉 See later on in the MultiQC process: Line 1092 in 37f260d
It should show up as a section right at the bottom of the report. Is this not the case? Phil |
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 :) |
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 |
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
Best,
Silvia
The text was updated successfully, but these errors were encountered: