core charge AECCAR0 and valance charge AECCAR2

Queries about input and output files, running specific calculations, etc.


Moderators: Global Moderator, Moderator

Post Reply
Message
Author
lsam
Newbie
Newbie
Posts: 9
Joined: Mon May 28, 2007 9:21 am
Location: Universidade do Minho

core charge AECCAR0 and valance charge AECCAR2

#1 Post by lsam » Wed Sep 26, 2007 1:32 pm

I want to write the files AECCAR0 and AECCAR2. So, I added in my INCAR file the line LAECHG=.TRUE., but the run stops due to the follow error:

forrtl: severe (174): SIGSEGV, segmentation fault occurred
Stack trace terminated abnormally.

Help please?

Regards
Last edited by lsam on Wed Sep 26, 2007 1:32 pm, edited 1 time in total.

admin
Administrator
Administrator
Posts: 2921
Joined: Tue Aug 03, 2004 8:18 am
License Nr.: 458

core charge AECCAR0 and valance charge AECCAR2

#2 Post by admin » Wed Sep 26, 2007 1:51 pm

at which stage did the execution of vasp stop?
Last edited by admin on Wed Sep 26, 2007 1:51 pm, edited 1 time in total.

lsam
Newbie
Newbie
Posts: 9
Joined: Mon May 28, 2007 9:21 am
Location: Universidade do Minho

core charge AECCAR0 and valance charge AECCAR2

#3 Post by lsam » Wed Sep 26, 2007 2:13 pm

There is all the output:

vasp.4.6.31 08Feb07 complex
POSCAR found : 2 types and 2 ions
LDA part: xc-table for Ceperly-Alder, Vosko type interpolation para-ferro
POSCAR, INCAR and KPOINTS ok, starting setup
WARNING: wrap around errors must be expected
FFT: planning ... 1
reading WAVECAR
forrtl: severe (174): SIGSEGV, segmentation fault occurred

Regards
Stack trace terminated abnormally.
Last edited by lsam on Wed Sep 26, 2007 2:13 pm, edited 1 time in total.

graeme
Jr. Member
Jr. Member
Posts: 54
Joined: Sat Jul 02, 2005 6:11 am
Location: Austin, TX
Contact:

core charge AECCAR0 and valance charge AECCAR2

#4 Post by graeme » Wed Sep 26, 2007 4:14 pm

I have seen this before and found that it is caused by insufficient memory. If you run the same job in parallel, spreading the memory across several machines, you can generate these charge density files.
Last edited by graeme on Wed Sep 26, 2007 4:14 pm, edited 1 time in total.

admin
Administrator
Administrator
Posts: 2921
Joined: Tue Aug 03, 2004 8:18 am
License Nr.: 458

core charge AECCAR0 and valance charge AECCAR2

#5 Post by admin » Thu Sep 27, 2007 8:17 am

another alternative (if you have no possibility to run vasp parallel, which would be the best solution to your problem) would be to reduce the required memory wherever reasonable (KPOINTS, PREC, ENCUT,....)
Last edited by admin on Thu Sep 27, 2007 8:17 am, edited 1 time in total.

Post Reply