nf-core / nf-core/chipseq

Add --only_step options

Open
#337 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
Nextflow
Stars
246
Forks
184
PR merge metrics
No merged PRs in 30d

Description

Description of feature

Hi!

in the cutandrun pipeline, I really appreciate the option to run only one part of the pipeline such as --only_alignment to stop just after mapping the data.
Would it be possible to implement something similar for the chipseq pipeline?

My usage: I am running the chipseq pipeline on cutandrun data because single-end reads are not supported in the cutandrun pipeline. My data contain E.coli spike-ins that I would like to quantify in the exact same condition the samples are processed. If I run the pipeline on the E.coli genome just to quantify the E.coli reads, the pipeline fails while some samples are still mapping because the first sample to finish the mapping goes for peak calling which obviously fails due of the law amount of reads. As such, I have to re-run the pipeline on the unfinished samples again to until all samples are eventually mapped.
If an --only_alignment option existed, I could map my spike-ins and stop before the peak calling.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start at the chipseq pipeline entry point and compare its execution options with the cutandrun pipeline's --only_alignment behavior. Trace how the alignment stage is selected and where peak calling begins. Done means chipseq supports an --only_alignment option that completes mapping for all samples and stops before peak calling.

Written by the indexing model from the issue text.

Assessment

Domain
bioinformatics
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.