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

[Dimitris Menemenlis]

Jean-Michel thanks for getting back.

Can I rephrase my question a little differently then:
What is the correct range for EXTERNAL_FORCING_T computations?

The i-j-Min-Max range going in EXTERNAL_FORCING_T is:
          iMin = 1-OLx+2
          iMax = sNx+OLx-1
          jMin = 1-OLy+2
          jMax = sNy+OLy-1

Yet most computations (except for OBCS_SPONGE_T) are carried out
in a smaller domain:
        iMin = 1
        iMax = sNx
        jMin = 1
        jMax = sNy

As far as I can see there is no exchange on gT between
EXTERNAL_FORCING_T and the application of diffusion terms that follow
in THERMODYNAMICS.  Is this correct?

In adjoint cube-sphere computations, if I squint the right way, I can see
lines at the tile edges.  I am wondering whether the above discrepancy
in computation domain could be part of the cause?

Dimitris

On Jan 29, 2010, at 7:17 AM, Jean-Michel Campin wrote:

> 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
> 
> _______________________________________________
> MITgcm-devel mailing list
> MITgcm-devel at mitgcm.org
> http://mitgcm.org/mailman/listinfo/mitgcm-devel