question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Cannot find total energies in XTB output files

See original GitHub issue

Describe the bug When running an XTB geometry optimisation, a CouldNotGetProperty(energy) error is raised, despite the total energy being available in the XTB output file. Looking at the source-code in XTB.py (191-199) the line containing the total energy in the output file is expected in autodE to be in capitals (i.e. TOTAL ENERGY), but in the .out file is lowercase ‘total energy’. Changing this line locally on the source code fixes the big.

To Reproduce

mol = autode.Molecule(name='test', smiles='FC1=CC=C(NC(N2CCCC2)=O)C=C1C3=NC4=NC=C(N5CCOCC5)N4C=C3')
mol.optimise(method=ade.methods.XTB())

This raises a CouldNotGetProperty error

Expected behavior The energy to be located, and the optimisation to complete normally

Environment

  • Operating System: MacOS Monterey 12.2.1
  • Python version: 3.9.6
  • autodE version: 1.2.1
  • XTB version: 6.4.1

Additional context image

Issue Analytics

  • State:closed
  • Created 2 years ago
  • Comments:6 (4 by maintainers)

github_iconTop GitHub Comments

1reaction
awvwgkcommented, Mar 21, 2022

Redirecting the standard output will not necessarily work around the problem, we had this problem in crest (see https://github.com/grimme-lab/crest/issues/73#issuecomment-964562499). A safer fix would be setting the GFORTRAN_UNBUFFERED_ALL=1 environment variable on MacOS Monterey.

I heard homebrew was able to patch this issue in their GFortran, but I’m not aware whether this has been fixed in conda-forge’s GFortran yet (and requiring a rebuild of xtb). I created a homebrew tap for xtb at https://github.com/grimme-lab/homebrew-qc, which might provide a fixed version of xtb for MacOS.

0reactions
t-young31commented, Mar 24, 2022

Thanks @awvwgk for suggesting the fix and @matthewtoholland for reporting this. This is now merged into master 😄

Read more comments on GitHub >

github_iconTop Results From Across the Web

Quickstart into Production — xtb doc 2021 documentation
The log-file is in Xmol format and contains the current total energy and the gradient norm in the comment line, gmolden usually works...
Read more >
command-line xtb can't find configuration files #190 - GitHub
Hi Everyone, Since the Python API for xtb is still buggy, I have been running xtb from the command line. Unfortunately, I am...
Read more >
Extended tight‐binding quantum chemistry methods - Bannwarth
Abstract This review covers a family of atomistic, mostly quantum chemistry (QC) based semiempirical methods for the fast and reasonably ...
Read more >
Source code for morfeus.xtb - GitHub Pages
See xtb -python documentation electronic_temperature: Electronic ... _electronic_temperature = electronic_temperature # Set up results dictionary self.
Read more >
GFN1-xTB Method - PMC - NCBI - NIH
This is because the geometry of the system does not change during the calculation, and then, the D3 term only contributes to the...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found