![]() |
|
|||||||
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| Centos for Roche 454 Data Analysis software | lyuen | General | 7 | 10-15-2012 10:50 PM |
| Installing Roche 454 Analysis software version 2.6 (gsAssembler) on Fedora 15 | dsenalik | 454 Pyrosequencing | 1 | 09-27-2011 06:29 AM |
| how to run amplicon variant analysis in sever | liuseq | 454 Pyrosequencing | 0 | 12-28-2010 10:05 AM |
| amplicon-import data into the 454 software | litali | Bioinformatics | 0 | 08-24-2010 10:57 PM |
| Roche/454 Titanium Amplicon sequencing? | robhall | Sample Prep / Library Generation | 7 | 09-01-2009 09:58 AM |
![]() |
|
|
Thread Tools |
|
|
#1 |
|
Junior Member
Location: USA Join Date: Sep 2009
Posts: 1
|
Any suggestions for software alternatives to the Roche AVA module for analyzing amplicon variation in 454 data where individuals are identified with tagged primers?
Many thanks, Lisle Gibbs |
|
|
|
|
|
#2 |
|
Member
Location: Wisconsin Join Date: Jul 2009
Posts: 21
|
We do highly multiplexed amplicon-based genotyping with 454 and have found AVA inadequate.
Here's how we deconvolute and analyze the tagged sequence data. The key is to split apart the .sff files from the sequencer using Roche's command-line tool called "sfffile" which is available as part of the Roche-454 off-instrument software package. By using the correct arguments and MID-configuration file this will break your data into MID specific .sff files. Then, we analyze each patient specific sequence data individually. A scriptable assembly software package will allow you to do this in batch. In our case we use Seqman, from DNAstar, to assemble the reads at high identity (99.5 - 100%) and then blast them against a genotyping database. |
|
|
|
|
|
#3 |
|
Senior Member
Location: Denmark Join Date: Apr 2009
Posts: 137
|
How is such a MID configuration file defined?
|
|
|
|
|
|
#4 |
|
Rick Westerman
Location: Purdue University, Indiana, USA Join Date: Jun 2008
Posts: 685
|
In your 454 software's config directory there will be an MIDConfig.parse file that contains the information in the form:
GSMIDs { mid = "MID1", "ACGAGTGCGT", 2; mid = "MID2", "ACGCTCGACA", 2; ... |
|
|
|
![]() |
| Thread Tools | |
|
|