You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thanks for this nice tool. I used an older version a lot and upgraded recently to 2.1.10.
But there is one thing that I don't understand and it's maybe a bug.
If I have a point in the first sequence name of the alignment (e.g. ara|AT4G36090.3) the program stops with the following error message:
The specified file "test.fasta" cannot be read as an alignment
failed.
Alignment parse exception: Copy character (.) in first sequence not allowed (pos. 4)
But if the first sequence does not contain a point, it works even if the following sequence names contain a point again. E.g:
>stu|PGSC0003DMP400006353
...
>araAT4G36090.3
...
It doesn't matter if it's a fasta or phylip input file.
Can you please take a look in this problem? (Otherwise, I would have to edit several thousand files.)
PS: a minor thing: In the manual file, you referring to version 0.1.10 instead of 2.1.10.
\providecommand{\versionnumber}{0.1.10}
The text was updated successfully, but these errors were encountered:
thobrock
changed the title
Point (.) in first sequence name
Error: point (.) in first sequence name
Mar 11, 2016
Till this issue is fixed, I renamed all the sequences to remove the '.'. But it's a bit frustrating, because I have to rename the files afterwords again to get the original geneIDs back. It's an unnecessary step.
Thanks for this nice tool. I used an older version a lot and upgraded recently to 2.1.10.
But there is one thing that I don't understand and it's maybe a bug.
If I have a point in the first sequence name of the alignment (e.g. ara|AT4G36090.3) the program stops with the following error message:
But if the first sequence does not contain a point, it works even if the following sequence names contain a point again. E.g:
It doesn't matter if it's a fasta or phylip input file.
Can you please take a look in this problem? (Otherwise, I would have to edit several thousand files.)
PS: a minor thing: In the manual file, you referring to version 0.1.10 instead of 2.1.10.
The text was updated successfully, but these errors were encountered: