SEQanswers

Go Back   SEQanswers > Sequencing Technologies/Companies > 454 Pyrosequencing



Similar Threads
Thread Thread Starter Forum Replies Last Post
Using solexa to correct 454 homopolymer errors coldturkey Bioinformatics 21 01-26-2016 02:39 AM
Pileup - Filter SNP/Indel linked to 454 homopolymer bardou Bioinformatics 0 06-30-2010 08:17 AM
454 homopolymer error rate joa_ds 454 Pyrosequencing 10 12-18-2009 11:33 AM
Homopolymer error in 454 sequencing data Salmon 454 Pyrosequencing 3 02-06-2009 10:08 AM
454 homopolymer errors or???? ian Adams 454 Pyrosequencing 9 12-02-2008 02:46 AM

Reply
 
Thread Tools
Old 06-02-2015, 12:46 AM   #1
rubyb
Junior Member
 
Location: paris

Join Date: Jun 2011
Posts: 6
Default 454 Roche. homopolymer error

Hi Everybody,
I'm currently working on 454 sequencing data generated by roche. I would like to correct homopolymer errors (indels). Do you have a software to recommend me?

Thank you very much!
rubyb is offline   Reply With Quote
Old 06-17-2015, 08:54 AM   #2
martin2
Member
 
Location: Prague, Czech Republic

Join Date: Nov 2010
Posts: 40
Default

Error corrector for Illummina and Roche/454 able to also fix insertions and deletions

http://www.bioinformatics.csiro.au/blue


Below are some comments from its author from my Inbox:

<quote>
The -hp option sets a flag that is checked when Blue is scanning along a read trying to find errors that could be corrected. There are a number of tests done at every base position, all based on depth of coverage. These tests will pick up random indel errors, but indels are so common at the end of homopolymer runs in 454 and IonTorrent data that multiple hp run lengths all look to be OK. For example, if our genome had AAAAAA then with Illumina data this is what we'd see almost all the time, with very rare indels at the end of the hp run resulting in runs of 5 or 7 As. With 454-like data, we'd probably get 5 As as frequently as 6 As so depth of coverage would say that neither of them are errors. The -hp flag looks out for the end of hp runs and forces an attempt at correction at that point. If the read wasn't in error, then no correction will be made.

In general Blue will correct Ns - if a correct replacement can be found. The only time it doesn't do this is if there are too many consecutive Ns - as the process of finding likely replacements is combinatoric and the cost goes up exponentially with the number of consecutive Ns. In these cases, the read is abandoned and passed through uncorrected.
</quote>

I did not get to test it (yet).
martin2 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 11:58 AM.


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