-
Notifications
You must be signed in to change notification settings - Fork 77
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
ValueError: HMMER added identifier prefixes to alignment because of non-unique sequence identifiers #189
Comments
This is the more informative error message I added as part of the solution to #175 so this appears to be in your branch already. My guess is that you are still using outdated SIFTS database files that were made with a version that doesn't have the fix (in the fixed version, the sequences in the FASTA file are prefixed with >evsp and >evtr instead of >sp and >tr to avoid the identifier clashes). if you remake these using the most recent develop or master branch version, the problem should be gone. |
That's fair. Problem: currently the
there are later versions on o2, but they are broken:
I supposed the Pinging: @b-schubert @aggreen This needs fixing ASAP because about 50% of the runs that I see being submitted via web fail at this stage. |
Plan: High prio
medium prio
|
Update : I've mistakenly committed directly to develop, but it's a super small update, see 1f9f35d Neccessary, because
which apparently means that one way or another, |
This is now done. If this problem persist, I'll re-open. |
Seems like this is still a problem?
just for one threshold (two other ones went through, so maybe it's just a problem in the SIFTs file?) in a web submitted job. See Using all the |
Nope if you check the stack trace this happens in the align stage. Reason is that a full Uniprot identifier (like sp|P01112|RASH_HUMAN) is searched against Uniprot and the region of the hit is exactly that of the query which triggers the HMMER renumbering. I mentioned this problem and the solution in the original issue #175 (comment) - fixing the identifier on the server is one line of code vs. introducing massive ugliness in the pipeline, so this one is on the server. |
Ref: #175 #151
A job for alpha-synuclein failed on compare with the following log:
This is different from the issues reported above, but seems related.
It is worth mentioning that this is running from the branch of #166 , which if I'm not mistaken doesn't include the changes of #180
I'll try to merge the latest develop into Management and run this again. Maybe @thomashopf you immediately see what happens and can deny/confirm that that's the issue.
The text was updated successfully, but these errors were encountered: