I got to be able to avoid this problem.
It turned out that epsilon.x is not responsible to it, sorry.
Seemingly pw.x in many-band calculation or pw2bgw.x overwrites some of the input files generated by scf calculation.
First I executed codes in the following orders:
i. scf calculation by pw.x
ii. many-band calculation with 'bands' option by pw.x for WFN
iii. many-band calculation with 'bands' option by pw.x for WFN_inner
iv. conversion of WFN by pw2bgw.x
v. conversion of WFN_inner by pw2bgw.x
(and also for WFNq)
vi. run epsilon.x
I let epsilon.x and pw2bgw.x write down k points which they actually read, and found that pw2bgw.x at step iv is reading k point set of WFN_inner.
So I rearranged the order as:
i. scf calculation by pw.x
ii. many-band calculation with 'bands' option by pw.x for WFN
iii. conversion of WFN by pw2bgw.x
iv. scf calculation by pw.x
v. many-band calculation with 'bands' option by pw.x for WFN_inner
vi. conversion of WFN_inner by pw2bgw.x
(and also for WFNq)
vii. run epsilon.x
and it correctly worked.
Perhaps it might be trivial, but I wasn't aware of it.
Thank you so much if someone already considered this question.
Best,
Hiroki Katow
2022年8月26日金曜日 14:38:33 UTC+9 加藤洋生: