[MITgcm-support] tracer's time step

[Eli Biton]

Hi Stefano
Regarding your first question I'm compiling, building and running the
code 
in the same directory.  I have also checked at the STDOUT files (of both
experiments which differ just by their tracer time step) that the model
reads the 'data' file correctly. In addition, I  also compared between
the 'User time' of both tests at the end of their STDOUT files,  and
they show no difference between the two experiment in terms of
computation time.
Thanks, Eli   

>>> squerin at ogs.trieste.it 11/23/05 11:27 AM >>>
Hi Eli,
just a doubt (trivial...): are you compiling, building and running the
code 
in the same directory?
The STDOUT file should at least confirm that the executable reads the
input 
files correctly.

Cheers,

Stefano


----- Original Message ----- 
From: "eliyahu biton" <eliyahu.biton at weizmann.ac.il>
To: <mitgcm-support at mitgcm.org>
Sent: Wednesday, November 23, 2005 9:47 AM
Subject: [MITgcm-support] tracer's time step


> Dear all
> I have tried to save computation time by increasing my tracer's time
step 
> from 100 sec to 800 sec (changing the parameter 'deltaTtracer' at the
data 
> file under my 'build' directory). The results, however, show no
benefit at 
> all in terms of comutation time.
> Does anyone know if this is normal?
> thanks alot, Eli
>
> _______________________________________________
> MITgcm-support mailing list
> MITgcm-support at mitgcm.org
> http://mitgcm.org/mailman/listinfo/mitgcm-support
> 

_______________________________________________
MITgcm-support mailing list
MITgcm-support at mitgcm.org
http://mitgcm.org/mailman/listinfo/mitgcm-support