The actual CMEMS Mediterranean sea configuration is running with NEMO v3.6 and we are now testing the 4.2_RC. Simulations with closed boundaries are running but when we open the Atlantic boundaries several problems are coming. We appreciate any comment that might help us.
Here is a picture of the actual CMEMS Medsea configuration and the boundary options defined in the 3.6 version:
- We have a problem with domain decomposition. We tried several options for
jpnjand the cases with
jpni>1gave this error:
Abort(738313486) on node 71 (rank 71 in comm 0): Fatal error in PMPI_Recv: Message truncated, error stack: PMPI_Recv(173): MPI_Recv(buf=0x48cbb0d0, count=655, MPI_DOUBLE_PRECISION, src=69, tag=4, comm=0x84000006, status=0x1) failed (unknown)(): Message truncated
ln_bdy=.true. / OK
ln_bdy=.false. / OK
Fatal error in PMPI_Recv: Message truncated, error stack
We tried to define the boundary with segments (in case the coordinate.bdy.nc was wrong) but the same error appears when the northern and/or southern Atlantic boundaries are opened. There is no problem with the western boundary.
If it can help, this error does not appear with the trunk revision 14657.
Would you have suggestions for the choice of the domain decomposition or any idea about this error?
- If we follow the run using the decomposition with
jpni=1, the model blow-up after a few times step. The model blows up only with the
dyn3d. The problem is not visible for
'orlanski'. It seems an MPI issue at point 1 and jpj-1 (see picture with 48 processors).
We are using the same coordinates.bdy and
nambdy_dta files as for the CMEMS Medsea configuration with NEMO 3.6, could it be a problem?
- Another point is about the Dardanelles strait. Could someone explain to us why the Orlanski option cannot be used anymore when boundaries are on the interior of the computational domain ( see the message in
' Orlanski is not safe when the open boundaries are on the interior of the computational domain’)?