You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
slurm scheduler plugin parses two additional key values: num_mpiprocs & num_machines from Slurm's squeue response. The later is number of nodes in use, and the former is number of cpus.
FirecREST server however doesn't return the raw response of squeue to use, but parse it themselves and return a modified raw response, in which they don't specify num_mpiprocs.
However, I'm not aware of any crucial usecase in aiida-core for num_mpiprocs.
Therefore we just document here for future if needed as suggested by @agoscinski
The text was updated successfully, but these errors were encountered:
slurm
scheduler plugin parses two additional key values:num_mpiprocs
&num_machines
from Slurm'ssqueue
response. The later is number of nodes in use, and the former is number of cpus.FirecREST
server however doesn't return the raw response ofsqueue
to use, but parse it themselves and return a modified raw response, in which they don't specifynum_mpiprocs
.However, I'm not aware of any crucial usecase in
aiida-core
fornum_mpiprocs
.Therefore we just document here for future if needed as suggested by @agoscinski
The text was updated successfully, but these errors were encountered: