I updated the bathymetry of a coupling case. Before I updated the bathymetry, the model could run successfully. But now, it can’t run.
Firstly, I updated the bathymetry and the mask of ROMS grid file. Then, generated SWAN grid file, bathymetry file and wind files with new ROMS grid file.
When only 1 cpu was allocated for SWAN, ROMS exchanged data with SWAN before the first step. Then model crashed after fisrt step.
In log file:
STEP Day HH:MM:SS KINETIC_ENRG POTEN_ENRG TOTAL_ENRG NET_VOLUME
0 0 00:00:00 0.000000E+00 1.339995E+02 1.339995E+02 2.034991E+12
DEF_HIS - creating history file: Yrm/Output/Yrm_his_uvt2.nc
WRT_HIS - wrote history fields (Index=1,1) into time record = 0000001
DEF_AVG - creating average file: Yrm/Output/bohaih_avgwo5nbl.nc
rank 1 in job 1 c0212_32945 caused collective abort of all ranks
exit status of rank 1: killed by signal 9
In PRINT file , the bottom line is
+time 20061015.000500 , step 1; iteration 1; sweep 1
When more than 1 cpu were allocated for SWAN, the model crashed before the first step.
In log file:
WESTERN_WALL Wall boundary at Western edge.
rank 1 in job 1 c0212_51818 caused collective abort of all ranks
exit status of rank 1: killed by signal 9
In PRINT file , the bottom line is
COMPUTE NONSTAT 20061015.000000 300 SEC 20061113.240000
And ecs.err file :
MCT::m_ExchangeMaps::ExGSMapGSMap_:: MCTERROR, Grid Size mismatch
LocalMap Gsize = 36000 RemoteMap Gsize = 35460
MCT::m_ExchangeMaps::ExGSMapGSMap_: Map Grid Size mismatch error, stat =3
000.MCT(MPEU)::die.: from MCT::m_ExchangeMaps::ExGSMapGSMap_()
application called MPI_Abort(MPI_COMM_WORLD, 2) - process 0 MCT::m_ExchangeMaps::ExGSMapGSMap_:: MCTERROR, Grid Size mismatch
LocalMap Gsize = 35460 RemoteMap Gsize = 36000
MCT::m_ExchangeMaps::ExGSMapGSMap_: Map Grid Size mismatch error, stat =3
001.MCT(MPEU)::die.: from MCT::m_ExchangeMaps::ExGSMapGSMap_()
application called MPI_Abort(MPI_COMM_WORLD, 2) - process 1
The ROMS grid size is 200 by 180. And the SWAN grid has same size with ROMS grid. I down't know why the grid size mismatched.
Any suggestions?
PS:The ocean model can run without wave model.
Problem on coupling
Re: Problem on coupling
grid size mismatch.
looks like 36000-35460=540. are you giving the right grid size to swan (180*3=540).
-j
looks like 36000-35460=540. are you giving the right grid size to swan (180*3=540).
-j
Re: Problem on coupling
grid size mismatch.
looks like 36000-35460=540. are you giving the right grid size to swan (180*3=540).
-j
looks like 36000-35460=540. are you giving the right grid size to swan (180*3=540).
-j
Re: Problem on coupling
One possible explanation for this problem is that SWAN reduces his grid when it has full land mask on it. This allows it to gain a little in speed but creates a mismatch in grid size.
The solution to this problem is to set up the bathymetry to zero in the swan grid when there is land.
The solution to this problem is to set up the bathymetry to zero in the swan grid when there is land.
-
- Posts: 5
- Joined: Thu Jan 08, 2015 11:16 pm
- Location: Institute of Atmospheric Physics, Chinese Academy
Re: Problem on coupling
I got the same mistake when I do a coupled modelling IN WRF-ROMS-SWAN. and the reason lies in the setting of SWAN INPUT GRID in INPUT file.
thanks
thanks