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

PyPDB for fetching .sdf (or .mol2) ligand coordinate #42

Open
areyesromero opened this issue Jun 12, 2021 · 2 comments
Open

PyPDB for fetching .sdf (or .mol2) ligand coordinate #42

areyesromero opened this issue Jun 12, 2021 · 2 comments

Comments

@areyesromero
Copy link

areyesromero commented Jun 12, 2021

Dear William,
Thanks for creating 'pypdb' module for such a large range of protein data.

As you can see from the picture, the PDB allows downloading either ideal CCDs or instance coordinates.

picture

In the current state of pypdb development, do you think there is/will be a possibility to download specifically only ligands coordinates (.sdf of .mol2) similarly to the "get_pdb_file" function?
This would speed up the process of collecting crystallographic reference libraries. In addition, I noticed that these coordinates are already represented in Kekulè form without therefore adding an extra step of preparing the downstream molecules.
Best regards
Atilio

@williamgilpin
Copy link
Owner

Hi Atilio, I will take a look at this to see if I can figure it out. I'll warn that I'm a bit slow to add new features these days, but I will leave this open in case any of our other contributors knows how to do it.

@danny305
Copy link

I have some scripts that will download mol2 files for ligands within a particular PDB. Does this sound like the functionality you guys want? If so I can make a PR and commit my scripts.

I have never used this repo and came by this issue in passing and just happen to already have code that does something similar.

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