-
Notifications
You must be signed in to change notification settings - Fork 111
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
stderr=FAILURE: bad fasta character #1466
Comments
Note searching the original file for illicit characters does not return anything..
|
That's a new one. Given the error says You should be able to confirm by creating a work directory (I'm using
then pull the relevant fasta files being input into |
yup so there are some issues with some of the fasta files - but not empty headers. 1st lines of one of the offending fasta files (which I wrapped to make parsing easier) - looks good here.
Somewhere in the middle of the file a newline character was missed for a 2nd fasta entry.
I certainly hope this is not a fatal flaw requiring a total restart but i suspect it is. Wondering about the cause here. Any ideas? |
@glennhickey any chance it's the pipes in the fasta headers that are causing this issue? |
Could be. When I try to change some names in the test data to look like yours, I get an error right away
|
it's funny that I don't get that error until much later - does "sanitize_fasta" deal with Anyway I went for the clean/full restart to see if the error is reproducible or if it could have been related to some ?transient read/write issue. |
That check is on by default because the ucsc genome browser doesn't (or didn't) support these characters in assembly hubs. If I disable the check by setting
but since the check is on by default, I don't know why it didn't complain for you. It's not in In any case, I do not know what caused your error, and suggest double checking your input file. But if you are sure it's cactus causing the problem, please send me the input so I can try to reproduce. |
Hi All - having many jobs fail with this type of error, which seems to indicated perhaps something about a poorly formatted fasta file? One issue is that I can't seem to find the offending file
GCF_011100685.1_UU_Cfam_GSD_1.0_5.fa
. Not sure if this is related to some upstream error that was not handled properly.Any help here greatly appreciated!
The text was updated successfully, but these errors were encountered: