-
Notifications
You must be signed in to change notification settings - Fork 4
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
Fix key in _ma_model_list #23
Comments
That's not quite true. ModBase does support multiple models in one file if you select multiple sequences in the Sequence Overview (e.g. https://modbase.compbio.ucsf.edu/modbase-cgi/model_search.cgi?dataset=dengue) and then request coordinate files in mmCIF format. But you'll get each model in a separate data block.
python-modelcif uses python-ihm to assign model IDs. They are globally unique. You can see duplicate model IDs in the output (as above) if a given model is placed in multiple groups, but there are not multiple models with the same ID. |
Ah ok. Thanks @benmwebb for the clarification. In terms of multiple models in ModBase, I think that having them in separate data block is about the same as having them in separate files and so that doesn't change the conclusions. For the case of having the same model in multiple groups: was there any practical use case for this in IHM? I cannot think of a situation where I would have that for computed structure models and so I would be ok with simply not allowing this type of duplication. |
Agreed (internally it does indeed just concatenate multiple files).
I've never used it but the dictionary allows for it. |
Ok in that case I would suggest that we deprecate model_id altogether and disallow duplicated models to show up in ma_model_list. For the dictionary this means (updated suggestion compared to above):
|
In addition to the changes discussed above, I also suggest the following.
The changes will allow for many-to-many relationships between models and model groups and follow definitions similar to IHMCIF. All updates are implemented in #25 but can be rolled back if needed. |
Ok. Sounds reasonable. I will check in detail in #25 . One related comment though: the examples about |
Thanks for pointing out the outdated documentation in IHMCIF. We have not updated/maintained it after IHMCIF was included in https://mmcif.wwpdb.org/dictionaries/mmcif_ihm_ext.dic/Index/. Perhaps we should remove it completely. |
As discussed in other meetings, there is an issue with _ma_model_list since the primary key is ordinal_id but everything points to model_id. The possible solutions are to either move the primary key to model_id and deprecate ordinal_id or move parent-child relations to ordinal_id and deprecate model_id.
Practically the situation for current ModelCIF files (in ModelArchive, AlphaFold DB, AlphaPulldown, D-I-TASSER, ModBase and SWISS-MODEL) and tool support (python-modelcif) is as follows:
Suggested solution:
The text was updated successfully, but these errors were encountered: