Standalone blast: how to display only results with positive number of hits ?
0
0
Entering edit mode
8.2 years ago
lordbleys ▴ 10

Hi!

Here is my problem: I have a list of sequences (reads in fasta format) from a NGS experiment, and I want to identify some specific sequences in this list and count the number of occurrences they occur. The sequences I am looking for are grouped into a database (another fasta file).

I use a local standalone blast the following way:

makeblastdb -in database.fasta -out database -dbtype nucl
blastn -db database -query ngs_reads.fasta -out results.out

The problem is that the output file displays all the input sequences (several millions in my case), and only a handful of them actually score hits in the database. As a results I have a very impractical file to read until I find the results I am looking for.

I tried using the -outfmt option, but to no avail:

-outfmt "7 qacc sacc evalue length nident"

Also, the database is pretty big also, so inverting db/query doesn't really help (already tried).

My question is : is there a way to display only the query sequences for which the number of hits is > or = to 1 in the blastn output?

Any help would be most welcome! :)

next-gen blast • 3.7k views
ADD COMMENT
1
Entering edit mode
Why did you try outfmt 7 in particular? Have you read the manual/even checked the -help option? There are multiple suitable outfmts for you..
ADD REPLY
1
Entering edit mode

See this thread for some discussion about this: http://seqanswers.com/forums/showthread.php?t=14498

ADD REPLY
0
Entering edit mode

Thanks !

I tried outfmt 7 because of the formatting and the options, I didn't realize the "comment line" was my problem. Indeed very simply with the outfmt 6 it works perfectly.

ADD REPLY
0
Entering edit mode

Have you try to specify a value for evalue parameter?

ADD REPLY

Login before adding your answer.

Traffic: 2893 users visited in the last hour
Help About
FAQ
Access RSS
API
Stats

Use of this site constitutes acceptance of our User Agreement and Privacy Policy.

Powered by the version 2.3.6