[MITgcm-devel] timeave

[Martin Losch]

Hi Dimitris,

I was just wondering, whether only I experience this problem:
the surface fluxes of my runs (I have made many changes to the code, 
but not to the timeave pkg) are not "normalized" by the averaging 
period (I get e.g. sFluxtave*deltaTclock in the outfput files). I 
printed out this period (TimeAve_full), but that's zero for me (in 
timeave_statv_write, just before timeave_normaliz is called) and I 
cannot understand why. When I do a grep on timeave_full in all my 
source files, it's only used in timeave_statvars and 
timeave_statv_write, but I cannot see where and how it get's the 
numbers that I printed out.

So, there doesn't seem to be a problem with timeave_surf_flux itself 
but with the variable timeave_full (in my LOCAL version of the code), I 
don't think that you need to be sweating (o:
As Jean-Michel wrote, he cannot reproduce the problem so it's got to be 
my mistake somewhere (I just haven't found it yet).

Martin

On Mar 3, 2005, at 5:36 PM, Dimitris Menemenlis wrote:

>> I haven't checked what's in u/v/t/sFluxtave files (I assume Dimitri
>> did it right) but regarding TimeAve_full, I don't see the problem.
>
> Hi Martin, Jean-Michel has me sweating with above statement.
> Could you elaborate a little on what is fishy with u/v/t/sFluxtave.
>
> I fully concur with JMs comments re pkg/diagnostics.
>
> Cheers, D.
>
> -- 
> Dimitris Menemenlis <menemenlis at jpl.nasa.gov>
> Jet Propulsion Lab, California Institute of Technology
> MS 300-323, 4800 Oak Grove Dr, Pasadena CA 91109-8099
> tel: 818-354-1656;  fax: 818-393-6720
> _______________________________________________
> MITgcm-devel mailing list
> MITgcm-devel at mitgcm.org
> http://dev.mitgcm.org/mailman/listinfo/mitgcm-devel