Go Back   SEQanswers > Applications Forums > Sample Prep / Library Generation

Similar Threads
Thread Thread Starter Forum Replies Last Post
Agilent SureSelect XT2 pre-capture library construction rthornton4 Sample Prep / Library Generation 1 01-30-2013 06:17 AM
Agilent SureSelect pre-capture multiplexing: which service provider ? carole_smadja Core Facilities 3 11-21-2012 09:14 AM
Pre-capture barcoding Sureselect and SOLID nighteffect SOLiD 1 04-13-2012 09:07 PM
about Agilent's SureSelect DNA Capture Array chenjy Bioinformatics 2 05-02-2011 08:11 PM
Procedure for paired-end with Agilent SureSelect array capture dnaeve Genomic Resequencing 5 04-16-2010 10:09 AM

Thread Tools
Old 07-23-2013, 03:28 PM   #1
Location: Brighton

Join Date: Jul 2011
Posts: 18
Default Agilent SureSelect XT Capture vs. SureSelect XT2 Capture ? What's the difference ?

I am trying to understand the difference between Agilent's Sureselect XT vs. XT2 exon captures.

From what I understand, with XT2, you pool all of the samples together and then use the capture. (V4 Exome + UTR) while with XT, you use the capture individually on each sample.

Is this understanding correct ?

Sorry if this question is too naive, I am mainly a bioinformatics person trying to understand the process.

From a Bioinformatics point of view, do you know if Agilent has separate BED files of targeted regions for XT and XT2 ? This is because I recently analyzed a set of samples, some of which were prepped using XT and others using XT2.

And for the ones with XT2, we did not find many reads mapping in the regions defined by Agilent's V4 + UTR BED file ? But there were a good amount of reads mapping in these regions for the XT samples.

Has anyone come across something like this before ?
medalofhonour is offline   Reply With Quote
Old 07-23-2013, 03:31 PM   #2
Senior Member
Location: St. Louis

Join Date: Dec 2010
Posts: 535

At least a year ago when I did targeted capture I was able to access the bed files of targeted regions through earray; is that possible now? I'd give that a try.
Heisman is offline   Reply With Quote
Old 07-23-2013, 04:02 PM   #3
Location: Brighton

Join Date: Jul 2011
Posts: 18

Yes I have the BED file, but it's just one bed file for V4 Exome + UTR capture. I am wondering if there are separate BED files for XT and XT2 protocols ?

This is because the BED file I am using gives me very low number of reads mapping in the target regions for the XT2 data.
medalofhonour is offline   Reply With Quote
Old 07-24-2013, 08:34 AM   #4
Cofactor Genomics
Registered Vendor
Location: St. Louis

Join Date: Jan 2010
Posts: 52

Have you run any qc on the data (FASTQC etc)? I would be suspect of the data and not the BED file if you are seeing few reads map back to the regions. I do not believe there are different BED files for pre and post-pooling captures.

Have you taken the data and aligned to the reference genome, not the BED file, to see the percentage of reads that hit the genome? This will tell you at least if it is the right sample or if there is some other contamination going on. Something could have gotten mixed up before it came to you.

There are quite a few other simply QC procedures that can be performed as it sounds like to me that it is a data problem and not an incorrect reference.

Jon Armstrong
Cofactor Genomics
Cofactor Genomics is offline   Reply With Quote
Old 08-07-2013, 10:40 AM   #5
Junior Member
Location: California

Join Date: Aug 2013
Posts: 1

Did anyone figure out whether this was a bed file associated issue or whether it was the pre-capture (XT2) library prep steps that affected capture efficiency?
Any updates on XT2 performance would be appreciated.
sprabhu is offline   Reply With Quote

agilent sureselect xt xt2

Thread Tools

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

All times are GMT -8. The time now is 10:09 AM.

Powered by vBulletin® Version 3.8.9
Copyright ©2000 - 2021, vBulletin Solutions, Inc.
Single Sign On provided by vBSSO