VASP5.4.4 + wan90v2 memory issue? #13
Dongsheng-Wen
started this conversation in
General
Replies: 2 comments 1 reply
-
Hi Dongsheng 👋 Pleas see https://github.com/Chengcheng-Xiao/VASP2WAN90_v2_fix/wiki/what's-wrong-with-the-original-interface%3F#original-symptoms for more insight. |
Beta Was this translation helpful? Give feedback.
0 replies
-
Hi Chengcheng, |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hello,
I have a question about compiling/using the vasp and wannier90 codes, but I couldn't find useful resources online. Then I saw this patch and think you might be able to give me some hints.
I was trying to compile vasp5.4.4 with wannier90v2 interface for SOC calculations. The compiled vasp seemed to be working fine. The executables were working without setting the wannier tags. Then I tested the code with the iron example on your repo. When I turned on the wannier tags to write the outputs .mmn and .amn, vasp stopped with errors like:
Program received signal SIGSEGV: Segmentation fault - invalid memory reference.
The .mmn file was written but .amn was not created.
For this simple Fe system, my computational power is good enough (512G memory + 128 cpus). It seems to me the memory issure is related to the wannier interface. So I wonder if the patch could solve this problem?
Thanks,
Dongsheng
Beta Was this translation helpful? Give feedback.
All reactions