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

CREST somewhat ignores param_gfn1-xtb? #223

Closed
yk07212 opened this issue Aug 27, 2023 · 7 comments
Closed

CREST somewhat ignores param_gfn1-xtb? #223

yk07212 opened this issue Aug 27, 2023 · 7 comments

Comments

@yk07212
Copy link

yk07212 commented Aug 27, 2023

Hi,
I am trying to run CREST using some different parameters for GFN1. However, the structures and energies it gives are based on the original parameters?
The odd thing is that it seems to load the custom parameters for the initial structure optimization as I get the "Initial geometry optimization failed!" error if I set the parameters to some absurd number (kexp=10000).
Am I misunderstanding something or does CREST not support xtb with a custom parameter file?
Thanks!

Edit: Explicitly setting the XTBPATH to the paramether file path did not help, also I am using the -nci mode !

@pprcht
Copy link
Contributor

pprcht commented Aug 28, 2023

Parameter files do not get copied locally, so having one in the working directory won't work automatically.
However, working with the XTBPATH variable should be possible, we are never telling xtb to not follow its parameter loading instructions.

@yk07212
Copy link
Author

yk07212 commented Aug 28, 2023

Giving the parameter file its own folder and setting the XTBPATH variable made it work !

  • Thanks

@yk07212 yk07212 closed this as completed Aug 28, 2023
@ismiek
Copy link

ismiek commented May 3, 2024

Hi,
I am a new user of CREST. I wanted to run Crest with gfn1 and Si parameters, which are now "implemented" in the new version. First, I tried as in xtb and then your way, but both didn't work. Could one of you explain how to let crest know to use gfn1-si?

@pprcht
Copy link
Contributor

pprcht commented May 3, 2024

If you are using the 2.12 version, or a >3.0 version in combination with the --legacy option, then the parameter change will probably work as described above.

For the default of CREST >3.0, I'll need to check how tblite can handle different xtb parameters.

@pprcht
Copy link
Contributor

pprcht commented May 6, 2024

@ismiek, for tblite this is not as straight-forward as for xtb. However, I think I made it work properly #303

Parameter files must be in toml format. Examples are located at assets/tblite/

The parameter file can be specified within the [[calculation.level]] block:

[[calculation.level]]
method='tblite'
tblite_param='gfn1.toml'

which formally replaces any other tblite method selection.

@ismiek
Copy link

ismiek commented May 10, 2024

Hi,
I am very thankful for your response. Unfortunately, the tblite method didn't work. I downloaded the gfn1-si.toml file and my input file looks like this:

#this is a crest input file
input='crest_input_copy.xyz'
runtype='imtd-gc'

#parallelization
threads=8

[calculation]
[[calculation.level]]
method='tblite'
tblite_param='gfn1-si.toml'

my command to start the conformation analysis was: crest konf_analys_nsi4.toml > gfn1_si.out
The calculation did run, but it didn't use gfn1-si as I can tell them apart from their si-si-binding length. Maybe I did something wrong, that's why I have put all these things.

@pprcht
Copy link
Contributor

pprcht commented May 10, 2024

Maybe a stupid question, but did you also update your CREST binary?
I can reproducibly affect the optimization of a Si dimer by providing the gfn1-si.toml file

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

3 participants