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

pdb2sql selects one alternative location for atoms #83

Open
FarzanehParizi opened this issue Sep 23, 2022 · 3 comments
Open

pdb2sql selects one alternative location for atoms #83

FarzanehParizi opened this issue Sep 23, 2022 · 3 comments
Labels

Comments

@FarzanehParizi
Copy link

FarzanehParizi commented Sep 23, 2022

Better pdb2sql has an option to select one alternative location for atoms of a residue

Description of problem
While checking the similarity of two PDBs (decoy & ref) when there are alternative locations of atoms for a PDB, it fails to calculate RMSD, as one has more atoms for a residue.

Suggested solution
pdb2sql can have a feature that the user selects which of the alternative locations to select (e.g. altloc= "A") while generating a pdb2sql object (not using only occ value on PDB column)

Alternative solution
While checking the similarity of two pdb2sql objects, selects one alternative location

Additional context
If letting the user defines based on occ value on PDB column, it happens in some PDBs that the occ value is around 50 and that would not be that much helpful

@FarzanehParizi FarzanehParizi changed the title pdb2sql selects one alternative location for residues pdb2sql selects one alternative location for atoms Sep 23, 2022
@FarzanehParizi
Copy link
Author

You can use the following PDB files for this issue for PDB ID: 5KSA (change the extension from txt to pdb)

BL00060001_decoy.txt
BL00060001_ref.txt

@FarzanehParizi
Copy link
Author

The previous case had an alternative location in the Receptor region.
The following case has an alternative location in the Ligand region. PDB ID: 6DFS

6DFS_6BLX_BL00140001_decoy.txt
6DFS_6BLX_BL00140001_ref.txt

@github-actions
Copy link

github-actions bot commented Nov 4, 2022

This issue is stale because it has been open for 30 days with no activity. Remove stale label or comment or this will be closed in 7 days.

@github-actions github-actions bot added the stale label Nov 4, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant