Skip to content

First pipeline release - #54

Open
BenjaminWehnert1008 wants to merge 531 commits into
masterfrom
dev
Open

First pipeline release#54
BenjaminWehnert1008 wants to merge 531 commits into
masterfrom
dev

Conversation

@BenjaminWehnert1008

Copy link
Copy Markdown
Collaborator

PR checklist

  • This comment contains a description of changes (with reason).
  • If you've fixed a bug or added code that should be tested, add tests!
  • If you've added a new tool - have you followed the pipeline conventions in the contribution docs
  • If necessary, also make a PR on the nf-core/dmscore branch on the nf-core/test-datasets repository.
  • Make sure your code lints (nf-core pipelines lint).
  • Ensure the test suite passes (nextflow run . -profile test,docker --outdir <OUTDIR>).
  • Check for unexpected warnings in debug mode (nextflow run . -profile debug,test,docker --outdir <OUTDIR>).
  • Usage Documentation in docs/usage.md is updated.
  • Output Documentation in docs/output.md is updated.
  • CHANGELOG.md is updated.
  • README.md is updated (including new tool citations and authors/contributors).

@nf-core-bot

Copy link
Copy Markdown
Member

Warning

Newer version of the nf-core template is available.

Your pipeline is using an old version of the nf-core template: 4.0.2.
Please update your pipeline to the latest version.

For more documentation on how to update your pipeline, please see the nf-core documentation and Synchronisation documentation.

MaximilianStammnitz and others added 15 commits July 25, 2026 16:41
improved false-double variant filtering
min_counts (1) and base_qual (40) were changed in nextflow.config but not in the
schema, which fails the nf-core lint check nextflow_config/config_defaults.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Two small robustness fixes, both leaving the estimator's logic unchanged:

* lm() is fitted on the finite rows only. .usable is already computed directly
  above and the guard already tests it, but the fit ran on the full vector, so a
  single -Inf (log of a zero-coverage double) aborted it with 'NA/NaN/Inf in y'.
  R's default na.action=na.omit already drops NA rows, so pre-subsetting gives
  identical coefficients wherever the fit currently succeeds; it only differs
  where lm() errors out today. The distance range is captured beforehand so the
  coverage lookup cannot end up shorter than the distances it is queried with.

* counts_per_cov_corrected is clamped at zero. The existing guard zeroes both
  columns but tests the *rounded* count, so a subtraction landing in (-0.5, 0]
  rounds to 0, skips the guard, and leaves a negative frequency behind. This
  completes the intent already stated in the code comment.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
The nf-test job fails while pulling the multiqc image with
'failed to register layer: no space left on device' (docker exit 125). The
pipeline pulls ~17 container images, three of them heavy bioconductor/R stacks
(mutscan, DiMSum), which overruns the runner disk part-way through.

Reclaim the preinstalled toolchain before anything is downloaded. The RunsOn
default image is ubuntu24-full-x64, so the same Android/.NET/Haskell bloat as a
GitHub-hosted runner is present and removable. The action SHA is the one already
pinned in download_pipeline.yml.

If this proves insufficient, the next lever is a larger runner volume via a
'volume=80gb' label on the nf-test job.
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

Successfully merging this pull request may close these issues.

4 participants