scf calculation is too slow #265
Replies: 3 comments 2 replies
-
|
Hi, " "some processors have no G-vectors for symmetrization" means that your number of cores are more your number of k points. How many nbands you have used in scf? Number of nbands must be complied with the number of bands used in wannier90 later. If everything is right, then you can try with mpirun/srun -n pw.x -npool -n option. Check if it might work |
Beta Was this translation helpful? Give feedback.
-
|
Hi Jenny and Anish, Thanks for your reply. There are 184 electrons and my cutoff is 75 Ry. %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% Here is my scf and ph input files &CONTROL / &SYSTEM / &ELECTRONS / &CELL K_POINTS {automatic} ATOMIC_SPECIES CELL_PARAMETERS (angstrom) ATOMIC_POSITIONS (crystal) phonons for HfTe5 |
Beta Was this translation helpful? Give feedback.
-
|
Hi Jenny, I am trying to compute Linewidth along a Band Path (following the same tutorial). I have the rta_ph_relaxation_times.json and path_ph_bandstructure.json. When I do tau_path.py rta_ph_relaxation_times.json and path_ph_bandstructure.json I get this complaint INPUT INPUT2 calcIndex, I dont see anything regarding calcIndex in the inputs. Did I miss something? Rijan |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi,
I am new user of Phoebe. I am running a HfTe5 (12 atoms) calculations and the scf calculation is too slow from the quantum espresso patch.
Is this expected or did I miss something?
On regular quantum espresso, the scf calculations takes about 2 min. But this is taking longer ~ 50 mins.
It also complained about "some processors have no G-vectors for symmetrization" after printing FFT dimension and RAM estimation (this was not present in the regular QE)
Can you please help?
Thanks
Rijan
Beta Was this translation helpful? Give feedback.
All reactions