[MITgcm-support] OB file
Riema Rachmayani
imoth_22 at yahoo.com
Mon Feb 26 21:09:21 EST 2007
hi all,
now i'd like to ask about open boundaries file, as in \verification\exp4\input\data.obcs :
# Open-boundaries
&OBCS_PARM01
OB_Jnorth=80*-1,
OB_Jsouth=80*1,
OB_Ieast=42*-1,
OB_Iwest=42*1,
#useOrlanskiNorth=.TRUE.,
#useOrlanskiSouth=.TRUE.,
#useOrlanskiEast=.TRUE.,
#useOrlanskiWest=.FALSE.,
useOBCSprescribe = .TRUE.,
OBNuFile = 'OBmeridU.bin',
OBSuFile = 'OBmeridU.bin',
OBWuFile = 'OBzonalU.bin',
OBEuFile = 'OBzonalU.bin',
OBWsFile = 'OBzonalS.bin',
OBWptrFile(1) = 'OBzonalS.bin',
&
# Orlanski parameters
&OBCS_PARM02
#Cmax=0.45,
#cVelTimeScale=1000.,
&
in the blue line means that data open boundaries is given from data observation/prediction?? may i know how to read and to write (format) for that open bondaries file?? is the data read every time step or every one hour??in what routines that files read??
in my case, i'm gonna use tidal prediction data of eta (elevation) from ORITIDE from Ocean Research Instute, University of Tokyo, the data is in every one hour, and usually we use spline cubic subroutine to interpolated one hour data become every time step data, so that every time step data/value used for open boundaries input/value...how to modify my case in MITgcm?? because as far i can see there is no open boundaries file for eta...
thank you,
regards
rima
----- Original Message ----
From: "mitgcm-support-request at mitgcm.org" <mitgcm-support-request at mitgcm.org>
To: mitgcm-support at mitgcm.org
Sent: Saturday, February 24, 2007 12:00:10 AM
Subject: MITgcm-support Digest, Vol 44, Issue 17
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. nonhydrostatic (Riema Rachmayani)
2. Re: nonhydrostatic (Martin Losch)
----------------------------------------------------------------------
Message: 1
Date: Fri, 23 Feb 2007 00:34:57 -0800 (PST)
From: Riema Rachmayani <imoth_22 at yahoo.com>
Subject: [MITgcm-support] nonhydrostatic
To: mitgcm-support at mitgcm.org
Message-ID: <20070223083457.65898.qmail at web53802.mail.yahoo.com>
Content-Type: text/plain; charset="iso-8859-1"
hi, all...
when we define our model for nonhydrostatic...we just describe :
#define ALLOW_NONHYDROSTATIC in code/CPP_OPTIONS.h and activated nonHydrostatic=.TRUE. in input/data and automatically MITgcm will compute the experiment by it self specially for vertical velocity right??? just want to make it clear and my curiousity about it...
is theta' in rho=rho0(1-alfatheta*theta') ...eq (3.12) in chapter 3 is define as Tref in input/data???
Tref is reference potential temperature (theta0) or fluctuation potential temperature (theta')?? or total potential temperature (theta=theta0+theta') ?? or we use eq 3.13 to find Tref??
thank you,
regards
-rima-
Send instant messages to your online friends http://uk.messenger.yahoo.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://forge.csail.mit.edu/pipermail/mitgcm-support/attachments/20070223/ccfadb81/attachment-0001.html
------------------------------
Message: 2
Date: Fri, 23 Feb 2007 13:52:46 +0100
From: Martin Losch <Martin.Losch at awi.de>
Subject: Re: [MITgcm-support] nonhydrostatic
To: mitgcm-support at mitgcm.org
Message-ID: <91141BF8-406B-4F1E-AA1D-7D1A5B99D369 at awi.de>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Riema,
to turn on non-hydrostatic code you do exactly what you described.
However, you can also set additional parameters for the cg3d solver
(in analogy to cg2d), for example cg3dMaxIters, and
cg3dTargetResidual, otherwise you'll use some defaults for those
parameters (150 and 1e-7).
if (and only if) eosType = 'LINEAR', then
rho = rhoNil*(1-talpha*(theta-tRef) + sbeta*(salt-sRef))
default for rhoNil=999.8, but you can set that in in "data",
talpha=2e-4,sbeta=7.4e-4 by default and you can set those parameters
in "data" as well. tRef(k) and sRef(k) on the other hand, you have to
set in "data". They are meant to be a reference temperature/salinity
for the model level k. How you choose them is up to you.
You can also use other eosTypes, where the density is a nonllinear
function of theta and salt and pressure (JMD95Z, JMD95P, MDJWF),
based on observations.
Martin
On 23 Feb 2007, at 09:34, Riema Rachmayani wrote:
> hi, all...
>
> when we define our model for nonhydrostatic...we just describe :
> #define ALLOW_NONHYDROSTATIC in code/CPP_OPTIONS.h and activated
> nonHydrostatic=.TRUE. in input/data and automatically MITgcm will
> compute the experiment by it self specially for vertical velocity
> right??? just want to make it clear and my curiousity about it...
>
> is theta' in rho=rho0(1-alfatheta*theta') ...eq (3.12) in chapter 3
> is define as Tref in input/data???
> Tref is reference potential temperature (theta0) or fluctuation
> potential temperature (theta')?? or total potential temperature
> (theta=theta0+theta') ?? or we use eq 3.13 to find Tref??
>
> thank you,
> regards
> -rima-
>
>
>
> Send instant messages to your online friends http://
> uk.messenger.yahoo.com
> _______________________________________________
> 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
End of MITgcm-support Digest, Vol 44, Issue 17
**********************************************
Send instant messages to your online friends http://uk.messenger.yahoo.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mitgcm.org/pipermail/mitgcm-support/attachments/20070226/69d10d47/attachment.htm>
More information about the MITgcm-support
mailing list