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

unclear "dock" documentation #1126

Open
camattelaer opened this issue Nov 4, 2024 · 2 comments
Open

unclear "dock" documentation #1126

camattelaer opened this issue Nov 4, 2024 · 2 comments
Assignees
Labels
enhancement New feature or request

Comments

@camattelaer
Copy link

Hi all

not really a bug report, but i would like to clarify that the way of setting the level of theory for final optimizations in the documentation is unclear ( link to documentation ). More specifically this snippet:
afbeelding

I could not change the level of theory with either of these flags, so i had a look in the source and found that the correct way is by setting --optlvl <method> where <methid> is either gfn2, gfn1 or gfnff. (This is also defined in xtb dock --help)

I have two additional questions:

  1. I could not find any way to turn off the fast flag. Is it even possible to do so?
  2. Is there a way to monitor if dock is correctly applying e.g. the specified alpb or convergence criteria flag? since there is no individual output on optimizations, i can only monitor coordinates and respective energy/gnorm in final_opt.xyz. (Currently the --alpb flag is missing from the xtb dock --help but i did find a select-case for it in the dock.f90 source )

Thanks in advance!

Charles-Alexandre

@camattelaer camattelaer added the unconfirmed This report has not yet been confirmed by the developers label Nov 4, 2024
@cplett
Copy link
Member

cplett commented Nov 8, 2024

Hi,
Thank you for the feedback.
Using the --gfnff, --gfn2, or --gfn1 flag should also work in addition to the --optlvl <method> flag. I will add the latter to the documentation for consistency.
The fast mode is turned off by default so you don't need to switch it off as long as you don't provide the --fast flag.
Currently, there isn’t a way to monitor whether setting the convergence criterion or solvation model was successful, but that's a great suggestion. I’ll consider adding it in future releases.

@cplett cplett added enhancement New feature or request and removed unconfirmed This report has not yet been confirmed by the developers labels Nov 8, 2024
@camattelaer
Copy link
Author

Hi
Thanks for the reply! I've been trying to reproduce the --gfnX problem, but unsuccesful so i am not sure what caused it but good to know that it should work.

On the fast flag: even if i call xtb without the flag, the output mentions that fast mode is selected (recommended) (see attached output example:
xtb_docking.txt

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