Obsolete comments on ddk calculation in toptic_3.in?

Documentation, Web site and code modifications

Moderators: baguetl, routerov

Locked
Robin
Posts: 61
Joined: Thu Jan 14, 2010 3:18 am

Obsolete comments on ddk calculation in toptic_3.in?

Post by Robin » Wed May 04, 2011 1:51 pm

Dear Developers,

Comments in toptic_3.in indicate that only Time-reversal symmetry can be used in a ddk response calculation. However, after doing several tests by using Abinit-6.2.2 I found these comments to be obsolete: using kptopt=1 will not cause a program abortion and it gives nearly the same result as kptopt=2 when the k-point sampling is dense enough.

Considering the tutorials are the main resource for new users to teach themselves and whether or not to employ the full symmetry means huge differences in a real calculation, could you please update them?

Sincerely,
Guangfu Luo

mverstra
Posts: 655
Joined: Wed Aug 19, 2009 12:01 pm

Re: Obsolete comments on ddk calculation in toptic_3.in?

Post by mverstra » Thu May 05, 2011 8:32 am

Hello Guangfu,

good that you checked. Could you be more precise on your test case, and quantify, please? In some cases you may get a reasonable answer even if things are formally wrong. To my knowledge no one has actually implemented this.

matthieu
Matthieu Verstraete
University of Liege, Belgium

Robin
Posts: 61
Joined: Thu Jan 14, 2010 3:18 am

Re: Obsolete comments on ddk calculation in toptic_3.in?

Post by Robin » Fri May 06, 2011 5:11 am

Dear Matthieu,

I did my tests this way to toptic_3.in. First, I increase ecut to 4 (just in case). Then I compare the final results (optical spectra) between kptopt=1 and kptopt=2 with different ngkpt (4x4x4, 24x24x24, and 36x36x36).

The tests show that different kptopt options display major spectrum differences in the low energy region, which decrease with increasing k-point sampling. For your convenience, all the test files and the comparison graph are attached.

Two additional things: (1) when kptopt=1 is specified for all datasets, kptopt is not printed in the *out file (but the *1WF file size is much smaller). (2) It seems that CASTEP can use the full symmetry in this kind of calculation.

Sincerely,
Guangfu Luo
test-files-for-toptic_3.tar.bz2.in
remove suffix .in
(165.09 KiB) Downloaded 351 times

User avatar
jzwanzig
Posts: 504
Joined: Mon Aug 17, 2009 9:25 am

Re: Obsolete comments on ddk calculation in toptic_3.in?

Post by jzwanzig » Fri May 06, 2011 12:29 pm

Before worrying too much about kptopt I would check carefully the ecut convergence. There is no way that ecut = 4 is high enough to be converged for any pseudopotential. We use values that low in the tutorials just so the calculations run really fast, but for real work you have to do a full convergence study of the pseudopotentials you are using.
Josef W. Zwanziger
Professor, Department of Chemistry
Canada Research Chair in NMR Studies of Materials
Dalhousie University
Halifax, NS B3H 4J3 Canada
jzwanzig@gmail.com

mverstra
Posts: 655
Joined: Wed Aug 19, 2009 12:01 pm

Re: Obsolete comments on ddk calculation in toptic_3.in?

Post by mverstra » Thu May 12, 2011 5:47 pm

Hi Joe and Robin,

Ecut convergence is not needed, the point here is to see whether kptopt 1 is actually admitted and works fine for ddk calculations. In theory it is possible, but we don't know if it has been coded. It looks like in this case it works, but I am wary - the real way to go is to check the code, or at very least to try many types of symmetry - it is possible that cases with more or less symmetrical unit cells will fail...

ciao

Matthieu
Matthieu Verstraete
University of Liege, Belgium

Robin
Posts: 61
Joined: Thu Jan 14, 2010 3:18 am

Re: Obsolete comments on ddk calculation in toptic_3.in?

Post by Robin » Mon May 16, 2011 12:20 pm

Dear Matthieu,

Actually, I tried a different system with hexagonal symmetry and also got consistent result with that from CASTEP (the intensity however differs by a constant).

Sincerely,
Guangfu Luo

mverstra
Posts: 655
Joined: Wed Aug 19, 2009 12:01 pm

Re: Obsolete comments on ddk calculation in toptic_3.in?

Post by mverstra » Wed May 25, 2011 4:34 pm

well, that constant could be due to the incomplete k-points: have you also compared kptopt 1 and 3 for the hexagonal case?
Matthieu Verstraete
University of Liege, Belgium

Locked