Crashing Structure & "hit a member that was already found in another star"

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


Moderators: Global Moderator, Moderator

Post Reply
Message
Author
Greekman
Newbie
Newbie
Posts: 11
Joined: Fri Mar 02, 2007 1:55 pm
License Nr.: i will get one soon

Crashing Structure & "hit a member that was already found in another star"

#1 Post by Greekman » Wed Aug 01, 2007 8:52 am

Hello,

i have again a problem in one binary 2D-Alloy structure A1B5:

POSCAR:
-Vol
3.0 -1.0 0.0
2.0 1.0 0.0
0 0 6.192497648827324473
1 4
C
0 0 0 A
1 0 0 B
2 0 0 B
3 0 0 B
4 0 0 B

with KPOINTS:
Gamma
7 7 1
0 0 0


the Problem is that
1) in my OUTPUT-FILE the Sentence
"hit a member that was already found in another star"
is written really alot! and the outputfile is than around 10GB!!
i checked in the Forum than i can ignore it ... but it's really almost the whole outputfile!
2) after the first 7-10 electronic steps VASPs stops or crashed!

I am calculating on a Linux-based Cluster each time with 32 CPUs

Does anybody know what could be the problem?

thank you!
Last edited by Greekman on Wed Aug 01, 2007 8:52 am, edited 1 time in total.

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

Crashing Structure & "hit a member that was already found in another star"

#2 Post by admin » Wed Aug 01, 2007 12:41 pm

the easiset way is to set ISYM=0 to avoid this error.
Last edited by admin on Wed Aug 01, 2007 12:41 pm, edited 1 time in total.

sven
Newbie
Newbie
Posts: 3
Joined: Thu Aug 17, 2006 12:26 pm
Location: Sweden

Crashing Structure & "hit a member that was already found in another star"

#3 Post by sven » Thu May 15, 2008 11:45 pm

I have also encountered this error, but only when I used a geometry according to the following lattice vectors

5.8380000000000000 0.0000000000000000 0.0000000000000000
-1.4595000000000000 2.5279281536467763 0.0000000000000000
0.0000000000000000 0.0000000000000000 53.6633861430581049

The absolute lengths of the vectors are of course irrelevant, but |a1|=2|a2|, where a1 (a2) is the first (second) lattice vector.

If NGX != 2 NGY, the "hit a member" error arises.

So the solution in my case is either to explicitly set NGX and NGY in the INCAR file, so that NGX = 2 NGY or to set PREC = High or PREC = Accurate, in which case the relation NGX = 2 NGY is fulfilled by the default choice of NGX and NGY done by Vasp.

Maybe the solution to your problem can be found along the same lines, i.e. a careful choice of NGX and NGY.
<span class='smallblacktext'>[ Edited Fri May 16 2008, 01:48AM ]</span>
Last edited by sven on Thu May 15, 2008 11:45 pm, edited 1 time in total.

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

Crashing Structure & "hit a member that was already found in another star"

#4 Post by admin » Fri May 16, 2008 4:20 pm

please have a look whether it helps to set SYMPREC to the precision which has to be accounted for the read lattice vectors of the Bravais matrix. The default value is 10-5 this might not be enough (within the numerical accuracy) if you give the Bravais matrix with an accuracy of 10-16
Last edited by admin on Fri May 16, 2008 4:20 pm, edited 1 time in total.

sven
Newbie
Newbie
Posts: 3
Joined: Thu Aug 17, 2006 12:26 pm
Location: Sweden

Crashing Structure & "hit a member that was already found in another star"

#5 Post by sven » Mon May 19, 2008 12:13 pm

No, I have tried varying SYMPREC from 1E-3 down to 1E-16. From 1E-16 and lower, I got another error:

VERY BAD NEWS! internal error in subroutine SGRCON:
Found some non-integer element in rotation matrix 1

This error makes Vasp exit, so I have not been able to try smaller values of SYMPREC. However, none of the SYMPREC settings above 1E-16 resolved the "hit a member" error. The only thing that seems to help is to always let NGX = 2 NGY.
Last edited by sven on Mon May 19, 2008 12:13 pm, edited 1 time in total.

Post Reply