and it ran for a while (several hours at least), but when I checked it this morning the last few lines of text in mothur.exe read as follows:
[..]
1727828
888427
Error in reading your fastafile, at position -1. Blank name.
496418
Error in reading your fastafile, at position -1. Blank name.
1446998
1847098
mothur >
There were no output files listed so I am inclined to believe that along with the errors, the command didn’t actually compete - though I may be wrong. If someone could offer some guidance that would be greatly appreciated.
This command failed before and the issue I’m posting about is what occurred when I tried to rerun the command… I am wondering at this point if I ought to just restart the pipeline? I can’t remember the issue when it first failed (it was not this same one), but I remember the Mothur.exe file being closed when it shouldn’t have been and no listing of output files.
The error you are getting seems to indicate an issue reading the fasta file, but the summary.seqs command is able to read it without failing. I would be happy to troubleshoot this for you. Could you send your fasta and count files to mothur.westcott@gmail.com?