Closed svandenhaute closed 4 months ago
ELECTRONIC_STRUCTURE_METHOD full_potential_lapwlo
of course had to be
ELECTRONIC_STRUCTURE_METHOD pseudopotential
Changing that fixed the issue.
On that note: how would I perform LAPW calculations, i.e. all-electron, without pseudopotentials?
@svandenhaute you need to provide json files of LAPW species. That's the only difference.
Oh that's probably a sign that the potential you took are pseudo-potentials not all-electron one.
Ah, OK! Do those other settings look reasonable or are there particular things I need to benchmark? Gamma point only calculation, about 150 atoms, insulator, and it's important that the energies and forces are well-converged.
In terms of OMP/MPI parallelization, what does SIRIUS typically prefer?
@svandenhaute I porpose to change DFT section as following
&PW_DFT
&CONTROL
GEN_EVP_SOLVER_NAME lapack
PROCESSING_UNIT cpu
STD_EVP_SOLVER_NAME lapack
VERBOSITY 2
&END CONTROL
&MIXER
BETA 0.95
MAX_HISTORY 8
TYPE anderson
&END MIXER
&PARAMETERS
DENSITY_TOL 1e-7
ELECTRONIC_STRUCTURE_METHOD full_potential_lapwlo
ENERGY_TOL 1e-7
MOLECULE true
NGRIDK 1 1 1
NUM_DFT_ITER 20
PW_CUTOFF 20.00
GK_CUTOFF 8
SMEARING_WIDTH 0.05
USE_SYMMETRY true
&END PARAMETERS
&END PW_DFT
You might need to change mixing parameter beta in case of poor convergence. Paramaters PW_CUTOFF and GK_CUTOFF control density/potential and wave-functions correspondingly. Units are inverse atomic units, not energy.
@svandenhaute I forgot to mention: with single k-point band parallelisation is the only opption. In control section you need to specify mpi_grid_dims variable (https://manual.cp2k.org/trunk/CP2K_INPUT/FORCE_EVAL/PW_DFT/CONTROL.html#CP2K_INPUT.FORCE_EVAL.PW_DFT.CONTROL.MPI_GRID_DIMS). It's a pair of integers that controls how MPI ranks will be split. For the beginning, you can set it to 1, N (N is the total number of MPI ranks in your calculation).
I'm trying to use SIRIUS with CP2K. I'm using the 2024.1 generic docker image with the following input file:
The
.json
files are bound into the/mnt
folder in the container upon execution, and they were taken from the SIRIUS species repository so they should be good. Somehow, I get a bunch of the following exceptions without any additional info:What's going on?