Skip to content

Releases: dftlibs/xcfun

XCFun v2.1.1

12 Nov 14:49
f9b5fdb
Compare
Choose a tag to compare

This patch release fixes two bugs:

  • The SCAN functionals were affected by numerical issues with small gradient values. Spotted by @fishjojo and fixed by @JFurness1. Thank you both!
  • The installation of header files, CMake export files, and the Python module was also fixed. Mostly relevant for the Conda package.

XCFun v2.1.0

18 Sep 12:39
8ec13b0
Compare
Choose a tag to compare

This minor release adds new functionals and usage improvements:

  • Thanks to @JFurness1, XCFun now provides many functionals in the SCAN family of metaGGAs.
  • The code can be built natively on Windows.
  • XCFun and its Python bindings can be installed in a Conda environment. The package is on the conda-forge channel.

XCFun v2.0.2

15 Jul 16:33
3751220
Compare
Choose a tag to compare

This release fixes a bug in the definition of the VWN3 correlation functional in the spin-polarized case.

XCFun v2.0.1

06 May 09:48
Compare
Choose a tag to compare

This release fixes build problems when using through CMake FetchContent.

XCFun v2

14 Apr 15:04
Compare
Choose a tag to compare

XCFun v2.0.0 is finally out as a stable release!

XCFun v2: seventh alpha version

10 Apr 08:49
4614fe5
Compare
Choose a tag to compare
Pre-release

Silence compiler warnings.

XCFun v2: sixth alpha version

23 Feb 09:55
16782af
Compare
Choose a tag to compare
Pre-release

Fix a compilation error with GCC 5.4.0

XCFun v2: fifth alpha version

20 Feb 11:28
f0f8835
Compare
Choose a tag to compare
Pre-release

Fixes handling of 64-bit integers when coupled to Fortran hosts.

XCFun v2: fourth alpha version

02 Feb 20:56
555b944
Compare
Choose a tag to compare
Pre-release

Further improvements to the documentation and a bugfix for the Fortran binding of the xcfun_get API function.

XCFun v2: third alpha version

31 Jan 08:30
84814d2
Compare
Choose a tag to compare
Pre-release

This alpha version introduces a number of breaking changes, motivated by the need to modernize the library.
It also means we are getting closer to a proper v2.0.0 release! 🎊 🥂

See the change log for a list of these changes and the migration guide for help on how to adapt to these breaking changes.