Search found 9 matches
- Thu Jan 10, 2019 9:36 am
- Forum: Running the code
- Topic: Possibility to calculate mobility for 2d materials using EPW
- Replies: 7
- Views: 8154
Re: Possibility to calculate mobility for 2d materials using
Dear Samuel, Although I calculated the mobility of 2d materials, but the mobility in the z axis was very large, which is not true for the real situation. Is it okay if I just pick up the mobility in x-axis and y-axis to analyze the materials and ignore the z-axis' mobility? Or I change the codes in ...
- Thu Dec 06, 2018 9:31 am
- Forum: Running the code
- Topic: Possibility to calculate mobility for 2d materials using EPW
- Replies: 7
- Views: 8154
Re: Possibility to calculate mobility for 2d materials using
Dear Samuel,
Thank you very much for your ideas.
I have solved the problem and got the mobility successfully with defaulting the mp_mesh_k.
Best wishes,
CHOU
Thank you very much for your ideas.
I have solved the problem and got the mobility successfully with defaulting the mp_mesh_k.
Best wishes,
CHOU
- Wed Nov 21, 2018 8:55 am
- Forum: Running the code
- Topic: Possibility to calculate mobility for 2d materials using EPW
- Replies: 7
- Views: 8154
Re: Possibility to calculate mobility for 2d materials using
Hello Samuel? Thank you very much for your reply. Here is my input file. scf.in &CONTROL calculation='scf' restart_mode='from_scratch' outdir='./' pseudo_dir='/home/k0116/k011622/pseudo' prefix= 'MoO3' etot_conv_thr=1.0D-09 forc_conv_thr=1.0D-09 wf_collect=.true. tstress=.true. tprnfor=.true ...
- Thu Nov 15, 2018 6:28 am
- Forum: Running the code
- Topic: Possibility to calculate mobility for 2d materials using EPW
- Replies: 7
- Views: 8154
Possibility to calculate mobility for 2d materials using EPW
Dear all, I have been trying to use EPW to calculate mobility for 2d MoO3 for a long time. I saw that EPW could not calculate mobility for 2d materials and if wanted to do it, had to treat it as 3d, put more k points along the vacuum direction. So I used 8*8*2 mesh. But it always failed in the ...
- Wed Oct 10, 2018 2:27 am
- Forum: General discussion
- Topic: About mobility calculation using EPW
- Replies: 1
- Views: 5828
About mobility calculation using EPW
Dear developers, I am using EPW to calculate the mobility of 2D MoO3. But it failed with the strange output. I set efermi_read and fermi level to be -4.7328. But the results showed " Temperature 100.000 K Valence band maximum = 4.051599 eV Conduction band minimum = ********** eV Warning: too many ...
- Tue Aug 14, 2018 4:02 am
- Forum: Running the code
- Topic: About error of "too many g-vector"
- Replies: 6
- Views: 6923
Re: About error of "too many g-vector"
Dear Samuel,
Thank you for your advice.
Best wishes,
CHOU
Thank you for your advice.
Best wishes,
CHOU
- Sat Aug 04, 2018 2:05 am
- Forum: Running the code
- Topic: About error of "too many g-vector"
- Replies: 6
- Views: 6923
Re: About error of "too many g-vector"
Dear Samuel, Sorry for my late reply. I removed the FFT setting from scf and nscf. It worked now. The reason I set FFT mesh by myself is because "note: 2 additional sym.ops. were found but ignored?their fractional translations are incommensurate with FFT grid) " appeared in my output file. I want to ...
- Mon Jul 30, 2018 1:21 am
- Forum: Running the code
- Topic: About error of "too many g-vector"
- Replies: 6
- Views: 6923
Re: About error of "too many g-vector"
Dear Samuel, Thank you for your reply. I used the same ecut for phonon calculation and for the scf and nscf in the epw calculation. But the error happened. For example, I set 90 Ry for phonon calculation, and 90 Ry for epw calculation, but it failed. I changed to 80 Ry for epw while keeping ecut to ...
- Thu Jul 26, 2018 2:05 am
- Forum: Running the code
- Topic: About error of "too many g-vector"
- Replies: 6
- Views: 6923
About error of "too many g-vector"
Dear developers, I want to calculate the electron self energy. However, it always appeared error of too many g-vector. I used a smaller energy cutoff and it worked. However, I wonder if there is any other method to fix up the problem, since I do not want to sacrifice the precision. Here are my input ...