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

pipeline_report.{txt,html} missing from pipeline_info directory #697

Closed
2 tasks done
ChristopherBarrington opened this issue Sep 20, 2021 · 2 comments
Closed
2 tasks done
Labels
bug Something isn't working
Milestone

Comments

@ChristopherBarrington
Copy link

Check Documentation

I have checked the following places for your error:

Description of the bug

The pipeline_report.txt file is not written by v3.3

Expected behaviour

In previous versions the pipeline_info/pipeline_report.txt file contained (pretty much) the top lines of the output of the pipeline with each parameter listed.

System

I am using -profile crick

Nextflow Installation

  • Version:21.04.0

Container engine

  • Engine: Singularity
  • version: 3.4.2

Additional context

I checked in the rnaseq repo for where the file is written but could not see it. I'm not sure if it is part of the nf-core/tools repo and how those parts of nfcore work together with the DSL2 version?

@ChristopherBarrington ChristopherBarrington added the bug Something isn't working label Sep 20, 2021
@drpatelh drpatelh added this to the 3.4 milestone Sep 22, 2021
drpatelh added a commit to drpatelh/nf-core-rnaseq that referenced this issue Sep 22, 2021
@drpatelh
Copy link
Member

Thanks for reporting @ChristopherBarrington. So these files are created but only if you provide --email / --email_on_fail. The metrics that are dumped to those files are a byproduct of creating all of the info required to generate and send the email. This email code has required refactoring for the longest time (see nf-core/tools#112) so this is the best we can do for now :)

I have clarified this in the docs too drpatelh@8a558d3

drpatelh added a commit that referenced this issue Sep 22, 2021
@ChristopherBarrington
Copy link
Author

That makes sense, I had omitted that option for this run simply to avoid getting the email. But it's a small price to pay to get the parameter information recorded.

Thank you

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants