[Pw_forum] GIPAW memory problem?

[Davide Ceresoli]

Dear Aleksander,
     the gipaw behavior you reported is clearly odd. The initialization
phase should last few seconds and do not consume much memory.

I've just tested your input files and they work on my machine.
In your case, GIPAW appears to be stuck while reading the charge
density or in check_para_diag routine. Could you have an I/O problem?
Which compiler/MPI are you using?

Could you try gipaw with '-ndiag 1'? or, could you try the SVN
version (both QE and GIPAW)?

Let me know if nothing can work.

Best,
     Davide




On 05/12/2014 05:18 PM, Aleksander Jaworski wrote:
> Dear QE users and developers,
>
>
> I'm experiencing issues with running gipaw.x on the glass structures which
> have been created from the classical MD simulations trajectories.
> On the glass pw.x is running smoothly and converging properly. Gipaw.x is
> starting, but showing very strange behavior in terms of memory handling and
> never terminating the job.