Open coltonbh opened 1 month ago
Also, I can confirm the same error when running example 2 on the documentation website found here. I'm using crest 3.0.2
.
Also can confirm this isn't a /n
issue. Tried solvent and solute with/without /n
characters to terminate their xyz
files.
Hi, which version of xtb are you using for the CREST runs? In version 6.7.1, there was a bug that caused a segmentation fault in the docking module, which might be the reason for the error you encountered. If you're using this version, I recommend switching to 6.7.1 or to the bleeding edge version of xtb to avoid this issue.
I'm not using an xtb binary. I'm using the CREST 3.0.2
binary available here on GitHub, which I believe uses tblite
under the hood (though I could be mistaken!).
QCG still uses xtb, there is a disclaimer in the README.md. It will have uses whatever binary it has found as there should be a error stop if none is present.
I see! That could be the issue! Really appreciate the feedback here to know what's going on.
It would be excellent if the program communicated these types of messages (ERROR: no xtb executable found.
) or something like that. Then I'd know how to proceed without harassing you here :)
Much thanks! Lemme try to run in an environment with an xtb
executable and see if that fixes it...
It actually already does that, here's the relevant part in QCG: https://github.com/crest-lab/crest/blob/a12cb4852e861864b7f220b1e51573c00ca33586/src/qcg/solvtool.f90#L56-L71
Are you sure there wasn't an xtb somewhere in path?
Ah. I see. And yes, I have xtb-python
installed, version 22.1
(though if you check xtb.__version__
it will say 20.2
due to this issue, the fix for which never got published to pypi).
Is there some reason you'd expect this executable to not work?
In the interests of not making yet another thread to report this, I'll comment here to report that I am also having the same issue.
In contrast to @matsumuraf in the other related thread, I can't run QCG example 1 either though and get the following output:
...
Command line input:
$ ../bin/crest bacillaene.xyz --qcg water.xyz --nsolv 100 --gfnff --T 12 --alpb water --nofix --xnam ../bin/xtb-bleed/bin/xtb
--gfnff : Use of GFN-FF requested.
--T 12 (CPUs/Threads selected)
--alpb water : implicit solvation
-xnam :
xtb executable was set to: "../bin/xtb-bleed/bin/xtb"
> Setting up backup calculator ... done.
----------------
Calculation info
----------------
> User-defined calculation level:
: GFN-FF calculation via GFNFF lib
: Molecular charge : 0
: Solvation model : alpb
: Solvent : water
========================================
| ---------------- |
| Q C G |
| ---------------- |
| Quantum Cluster Growth |
| University of Bonn, MCTC |
========================================
S. Grimme, S. Spicher, C. Plett.
Cite work conducted with this code as
S. Spicher, C. Plett, P. Pracht, A. Hansen, S. Grimme, JCTC, 2022, 18, 3174-3189.
The use of the aISS algorithm is requested (recommend).
This requires xtb version 6.6.0 or newer.
xTB-IFF can still be used with the --xtbiff flag.
=========================================
| quantum cluster growth: INPUT |
=========================================
QCG: Only Cluster Generation
input parameters
solute : bacillaene.xyz
charge : 0
uhf : 0
solvent : water.xyz
# of solvents to add : 100
Cluster generated that are above 10 % populated
# of CPUs used : 12
Solvation model : water
xtb opt level : normal
System temperature [K] : 298.1
RRHO scaling factor : 0.75
Solute geometry
molecular radius (Bohr**1): 11.20
molecular area (Bohr**2): 2554.19
molecular volume (Bohr**3): 5887.65
Solvent geometry
molecular radius (Bohr**1): 3.88
molecular area (Bohr**2): 194.90
molecular volume (Bohr**3): 244.27
radius of solute : 18.06
radius of solvent : 6.25
=========================================
| Preoptimization |
=========================================
error while reading coord line. EOF
Total Energy of solute not found
error while reading coord line. EOF
Total Energy of solvent not found
________________________________________________________________________
__________________ Solute Cluster Generation _____________________
________________________________________________________________________
=========================================
| quantum cluster growth: GROW |
=========================================
Water as solvent recognized, adjusting scaling factor for outer wall pot to 0.80
Solute:
unit ellipsoid axis a,b,c : 0.431 0.287 0.282
Solvent:
unit ellipsoid axis a,b,c : 0.386 0.322 0.292
solvent anisotropy : 1.133
solute anisotropy : 1.202
roff inner wall : 7.079
solute max dist : 41.009
solvent max dist : 7.278
inner unit axis : 0.534 0.236 0.229
inner ellipsoid/Bohr : 37.759 16.694 16.217
scaling factor outer ellipsoid: 0.800
outer ellipsoid/Bohr : 23.222 15.441 15.219
Size E De Detot Density Eatom av. R Rlast Volume Opt
[Eh] [kcal] [kcal] [u/Å^3] [kcal] [bohr] [bohr] [bohr^3]
Wall Potential too small, increasing size by 5 %
New scaling factor 0.84
Wall Potential too small, increasing size by 5 %
New scaling factor 0.88
Wall Potential too small, increasing size by 5 %
New scaling factor 0.93
Wall Potential too small, increasing size by 5 %
New scaling factor 0.97
Wall Potential too small, increasing size by 5 %
New scaling factor 1.00
ERROR STOP error while reading input coordinates
Error termination. Backtrace:
#0 0xced1d0 in ???
#1 0xced479 in ???
#2 0xcee587 in ???
#3 0x845de4 in __strucrd_MOD_rdxmol
at /home/runner/work/crest/crest/src/strucreader.f90:1028
#4 0x846c83 in __strucrd_MOD_rdcoord
at /home/runner/work/crest/crest/src/strucreader.f90:936
#5 0x6a94d3 in qcg_grow_
at /home/runner/work/crest/crest/src/qcg/solvtool.f90:661
#6 0x6b3e68 in crest_solvtool_
at /home/runner/work/crest/crest/src/qcg/solvtool.f90:87
#7 0x40e52b in crest
at /home/runner/work/crest/crest/src/crest_main.f90:261
#8 0x408f7e in main
at /home/runner/work/crest/crest/src/crest_main.f90:26
The error output with example 2 is similar:
...
Size E De Detot Density Eatom av. R Rlast Volume Opt
[Eh] [kcal] [kcal] [u/Å^3] [kcal] [bohr] [bohr] [bohr^3]
Note: The following floating-point exceptions are signalling: IEEE_UNDERFLOW_FLAG IEEE_DENORMAL
ERROR STOP error while reading input coordinates
Error termination. Backtrace:
#0 0xced1d0 in ???
#1 0xced479 in ???
#2 0xcee587 in ???
#3 0x845de4 in __strucrd_MOD_rdxmol
at /home/runner/work/crest/crest/src/strucreader.f90:1028
#4 0x846c83 in __strucrd_MOD_rdcoord
at /home/runner/work/crest/crest/src/strucreader.f90:936
#5 0x6a94d3 in qcg_grow_
at /home/runner/work/crest/crest/src/qcg/solvtool.f90:661
#6 0x6b3e68 in crest_solvtool_
at /home/runner/work/crest/crest/src/qcg/solvtool.f90:87
#7 0x40e52b in crest
at /home/runner/work/crest/crest/src/crest_main.f90:261
#8 0x408f7e in main
at /home/runner/work/crest/crest/src/crest_main.f90:26
And with my own attempt:
free(): invalid pointer
Program received signal SIGABRT: Process abort signal.
Backtrace for this error:
#0 0xced1d0 in ???
#1 0xcec805 in ???
#2 0x26c9cef in ???
#3 0x26edd3c in ???
#4 0x26c9c75 in ???
#5 0x4085ce in ???
#6 0x26e4335 in ???
#7 0x26f14cb in ???
#8 0x26f2603 in ???
#9 0x26f5c40 in ???
#10 0xa52a04 in get_volume_
at /home/runner/work/crest/crest/src/qcg/volume.f90:52
#11 0x6978e7 in get_sphere_
at /home/runner/work/crest/crest/src/qcg/solvtool.f90:2458
#12 0x6a3d0a in get_ellipsoid_
at /home/runner/work/crest/crest/src/qcg/solvtool.f90:2561
#13 0x6a8da4 in qcg_grow_
at /home/runner/work/crest/crest/src/qcg/solvtool.f90:545
#14 0x6b3e68 in crest_solvtool_
at /home/runner/work/crest/crest/src/qcg/solvtool.f90:87
#15 0x40e52b in crest
at /home/runner/work/crest/crest/src/crest_main.f90:261
#16 0x408f7e in main
at /home/runner/work/crest/crest/src/crest_main.f90:26
fish: Job 1, '../bin/crest input.xyz --qcg ./…' terminated by signal SIGABRT (Abort)
This last calculation was run with methanol rather than water as the solvent, I can provide structures if desired but it doesn't seem to be specific to that.
Following the advice above I tried using the bleeding-edge binary of xtb rather than 6.7.1 but that doesn't change anything.
This is with the pre-built binary of CREST 3.0.2, not the conda version, for reference, and all on Linux.
Describe the bug Running a quantum cluster growth calculation terminates with what appears to be a an issue reading structures.
To Reproduce
crest solute.xyz --qcg solvent.xyz --nsolv 10 --keepdir --gfnff --chrg 0 --uhf 0
solute.xyz
solvent.xyz
CREST Stdout
Expected behavior The QCG algorithm would execute correctly.