Skip to content

Contigs without assigned phaseblocks in their name #38

@sivico26

Description

@sivico26

Hi @fenderglass,

Thanks for developing Hapdup. I am trying to phase some loci of an allopolyploid plant into what should be the 2 subgenomes of its parents. After checking the output, I have some questions. I will use one of the assemblies as an example.

For one of my locus if I look into the hapdup_phased_* assemblies, I can see the following names for hap1:

contig_10_phaseblock_0  33510
contig_12       5153
contig_14_phaseblock_0  11146
contig_16_phaseblock_0  9374
contig_20       34460
contig_23_phaseblock_0  35265
contig_7_phaseblock_0   8359
contig_7_phaseblock_1   66335

While for hap2 it is:

contig_10_phaseblock_0  31793
contig_12       5153
contig_14_phaseblock_0  9818
contig_16       13178
contig_20_phaseblock_0  38831
contig_23_phaseblock_0  36404
contig_7_phaseblock_0   7893
contig_7_phaseblock_1   66913

As you can see, most of the contigs have their homolog in both haplotypes (contigs 7, 10, 14, and 23). But there are other two categories that confuse:

  • Contig 12 does not have any phaseblock assigned in either of the haplotypes. I take this as that there were reads mapping into that contig after filtering, or maybe there were but not with enough variant information (e.g. a very homozygous region). In short, insufficient info to actually phase it.
  • But then I stumble to extend the previous reasoning with contigs 16 and 20. They are, respectively, assigned a phaseblock in haplotype 1 and haplotype 2, but not in the other. How should I interpret this?

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions