[MITgcm-devel] iMin, iMax, jMin, and jMax in EXTERNAL_FORCING_T
Dimitris Menemenlis
menemenlis at jpl.nasa.gov
Thu Jan 28 19:02:55 EST 2010
Jean-Michel or Martin, is there a reason why iMin, iMax, jMin, and jMax
are passed to EXTERNAL_FORCING_T but then are ignored?
Most computations (with exception of OBCS_SPONGE_T) are carried out in a 1, sNx, 1, sNy domain.
In particular, SHELFICE_FORCING_T only applies forcing a 1, sNx, 1, sNy domain.
Is this the correct way to proceed? Thanks, Dimitris
More information about the MITgcm-devel
mailing list