mpirun: Error: sizex*sizey ne size0size0= 4 sizez= 1 sizey= 120

[RobbieTheK]

We're having an issue a researcher is having with mpiexec/mpirun running against TRISTAN-MP parallel electromagnetic 3D particle-in-cell code. I have never seen this an error like this: Error: sizex*sizey ne size0size0=4 sizez=1   sizey=120

Modules loaded are:

 1) IDL/8.4                                 10) oneapi/mkl/2024.0                  19) oneapi/dal/2024.0.0       
 2) oneapi/compiler-rt/2024.0.2             11) oneapi/intel_ippcp_intel64/2021.9  20) oneapi/compiler/2024.0.2  
 3) oneapi/hpctoolkit/compiler-rt/2024.0.2  12) oneapi/intel_ipp_intel64/2021.10   21) oneapi/ccl/2021.11.2      
 4) oneapi/hpctoolkit/hpctoolkit-2024.0.0   13) oneapi/ifort/2024.0.2              22) oneapi/advisor/2024.0     
 5) hdf5p-intel/1.14.3                      14) oneapi/dpl/2022.3                  23) oneapi/2024.0.0/2024.0.0  
 6) oneapi/tbb/2021.11                      15) oneapi/dpct/2024.0.0               
 7) oneapi/oclfpga/2024.0.0                 16) oneapi/dnnl/3.3.0                  
  oneapi/vtune/2024.0                     17) oneapi/dev-utilities/2024.0.0      
 9) oneapi/mpi/2021.11                      18) oneapi/debugger/2024.0.0          

mpirun -v -np 4 ./tristan-mp2d
[mpiexec@2402-node004] Launch arguments: /usr/bin/srun -N 1 -n 1 --ntasks-per-node 1 --external-launcher --nodelist 2402-node004 --input none /insomnia001/shared/apps/oneapi/mpi/2021.11/bin//hydra_bstrap_proxy --upstream-host 2402-node004 --upstream-port 36537 --pgid 0 --launcher slurm --launcher-number 1 --base-path /insomnia001/shared/apps/oneapi/mpi/2021.11/bin/ --tree-width 16 --tree-level 1 --time-left -1 --launch-type 0 --debug /insomnia001/shared/apps/oneapi/mpi/2021.11/bin//hydra_pmi_proxy --usize -1 --auto-cleanup 1 --abort-signal 9 
[proxy:0:0@2402-node004] pmi cmd from fd 9: cmd=init pmi_version=1 pmi_subversion=1
[proxy:0:0@2402-node004] PMI response: cmd=response_to_init pmi_version=1 pmi_subversion=1 rc=0
[proxy:0:0@2402-node004] pmi cmd from fd 9: cmd=get_maxes
[proxy:0:0@2402-node004] PMI response: cmd=maxes kvsname_max=256 keylen_max=64 vallen_max=4096
[proxy:0:0@2402-node004] pmi cmd from fd 9: cmd=get_appnum
[proxy:0:0@2402-node004] PMI response: cmd=appnum appnum=0
[proxy:0:0@2402-node004] pmi cmd from fd 9: cmd=get_my_kvsname
[proxy:0:0@2402-node004] PMI response: cmd=my_kvsname kvsname=kvs_1481562_0
[proxy:0:0@2402-node004] pmi cmd from fd 9: cmd=get kvsname=kvs_1481562_0 key=PMI_process_mapping
[proxy:0:0@2402-node004] PMI response: cmd=get_result rc=0 msg=success value=(vector,(0,1,4))
[proxy:0:0@2402-node004] pmi cmd from fd 6: cmd=init pmi_version=1 pmi_subversion=1
[proxy:0:0@2402-node004] PMI response: cmd=response_to_init pmi_version=1 pmi_subversion=1 rc=0
[proxy:0:0@2402-node004] pmi cmd from fd 6: cmd=get_maxes
[proxy:0:0@2402-node004] PMI response: cmd=maxes kvsname_max=256 keylen_max=64 vallen_max=4096
[proxy:0:0@2402-node004] pmi cmd from fd 6: cmd=get_appnum
[proxy:0:0@2402-node004] PMI response: cmd=appnum appnum=0
[proxy:0:0@2402-node004] pmi cmd from fd 6: cmd=get_my_kvsname
[proxy:0:0@2402-node004] PMI response: cmd=my_kvsname kvsname=kvs_1481562_0
[proxy:0:0@2402-node004] pmi cmd from fd 6: cmd=get kvsname=kvs_1481562_0 key=PMI_process_mapping
[proxy:0:0@2402-node004] PMI response: cmd=get_result rc=0 msg=success value=(vector,(0,1,4))
[proxy:0:0@2402-node004] pmi cmd from fd 4: cmd=init pmi_version=1 pmi_subversion=1
[proxy:0:0@2402-node004] PMI response: cmd=response_to_init pmi_version=1 pmi_subversion=1 rc=0
[proxy:0:0@2402-node004] pmi cmd from fd 5: cmd=init pmi_version=1 pmi_subversion=1
[proxy:0:0@2402-node004] PMI response: cmd=response_to_init pmi_version=1 pmi_subversion=1 rc=0
[proxy:0:0@2402-node004] pmi cmd from fd 4: cmd=get_maxes
[proxy:0:0@2402-node004] PMI response: cmd=maxes kvsname_max=256 keylen_max=64 vallen_max=4096
[proxy:0:0@2402-node004] pmi cmd from fd 5: cmd=get_maxes
[proxy:0:0@2402-node004] PMI response: cmd=maxes kvsname_max=256 keylen_max=64 vallen_max=4096
[proxy:0:0@2402-node004] pmi cmd from fd 4: cmd=get_appnum
[proxy:0:0@2402-node004] PMI response: cmd=appnum appnum=0
[proxy:0:0@2402-node004] pmi cmd from fd 5: cmd=get_appnum
[proxy:0:0@2402-node004] PMI response: cmd=appnum appnum=0
[proxy:0:0@2402-node004] pmi cmd from fd 4: cmd=get_my_kvsname
[proxy:0:0@2402-node004] PMI response: cmd=my_kvsname kvsname=kvs_1481562_0
[proxy:0:0@2402-node004] pmi cmd from fd 5: cmd=get_my_kvsname
[proxy:0:0@2402-node004] PMI response: cmd=my_kvsname kvsname=kvs_1481562_0
[proxy:0:0@2402-node004] pmi cmd from fd 4: cmd=get kvsname=kvs_1481562_0 key=PMI_process_mapping
[proxy:0:0@2402-node004] PMI response: cmd=get_result rc=0 msg=success value=(vector,(0,1,4))
[proxy:0:0@2402-node004] pmi cmd from fd 5: cmd=get kvsname=kvs_1481562_0 key=PMI_process_mapping
[proxy:0:0@2402-node004] PMI response: cmd=get_result rc=0 msg=success value=(vector,(0,1,4))
[proxy:0:0@2402-node004] pmi cmd from fd 9: cmd=barrier_in
[proxy:0:0@2402-node004] pmi cmd from fd 6: cmd=barrier_in
[proxy:0:0@2402-node004] pmi cmd from fd 5: cmd=barrier_in
[proxy:0:0@2402-node004] pmi cmd from fd 4: cmd=put kvsname=kvs_1481562_0 key=-bcast-1-0 value=2F6465762F73686D2F496E74656C5F4D50495F38444B474B6D
[proxy:0:0@2402-node004] PMI response: cmd=put_result rc=0 msg=success
[proxy:0:0@2402-node004] pmi cmd from fd 4: cmd=barrier_in
[proxy:0:0@2402-node004] PMI response: cmd=barrier_out
[proxy:0:0@2402-node004] PMI response: cmd=barrier_out
[proxy:0:0@2402-node004] PMI response: cmd=barrier_out
[proxy:0:0@2402-node004] PMI response: cmd=barrier_out
[proxy:0:0@2402-node004] pmi cmd from fd 5: cmd=get kvsname=kvs_1481562_0 key=-bcast-1-0
[proxy:0:0@2402-node004] PMI response: cmd=get_result rc=0 msg=success value=2F6465762F73686D2F496E74656C5F4D50495F38444B474B6D
[proxy:0:0@2402-node004] pmi cmd from fd 6: cmd=get kvsname=kvs_1481562_0 key=-bcast-1-0
[proxy:0:0@2402-node004] PMI response: cmd=get_result rc=0 msg=success value=2F6465762F73686D2F496E74656C5F4D50495F38444B474B6D
[proxy:0:0@2402-node004] pmi cmd from fd 9: cmd=get kvsname=kvs_1481562_0 key=-bcast-1-0
[proxy:0:0@2402-node004] PMI response: cmd=get_result rc=0 msg=success value=2F6465762F73686D2F496E74656C5F4D50495F38444B474B6D
[proxy:0:0@2402-node004] pmi cmd from fd 9: cmd=barrier_in
[proxy:0:0@2402-node004] pmi cmd from fd 4: cmd=put kvsname=kvs_1481562_0 key=bc-0 value=mpi#03A9EB010400000000000000000080FEFE694A0003D23FB80000000000000000$
[proxy:0:0@2402-node004] PMI response: cmd=put_result rc=0 msg=success
[proxy:0:0@2402-node004] pmi cmd from fd 4: cmd=barrier_in
[proxy:0:0@2402-node004] pmi cmd from fd 5: cmd=barrier_in
[proxy:0:0@2402-node004] pmi cmd from fd 6: cmd=barrier_in
[proxy:0:0@2402-node004] PMI response: cmd=barrier_out
[proxy:0:0@2402-node004] PMI response: cmd=barrier_out
[proxy:0:0@2402-node004] PMI response: cmd=barrier_out
[proxy:0:0@2402-node004] PMI response: cmd=barrier_out
[proxy:0:0@2402-node004] pmi cmd from fd 9: cmd=get kvsname=kvs_1481562_0 key=bc-0
[proxy:0:0@2402-node004] PMI response: cmd=get_result rc=0 msg=success value=mpi#03A9EB010400000000000000000080FEFE694A0003D23FB80000000000000000$
           0 :Error: sizex*sizey ne size0size0=           4 sizez=           1 
 sizey=         120

That error is no where to be found in these forums nor Google.

[RobbieTheK]

This is not an Intel error rather and error with the Tristan application that requires and input file with those dimensions.

However what does this error mean, 

if I add flag
-xCORE-AVX512

it says "ifx: command line warning #10121: overriding '-xCORE-AVX512' with '-xCORE-AVX512'"

[TobiasK]

@RobbieTheK 

that's exactly what the warning says, you have multiple -x options in your compile line, in your case you have at least two times -xCORE-AVX512 defined so it does not change anything.

ifx -xCORE-AVX2 -xCORE-AVX512

That would result in a different warning:
 

ifx: command line warning #10121: overriding '-xCORE-AVX2' with '-xCORE-AVX512