SEQanswers

Go Back   SEQanswers > Sequencing Technologies/Companies > Illumina/Solexa



Similar Threads
Thread Thread Starter Forum Replies Last Post
Bad read2 quality in Miseq Elham1 Illumina/Solexa 3 10-20-2014 10:44 PM
Poor Nextera XT index read quality on Miseq ustar Illumina/Solexa 2 07-22-2014 08:12 AM
bad quality of Read2 using a MiSeq ReagenKit v2 MiSeq_Issues? Bioinformatics 2 07-11-2013 07:37 AM
poor quality of seqeunce jali RNA Sequencing 0 11-02-2012 05:33 PM
Current read1, index, and read2 primers for HiSeq2000 SeqVicious Illumina/Solexa 1 09-26-2011 03:12 PM

Reply
 
Thread Tools
Old 05-05-2015, 07:59 AM   #1
rogerzzw
Member
 
Location: Grand Rapids

Join Date: Mar 2015
Posts: 16
Default partial poor quality index and read2

Hi, Guys

I am new to NGS. We've been trying to do whole genome bisulfite sequencing on Nextseq 500 for a few times with 2 samples.

We always encountered the same problem. After demultiplexing, there is about 50% of unknown index reads (most of them are "GGGGG" and "NNNNNN") . According to other centers using exact same kit and machine, they do not have any problems with adapters and indexes. And we always use single-use illumina kit and reagent for each run. So we do not know what happens.

We ve also tried to map read1 and read2 (with unknown barcodes). The alignment of read1 is quite good (90% aligniable), but reads2 is not good (~40%).

We used custom primer for read1 and illumina primers for read2 and index.

Many thanks in advance!

Roger
rogerzzw is offline   Reply With Quote
Old 05-05-2015, 10:58 AM   #2
pmiguel
Senior Member
 
Location: Purdue University, West Lafayette, Indiana

Join Date: Aug 2008
Posts: 2,237
Default

Not sure. Are you running just 2 samples per flowcell? Maybe you could drop down to one sample/flow cell and not use the index read?
How long are your reads?

--
Phillip
pmiguel is offline   Reply With Quote
Old 05-05-2015, 11:01 AM   #3
GenoMax
Senior Member
 
Location: East Coast USA

Join Date: Feb 2008
Posts: 6,548
Default

Phillip makes an excellent point. @rogerzzw: If your two indexes are very similar (can you post them) then you could essentially have a low nucleotide diversity/can't call bases type problem.
GenoMax is offline   Reply With Quote
Old 05-05-2015, 11:07 AM   #4
pmiguel
Senior Member
 
Location: Purdue University, West Lafayette, Indiana

Join Date: Aug 2008
Posts: 2,237
Default

Ah, yeah. I was going to mention that possibility as well.
I've noticed recently that for the HiSeq, its ability to demultiplex single indexes seems to have plummeted with a couple of recent HCS upgrades. In principle, demultiplexing a single index is not of much importance. But it suggests that its ability to demultiplex two indexes that are not "well balanced" might also have dropped.

However, the issue you are having with read2 mapping at low rates makes it sound like an instrument issue.

Also, obviously, a NextSeq uses completely different chemistry than a HiSeq, so who knows?

Very funny that your failed indexes are either poly N or poly G as "G" in NextSeq chemistry is encoded as no fluorescence. I'm unclear how the instrument can distinguish between "N" -- no signal and "G" -- no signal. Although my Illumina sales rep assures me that these two states do not look the same...
--
Phillip

Last edited by pmiguel; 05-05-2015 at 11:11 AM.
pmiguel is offline   Reply With Quote
Old 05-05-2015, 11:12 AM   #5
rogerzzw
Member
 
Location: Grand Rapids

Join Date: Mar 2015
Posts: 16
Default

Quote:
Originally Posted by pmiguel View Post
Not sure. Are you running just 2 samples per flowcell? Maybe you could drop down to one sample/flow cell and not use the index read?
How long are your reads?

--
Phillip
Hi, Phillip.

I am always using 2 samples. I will use only one sample for next run to see what happens. We are doing 150bp PE
rogerzzw is offline   Reply With Quote
Old 05-05-2015, 11:17 AM   #6
GenoMax
Senior Member
 
Location: East Coast USA

Join Date: Feb 2008
Posts: 6,548
Default

We had empirically determined that using 2 index pools (even though they may be well apart) was a recipe for problems. Three or more always seems to work best for HiSeq.

@Phillip: Interesting point about poly-G and poly-N.

Last edited by GenoMax; 05-05-2015 at 11:23 AM.
GenoMax is offline   Reply With Quote
Old 05-05-2015, 11:17 AM   #7
rogerzzw
Member
 
Location: Grand Rapids

Join Date: Mar 2015
Posts: 16
Default

Quote:
Originally Posted by GenoMax View Post
Phillip makes an excellent point. @rogerzzw: If your two indexes are very similar (can you post them) then you could essentially have a low nucleotide diversity/can't call bases type problem.
The barcodes I am using is
1. AGTGAG and GCACTA
2. AGTGAG and TGGTGA

But there are other groups suggesting they have no issue on barcodes, which makes me even more confused.

Thanks
rogerzzw is offline   Reply With Quote
Old 05-06-2015, 07:47 AM   #8
pmiguel
Senior Member
 
Location: Purdue University, West Lafayette, Indiana

Join Date: Aug 2008
Posts: 2,237
Default

Quote:
Originally Posted by rogerzzw View Post
The barcodes I am using is
1. AGTGAG and GCACTA
2. AGTGAG and TGGTGA

But there are other groups suggesting they have no issue on barcodes, which makes me even more confused.

Thanks
Right, we had no trouble with bar codes, even single ones, until the two most recent HCS updates. Now unbalanced ones seem to be problematic again.

How about the instrument that these are run on. Any issues with demultiplexing other projects?

--
Phillip
pmiguel is offline   Reply With Quote
Old 02-21-2017, 01:00 PM   #9
tacana
Member
 
Location: MD

Join Date: Feb 2011
Posts: 10
Default

Hello all,

I was wondering what was the resolution of rogerzzw problem? We are having similar issues with our next seq. and would love to hear how was this resolved.

Thanks in advance,

Al
tacana is offline   Reply With Quote
Reply

Tags
illumina, poor index and read2

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 09:43 PM.


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