Ploidy restrictions in norm and csq

Open
#973 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
30/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
c

Research direction

Start by reproducing the trisomy-X case with a genotype represented as 0/1/1, then inspect the implementations and tests for the bcftools norm and csq commands. Determine where ploidy is restricted and assess the implications for both commands. Done means ploidy-three records work correctly in norm and csq without regressing existing diploid behavior.

Written by the indexing model from the issue text.

Description

D1: Difficult

When splitting multiallelics using bcftools norm in one of our cohorts it fails on reaching the X chromosome because we have an individual with trisomy X in there, which we have called appropriately for the X chromosome using GATKs HaplotypeCaller ie the genotypes are represent in the form 0/1/1 for the trisomic X chromosome. We would really like to keep this individual, and any other sex chromosome aneusomies that we might find, represented appropriately in our cohort as it may well be relevant to the biology of the disease. Is it possible to increase the ploidy allowed to three?
Similarly we are finding bcftools csq very useful and it also fails when the ploidy is 3 - probably a more difficult problem to address, but any possibility?
Thanks

Dominant language
C
Stars
891
Forks
277
Avg merge
2d 23h
Merged PRs (30d)
2

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.

More from samtools/bcftools

All issues in samtools/bcftools

Similar issues

More C issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.