[MITgcm-support] MITgcm Parallel Computing

[Yong Liang]

Dear All,

I am trying to learn how to use parallel computing in MITgcm. I do tests on
the case "short_surf_wave". It works very well with one core on my desktop.
But when I use the following commands: "../../../tools/genmake2
-mods=../code  -mpi -of=../../../tools/build_options/linux_amd64_gfortran
&& make depend && make -j 4 && ln -s ../input/* " and "mpirun -np 4
./mitgcmuv", it gives me the following error information:

liang at liang-XPS-8500:~/TESTMITGCM/MITgcm/verification/short_surf_wave/build$
mpirun -np 4 ./mitgcmuv
[liang-XPS-8500:16831] *** An error occurred in MPI_Comm_rank
[liang-XPS-8500:16831] *** on communicator MPI_COMM_WORLD
[liang-XPS-8500:16831] *** MPI_ERR_COMM: invalid communicator
[liang-XPS-8500:16831] *** MPI_ERRORS_ARE_FATAL: your MPI job will now abort
--------------------------------------------------------------------------
mpirun has exited due to process rank 2 with PID 16833 on
node liang-XPS-8500 exiting improperly. There are two reasons this could
occur:

1. this process did not call "init" before exiting, but others in
the job did. This can cause a job to hang indefinitely while it waits
for all processes to call "init". By rule, if one process calls "init",
then ALL processes must call "init" prior to termination.

2. this process called "init", but exited without calling "finalize".
By rule, all processes that call "init" MUST call "finalize" prior to
exiting or it will be considered an "abnormal termination"

This may have caused other processes in the application to be
terminated by signals sent by mpirun (as reported here).
--------------------------------------------------------------------------
[liang-XPS-8500:16830] 3 more processes have sent help message
help-mpi-errors.txt / mpi_errors_are_fatal
[liang-XPS-8500:16830] Set MCA parameter "orte_base_help_aggregate" to 0 to
see all help / error messages

I did not edit any configuration files under the folder "short_surf_wave".
Does anyone have ideas how to solve this problem? Thanks.

Sincerely,
Yong Liang
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mitgcm.org/pipermail/mitgcm-support/attachments/20150512/c4afe963/attachment.htm>