SEQanswers

Go Back   SEQanswers > Bioinformatics > Bioinformatics



Similar Threads
Thread Thread Starter Forum Replies Last Post
Assertion failed error in BFAST localalign seeker Bioinformatics 7 09-02-2011 10:33 PM
Bfast localalign error dg.pooja General 1 01-31-2011 06:35 PM
bfast localalign error nimmi Bioinformatics 6 01-05-2011 09:40 AM
bfast localalign -U option? Protaeus Bioinformatics 2 09-17-2010 12:50 PM
BFAST match/localalign help Esther Bioinformatics 3 08-04-2010 06:19 AM

Reply
 
Thread Tools
Old 12-03-2010, 07:41 AM   #1
yy01
Junior Member
 
Location: Florida, USA

Join Date: Sep 2010
Posts: 4
Question bfast localalign issues

Hi, anyone has an idea what causes this error?
Please, help!

Thanks in advance.



bfast localalign -f mature_converted.fa -m bfast.matches.s_1_1_sequence_clean.bmf > bfast.aligned.s_1_1_sequence_clean.baf
************************************************************
Checking input parameters supplied by the user ...
Validating fastaFileName mature_converted.fa.
Validating matchFileNamebfast.matches.s_1_1_sequence_clean.bmf.
**** Input arguments look good! *****
************************************************************
************************************************************
Printing Program Parameters:
programMode: [ExecuteProgram]
fastaFileName: mature_converted.fa
matchFileName: bfast.matches.s_1_1_sequence_clean.bmf
matchFileNameOne: [Not Using]
matchFileNameTwo: [Not Using]
scoringMatrixFileName: [Not Using]
ungapped: [Not Using]
unconstrained: [Not Using]
space: [NT Space]
startReadNum: 1
endReadNum: 2147483647
offsetLength: 20
maxNumMatches: 384
avgMismatchQuality: 10
numThreads: 1
queueLength: 10000
timing: [Not Using]
************************************************************
************************************************************
Reading in reference genome from mature_converted.fa.nt.brg.
In total read 17341 contigs for a total of 377003 bases
************************************************************
************************************************************
Reading match file from bfast.matches.s_1_1_sequence_clean.bmf.
************************************************************
Performing alignment...
Reads processed: 0bfast: RGMatches.c:91: RGMatchesRead: Assertion `m->readNameLength < 4028' failed.
Aborted
yy01 is offline   Reply With Quote
Old 12-04-2010, 12:01 AM   #2
nilshomer
Nils Homer
 
nilshomer's Avatar
 
Location: Boston, MA, USA

Join Date: Nov 2008
Posts: 1,285
Default

Looks like you may have some file corruption as the read name check should have been caught at the match step if it was real. Re-run the match process, and if that does not work, post to bfast-help@lists.sourceforge.net
nilshomer is offline   Reply With Quote
Old 12-06-2010, 05:29 AM   #3
yy01
Junior Member
 
Location: Florida, USA

Join Date: Sep 2010
Posts: 4
Default

Thanks, Nils!
Matches were re-run, and everything went through smoothly for running localalign.

-Yanming
yy01 is offline   Reply With Quote
Old 12-13-2010, 07:15 PM   #4
xinwu
Member
 
Location: Beijing

Join Date: Jul 2010
Posts: 33
Default

Quote:
Originally Posted by nilshomer View Post
Looks like you may have some file corruption as the read name check should have been caught at the match step if it was real. Re-run the match process, and if that does not work, post to bfast-help@lists.sourceforge.net
I met the same issue. After rerun it, It still threw this exception. I tested the data with Bowtie, it worked. So, what is the read name check? and why it failed in this step? Thanks.
xinwu is offline   Reply With Quote
Old 12-13-2010, 09:48 PM   #5
nilshomer
Nils Homer
 
nilshomer's Avatar
 
Location: Boston, MA, USA

Join Date: Nov 2008
Posts: 1,285
Default

Quote:
Originally Posted by xinwu View Post
I met the same issue. After rerun it, It still threw this exception. I tested the data with Bowtie, it worked. So, what is the read name check? and why it failed in this step? Thanks.
The read name cannot be longer than 4028 characters.
nilshomer is offline   Reply With Quote
Old 12-13-2010, 10:16 PM   #6
xinwu
Member
 
Location: Beijing

Join Date: Jul 2010
Posts: 33
Default

Quote:
Originally Posted by nilshomer View Post
The read name cannot be longer than 4028 characters.
Thanks for the quick reply, Nils. But I am sure the name should not exceed
4028 which is really a large number for a name. There must be something wrong somewhere.
xinwu is offline   Reply With Quote
Old 12-13-2010, 11:15 PM   #7
nilshomer
Nils Homer
 
nilshomer's Avatar
 
Location: Boston, MA, USA

Join Date: Nov 2008
Posts: 1,285
Default

There definitely is. Could you try aligning subsets of your reads until you can identify the problem read? That is how I would begin to debug this problem.
nilshomer is offline   Reply With Quote
Old 12-14-2010, 08:09 PM   #8
xinwu
Member
 
Location: Beijing

Join Date: Jul 2010
Posts: 33
Default

Quote:
Originally Posted by nilshomer View Post
There definitely is. Could you try aligning subsets of your reads until you can identify the problem read? That is how I would begin to debug this problem.
I've checked all read names, the max length of them is 37. I've tried a small set with 1000 reads, it worked fine. The original reads file is about 7G with ~130M reads (100bp). Does its size matter?
xinwu is offline   Reply With Quote
Old 12-15-2010, 12:19 AM   #9
nilshomer
Nils Homer
 
nilshomer's Avatar
 
Location: Boston, MA, USA

Join Date: Nov 2008
Posts: 1,285
Default

Quote:
Originally Posted by xinwu View Post
I've checked all read names, the max length of them is 37. I've tried a small set with 1000 reads, it worked fine. The original reads file is about 7G with ~130M reads (100bp). Does its size matter?
It shouldn't matter no. Try breaking it up into chunks of 1M reads, then processing them separately.
nilshomer 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 12:46 PM.


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