This is tricky. It is dangerous to try it during a run_lapw, and the
results will be unpredictable.
If you are running on dedicated computers and not using pbs or some
other queue control then I suggest that you do "touch .stop" to
terminate them, then reduce the RMTs.
If you are running under pb
In this case I am inclined to think that the cause for termination is
not Wien2k.
Do you use a job scheduler? If yes, there should be a log file created
by the scheduler. (location of the file depends)
If you submit the calculation with 'nohup' command, there is a nohup.out
file.
Those fil
Dear Sir,
Thanks for your prompt reply.
Oleg:
The fact that _all_ your jobs terminated at the same time indicates that the
reason is likely outside of Wien2k.
venkatesh:
Yes sir, as you said all the calculations are stopped at the same time.
Further, "ls -ltr" gives <>.ouput1up/dn, <>.vectorup/dn
The fact that _all_ your jobs terminated at the same time indicates that
the reason is likely outside of Wien2k. I will describe how would I
approach this problem.
The error file is not always informative. It is created for each
executable when starting and is cleaned up upon its successful
c
Dear sir,
I am using departmental server computer system where many number of
calculations due to other programmes are going on in daily. In this, i am
also doing calculations using Wien2k. It is a serial processing system and
i started 5 calculations using different folders (different sessions).
5 matches
Mail list logo
