24小时热门版块排行榜    

查看: 11094  |  回复: 274
当前主题已经存档。

wuli8

荣誉版主 (知名作家)

★ ★ ★
wuchenwf(金币+3,VIP+0):谢谢 8-21 20:05
引用回帖:
I am calculating a big unit cell Sr-Bi-Ta-O ,including 223 atoms with space group P1, with wien2k V07.3 on Unix.

There are two problems during the calculation:
1  when setting "automatically RMT" in StructGenTM, the coordinates of the last 38 atoms lost. Only x=0,y=0,z=0 are left. The first 185 atoms did not change.

2 So, I set RMTs for each atoms manually.(I got the RMT from orinally SBT structure and no errors during "nn" then I got a problem in "dstart".
An error message in doing "dsart" as follows:

>>>>>>>>>>>>>

forrtl: severe (24): end-of-file during read, unit 81, file /panfs/hpc/home/dongsu/SBT3/SBT3.rsp
Image              PC                Routine            Line        Source            
dstart             000000000047518E  Unknown               Unknown  Unknown
dstart             0000000000473672  Unknown               Unknown  Unknown
dstart             000000000044CD5C  Unknown               Unknown  Unknown
dstart             0000000000426406  Unknown               Unknown  Unknown
dstart             0000000000426067  Unknown               Unknown  Unknown
dstart             000000000043365A  Unknown               Unknown  Unknown
dstart             000000000040DA37  Unknown               Unknown  Unknown
dstart             000000000040CB67  Unknown               Unknown  Unknown
dstart             0000000000402F6A  Unknown               Unknown  Unknown
libc.so.6          0000003E8401C3FB  Unknown               Unknown  Unknown
dstart             0000000000402EAA  Unknown               Unknown  Unknown
0.036u 0.016s 0:00.07 57.1%        0+0k 0+0io 0pf+0w
error: command   /home/dongsu/wien2k/dstart dstart.def   failed
>>>>>>>>>>>>>>>>>>>>>

Does the second problem related with the first one? I noticed there were same problems reported as same as the the second one here, but I do not find any answers. I think the situations suggested by Prof. Marks((wrong spacegroup, symmetry, overlapping RMT's)is not the reason for my case.


Any suggestion are welcome!

Thanks in advance

引用回帖:
a) I suggest you "learn" to master WIEN2k on smaller problems first.

b) Using WIEN2k_7.3 for such big systems is like competing in a
Formula-1 race with an old VW-beetle.
Most likely for 223 atoms the old version i) will not (or very slowly)
converge the scf-cycle ii) does not have iterative diagonalization, thus
is 5 times slower; iii) does not have a good MPI-parallel version, thus
you will run out of memory .....
Without these improvements I doubt that you will be successful.

c) Your dstart problem comes because you do not have a correct case.inst
file when running lstart, thus you are missing some atomic densities.

instgen_lapw
x lstart
x dstart (-c)

251楼2009-08-03 21:28:42
已阅   回复此楼   关注TA 给TA发消息 送TA红花 TA的回帖

wuli8

荣誉版主 (知名作家)

★ ★ ★
wuchenwf(金币+3,VIP+0):谢谢 8-21 20:05
引用回帖:
I have a question about the structure optimization using WIEN2k. I want
to optimize a crystal structure, say, tetragonal ZrO2,
which has three structural variables, the two lattice constants a, c,  
and an internal variable d_z.  WIEN2k provides the functions of
(1) optimize volume with fixed c/a ratio
(2) Optimize c/a ratio with fixed volume
(3) optimize internal variables with fixed lattice constant,
I guess taking different order of these optimization procedures would
lead to different results. Ideally I guess one should repeat these three
procedures
for several times until convergence is reached.
My questions are : are  there any empirical schemes to obtain the
optimized structure more efficiently ? Is the self-consistency really
necessary?
If not,  which order should one take to obtain the most reliable results?

Thank you very much in advance!

引用回帖:
In the latest option there is a possibility to generate struct files for
c and a variation simultaneously.

edit optimize.job (and uncomment/adapt the "min_lapw line", comment the
"run_lapw" line.)

This way you simultaneously optimize the internal parameters for each
pair of a and c.

PS: I do this in 2 steps, first with a rather small RKmax+ k-mesh; then
(using the "preoptimized" structures with a better RKmax and k-mesh).
But this requires some experience and "feeling" for proper parameters.

252楼2009-08-04 15:41:05
已阅   回复此楼   关注TA 给TA发消息 送TA红花 TA的回帖

wuli8

荣誉版主 (知名作家)

★ ★ ★
wuchenwf(金币+3,VIP+0):谢谢 9-6 21:22
引用回帖:
I have a strange quenstion. In files case.outputtup and case.qtlup the fermi energy is 0.40228, but in fiele case.scf the fermi energy is 0.52304.The dos in ev uses the fermi energy in case.qtlup,but the dos in Ry uses the fermi energy in case.scf. I can't find the answer,I would appreciate your suggestions.
Thank you for your time and best wishes

引用回帖:
EF in case.qtlup and case.scf2up must be the same (they are written at
the same time). If you have a self-consistent calculation and EF in
case.scf and case.scf2up (or qtlup) is so different, there might be some
inconsistency. Have made some changes to eg. k-mesh, positions in
case.struct, RKmax, ... ??

If you have in insulator, it can happen that EF is at the bottom of the
conduction band instead of the top of the valence band. This could
happen when you change the k-mesh between scf and DOS calculation. In
such cases correct EF manually in case.qtlup/dn. But make that the
current eigenvalues/qtls belong to the scf-potential and not some
strange mixture.

Since it looks as if you have made some mistake, I recommend to use
"restore_lapw"; and for security runsp_lapw to check that you have the
"correct" case. Then do the qtls/DOS again.

PS: The DOS in Ry does NOT use any EF, it just uses the plain energies
as calculated.

253楼2009-08-04 15:52:44
已阅   回复此楼   关注TA 给TA发消息 送TA红花 TA的回帖

wuli8

荣誉版主 (知名作家)

…………

优秀版主优秀版主

★ ★
qasd(金币+2,VIP+0):xiexie~ 8-12 15:02
> I've been changing the kmesh (100, 300, ... ) in my case, and i have been
> saving every SCF calculation in its own directory. Now i want to calculate
> DOS and band structure for some of this calculations. Should i only restore
> the calculation and run DOS for example? or i have to calculate SCF again? i
> found in this mail list that i must run one iteration of the scf again. Is
> this correct?

Yes. Restore one case (probably the most accurate one, with densest  
k-mesh), run one iteration (to re-create the necessary temporary  
files) and produce the DOS.
…………
254楼2009-08-04 15:54:12
已阅   回复此楼   关注TA 给TA发消息 送TA红花 TA的回帖

wuli8

荣誉版主 (知名作家)

…………

优秀版主优秀版主

★ ★ ★
qasd(金币+3,VIP+0):xiexie~ 8-12 15:02
Wien2k优化方法步骤



1:产生结构文件;
2:初始化结构文件; init_lapw
3:自洽计算力,看受力大小; run_lawp -fc 1
4:位置最优化;min_lapw -p   -没有NI选项则从头初始化
位置最优化初始文件; case.inM 同时产生case.hess
grep –e :LABEL case.outputM
where :LABEL can be any of
:ENE 能量(should decrease overall, but can go up for single steps),
:GRAD (should also go down, but could sometimes also go up for some time as
long as the energy still decreases),
:MIN (provides a condensed summary of the progress),
:WARN (may indicate a problem),
D (provides information about the step sizes and mode used).
产生case.struct 是最终位置文件; case.struct_org 是初始文件

case.inM 输入文件
The main control file is case.inM which has the format:
---------------- top of file: case.inM --------------------
PORT 2.0 (PORT tolf (a4,f5.2))
1.0 1.0 1.0 3.0 ( 1..3ELTA, eta)
1.0 1.0 1.0 6.0 ( 1..3=0 constraint)
------------------- bottom of file ------------------------
…………
255楼2009-08-09 13:27:44
已阅   回复此楼   关注TA 给TA发消息 送TA红花 TA的回帖

wuli8

荣誉版主 (知名作家)

…………

优秀版主优秀版主

★ ★
qasd(金币+2,VIP+0):xiexie~ 8-12 15:03
Cohesive energies
Problem: The cohesive energy of compounds with heavier elements is positive.
Analysis:
Lstart is a fully relativistic atomic code and thus provides a better (and thus lower) total energy than the LAPW calculations, which have only a scalar relativistic basis (even when SO is added a posteriori).
Fix:
Starting for second-row elements (this depends a little on the required accuracy) you must calculate the atomic energy not with LSTART, but with LAPW. Create a FCC box with lattice constants of about 30 bohr and your atom at (0,0,0). Use identical RMT, RKMAX, but only 1 k-point and spinpolarization (for non-closed shell atoms).
Some atoms (with partly occupied orbitals or in particular transition metal atoms, where the occupation flips between a 4s and 3d states) may be difficult to converge. Use a broadening method (e.g. TEMP 0.005) to get equal partial occupations and thus a stable solution.

WIEN2k-FAQ: Explanations on EFGs (EFG switch in case.in2)

Problem: The switch EFG in case.in2 produces an output, which can be used to analyse the different contributions to the EFG. However, it is not documented and not easy to understand.




WIEN2k-FAQ: DOS is calculated only up to a certain (low) energy

For some cases, the standard inputs provide a DOS only for energies close to EF, but not for higher energies, even when you specify a large E-range in case.int. The reason for that is, that the DOS is truncated at the lowest energy of the last fully available band in order to avoid plotting of an incomplete DOS. The solution is:
1. Edit case.in1 and increase the energy range: Increase E-max from 1.5 to a larger value (e.g. 2.5 or more).
2. Rerun "x lapw1" (lapw1c) and "x lapw2 -qtl" (lapw2c). This produces a case.qtl file with more bands.
3. Rerun tetra.


WIEN2k-FAQ: The SCF cycle fails after a few iterations

In cases with larger unit cells and various atoms with more or less localized electronic states it can happen, that the scf cycle fails in the second (or after a few more) iteration. Possible error messages include:
1. QTL-B value .gt. XXX in LAPW2
2. Could not find E-TOP/E-Bottom in LAPW1
Usually in such cases the mixing factor in MIXER was too large and too large charge fluctuations occured (You may see this using 'grep IS case.scf' or 'grep :NTOxx case.scf'). In such a case
1. remove the broyden and the scf files (rm *.broy* case.scf)
2. generate a new starting density (x dstart (-c/-up/-dn))
3. reduce the mixing parameter from 0.4 to e.g. 0.1 in case.inm (sometimes even 0.01 and/or a change to PRATT-mixing for some iterations may be necessary. Note: final convergence should always be reached using BROYD-mixing)
4. and restart the scf cycle (run_lapw or runsp_lapw).

Another possibility is that EF got quite large (usually this happens for heavy elements (actinides); check using grep :FER case.scf). Then the default E-parameters (0.30 Ry) in case.in1 are no longer a good choice because some LO-energies could be in the same range, which results in ghostbands.
Check in case.scf1 whether or not a "searched" energy and a fixed one got too close like:
OVERALL ENERGY PARAMETER IS 0.3000
E( 1)= 0.3000
E( 1)= 0.2875 E(BOTTOM)= 0.395 E(TOP)= 0.180
In such cases increase the default 0.30 to something close to EF, or fix the energy parameters without search (case.in1).


WIEN2k-FAQ: Charged cells

"Charged" cells will most likely require the construction of supercells, (see the faq on creating supercells) and this hole discussion targets charged impurities, vacancies,....
• Setup your supercell, put impurities, vacancies,.. (all with neutral atoms!)
• Run a standard initialization (init_lapw) with NEUTRAL atoms. Don't fiddle around with case.inst (positively charged atoms may work (and one can neglect the warnings "NUMBER OF ELECTRONS NE IZ ", but most negative ions are unstable in DFT and will not work.
• run_lapw (again for neutral atoms !) . Save the results using "save_lapw case_neutral"
• Edit case.in2: In the second line you see the number of electrons NE. Add or remove an electron to get the desired charged state.
• Edit case.inm: The first line must read:
• BROYD 1.0 YES (when you added an electron at step 4 or
• BROYD -1.0 YES (when you removed an electron at step 4
The position of "YES" is important!!! When reading characters in Fortran one must use a fixed format (or put characters into quotes).
• run_lapw
• I NEVER run init_lapw again!!! Usually init_lapw should be run only ONCE in a directory, because any changes which would require rerunning init_lapw (symmetry changes,....) should be done in a fresh "case"


WIEN2k-FAQ: Construction of supercells

For most (simple) supercells you can start with the regular case.struct file and use "supercell" to generate the supercell-struct file.
However, when you construct supercells, it is usually NOT possible just to double the cells and leave all atoms at their ideal and equivalent positions. This would lead to large multiplicities (e.g. in big supercells even more than 48 atoms could be "equivalent" and of course there is NO SPACEGROUP corresponding to this type of cell, since they all can be reduced by translation symmetry.
So during setup, you have at lest to:
• displace (at least one) atoms, or
• change one of the atoms to a different type (usually you do supercells for impurities,... so put the impurity into the cell), or
• set at least for one atom-name a special label (A label means an name like "Cr1", "Cr2" or "O 4", where in the 3rd position is a number. This indicates to WIEN2k that these atoms should be non-equivalent.).
Then run init_lapw
• nn and sgroup determine which atoms are still equivalent (if nn does not agree with sgroup in the first place, you may have to "label" non-equivalent atoms (see above). If you now rerun nn, you may get another (better) list of non-equivalent positions.
• symmetry: determines proper symmetry operations and rot.matrices,...
• Check if your case.inst file is still valid (when the number of non-equivalent atoms has changed, probably not). Generate a proper case.inst file (either using "instgen_lapw" or "Structgen of W2web" and rerun init_lapw.
Note, that WIEN always preserves symmetry. So when you want to allow certain relaxations around an impurity, it might be necessary to displace some atoms by hand to break the high symmetry and allow such relaxations.


WIEN2k-FAQ: Positive Fermi energy: What does it mean ?

Eigenvalues, core states, linearization energies, the Fermi energy,... are given in Rydberg units in wien2k, and are relative to a zero-point that is defined as the average of the potential in the interstitial region. This is an arbitrary choice (one half of this average, or 2.6128 times this average would have been good as well). Therefore, it might happen that for some compounds (solids) your Fermi energy (:FER) is positive, while for others (surfaces or molecules with lots of vacuum) it is negative. This has no physical meaning, and it is also not an indication of a possible error, it is just due to the choice of the zero-point.
Why is there a need to make such a choice? For a free atom, the choice of zero is arbitrary as well, but if one makes the usual convention that the potential at infinity is zero, then negative and positive energies indicate bound and unbound states, respectively. This is intuitively appealing. But for solids, there is nothing special about infinity: the solid is everywhere, also at infinity. Therefore, another convention has to be made, like the one explained above.
Please note, the TOTAL-Energy does NOT depend on this choice!!!)


--------------------------------------------------------------------------------

Cohesive energies
Problem: The cohesive energy of compounds with heavier elements is positive.
Analysis:
Lstart is a fully relativistic atomic code and thus provides a better (and thus lower) total energy than the LAPW calculations, which have only a scalar relativistic basis (even when SO is added a posteriori).
Fix:
Starting for second-row elements (this depends a little on the required accuracy) you must calculate the atomic energy not with LSTART, but with LAPW. Create a FCC box with lattice constants of about 30 bohr and your atom at (0,0,0). Use identical RMT, RKMAX, but only 1 k-point and spinpolarization (for non-closed shell atoms).
Some atoms (with partly occupied orbitals or in particular transition metal atoms, where the occupation flips between a 4s and 3d states) may be difficult to converge. Use a broadening method (e.g. TEMP 0.005) to get equal partial occupations and thus a stable solution.

WIEN2k-FAQ: Explanations on EFGs (EFG switch in case.in2)

Problem: The switch EFG in case.in2 produces an output, which can be used to analyse the different contributions to the EFG. However, it is not documented and not easy to understand.


WIEN2k-FAQ: Setup of antiferromagnetic calculations?

Setup of antiferromagnetic calculations requires some tricks which will be described below:
1. You need to construct a unit cell which allows for the desired AF ordering. E.g. for bcc Cr you have to put "P" lattice and 2 NON-equivalent atoms at (0,0,0) and (0.5,0.5,0.5). In order to make nn working properly, you should also specify different labels in the "name(3:10)"-field for the two AF-atoms (Eg. "Cr1" and "Cr2".
2. Run init_lapw. nn and/or sgroup determines equivalent atoms. Accept eventually the new struct_nn file (You may have to use the same procedure as described in faq:supercells).
3. Edit case.inst and flip the spin of the second AF atom. This means you must invert the spin-up and dn occupation of this atom. Atoms which carry no spin (e.g. an O between two AF metal atoms) should be made non-spinpolarized by setting equal numbers of up and dn-electrons.
For AFM NiO case.inst looks like:
4. Ni
5. Ar 3 5
6. 3, 2,2.0 N
7. 3, 2,2.0 N
8. 3,-3,3.0 N
9. 3,-3,1.0 N
10. 4,-1,1.0 N
11. 4,-1,1.0 N
12. Ni
13. Ar 3 5
14. 3, 2,2.0 N
15. 3, 2,2.0 N
16. 3,-3,1.0 N <=== spin flipped
17. 3,-3,3.0 N <=== spin flipped
18. 4,-1,1.0 N
19. 4,-1,1.0 N
20. O
21. He 3 5
22. 2,-1,1.0 N
23. 2,-1,1.0 N
24. 2, 1,1.0 N
25. 2, 1,1.0 N
26. 2,-2,1.0 N <=== equal occup for up/dn
27. 2,-2,1.0 N <=== equal occup for up/dn
28. **** End of Input
29. **** End of Input
30. Continue with init_lapw (rerunning lstart)
31. You may try to select "AFM-calculations", generate "case.inclmcopy" and use "runafm_lapw". For simplest use of "afminput" you should provide the nonmagnetic (or ferromagnetic) supergroup in "case.struct_supergroup". Please read the usersguide for more details. (help_lapw and search for AFM).
Since these programs are quite new and little tested, I recommend to check the final results of "runafm_lapw" by
32. "runsp_lapw". If the charge distance (grep IS case.scf) remains small and the magnetic moments do not change, runafm_lapw was successful, otherwise continue with runsp_lapw until convergence.


WIEN2k-FAQ: DOS is calculated only up to a certain (low) energy

For some cases, the standard inputs provide a DOS only for energies close to EF, but not for higher energies, even when you specify a large E-range in case.int. The reason for that is, that the DOS is truncated at the lowest energy of the last fully available band in order to avoid plotting of an incomplete DOS. The solution is:
1. Edit case.in1 and increase the energy range: Increase E-max from 1.5 to a larger value (e.g. 2.5 or more).
2. Rerun "x lapw1" (lapw1c) and "x lapw2 -qtl" (lapw2c). This produces a case.qtl file with more bands.
3. Rerun tetra.


WIEN2k-FAQ: The SCF cycle fails after a few iterations

In cases with larger unit cells and various atoms with more or less localized electronic states it can happen, that the scf cycle fails in the second (or after a few more) iteration. Possible error messages include:
1. QTL-B value .gt. XXX in LAPW2
2. Could not find E-TOP/E-Bottom in LAPW1
Usually in such cases the mixing factor in MIXER was too large and too large charge fluctuations occured (You may see this using 'grep IS case.scf' or 'grep :NTOxx case.scf'). In such a case
1. remove the broyden and the scf files (rm *.broy* case.scf)
2. generate a new starting density (x dstart (-c/-up/-dn))
3. reduce the mixing parameter from 0.4 to e.g. 0.1 in case.inm (sometimes even 0.01 and/or a change to PRATT-mixing for some iterations may be necessary. Note: final convergence should always be reached using BROYD-mixing)
4. and restart the scf cycle (run_lapw or runsp_lapw).

Another possibility is that EF got quite large (usually this happens for heavy elements (actinides); check using grep :FER case.scf). Then the default E-parameters (0.30 Ry) in case.in1 are no longer a good choice because some LO-energies could be in the same range, which results in ghostbands.
Check in case.scf1 whether or not a "searched" energy and a fixed one got too close like:
OVERALL ENERGY PARAMETER IS 0.3000
E( 1)= 0.3000
E( 1)= 0.2875 E(BOTTOM)= 0.395 E(TOP)= 0.180
In such cases increase the default 0.30 to something close to EF, or fix the energy parameters without search (case.in1).


WIEN2k-FAQ: Charged cells

"Charged" cells will most likely require the construction of supercells, (see the faq on creating supercells) and this hole discussion targets charged impurities, vacancies,....
• Setup your supercell, put impurities, vacancies,.. (all with neutral atoms!)
• Run a standard initialization (init_lapw) with NEUTRAL atoms. Don't fiddle around with case.inst (positively charged atoms may work (and one can neglect the warnings "NUMBER OF ELECTRONS NE IZ ", but most negative ions are unstable in DFT and will not work.
• run_lapw (again for neutral atoms !) . Save the results using "save_lapw case_neutral"
• Edit case.in2: In the second line you see the number of electrons NE. Add or remove an electron to get the desired charged state.
• Edit case.inm: The first line must read:
• BROYD 1.0 YES (when you added an electron at step 4 or
• BROYD -1.0 YES (when you removed an electron at step 4
The position of "YES" is important!!! When reading characters in Fortran one must use a fixed format (or put characters into quotes).
• run_lapw
• I NEVER run init_lapw again!!! Usually init_lapw should be run only ONCE in a directory, because any changes which would require rerunning init_lapw (symmetry changes,....) should be done in a fresh "case"


WIEN2k-FAQ: Construction of supercells

For most (simple) supercells you can start with the regular case.struct file and use "supercell" to generate the supercell-struct file.
However, when you construct supercells, it is usually NOT possible just to double the cells and leave all atoms at their ideal and equivalent positions. This would lead to large multiplicities (e.g. in big supercells even more than 48 atoms could be "equivalent" and of course there is NO SPACEGROUP corresponding to this type of cell, since they all can be reduced by translation symmetry.
So during setup, you have at lest to:
• displace (at least one) atoms, or
• change one of the atoms to a different type (usually you do supercells for impurities,... so put the impurity into the cell), or
• set at least for one atom-name a special label (A label means an name like "Cr1", "Cr2" or "O 4", where in the 3rd position is a number. This indicates to WIEN2k that these atoms should be non-equivalent.).
Then run init_lapw
• nn and sgroup determine which atoms are still equivalent (if nn does not agree with sgroup in the first place, you may have to "label" non-equivalent atoms (see above). If you now rerun nn, you may get another (better) list of non-equivalent positions.
• symmetry: determines proper symmetry operations and rot.matrices,...
• Check if your case.inst file is still valid (when the number of non-equivalent atoms has changed, probably not). Generate a proper case.inst file (either using "instgen_lapw" or "Structgen of W2web" and rerun init_lapw.
Note, that WIEN always preserves symmetry. So when you want to allow certain relaxations around an impurity, it might be necessary to displace some atoms by hand to break the high symmetry and allow such relaxations.


WIEN2k-FAQ: Positive Fermi energy: What does it mean ?

Eigenvalues, core states, linearization energies, the Fermi energy,... are given in Rydberg units in wien2k, and are relative to a zero-point that is defined as the average of the potential in the interstitial region. This is an arbitrary choice (one half of this average, or 2.6128 times this average would have been good as well). Therefore, it might happen that for some compounds (solids) your Fermi energy (:FER) is positive, while for others (surfaces or molecules with lots of vacuum) it is negative. This has no physical meaning, and it is also not an indication of a possible error, it is just due to the choice of the zero-point.
Why is there a need to make such a choice? For a free atom, the choice of zero is arbitrary as well, but if one makes the usual convention that the potential at infinity is zero, then negative and positive energies indicate bound and unbound states, respectively. This is intuitively appealing. But for solids, there is nothing special about infinity: the solid is everywhere, also at infinity. Therefore, another convention has to be made, like the one explained above.
Please note, the TOTAL-Energy does NOT depend on this choice!!!)

[ Last edited by wuli8 on 2009-8-9 at 13:30 ]
…………
256楼2009-08-09 13:28:39
已阅   回复此楼   关注TA 给TA发消息 送TA红花 TA的回帖

wuli8

荣誉版主 (知名作家)

…………

优秀版主优秀版主

★ ★ ★
qasd(金币+3,VIP+0):xiexie~ 8-12 15:03
WIEN2k关于k网格设置的一些技巧




1. 应当使用多少个k网格?
2. 是否加入时间反演对称操作?
3. 是否移动k网格?
译自:WIEN2k-FAQ
作者:Peter Blaha
1. 应当使用多少个k网格?
很难一般地回答,只能给出一般建议。注意:一定要检查k网格,首先用较粗糙的网格计算,接下来用精细的网格计算。通过比较两次的结果,决定选用较粗糙的网格,或是继续进行更精细网格的计算,直到达到收敛。金属体系需要精细的网格,绝缘体使用很少的k点通常就可以。小单胞需要精细格点,大单胞很可能不需要。因此:单位晶胞内原子数很多(比如40-60个)的绝缘体,可能仅需要一个(移动后的)k点。另一方面,面心立方的铝可能需要上万个k点以获得好的DOS。对于孤立原子或分子的超晶胞,仅需要在Gamma点计算。对于表面(层面)的超晶胞计算,仅需要(垂直于表面)z方向上有1个k点。甚至可以增加晶格参数c,这样即使对精细格点,沿z方向上也只产生一个k点(产生k点后,不要忘记再把c改回)。
2. 当体系没有出现时间反演对称操作时,是否加入?
大多数情况下的回答是“是”,只有包含自旋-轨道耦合的自旋极化(磁性)计算除外。这时,时间反演对称性被破坏(+k和-k的本征值可能不同),因此决不能加入时间反演对称性。
3. 是否移动k网格?(只对某些格子类型有效)
“移动”k网格意味着把所有产生的k点增加(x,x,x),把那些位于高对称点(或线)上的k点移动到权重更大的一般点上。通过这种方法(也即众所周知的“特殊k点方法”)可以产生等密度的,k点较少的网格。通常建议移动。只有一点注意:当对半导体的带隙感兴趣时(通常位于Gamma,X,或BZ边界上的其它点),使用移动的网格将不会得到这些高对称性的点,因此得到的带隙和预期结果相比或大或小。这个问题的解决:用移动的网格做SCF循环,但对DOS计算,改用精细的未移动网格。
关于k空间布点的问题,建议WIEN2K用户参阅以下文献Phys.Rev.B 49,16223 (1994)
…………
257楼2009-08-09 13:28:54
已阅   回复此楼   关注TA 给TA发消息 送TA红花 TA的回帖

yufeng1117

新虫 (初入文坛)

运行错误


小木虫(金币+0.5):给个红包,谢谢回帖交流
大家好,我们的wien2k装好运行时,出现这样的问题  argvl:subscript out of range,  请教高手,谢啦
258楼2009-09-02 20:25:14
已阅   回复此楼   关注TA 给TA发消息 送TA红花 TA的回帖

wuli8

荣誉版主 (知名作家)

…………

优秀版主优秀版主

★ ★
wuchenwf(金币+2,VIP+0):谢谢 9-6 21:23
http://www.wien2k.at/reg_user/mailing_list/搜一下下" argvl:subscript out of range"
…………
259楼2009-09-02 20:59:59
已阅   回复此楼   关注TA 给TA发消息 送TA红花 TA的回帖

yufeng1117

新虫 (初入文坛)

argvl问题


小木虫(金币+0.5):给个红包,谢谢回帖交流
我搜索了mailing list ,为什么只出现 一下两行文字:You have searched for: argvl:subscript out of range
in the WIEN2k mailing list . Please follow the links below:
然后就没下文了
谢了
260楼2009-09-03 19:03:42
已阅   回复此楼   关注TA 给TA发消息 送TA红花 TA的回帖
相关版块跳转 我要订阅楼主 wuli8 的主题更新
普通表情 高级回复 (可上传附件)
信息提示
请填处理意见