Skip to content

Representation of MNP #407

@lisosome

Description

@lisosome

I'm using Clair3 v1.2.0 to perform variant calling on ONT amplicon data. This is my Clair3 command:

/opt/bin/run_clair3.sh --threads=8 --platform="ont" --var_pct_full=1 --ref_pct_full=1 --var_pct_phasing=1 --min_mq=10 --enable_variant_calling_at_sequence_head_and_tail --haploid_sensitive --qual=15 --bam_fn=/orfeo/cephfs/scratch/burlo/nardone/minION_250331/reanalyses/STRC_analyses/25-703/2.ALIGNMENT/25-703.bam --ref_fn=/orfeo/cephfs/scratch/burlo/nardone/minION_250331/reanalyses/STRC_analyses/reference/STRC_ref.fasta --bed_fn=/orfeo/cephfs/scratch/burlo/nardone/minION_250331/reanalyses/STRC_analyses/25-703/3.VARIANT.CALLING/variant_calling_bed --model_path=/orfeo/LTS/burlo/LT_storage/shared/resources/clair3_model/r1041_e82_400bps_sup_v500 --output=${outdir}

In the resulting VCF I have two variants in two adjacent positions:

Image

However, after sequencing the sample using WES, an indel is called at the same position, with the deletion of the reference bases (GT) and insertion of the alternative bases (AG). Inspecting the BAM from the ONT sequencing, this is the site:

Image

What can be the reason why Clair3 is calling this variant as two distinct SNVs?

Best regards,
Giuseppe

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions