[MITgcm-support] Change relaxation forcing after the spin up

[Evangelia Efstathiou]

Hi Martin,

thank you for your reply!  That makes sense.

Best regards,

Elina
________________________________
From: MITgcm-support <mitgcm-support-bounces at mitgcm.org> on behalf of Martin Losch <Martin.Losch at awi.de>
Sent: Monday, March 8, 2021 3:02 PM
To: MITgcm Support <mitgcm-support at mitgcm.org>
Subject: Re: [MITgcm-support] Change relaxation forcing after the spin up

Hi Elina,

I am not entirely sure what you want to do, but rbcsIniter is replaced by rbcsForcingOffset (in seconds).

I think if you restart your model anyway, you can just change the relaxation parameters and the relaxation will start directly at your first timestep of the restarted simulation (which is nIter0) and you don’t have to set anything in addition (i.e. use the default rbcsForcingOffset=0.)

If you were to start your integration at nIter0 = 0 and you want to start the relaxation some time later, say at timestep 10886400, then you could set rbcsForcingOffset to 10886400*deltaT = 2177280000.0 (I am guessing deltaT=200.) to achieve that, but again, I think in your case you don’t have to do anything.

Martin

> On 8. Mar 2021, at 13:31, Evangelia Efstathiou <Evangelia.Efstathiou at uib.no> wrote:
>
> Hello everyone,
>
> I have a question about rbcsIniter parameter at the  data.rbcs file.
>
> I have already run my set up for 70 years and I want to change the relaxation for the next years, so I can create temperature anomalies. I restart the model by setting nIter0=10886400 at the data file. Is this the same number I should set the rbcsIniter?
>
> Thank you in advance,
>
> Elina
>
> _______________________________________________
> MITgcm-support mailing list
> MITgcm-support at mitgcm.org
> http://mailman.mitgcm.org/mailman/listinfo/mitgcm-support

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.mitgcm.org/pipermail/mitgcm-support/attachments/20210308/1d71ead1/attachment-0001.html>