HSE calculations stops with BUG report

Problems running VASP: crashes, internal errors, "wrong" results.

Moderators: Global Moderator, Moderator

Post Reply
Message
Author
kdoblhoff
Newbie
Newbie
Posts: 28
Joined: Thu Feb 04, 2021 12:10 pm

HSE calculations stops with BUG report

#1 Post by kdoblhoff » Mon Jan 30, 2023 11:36 am

I am running an HSE calculations. Some of the calculations stopped with the following report:

Code: Select all

 FFT: planning ... GRIDC
 FFT: planning ... GRID_SOFT
 -----------------------------------------------------------------------------
|                     _     ____    _    _    _____     _                     |
|                    | |   |  _ \  | |  | |  / ____|   | |                    |
|                    | |   | |_) | | |  | | | |  __    | |                    |
|                    |_|   |  _ <  | |  | | | | |_ |   |_|                    |
|                     _    | |_) | | |__| | | |__| |    _                     |
|                    (_)   |____/   \____/   \_____|   (_)                    |
|                                                                             |
|     internal error in: mkpoints_full.F  at line: 1170                       |
|                                                                             |
|     internal error in SET_INDPW_FULL: insufficient memory (see wave.F       |
|     safeguard) 541 540                                                      |
|                                                                             |
|     If you are not a developer, you should not encounter this problem.      |
|     Please submit a bug report.                                             |
|                                                                             |
 -----------------------------------------------------------------------------

 FFT: planning ... GRID
 -----------------------------------------------------------------------------
|                     _     ____    _    _    _____     _                     |
|                    | |   |  _ \  | |  | |  / ____|   | |                    |
|                    | |   | |_) | | |  | | | |  __    | |                    |
|                    |_|   |  _ <  | |  | | | | |_ |   |_|                    |
|                     _    | |_) | | |__| | | |__| |    _                     |
|                    (_)   |____/   \____/   \_____|   (_)                    |
|                                                                             |
|     internal error in: mkpoints_full.F  at line: 1170                       |
|                                                                             |
|     internal error in SET_INDPW_FULL: insufficient memory (see wave.F       |
|     safeguard) 541 540                                                      |
|                                                                             |
|     If you are not a developer, you should not encounter this problem.      |
|     Please submit a bug report.                                             |
|                                                                             |
 -----------------------------------------------------------------------------
I have not yet investigated in more detail what may have caused this. The only thing that I DO know is that other calculations (including calculations with the exact same setup but a k-point mesh of 7x7x1 and 8x8x1 instead of 6x6x1 DID run). I know that there have been issues with VASP on the cluster that I am using, but I believe that they are related to the use of vasp on the high memory nodes. I attach the input.

Code: vasp.6.3.0 20Jan22 (build Dec 15 2022 23:39:30) complex
toolchain used for compilation: foss-2021a
Executed on: 1 node, 32 out of 128 cpu and 256 GiB of memory in total (so 1/4 for use)

I would be grateful if someone could check whether this has to do with the particular compile or with the input.
Thank you and best regards,
Katharina
You do not have the required permissions to view the files attached to this post.

alex
Hero Member
Hero Member
Posts: 567
Joined: Tue Nov 16, 2004 2:21 pm
License Nr.: 5-67
Location: Germany

Re: HSE calculations stops with BUG report

#2 Post by alex » Tue Jan 31, 2023 8:12 am

Hello Katharina,

my first impression is that your memory restrictions in the INCAR for HSE and the 32 cores will not suffice.

Please compare the actual number of k-points plotted in the OUTCAR with the larger mesh (symmetry might help here).

Good luck!

alex

fabien_tran1
Global Moderator
Global Moderator
Posts: 316
Joined: Mon Sep 13, 2021 11:02 am

Re: HSE calculations stops with BUG report

#3 Post by fabien_tran1 » Tue Jan 31, 2023 9:55 am

Hi,

By running the calculation using 32 cores I can indeed see that it runs with 5x5x1, 7x7x1 and 8x8x1, but not with 6x6x6. I suppose (?) that the distribution of the k-points can be done less efficiently with 6x6x1. However, using KPAR=4 in INCAR seems to be helpful for 6x6x1.

Post Reply