[MITgcm-support] Error message, 2D run
Liam Brannigan
liam.brannigan at misu.su.se
Thu Nov 17 02:01:41 EST 2016
Hi Marta
It looks to me like you might have the vertical viscous or diffusive terms set to some non-zero value in your data file. These terms wouldn't make sense in a 2D run where there is only one layer as they lead to fluxes between layers. Only a bottom drag should be active in this 2D case.
Liam
________________________________________
From: mitgcm-support-request at mitgcm.org <mitgcm-support-request at mitgcm.org>
Sent: 16 November 2016 22:05
To: mitgcm-support at mitgcm.org
Subject: MITgcm-support Digest, Vol 161, Issue 18
Send MITgcm-support mailing list submissions to
mitgcm-support at mitgcm.org
To subscribe or unsubscribe via the World Wide Web, visit
http://mitgcm.org/mailman/listinfo/mitgcm-support
or, via email, send a message with subject or body 'help' to
mitgcm-support-request at mitgcm.org
You can reach the person managing the list at
mitgcm-support-owner at mitgcm.org
When replying, please edit your Subject line so it is more specific
than "Re: Contents of MITgcm-support digest..."
Today's Topics:
1. Error message, 2D run (Marta Trodahl)
2. Re: build errors for llc_1080 (Dimitris Menemenlis)
3. Re: build errors for llc_1080 (Ryan Abernathey)
4. Re: build errors for llc_1080 (Dimitris Menemenlis)
----------------------------------------------------------------------
Message: 1
Date: Wed, 16 Nov 2016 18:36:47 +0100
From: Marta Trodahl <marta.trodahl at gmail.com>
To: mitgcm-support at mitgcm.org
Subject: [MITgcm-support] Error message, 2D run
Message-ID:
<CAAYbUY0a+uvXndYLyZD3zWiuPLVXmdCRLLz-tf7pRii0aijRHw at mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
Hi all,
I have just started using MITgcm, and have tested some of the setups in the
verification/ directory. When trying to run any of the 2D setups, without
making any changes (for instance tutorial_barotropic_gyre), I get the
following error:
(PID.TID 0000.0001) *** ERROR *** S/R INI_PARMS: Partial setting ( 0 /
1) of viscArNr is not allowed
(PID.TID 0000.0001) *** ERROR *** S/R INI_PARMS: Partial setting ( 0 /
1) of diffKrNrT is not allowed
(PID.TID 0000.0001) *** ERROR *** S/R INI_PARMS: Partial setting ( 0 /
1) of diffKrNrS is not allowed
(PID.TID 0000.0001) *** ERROR *** S/R INI_PARMS: detected 3 fatal error(s)
This error also occurs when I amend other setups, which runs fine with >=2
vertical layers, to 1 layer.
Has anyone encountered something similar?
Thanks.
M.T.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mitgcm.org/pipermail/mitgcm-support/attachments/20161116/fc3beff3/attachment-0001.htm>
------------------------------
Message: 2
Date: Wed, 16 Nov 2016 09:42:52 -0800
From: Dimitris Menemenlis <dmenemenlis at gmail.com>
To: MITgcm Support <mitgcm-support at mitgcm.org>
Subject: Re: [MITgcm-support] build errors for llc_1080
Message-ID: <65617AEE-3981-4E5F-B5EB-0CB8786DACCE at gmail.com>
Content-Type: text/plain; charset="utf-8"
I just link the 2010 files to 2009.
It?s just for interpolation purposes for first 3 hours.
So should have minimal impact relative to having actual 2009 files.
Dimitris Menemenlis
> On Nov 16, 2016, at 9:34 AM, Ryan Abernathey <ryan.abernathey at gmail.com> wrote:
>
> Ok, I am up and running! Thanks for your help!
>
> The next problem I hit is with the exf forcing. I am starting from niter0=0 == Jan 1, 2010.
>
> (PID.TID 0000.0001) EXF_INTERP_READ: filename: EOG_rain_2009
> (PID.TID 0000.0001) EXF_INTERP_READ: File does not exist
>
> It is looking for EOG_rain_2009, which is not in the ECMWF_operation dataset. This is only a problem for precipitation, which has slightly different timing. Compare:
> apressurestartdate1 = 19790101,
> apressurestartdate2 = 000000,
> with
> precipstartdate1 = 19790101,
> precipstartdate2 = 030000,
>
> The three hour offset means that it needs to look for a 2009 file, which doesn't exist.
>
> -Ryan
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mitgcm.org/pipermail/mitgcm-support/attachments/20161116/ae291d36/attachment-0001.htm>
------------------------------
Message: 3
Date: Wed, 16 Nov 2016 14:59:23 -0500
From: Ryan Abernathey <ryan.abernathey at gmail.com>
To: "mitgcm-support at mitgcm.org" <mitgcm-support at mitgcm.org>
Subject: Re: [MITgcm-support] build errors for llc_1080
Message-ID:
<CAJAZx5CdUFn-F35LZntN7279m1=6uSqx7ZVorEz1VpfxvywVMw at mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
Thanks again for the advice. I got it to start timestepping!
...Unfortunately I had NaN's by timestep 2... ;p
My guess is that I have to reduce my timestep (it's 90 in the example) for
a few iterations to overcome the geostrophic adjustment shock, as with most
spinup. However, before embarking on this, since people (Dimitris) have
already been through the procedure, I thought I would ask for your guidance.
-Ryan
On Wed, Nov 16, 2016 at 12:42 PM, Dimitris Menemenlis <dmenemenlis at gmail.com
> wrote:
> I just link the 2010 files to 2009.
> It?s just for interpolation purposes for first 3 hours.
> So should have minimal impact relative to having actual 2009 files.
>
> Dimitris Menemenlis
>
> On Nov 16, 2016, at 9:34 AM, Ryan Abernathey <ryan.abernathey at gmail.com>
> wrote:
>
> Ok, I am up and running! Thanks for your help!
>
> The next problem I hit is with the exf forcing. I am starting from
> niter0=0 == Jan 1, 2010.
>
> (PID.TID 0000.0001) EXF_INTERP_READ: filename: EOG_rain_2009
> (PID.TID 0000.0001) EXF_INTERP_READ: File does not exist
>
> It is looking for EOG_rain_2009, which is not in the ECMWF_operation
> dataset. This is only a problem for precipitation, which has slightly
> different timing. Compare:
> apressurestartdate1 = 19790101,
> apressurestartdate2 = 000000,
> with
> precipstartdate1 = 19790101,
> precipstartdate2 = 030000,
>
> The three hour offset means that it needs to look for a 2009 file, which
> doesn't exist.
>
> -Ryan
>
>
>
> _______________________________________________
> MITgcm-support mailing list
> MITgcm-support at mitgcm.org
> http://mitgcm.org/mailman/listinfo/mitgcm-support
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mitgcm.org/pipermail/mitgcm-support/attachments/20161116/f0299cb0/attachment-0001.htm>
------------------------------
Message: 4
Date: Wed, 16 Nov 2016 13:05:28 -0800
From: Dimitris Menemenlis <dmenemenlis at gmail.com>
To: MITgcm Support <mitgcm-support at mitgcm.org>
Subject: Re: [MITgcm-support] build errors for llc_1080
Message-ID: <19D87032-DC8C-426A-B710-2E70E5742C03 at gmail.com>
Content-Type: text/plain; charset="us-ascii"
yup. initially you need to run with small time step, until you get rid of initialization shock.
here is a spin-up history for llc1080,
but note that first year is without tides
llc1080 initial conditions and spin-up:
- start on January 1, 2010
from Hong's 2009-2011 3-year CS510 adjoint-method estimate.
- run for one year with ERA-interim, with corrected dlw.
- kick in tides, atmospheric pressure forcing, and 0.14-degree
atmospheric analysis on January 1, 2011
run_day1, deltaT=30, dumpFreq=3600, ERAi, January 1, 2010
run_day2_10, deltaT=90, dumpFreq=21600, ERAi, January 2-10, 2010
run_day10_20, deltaT=120, dumpFreq=21600, ERAi, January 11-20, 2010
run_day20_45, deltaT=180, dumpFreq=21600, ERAi, January 21 - February 14, 2010
run_day45_90, deltaT=240, dumpFreq=86400, ERAi, February 15 - March 30, 2010
run_day135, deltaT=240, dumpFreq=86400, ERAi, March 31 - May 16, 2010
run_year1, deltaT=240, dumpFreq=86400, ERAi, May 17, 2010 - March 16, 2011
run_EOG, deltaT=240, dumpFreq=86400, ECMWF 0.14-deg analysis, January 1-20, 2011
run_EOG_pres, deltaT=240, dumpFreq=86400, ECMWF + atmos pressure, January 1-16, 2011
run_EOG_press_tides, deltaT=120, dumpFreq=86400, ECMWF + pressure + tides, January 1-20, 2011
run_cn_dt120_crash, deltaT=120, dumpFreq=86400, ECMWF + pressure + tides + Crank-Nickelson, January 1-5, 2011
run_2011, deltaT=90, dumpFreq=86400, ECMWF + pressure + tides + Crank-Nickelson, January 5 - December 31, 2011
run_day732_896, deltaT=90, dumpFreq=3600, ECMWF + pressure + tides + Crank-Nickelson, January 1 - June 20, 2012
Dimitris Menemenlis
> On Nov 16, 2016, at 11:59 AM, Ryan Abernathey <ryan.abernathey at gmail.com> wrote:
>
> Thanks again for the advice. I got it to start timestepping!
>
> ...Unfortunately I had NaN's by timestep 2... ;p
>
> My guess is that I have to reduce my timestep (it's 90 in the example) for a few iterations to overcome the geostrophic adjustment shock, as with most spinup. However, before embarking on this, since people (Dimitris) have already been through the procedure, I thought I would ask for your guidance.
>
> -Ryan
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mitgcm.org/pipermail/mitgcm-support/attachments/20161116/a354f6b0/attachment.htm>
------------------------------
_______________________________________________
MITgcm-support mailing list
MITgcm-support at mitgcm.org
http://mitgcm.org/mailman/listinfo/mitgcm-support
End of MITgcm-support Digest, Vol 161, Issue 18
***********************************************
More information about the MITgcm-support
mailing list