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

Deprotonation runtype in input file #377

Open
cfarm6 opened this issue Dec 4, 2024 · 1 comment
Open

Deprotonation runtype in input file #377

cfarm6 opened this issue Dec 4, 2024 · 1 comment
Assignees
Labels
enhancement New feature or request

Comments

@cfarm6
Copy link

cfarm6 commented Dec 4, 2024

Is your feature request related to a problem? Please describe.
The protonation workflow is accessible via the input file syntax. It would be beneficial to have the deprotonation workflow also available as a runtype in the input file.

Describe the solution you'd like
I would like to see an option for setting the runtype as "deprotonate" in the input file syntax.

Describe workarounds you've considered
It is possible to use the cli however for a unified approach to developing computations with crest, having it available as a runtype would be advantageous.

@cfarm6 cfarm6 added the enhancement New feature or request label Dec 4, 2024
@pprcht
Copy link
Contributor

pprcht commented Dec 6, 2024

Yes, done: #379

Please note the TOML input activates the revised implementation of protonate/deprotonate/tautomerize that uses the tblite calculator rather than the xtb binary. This is equivalent to adding -newversion in the cli handling. The default will be switched to that version in 3.1.

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

No branches or pull requests

2 participants