Hi,
I am trying to setup a high resolution Pan-Arctic domain. The average resolution is around 3 km.
I computed initial conditions for T,S, zeta and sea ice variables from 1/12 degree NEMO model.
The initial conditions look all right to me.
I computed the open boundary conditions using the PyCNAL_regridding where first I computed the rotated velocities
of the NEMO model, then the Pycnal_regridding computes the open boundary velocities (angle rotated back to model grid) by that code.
The model is forced by CORE-II, however I tried CORE-I as well, it only pushes the truncations errors couple of days later.
I attached my final parameter choices which it ran 15 days with out any truncatione error, then the model blows up, and I attached final day u-velocities.
I tried every trick in the book including changing horizontal Smag coefficients (both laplacian and biharmonic), changing time step down to 200 seconds.
Almost all the Barotropic/Coriolis computation options, even turning on the GM. I wanted no-GM at the beginning, but later to kill the instabilities/eddies etc, I turned it on.
The velocities looks like a Kelvin wave to me, and most of the time truncation errors are around bottom right corner (East Pacific side).
The things I didn't try so far are;
1) compute and balance total barotropic transport across the boundaries, but normally Flather should be good with that. And it is a hassle to do that.
2) nudging. I guess for this I need to generate 4D u,v variables across the domain and file size can be very big!
I am wondering if anybody has a suggestions.
Thanks in advance,
Best,
Mehmet
I am trying to setup a high resolution Pan-Arctic domain. The average resolution is around 3 km.
I computed initial conditions for T,S, zeta and sea ice variables from 1/12 degree NEMO model.
The initial conditions look all right to me.
I computed the open boundary conditions using the PyCNAL_regridding where first I computed the rotated velocities
of the NEMO model, then the Pycnal_regridding computes the open boundary velocities (angle rotated back to model grid) by that code.
The model is forced by CORE-II, however I tried CORE-I as well, it only pushes the truncations errors couple of days later.
I attached my final parameter choices which it ran 15 days with out any truncatione error, then the model blows up, and I attached final day u-velocities.
I tried every trick in the book including changing horizontal Smag coefficients (both laplacian and biharmonic), changing time step down to 200 seconds.
Almost all the Barotropic/Coriolis computation options, even turning on the GM. I wanted no-GM at the beginning, but later to kill the instabilities/eddies etc, I turned it on.
The velocities looks like a Kelvin wave to me, and most of the time truncation errors are around bottom right corner (East Pacific side).
The things I didn't try so far are;
1) compute and balance total barotropic transport across the boundaries, but normally Flather should be good with that. And it is a hassle to do that.
2) nudging. I guess for this I need to generate 4D u,v variables across the domain and file size can be very big!
I am wondering if anybody has a suggestions.
Thanks in advance,
Best,
Mehmet