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

Using XTB built-in constraining potentials for metal / ligand binding #4

Open
7 of 10 tasks
joshkamm opened this issue Apr 13, 2022 · 0 comments
Open
7 of 10 tasks
Assignees

Comments

@joshkamm
Copy link
Member

joshkamm commented Apr 13, 2022

Notes from simplification of metal-ligand binding using XTB built in biased optimization instead of GSM, as well as some other cleanup and refactoring.

  • go through main.cpp and clean up commented out code
  • test with phosphine literature ligands
  • After binding, sort conformers by energy to see the ostensibly most realistic first
  • Extend workflow from debugging in vscode to running in a slurm job
  • Try test using full xTB instead of FF for quick debugging
  • Use IQMol to generate Pd(CH3)2 for testing binding
  • Test binding to Ph(CH3)2
  • Debug why first conformer doesn't seem to be performing alignment
    • may be a conformer getting carried over in main.cpp line 191
  • Execute on test ancillary ligands
  • automatically generate xtb.inp file
@joshkamm joshkamm self-assigned this Apr 13, 2022
joshkamm added a commit that referenced this issue Apr 13, 2022
added support for using XTB built-in constraining potentials for metal /
ligand binding instead of relying on GSM

refactored a number of functions to consolidate molecule data being
passed around into openbabel molecule objects

added (bool) casts to getline calls for newer compiler compatibility
joshkamm added a commit that referenced this issue Apr 27, 2022
test phosphine ligands taken from literature
joshkamm added a commit that referenced this issue May 4, 2022
joshkamm added a commit that referenced this issue May 7, 2022
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