awips2/edexOsgi/com.raytheon.uf.tools.gfesuite/nwps/domains/LIX
2022-05-05 12:34:50 -05:00

182 lines
8.1 KiB
Text

#------------------------------------------------------------------------
# Domain File
# Original Author(s): Roberto Padilla-Hernandez,Douglas Gaer
# Alex Gibbs, Pablo Santos,Tony Freeman
# File Creation Date: 06/01/2012
# Date Last Modified: 02/01/13
#
# Version control: 1.33
#
# Support Team:
#
# Contributors:
#
# -----------------------------------------------------------------------
# ---------------------- Description and Details ------------------------
# -----------------------------------------------------------------------
#
# File used to setup a geographical domain for SWAN and WW3
#
# -----------------------------------------------------------
#========================================================================
# LIX =
# GEOGRAPHICAL DOMAIN, GEOGRAPHICAL RESOLUTION AND OUTPUT TIME STEP =
# =
# NOTE: RES = spatial resolution in km =
# TSTEP = request output time step (not the model time step) =
#========================================================================
#
export SITEID="LIX"
export REGIONID="SR"
export NELAT="30.60"
export NELON="-87.40"
export SWLAT="27.50"
export SWLON="-91.80"
export RES="1.8"
export TSTEP="3"
#
#========================================================================
# NESTED GRID CONFIGURATION =
# =
# These nested grids are non-telescopic grids (i.e all of them are =
# nested in the outer grid, and get the boundary conditions only from it) =
# Later versions of NWPS will either allow for telescopic nesting or =
# will be run on an unstructured grid characterized with a fine mesh =
# over the nearshore zones and a coarser mesh across the offshore areas. =
# =
#========================================================================
#
# TO DO: Update the domains below to reflect the area/s that you are
# interested in (must reside inside of you outer domain defined
# above). Also, remember to remove or comment out the remaining
# example nests below that were configured for another area. Once
# your nests are configured, just toggle the NESTGRIDS to '1'
# (Default configuration is off or '0') and you will have control
# from the GFE GUI to activate your nests during your runs.
#
# STATIONARY VS NONSTATIONARY MODE:
#
# STATN=STA for STATIONARY RUNS, STATN=NON for NON-STATIONARY RUNS.
# The default value is NONstationary for CG1 (outer grid) and STAtionary
# for the nested grids. Change this only if you know what you are doing.
# You can choose STA or NON for a particular nested grid. In general,
# if your domain that you define as a nest below is >= 100 km^2, then
# set STATN=NON. For the very small domains or nests (<= 100 km^2)
# set STATN=STA.
#
# ACTIVATE NEST/S: default is on for LIX
#
# NESTGRIDS="0" ... turns off nest options
# NESTGRIDS="1" ... turns on nest options
#
export NESTGRIDS="1"
export NESTINCG1="YES"
#
# NEST 1
export NELATN1="30.40"
export NELONN1="-88.8"
export SWLATN1="29.3"
export SWLONN1="-90.6"
export RESN1="1.25"
export TSTEPN1="3"
export STATN1="NON"
#
#
#========================================================================
# SPECTRA OUTPUT LOCATIONS
# =
# NOTE TO USER: the lat/lon points specified can be changed for any =
# arbitrary point of interest within your outer domain defined above. =
# One default buoy locations has already been configured for you =
# below. Add more as needed. =
#
# NOTE: These do not have to match NDBC locations. =
#
#========================================================================
# Spectra points defined as space delimited list of:
# "name1:lat1:lon1 name2:lat2:lon2 name3:lat3:lon3 name4:lat4:lon4 ...."
#
export SPECPOINTS="42040:29.212:-88.207 BPass:29.014:-90.206 ChRim:29.658:-88.799 BrRim:29.149:-89.536 SWPass:28.856:-89.456"
#
#========================================================================
# WAVE TRACKING (and WAVE PARTITION) ON/OFF =
# SET: SUBDOLIXN, GEOGRAPH RESOL and TOLERANCE WAVETRACK PARAMETERS =
#========================================================================
# IF WAVE TRACKING IS REQUIRED THEN WVTRCK="ON", OTHER WISE SET IT AS "OFF"
# IF WVTRCK IS "ON", ADDTIONAL INFORMATION IS REQUIRED, SEE BELOW
#
export WVTRCK="ON"
#
# IF WAVE TRACKING IS REQUIRED EXACTLY OVER THE COMPUTATIONAL GRID AND SAME SPATIAL
# RESOLUTION: SET WVTONCG="1"
# IF USER WANTS TO CHANGE ANYONE OF THE PARAMETERS THEN WVTONCG="0" AND USER MUST GIVE
# ALL INFORMATION FOR THE DOMAIN OR SUBDOMAIN AND GEOGRAPHICAL RESOLUTION.
# BE CAREFULL, IF THERE IS ANY SPECTRAL OUTPUT LOCATIONS OUT OF THE NEW (REDUCED) DOMAIN
# FOR WAVE TRACKING NWPS WILL ABORT.
# (This will be changed in a new version, the user can get 1d-spectra but not g-h plots).
#
export WVTONCG="0"
export NELATWT="30.60"
export NELONWT="-87.40"
export SWLATWT="27.50"
export SWLONWT="-91.80"
export GEORESWT="4.0"
#
# PARAMETERS FOR TRACKING ALGORITHM for WVTONCG=0 or =1 THIS IS ALWAYS READ
# *CAUTION* CHANGE THEM ONLY IF YOU KNOW WHAT YOU ARE DOING
# RECOMENDED VALUES WVTRKPA="10. 1. 0.25 0.1 10. 1."
# dirKnob, perKnob, hsKnob, wetPts, dirTimeKnob, tpTimeKnob
export WVTRKPA="10. 1. 0.25 0.1 10. 1."
#
#========================================================================
# CURRENTS DEFINITION (SEE SWAN MANUAL) =
#========================================================================
#export CURRL1="INPGRID CUR ............................."
#export CURRL2="READINP CUR ............................."
#
#========================================================================
# BOUNDARY CONDITIONS (SEE SWAN MANUAL) =
#========================================================================
# IF BOUNDARY CONDITIONS WILL BE USED then BOUNDCOND=1, Otherwise =0;
# Setting up BOUNDCOND here to zero will permanently disable BCs.
# If you leave it as 1 the user will still have the option to disable
# them from the interactive Run_NWPS GUI.
#
export BOUNCOND="1"
export FTPPAT1="multi_1"
export FTPPAT1B="multi_1"
export FTPPAT2="LIX"
export NFTPATTEMPTS="3"
export WAVECPS="multi_1.LIX54.spec.swan,multi_1.LIX63.spec.swan"
#
# THE FOLLOWING LINES MUST BE COMMENTED. IF YOU ADD BOUNDARY COMMAND LINES FOR YOUR
# DOMAIN, ADD THEM WITH THE "#" AS A FIRST CHARACTER, IF YOU DECIDE NOT TO USE BOUNARY
# CONDITIONS (BOUNCOND="0") THEY WILL REMAIN AS A COMMENTED LINES. IF YOU DECIDE TO USE
# BOUNDARY CONDITIONS (BOUNCOND="1") NWPS WILL INCLUDE THE INFORMATION IN THE ACTUAL
# INPUT FILES WITH NOT COMMENT CHARACTER
#
#$BOUNDARY COMMAND LINES
#BOUN SEG XY 268.2 28.90 268.2 27.50 VAR FILE 0.00 'multi_1.LIX51.spec.swan' 1 &
# 0.50 'multi_1.LIX52.spec.swan' 1 &
# 1.00 'multi_1.LIX53.spec.swan' 1 &
# 1.50 'multi_1.LIX54.spec.swan' 1
#$
#BOUN SEG XY 272.6 27.50 268.2 27.50 VAR FILE 0.00 'multi_1.LIX63.spec.swan' 1 &
# 0.50 'multi_1.LIX62.spec.swan' 1 &
# 1.00 'multi_1.LIX61.spec.swan' 1 &
# 1.50 'multi_1.LIX60.spec.swan' 1 &
# 2.00 'multi_1.LIX59.spec.swan' 1 &
# 2.50 'multi_1.LIX58.spec.swan' 1 &
# 3.00 'multi_1.LIX57.spec.swan' 1 &
# 3.50 'multi_1.LIX56.spec.swan' 1 &
# 4.00 'multi_1.LIX55.spec.swan' 1 &
# 4.40 'multi_1.LIX54.spec.swan.cp' 1
#$
#BOUN SEG XY 272.6 30.00 272.6 27.50 VAR FILE 0.00 'multi_1.LIX68.spec.swan' 1 &
# 0.50 'multi_1.LIX67.spec.swan' 1 &
# 1.00 'multi_1.LIX66.spec.swan' 1 &
# 1.50 'multi_1.LIX65.spec.swan' 1 &
# 2.00 'multi_1.LIX64.spec.swan' 1 &
# 2.50 'multi_1.LIX63.spec.swan.cp' 1
#$END BOUNSEG
#