Repository navigation
Corrections to the CHANGELOG and report no longer reading the trace - #98
Merged
Merged
Conversation
…TML report now links to Nextflow's execution report instead of reading the trace
|
MaximilianStammnitz
enabled auto-merge
November 4, 2026 14:49
maxulysse
approved these changes
Nov 6, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Small fixes based on @maxulysse's review comments (#54)
Execution trace in the report
Until now, the report's "Run statistics" panel was built from Nextflow's execution trace, which the workflow read back from
${outdir}/pipeline_info/while the run was still writing it. That breaks with remote outdirs, with user configs that switch the trace off or rename it, and with-resume. This PR:workflows/deepmutscan.nf: no longer passes the trace to the reportbuild_summary_report.py: removesrun_stats()and thetraceinputsummary_report_template.html: the "Run statistics" panel now links to Nextflow's execution report and timeline inpipeline_info/docs/output.md,docs/usage.md: updated to matchCHANGELOG
--min_counts(default 10): the line described the behaviour from before Samplesheet checks and parameter conventions (Issue #69) #82. It now says that the threshold only applies to fitness estimates; counting, error correction and library QC use all reads.--output_pseudocount.PR checklist
nf-core pipelines lint).nextflow run . -profile test,docker --outdir <OUTDIR>).docs/output.mdis updated.CHANGELOG.mdis updated.