SEQanswers

Go Back   SEQanswers > Sequencing Technologies/Companies > 454 Pyrosequencing



Similar Threads
Thread Thread Starter Forum Replies Last Post
Paired end library, 3kb woes Coyk 454 Pyrosequencing 18 10-25-2012 11:07 PM
RNA-Seq: Genome Wide Full-Length Transcript Analysis Using 5' and 3' Paired-End-Tag N Newsbot! Literature Watch 1 01-20-2012 05:38 PM
How long should paired-end alignment run? agc Bioinformatics 11 09-07-2011 12:31 AM
Paired end tag chip-seq data available? kristi Bioinformatics 2 02-17-2011 06:47 AM
Paired End Library Size Selection GeCKo 454 Pyrosequencing 2 11-16-2010 07:06 AM

Reply
 
Thread Tools
Old 10-29-2008, 04:55 AM   #1
kmcarr
Senior Member
 
Location: USA, Midwest

Join Date: May 2008
Posts: 1,169
Default Plasmid contamination in Long Tag Paired End library

Our core facility just did a long tag paired end library prep and sequencing run using the standard GS FLX kit and protocol. The sequence output looked fantastic but when I went to assemble it (gsAssembler v 2.0) a large fraction of the reads were rejected by the assembler. After a lot of head scratching and further analysis I discovered that 90% of the reads were plasmid DNA; that plasmid being some pBR derivative. Being on the bioinformtics side I didn't know the full details of the library prep but discovered the source of the problem after discussing it with the lab folks. For those who haven't done this protocol, at one step you are supposed to add 3 ug of pUC19 as a "carrier". You are supposed to separate your DNA of interest a few steps later via a biotin moiety on the paired end adaptor. Obviously our cleanup was not very efficient.

My question is, has anyone else experienced this plasmid carry over with the long tag protocol? If so what have you done to address the problem?

Thanks,

Kevin
kmcarr is offline   Reply With Quote
Old 11-06-2008, 07:58 PM   #2
glacerda
Member
 
Location: Brazil

Join Date: Aug 2008
Posts: 27
Default

I am working with a 3K-LT run and I did not figure this problem before. Thanks for noticing that.
However, in my run, only 3% of the reads match a plasmid sequence.
glacerda is offline   Reply With Quote
Old 03-11-2009, 04:17 AM   #3
jpp
Junior Member
 
Location: the earth

Join Date: Mar 2009
Posts: 3
Default

Kevin,
We have got the same problem but a lesser extent, 50%, what is still very high. From Roche we have been told it was a bead washing problem, altough we followed strictly the protocol guidelines. In the eScholarship Repository, University of California we have found the following information, see the link http://repositories.cdlib.org/lbnl/LBNL-773E/ , where using Tween-20 to block the beads before DNA incubation disminish the inespecific pUC binding.
I hope it helps,we are going to try it the next time. Have you got rid off the pUC contamination?
Cheers
jpp is offline   Reply With Quote
Old 03-11-2009, 04:29 PM   #4
kmcarr
Senior Member
 
Location: USA, Midwest

Join Date: May 2008
Posts: 1,169
Default

Thanks jpp. I had been directed to that poster by someone else as well and I passed the information along to our lab personnel (I'm bioinformatics and don't get my hands dirty at the bench ;-) ). We did some additional runs and I think they did implement some additional washing but I'm not sure if they used the method outlined in that poster. We ran three long tag paired end runs recently and still found some contamination but not nearly as bad. One sample was only a few percent but another was > 30%. I think the most significant factor effecting this was the amount of material we had to start with. We may tell customers if they want to do long tagged paired ends they will have to give us 15g to start with.
kmcarr is offline   Reply With Quote
Reply

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 06:47 AM.


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