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

MmCIF support #146

Open
xrobin opened this issue Sep 29, 2023 · 1 comment
Open

MmCIF support #146

xrobin opened this issue Sep 29, 2023 · 1 comment

Comments

@xrobin
Copy link
Contributor

xrobin commented Sep 29, 2023

Is your feature request related to a problem? Please describe.
The PDB is going to run out of 3 letter codes by the end of 2023 (see announcements 1, 2). This means that more and more PDB entries won't be available in legacy PDB format, adding to the growing list of reasons entries don't have a PDB file.

Describe the solution you'd like
Of course one can implement workaround (as I did previously for large structures).
But really, the long term, sustainable solution is support for mmCIF format as input.
In addition, this would mean such entries are available with the web tools (see for instance 4V9O, which cannot be analyzed currently).

Describe alternatives you've considered
Of course I could do some pre-processing of structures and rename 5-letter-code ligands to some of the reserved 3 letter codes (DRG, LIG, INH) and hope for the best.
But to be fair I'd rather not implement more and more workarounds. I don't think there are any long term alternative to mmCIF support.

Additional context
No

@xrobin
Copy link
Contributor Author

xrobin commented Jan 9, 2024

The PDB has started to release ligands with 5 letter codes. A1LU6 is the first one in entry 8XFM.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant