Skip to content
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

Exosome model is missing starting model coordinates for Rrp46_gfp-m2 #49

Closed
benmwebb opened this issue Nov 2, 2017 · 5 comments
Closed

Comments

@benmwebb
Copy link
Contributor

benmwebb commented Nov 2, 2017

We refer to a starting model Rrp46_gfp-m2 in the .cif file for the Exosome example but don't have any coordinates for it in ihm_starting_model_coord. This is probably because the residue numbers are offset between the starting model and the output IMP model, and the IMP code is confused somehow. Will investigate.

@benmwebb benmwebb added the bug label Nov 2, 2017
@benmwebb benmwebb self-assigned this Nov 2, 2017
@benmwebb
Copy link
Contributor Author

Out of curiosity, why doesn't the mmCIF validator complain about this?

benmwebb added a commit to salilab/pmi that referenced this issue Nov 16, 2017
If there's a sequence offset between our internal (FASTA)
numbering and that of a starting model, we need to account
for that when we try to read the PDB file for that starting
model, otherwise we'll get the wrong (or empty) set of
residues. Relates ihmwg/IHMCIF#49.
@brindakv
Copy link
Collaborator

Some of the starting models, localization densities and output models are not aligned when visualizing with ChimeraX.

@brindakv brindakv reopened this Nov 17, 2017
@benmwebb
Copy link
Contributor Author

Some of the starting models, localization densities and output models are not aligned when visualizing with ChimeraX.

Maybe I don't understand what you're getting at here, but this seems unrelated (or by "some" do you mean specifically the Rrp46_gfp-m2 starting model?) And in any case, starting models in IMP generally aren't aligned with localization densities or output models - that alignment is done by ChimeraX. Maybe ChimeraX is also confused by the offset here? @tomgoddard would know for sure.

@tomgoddard
Copy link
Collaborator

The ChimeraX log says it failed to align Ski7_3izq_modeller_vmd.pdb chain X starting model to the sphere models. That is the only obvious alignment issue I see with the exosome.cif example. The reason for that is that the exosome example has 2 states, Rrp6 and Ski7 and the unaligned starting model is only part of the Ski7 state. But ChimeraX is only trying to align it to the Rrp6 state output models. The reason for that is that ChimeraX shows just the first output model group. There are 4 groups in the exosome case, the first 2 or two clusters of Rrp6 and the second 2 are two clusters of Ski7. So ChimeraX is initially showing only the Rrp6 output model for cluster 1. But it tries to align all starting models to that output model, and it can't align the Ski7_3izq... starting model since it is not part of that state. The sensible behavior would be to hide that starting model. I'll make a ticket for that. Another issue is that there is only one copy of the starting models in ChimeraX, so if you switch to showing one of the other 4 output models, the starting models are no longer correctly aligned with those. There is currently no capability to realign the starting models to a different output model. I'll make a ticket for that too.

@benmwebb
Copy link
Contributor Author

benmwebb commented Apr 5, 2018

Closing as this is better handled now by #52 and #53.

@benmwebb benmwebb closed this as completed Apr 5, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants