nf-core / nf-core/crisprseq

Sample not being detected as edited despite evidence of editing in the bam file

Open
#188 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
Nextflow
Stars
63
Forks
39
PR merge metrics
No merged PRs in 30d

Description

Description of the bug

I’ve run this pipeline now with a few hundred samples - generally it seems to be working very well. However, I notice that one sample which clearly shows editing in the bam file, is not being detected as edited. Looking at the indels QC file, almost all the reads are not passing filter. However, I can’t see from the bam file why it shouldn’t be passing filter.
Screenshot 2024-07-09 at 13 25 58

Command used and terminal output

No response

Relevant files

No response

System information

No response

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 by reproducing the sample in the CRISPRseq pipeline and compare the BAM evidence with the indels QC filtering outcome. The issue names no source file, command, or test, so first locate the step that marks samples as edited and inspect why reads are rejected. Done means the demonstrated edited sample is detected without breaking filtering for other samples.

Written by the indexing model from the issue text.

Assessment

Domain
bioinformatics
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.