Currently, the SLURM scheduler checks that num_cores_per_machine == num_cores_per_mpiproc * num_mpiprocs_per_machine. However, a user may like to use a number of cores less than the number available because of parallelization restrictions (e.g. in pw.x, if you are running a calculation with 11 kpoints on a 12-core node, it may be best to use 11 k-pools on 11 mpiprocs with 1 core per mpiproc for the best performance).
It would be better to check that num_cores_per_machine >= num_cores_per_mpiproc * num_mpiprocs_per_machine.
Currently, the SLURM scheduler checks that
num_cores_per_machine == num_cores_per_mpiproc * num_mpiprocs_per_machine
. However, a user may like to use a number of cores less than the number available because of parallelization restrictions (e.g. in pw.x, if you are running a calculation with 11 kpoints on a 12-core node, it may be best to use 11 k-pools on 11 mpiprocs with 1 core per mpiproc for the best performance).It would be better to check that
num_cores_per_machine >= num_cores_per_mpiproc * num_mpiprocs_per_machine
.