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

Indices of atom loading from SMILES may not be definitive #1008

Open
daico007 opened this issue Feb 17, 2022 · 3 comments
Open

Indices of atom loading from SMILES may not be definitive #1008

daico007 opened this issue Feb 17, 2022 · 3 comments

Comments

@daico007
Copy link
Member

Bug summary

Atom order might not be definitive when loading from a SMILES string when using RDKit. Specifically, the index of the atoms when loading from a SMILES string with rdkit may changed with different rdkit version. This may affect functions that rely on atom indices like mbuild.lib.recipes.Polymer. This issue is not imminent, but we probably need to assert the order when loading in a SMILES string to ensure we got when we expect when select a compound by its index. This issue is brought up by Jeffrey Wagner during the MoSDeF-OpenFF meeting.

Software versions

  • Which version of mBuild are you using? (python -c "import mbuild as mb; print(mb.__version__)")
  • Which version of Python (python --version)?
  • Which operating system?
@CalCraven
Copy link
Contributor

Any updates on this @daico007?

@daico007
Copy link
Member Author

Nothing at the moment, I was thinking of implement some rudimentary sorting during the convert RDKit structure step to assert the orders are correct, but I have started nothing yet. This was something brought up by Jeff during one of our meeting with the OpenFF folks.

@CalCraven
Copy link
Contributor

Gotcha yeah, I think this is a worthwhile issue since so many of our workflows are starting to use the loading from SMILES. I'll see if I can generate some code here to post that replicates the issue, to make sure it's still here.

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

2 participants