Skip to content
This repository was archived by the owner on Oct 6, 2021. It is now read-only.

VASP5.4.4 compiling with DFT-D4 #3

Closed
scott-5 opened this issue Apr 2, 2021 · 5 comments · Fixed by dftd4/dftd4#113
Closed

VASP5.4.4 compiling with DFT-D4 #3

scott-5 opened this issue Apr 2, 2021 · 5 comments · Fixed by dftd4/dftd4#113

Comments

@scott-5
Copy link

scott-5 commented Apr 2, 2021

when I compiling VASP5.4.4 compiling with DFT-D4, and so anything according README.md. But it occurs " subdftd4.F(28): error #7002: Error in opening the compiled module file. Check INCLUDE paths. [MCTC_ENVIRONMENT] "

@awvwgk
Copy link
Member

awvwgk commented Apr 6, 2021

I have an issue regarding this at the main repository tracking this: dftd4/dftd4#85

The update from version 2.5 to 3.x is a breaking API change, therefore the latest dftd4 is currently incompatible with Vasp. You can still use dftd4 2.5 with Intel 18 or older for now. Newer Intel versions 19 and newer only work with the 3.x versions of dftd4.

This repository is out of sync with the actual Vasp/dftd4 interface anyway. Not sure what the best way forward is for this issue. @f3rmion any thoughts on this?

@yhzhang95
Copy link

I have tested dftd4-2.5.0 API for vasp.5.4.4 using intel compiler versions 15.0.0, 18.0.1, 19.1.3 and 2021.2.0. And only intel 18 works without any segmentation errors. Does anyone know the main reason for limiting the flexibility of dftd4 usage?

@yhzhang95
Copy link

@scott-5 dftd4-2.5.0 release package does not include the MCTC_ENVIRONMENT mod file. you could download the source package and compile it with meson and ninja, and mod files will locate at ${DFTD4}/build/libdftd4.a.p and copy these mod files to your include path or release include path.

@awvwgk
Copy link
Member

awvwgk commented Apr 6, 2021

I have tested dftd4-2.5.0 API for vasp.5.4.4 using intel compiler versions 15.0.0, 18.0.1, 19.1.3 and 2021.2.0. And only intel 18 works without any segmentation errors. Does anyone know the main reason for limiting the flexibility of dftd4 usage?

Mainly the issue originates from a change in Intel 19, which broke both do concurrent and OMP reductions on scalars in dftd4. Resolving those issues required larger refactoring and let to version 3.

@yhzhang95
Copy link

@awvwgk thanks!

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants