Skip to content

feat: Add cadd for indels#59

Draft
kristinebilgrav wants to merge 15 commits intodevfrom
add-cadd
Draft

feat: Add cadd for indels#59
kristinebilgrav wants to merge 15 commits intodevfrom
add-cadd

Conversation

@kristinebilgrav
Copy link
Copy Markdown
Contributor

@kristinebilgrav kristinebilgrav commented Mar 27, 2026

Closes https://github.com/Clinical-Genomics/wgs-cancer-pipeline/issues/27

Added

  • CADD score annotation for indels
    • created a subworkflow for the process (annotate_cadd)
      • Only runs if the val_cadd_resources is populated
    • added modules GAWK, CADD
    • compatibility with both GRCh37 and GRCh38
  • test for subworkflow:
    • NOTE: cadd resources are very large, which makes creating a test dataset hard, but this is being worked on in raredisease Add annotate_cadd subworkflow test nf-core/raredisease#794. We can update the test when this is completed. Therefore:
      • the subworkflow test is run in stub mode only currently
      • the default test does not run the annotate_cadd subworkflow

Test on hasta

@kristinebilgrav kristinebilgrav requested a review from a team as a code owner March 27, 2026 15:20
@github-actions
Copy link
Copy Markdown

PR checklist

  • Fill in description of the PR and link to any relevant issues.
  • If you've fixed a bug or added code that should be tested, add tests!
  • If you've added a new tool, follow the pipeline conventions in the contribution docs.
  • Usage Documentation in docs/usage.md is updated.
  • Output Documentation in docs/output.md is updated.
  • README.md is updated (including new tool citations and authors/contributors).

@github-actions
Copy link
Copy Markdown

github-actions bot commented Mar 27, 2026

nf-core pipelines lint overall result: Passed ✅ ⚠️

Posted for pipeline commit 8e0d785

+| ✅ 181 tests passed       |+
#| ❔  14 tests were ignored |#
!| ❗  25 tests had warnings |!
Details

❗ Test warnings:

  • readme - README contains the placeholder zenodo.XXXXXXX. This should be replaced with the zenodo doi (after the first release).
  • pipeline_todos - TODO string in README.md: TODO nf-core:
  • pipeline_todos - TODO string in README.md: Include a figure that guides the user through the major workflow steps. Many nf-core
  • pipeline_todos - TODO string in README.md: Fill in short bullet-pointed list of the default steps in the pipeline 2. Present QC for raw reads (MultiQC)
  • pipeline_todos - TODO string in README.md: Describe the minimum required steps to execute the pipeline, e.g. how to prepare samplesheets.
  • pipeline_todos - TODO string in README.md: update the following command to include all required parameters for a minimal example
  • pipeline_todos - TODO string in README.md: Add citation for pipeline after first release. Uncomment lines below and update Zenodo doi and badge at the top of this file.
  • pipeline_todos - TODO string in README.md: Add bibliography of tools and data used in your pipeline
  • pipeline_todos - TODO string in nextflow.config: Specify your pipeline's command line flags
  • pipeline_todos - TODO string in nextflow.config: Optionally, you can add a pipeline-specific nf-core config at https://github.com/nf-core/configs
  • pipeline_todos - TODO string in nextflow.config: Update the field with the details of the contributors to your pipeline. New with Nextflow version 24.10.0
  • pipeline_todos - TODO string in base.config: Check the defaults for all processes
  • pipeline_todos - TODO string in base.config: Customise requirements for specific processes.
  • pipeline_todos - TODO string in test.config: Specify the paths to your test data on nf-core/test-datasets
  • pipeline_todos - TODO string in test.config: Give any required params for the test so that command line flags are not needed
  • pipeline_todos - TODO string in test_full.config: Specify the paths to your full test data ( on nf-core/test-datasets or directly in repositories, e.g. SRA)
  • pipeline_todos - TODO string in test_full.config: Give any required params for the test so that command line flags are not needed
  • pipeline_todos - TODO string in main.nf: Optionally add in-text citation tools to this list.
  • pipeline_todos - TODO string in main.nf: Optionally add bibliographic entries to this list.
  • pipeline_todos - TODO string in main.nf: Only uncomment below if logic in toolCitationText/toolBibliographyText has been filled!
  • pipeline_todos - TODO string in methods_description_template.yml: #Update the HTML below to your preferred methods description, e.g. add publication citation for this pipeline
  • pipeline_todos - TODO string in nextflow.config: Specify any additional parameters here
  • pipeline_todos - TODO string in usage.md: Add documentation about anything specific to running your pipeline. For general topics, please point to (and add to) the main nf-core website.
  • pipeline_todos - TODO string in output.md: Write this documentation describing your workflow's output
  • local_component_structure - prepare_references.nf in subworkflows/local should be moved to a SUBWORKFLOW_NAME/main.nf structure

❔ Tests ignored:

✅ Tests passed:

Run details

  • nf-core/tools version 3.5.2
  • Run at 2026-03-30 15:07:49

@kristinebilgrav kristinebilgrav marked this pull request as draft March 27, 2026 15:33
include { paramsSummaryMultiqc } from '../subworkflows/nf-core/utils_nfcore_pipeline'
include { softwareVersionsToYAML } from '../subworkflows/nf-core/utils_nfcore_pipeline'
include { methodsDescriptionText } from '../subworkflows/local/utils_nfcore_oncorefiner_pipeline'
include { PREPARE_REFERENCES } from '../subworkflows/local/prepare_references'
Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

IDK why this appears here - could be something weird from my merge with dev?

Comment on lines +48 to +68
ch_samplesheet // channel: [mandatory] samplesheet read in from --input
ch_cadd_header // channel: [mandatory] [ path(txt) ]
ch_cadd_prescored_indels // channel: [optional] [ val(meta), path(dir) ]
ch_cadd_resources // channel: [optional] [ val(meta), path(dir) ]
ch_genome_fasta // channel: [optional] [val(meta), path(fasta)]
ch_genome_fai // channel: [optional] [val(meta), path(fai)]
ch_snv_vcf // channel: [optional] [val(meta), path(vcf)]
ch_snv_vcf_tbi // channel: [optional] [val(meta), path(vcf.tbi)]
ch_sv_dbs // channel: [optional] [path(csv)]
ch_sv_vcf // channel: [optional] [val(meta), path(vcf)]
ch_sv_vcf_tbi // channel: [optional] [val(meta), path(vcf.tbi)]
ch_vcfanno_extra // channel: [optional] [path(extra_file1), path(extra_file2), ...]
ch_vcfanno_lua // channel: [optional] [path(lua_file)]
ch_vcfanno_resources // channel: [optional] [path(resource_file1), path(resource_file2), ...]
ch_vcfanno_toml // channel: [optional] [path(toml_file)]
ch_vep_cache // channel: [optional] [vep_cache_files]
ch_vep_extra_files // channel: [optional] [path(plugin_file1), path(plugin_file2), ...]
val_cadd_resources // string: [optional] path to CADD resources directory
val_genome // string: [optional] genome assembly (e.g. "GRCh38")
val_species // string: [optional] species (e.g. "homo_sapiens")
val_vep_cache_version // string: [optional] version of vep cache to use (e.g. "107")
Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same here, I think I just fixed the spacing of the comments for the ones I did not add


PREPARE_REFERENCES (
params.vep_cache
val_vep_cache
Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Noticed that this was still param and not val (#58)

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.

1 participant