Yes, I had QTL in case.in2. Thank you very much Prof. Blaha for the
explanation, the problem was in vec2old. The condition in line 10 seems to be
too weak to handle my case. It only looks for rsh, while my $remote is called
"pbs_remsh", which does the same job but the inner workings are suited t
You got:
*calculating QTL's from parallel vectors*!!!
If I understand the message correctly, it happens ONLY ?? when you
calculate the qtls, not during scf.
So your command is either x lapw2 -p -qtl or you have QTL instead of
TOT (FOR) in case.in2 ???
In "qtl" mode, lapw2 runs
Sorry, the first sentence should read lapwso: why does "x lapw0 -p", "x lapw1
-p" and "x lapwso -p" work every time?
W dniu 12/10/17 04:25 Maciej Polak napisaĆ:
>
> Thank you for your answer, but do you know then why does "x lapw0 -p", "x
> lapw1 -p" and "x lapw2 -p" work every time? run_lapw,
Thank you for your answer, but do you know then why does "x lapw0 -p", "x lapw1
-p" and "x lapw2 -p" work every time? run_lapw, also works very well. I have
set the "$REMOTE" variable to "pbs_remsh", which is what my cluster uses, and
everything works perfectly, except for "x lapw2 -p", which us
This is local to your cluster. You almost need to talk to your sysadmins.
There are many possible solutions, but without knowing how your OS/ssh/jobs
are setup nobody will be able to do more than guess.
On Oct 11, 2017 8:36 PM, "Maciej Polak" wrote:
> Dear WIEN2k community,
>
> I am faced with a
Dear WIEN2k community,
I am faced with a problem, where the "x lapw2 -p" procedure on my cluster asks
me for passwords to all the nodes it uses:
calculating QTL's from parallel vectors
mpo...@wn0125.ib.trojan.kdm.wcss.pl's password:
no matter what I do after i get:
Received disconnect fro
6 matches
Mail list logo