[MITgcm-support] PTRACERS Initialization

[Martin Losch]

Hi Ryan and Helen,

the PTRACERS_niter0 flag was introduced exactly for the situation  
that Jody has described (and that's how I do it rountinely).

I think what you tried initially was to set PTRACER_niter0>niter0 and  
have the tracers being initialized at myIter=PTRACER_niter0 in the  
ongoing integration, right? I don't recall that this has ever worked  
and I it probably never will. (see ptracers_init_varia.F to see how  
it works).

Martin

On 3 Nov 2008, at 20:55, Ryan Abernathey wrote:

> This seems like the simplest suggestion, because you don't have to  
> fake the pickup file. I tried it and it worked!
>
> Thanks for your suggestions everyone.
>
> -Ryan
>
> On Nov 2, 2008, at 6:27 PM, Klymak Jody wrote:
>
>> Hi Ryan,
>>
>>> I just want to start the tracer from my initialFile at an  
>>> advanced timestep.
>>
>>
>> I can see your frustration, and there may be a proper way to do  
>> what you want.  However, as a work around, why not set chkptFreq  
>> to 2000*dt and restart the gcm after spin up with nIter0=2000?
>>
>> Cheers,  Jody
>>
>>
>> --
>> Jody Klymak
>> http://web.uvic.ca/~jklymak/
>>
>>
>>
>>
>> _______________________________________________
>> 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