SET_INDPW_FULL: insufficient memory

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

Moderators: Global Moderator, Moderator

Locked
Message
Author
verena_neufeld1
Newbie
Newbie
Posts: 1
Joined: Mon Jul 31, 2023 4:58 am

SET_INDPW_FULL: insufficient memory

#1 Post by verena_neufeld1 » Thu Oct 12, 2023 6:01 pm

I'm receiving this error. What can I do?

Code: Select all

 -----------------------------------------------------------------------------
|                     _     ____    _    _    _____     _                     |
|                    | |   |  _ \  | |  | |  / ____|   | |                    |
|                    | |   | |_) | | |  | | | |  __    | |                    |
|                    |_|   |  _ <  | |  | | | | |_ |   |_|                    |
|                     _    | |_) | | |__| | | |__| |    _                     |
|                    (_)   |____/   \____/   \_____|   (_)                    |
|                                                                             |
|     internal error in: mkpoints_full.F  at line: 1172                       |
|                                                                             |
|     internal error in SET_INDPW_FULL: insufficient memory (see wave.F       |
|     safeguard) 4881 4880                                                    |
|                                                                             |
|     If you are not a developer, you should not encounter this problem.      |
|     Please submit a bug report.                                             |
|                                                                             |
 -----------------------------------------------------------------------------
[MS]: I formatted the message to make the error more readable

martin.schlipf
Global Moderator
Global Moderator
Posts: 495
Joined: Fri Nov 08, 2019 7:18 am

Re: SET_INDPW_FULL: insufficient memory

#2 Post by martin.schlipf » Fri Oct 13, 2023 8:39 am

Can you please provide the input files of your calculation so that we can reproduce the issue?

Locked