The ABINIT Users Mailing List ( CLOSED )

[<jimprtlnd01@gmail.com>]

I'm running a dataset to calculate phonon response and eigendisplacements.  My
initial run took 3 hours (on 10 processors), but was a run for only 1 atom, 
and
in 1 direction.

I have started another run, again on 10 processors, but this time for all 43
atoms in all 3 directions.  I obviously understand that this may take
significantly longer.  so far, it's over 167 hours in.

It appears to be running, and Activity Monitor appears to be updating, but the
log file hasn't been modified since the day I started the process.  The same
goes for the .out file, although it appears to have worked up to the point
where it would start calculating the response functions.

Is this normal, for it to go so long without updating the log file or the
output file?  If not, is it stuck, and I have to restart it?  Are there 
reports
of ABINIT getting stuck in a loop of some sort?  I have personally seen times
where abinip doesn't fully stop, but in those cases the log file still 
signaled
that it was going to exit.  My current process doesn't say anything of the
sort.

The 10 processors are on 2 computers, both in the same room.  I am compiling
ABINIT 5.5.4, with openMPI 1.2.8, which seems to have fixed the segmentation
faults I was having with openMPI 1.2.7.

What should I look for to know if this is still running successfully?

Thanks,

Jim