Haloplex & Allele Calling
Entering edit mode
11.3 years ago

My lab has started using the Haloplex technology to capture the regions of interest.

With this technology most of the reads have the same start/end (I've found that removing the duplicates would reduce the coverage to ~1 base). The reads are grouped in a vertical 'cluster' that can contains more than 1000 reads.

enter image description here

Have you ever used this technology ? I'm currently using samtools mpileup with the option "-A" ( count anomalous read pairs) and "-d 8000" ( max per-BAM depth).

I'm afraid there is a kind of bias with haloplex: is it safe to use samtools or Gatk to call the variants ?


allele calling next-gen samtools gatk duplicates • 5.5k views
Entering edit mode
11.3 years ago
Erik Garrison ★ 2.4k

In general, any capture-based technology will have bias. In your case, you're worried that the the bias will be amplified in the detection step.

I would use as many methods as possible to call these alleles, and see what the differences are. With coverage this high, there should be little variation in results.

Furthermore, simulation could provide an avenue to assessing potential bias in the case of haploplex resequencing. In simulated tests, I have observed that samtools and GATK have lower sensitivity than our caller (freebayes) at high depths, but all perform roughly the same at lower coverage. It's not entirely clear to me why this is, but I suspect default parameter selection may play a role. I haven't evaluated other callers, and it's possible that others may perform even better in high-depth contexts.

Entering edit mode
11.3 years ago
User 59 13k

Agilent will say that you should not de-duplicate Halo data. The vertical clusters are due to the placement of the restriction enzyme sites used to create the capture kits. There's very little off-target capture with Halo and the coverage can vary widely across an capture region ('Manhattan skyline' I think of it as).

You can use, and I have used samtools, GATK or VarScan to call variants from Halo data. However if you do use GATK then if you're post-filtering UnifiedGenotyper calls based on assumptions for exome or WGS data, you will probably find variants which do not pass your standard filtering test that are almost certainly genuine. Strand bias filters etc. seem to be the most prone to being tripped.

I've spoke to Agilent technical support before Christmas about what they propose for best practice genotyping, and the impression I got is that it's something they're working on but don't have a definitive answer for yet. I hope you're trimming the reads in conjunction with their guidelines as well.

EDIT: Since I wrote this post SureCall was released:


This is capable of analysing HaloPlex data and comes directly from Agilent to support the analysis of Haloplex designs from the SureDesign wizard.


Login before adding your answer.

Traffic: 3088 users visited in the last hour
Help About
Access RSS

Use of this site constitutes acceptance of our User Agreement and Privacy Policy.

Powered by the version 2.3.6