Skip to content

IUPAC bases in bcfnorm are converted to N instead of the bases from the VCF spec #2551

@bartcharbon

Description

@bartcharbon

We are using bcftools norm with --check-ref e, but it fails for structural variants in regions with IUPAC bases in the reference genome.
The SV caller we are using converts the IUPAC in the VCF REF field like:

R -> A
Y -> C
S -> C
W -> A
K -> G
M -> A
B -> C
D -> A
H -> A
V -> A

Which I think is following the latest VCF specs.
But since bcftools norm converts the non-N IUPACS to N the comparison then fails.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions