[MITgcm-devel] iMin, iMax, jMin, and jMax in EXTERNAL_FORCING_T

[Jean-Michel Campin]

Hi Dimitris,

Here is what I think (might not be completly true, but ...)
1) Hard coded loop range can speed-up the compiler optimisation.
2) removing those arguments from the EXTERNAL_FORCING_ S/R 
could embarasse people that have their own version of these S/R
and I think it's why Alistair was reluctant to change this.

Cheers,
Jean-Michel

On Thu, Jan 28, 2010 at 04:02:55PM -0800, Dimitris Menemenlis wrote:
> 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
> 
> 
> _______________________________________________
> MITgcm-devel mailing list
> MITgcm-devel at mitgcm.org
> http://mitgcm.org/mailman/listinfo/mitgcm-devel