Replies: 2 comments 2 replies
-
Hi Marina, Thank you for your suggestion! :) The reason gget blast currently only takes into account the first sequence is that each sequence will have many rows of output. To BLAST all sequences in a fasta, I would have to concatenate the outputs while making clear which results belong to which sequence. For now, I would recommend passing each sequence in a fasta to gget blast in a loop. For example, the code below will pass each sequence in "test.fa" to gget blast and then save the results in a csv named after the sequence ID (text next to the ">").
|
Beta Was this translation helpful? Give feedback.
-
Hi Marina, A bit of a late reply, but |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi,
For the blast module, I think it would be convenient to modify the way fasta files are read, so that it is not sensitive to the number of lines in the file.
update:
As I understand it, a sequence record in a Fasta format consists of a single line of description starting with >, followed by a line(s) of sequence data, i.e. the sequence can be split into multiple lines and does not necessarily have to be a single line (as required by
gget
).For example, if the sequence record is as follows:
gget
will raise an exception since the sequence is split into 3 lines.Beta Was this translation helpful? Give feedback.
All reactions