-
Notifications
You must be signed in to change notification settings - Fork 3
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
Model couldn't be built #41
Comments
@cbaakman Can you find out why the model isn't being created and comment on this issue, please?
|
Template 4RH7_A doesn't cover position 3373 in that sequence. Only positions 1255 - 2575. (see alignment) So A model can be built, but not if you specifically ask for position 3373. |
OK..so after a more thorough check we can see that BLASTing of the query sequence against the PDB indeed results in 4RH7 as a 99% hit. This is a good one, and the hit also contains the mutant position 3373. Double check in the PDB file itself indeed shows the residue of interest nicely clear and present. |
HOPE uses hommod, which uses a local version of the blast program. Coos ran the blast program locally and it works, so the bug is likely in processing the output. Incidentally, mrs seems to suffer from the same problem. Coos is looking into it. |
It seems that the template 4RH7 isn't even in the blast database that hope uses. I'm now trying to find out why. |
It appears that 4RH7 contains the HET-group ADP ORTHOVANADATE. Vanadate is on hommod's black list, because yasara's modeling crashes whenever a template contains it. (some force-field parameter problem) The policy right now is not to use structures with such HET-groups as templates. @hanka would you rather have problematic HET-groups removed from the template before modeling? |
|
It seems that in yasara 16.4.6, vanadate is no longer a problem, so I've made changes to hommod in a pull request here: https://github.com/cmbi/hommod-rest/pull/43/files |
I get the feeling that Hommod is less able to build models for HOPE than the old solution. Many more reports are "empty" because there's no structure. This is a feeling, so we need to first check if this is the case.
Once we answer these questions, we can decide what to do about it, if anything.
@hvenselaar Would you be able to look at point 1?
@cbaakman Would you be able to look at point 2?
The text was updated successfully, but these errors were encountered: