CMS-Flow Boundary Conditions/WSE Nesting: Difference between revisions
mNo edit summary |
mNo edit summary |
||
| (2 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
= | =Nested Water Levels Boundary Condition= | ||
CMS supports automated one-way nesting within parent CMS and ADCIRC models. When using this feature, the CMS automatically extracts the boundary condition information from the parent model solution. The user only has to specify to point to the boundary cellstring and the location and name of the parent model simulation. The user may force the CMS with either water levels or water levels and velocities extracted from the parent simulation. | CMS supports automated one-way nesting within parent CMS and ADCIRC models. When using this feature, the CMS automatically extracts the boundary condition information from the parent model solution. The user only has to specify to point to the boundary cellstring and the location and name of the parent model simulation. The user may force the CMS with either water levels or water levels and velocities extracted from the parent simulation. | ||
| Line 6: | Line 6: | ||
Since the ADCIRC simulation files do not contain information on the starting date or horizontal projection, this information needs to be provided in the model input. | Since the ADCIRC simulation files do not contain information on the starting date or horizontal projection, this information needs to be provided in the model input. | ||
BOUNDARY_BEGIN | BOUNDARY_BEGIN | ||
| Line 31: | Line 32: | ||
If a parent CMS simulation is used, all of the necessary information including horizontal projection, grid file name, and water level solution file are extracted from the CMS Card File. | If a parent CMS simulation is used, all of the necessary information including horizontal projection, grid file name, and water level solution file are extracted from the CMS Card File. | ||
BOUNDARY_BEGIN | BOUNDARY_BEGIN | ||
| Line 45: | Line 47: | ||
::CONTROL_FILE "..\CMS_Regional\Flow_Reg.cmcards" | ::CONTROL_FILE "..\CMS_Regional\Flow_Reg.cmcards" | ||
::!All other settings are obtained from the control file | ::!All other settings are obtained from the control file | ||
:PARENT_END | |||
BOUNDARY_END | |||
Because the CMS-Flow Control (Card) File contains all of the information regarding the horizontal projection, simulation time period, and output files, nothing else needs to be specified except the parent CMS-Flow simulation Card File. | |||
=Nested Water Level and Velocity Boundary Condition= | |||
CMS supports automated one-way nesting within parent CMS and ADCIRC models. When using this feature, the CMS automatically extracts the boundary condition information from the parent model solution. The user only has to specify to point to the boundary cellstring and the location and name of the parent model simulation. The user may force the CMS with either water levels or water levels and velocities extracted from the parent simulation. | |||
If the ADCIRC simulation is 3D, it is important to export the depth- averaged current velocity file (fort.63 or *_.h5) so that this file can be used for current velocity extraction. Additional support for other models is currently in development. A description of both with examples is provided below. | |||
==Example 1: Extracting water levels and velocities from parent ADCIRC simulation== | |||
BOUNDARY_BEGIN | |||
:NAME "Nested ADCIRC wse and velocity boundary" | |||
:CELLSTRING "Flow_mp.h5" "PROPERTIES/Model Params/Boundary" | |||
:WSE_BEGIN | |||
::WSE_OFFSET 0.1 m | |||
::TIME_INTERP_ORDER 2 !optional, temporal interpolation | |||
::SPACE_SMOOTH_ITER 1 !optional, spatial smoothing iterations | |||
::SPACE_SMOOTH_WIDTH 3 !optional, spatial smoothing window width | |||
:WSE_END | |||
:VEL_BEGIN | |||
:VEL_END | |||
:PARENT_BEGIN | |||
::GRID_FILE "..\ADCIRC_Regional\fort.14" | |||
::WSE_FILE "..\ADCIRC_Regional\fort.63" | |||
::VEL_FILE "..\ADCIRC_Regional\fort.64" | |||
::STARTING_DATE_TIME 2012-12-01 00:00:00 UTC | |||
::HORIZONTAL_PROJECTION_BEGIN !Optional, assumed if not specified | |||
:::DATUM NAD83 !NAD27 | NAD83 | LOCAL | |||
:::SYSTEM GEOGRAPHIC !UTM | STATE_PLANE| GEOGRAPHIC | LOCAL | |||
:::UNITS DEGREES !METERS | FEET | DEGREES | etc. | |||
::HORIZONTAL_PROJECTION_END | |||
:PARENT_BEGIN | |||
BOUNDARY_END | |||
It is noted that since the ADCIRC simulation files do not contain information on the starting date or horizontal projection, this information should to be provided in the model input. If the horizontal projection is not specified, then it is assumed to be NAD83 Geographic in degrees. | |||
In the example below, only the CMS Card file is specified for the parent simulation. The model automatically obtains the parent simulation starting time, horizontal projection, and output file names. The water level and velocity blocks are left empty so all of the default parameters are used. | |||
==Example 2: Interpolated water levels and velocities from parent CMS simulation== | |||
BOUNDARY_BEGIN | |||
:CELLSTRING "Flow_mp.h5" "PROPERTIES/Model Params/Boundary" | |||
:WSE_BEGIN | |||
:WSE_END | |||
:VEL_BEGIN | |||
:VEL_END | |||
:PARENT_BEGIN | |||
::CONTROL_FILE "..\CMS_Regional\Flow_Reg.cmcards" | |||
:PARENT_END | :PARENT_END | ||
BOUNDARY_END | BOUNDARY_END | ||
Latest revision as of 21:53, 3 January 2014
Nested Water Levels Boundary Condition
CMS supports automated one-way nesting within parent CMS and ADCIRC models. When using this feature, the CMS automatically extracts the boundary condition information from the parent model solution. The user only has to specify to point to the boundary cellstring and the location and name of the parent model simulation. The user may force the CMS with either water levels or water levels and velocities extracted from the parent simulation.
Example 1: Extracting water levels from parent ADCIRC simulation
Since the ADCIRC simulation files do not contain information on the starting date or horizontal projection, this information needs to be provided in the model input.
BOUNDARY_BEGIN
- NAME "Nested Boundary"
- CELLSTRING "Flow_mp.h5" "PROPERTIES/Model Params/Boundary"
- WSE_BEGIN !All settings for wse at the boundary set here
- OFFSET 0.1 m !optional, positive is upwards
- TIME_INTERP_ORDER 2 !optional, temporal interpolation
- SPACE_SMOOTH_ITER 1 !optional, spatial smoothing iterations
- SPACE_SMOOTH_WIDTH 3 !optional, spatial smoothing window width
- WSE_END
- PARENT_BEGIN !All settings for parent simulation set here
- GRID_FILE "..\ADCIRC_Regional\fort.14"
- WSE_SOL_FILE "..\ADCIRC_Regional\fort.63" !Optional
- STARTING_DATE_TIME 2012-12-01 00:00:00 UTC
- HORIZ_PROJ_BEGIN !Optional, assumed if not specified
- DATUM NAD83 !NAD27 | NAD83 | LOCAL
- SYSTEM GEOGRAPHIC !UTM | STATE_PLANE| GEOGRAPHIC | LOCAL
- UNITS DEGREES !METERS | FEET | DEGREES | etc.
- HORIZ_PROJ_END
- PARENT_END
BOUNDARY_END
Example 2: Extracting water levels from parent CMS simulation
If a parent CMS simulation is used, all of the necessary information including horizontal projection, grid file name, and water level solution file are extracted from the CMS Card File.
BOUNDARY_BEGIN
- NAME "Nested CMS Boundary"
- CELLSTRING "Flow_mp.h5" "PROPERTIES/Model Params/Boundary"
- WSE_BEGIN
- WSE_SOLUTION PARENT !required
- WSE_OFFSET 0.1 m !optional, positive is upwards
- TIME_INTERP_ORDER 2 !optional, temporal interpolation
- SPACE_SMOOTH_ITER 1 !optional, spatial smoothing iterations
- SPACE_SMOOTH_WIDTH 3 !optional, spatial smoothing window width
- WSE_END
- PARENT_BEGIN
- CONTROL_FILE "..\CMS_Regional\Flow_Reg.cmcards"
- !All other settings are obtained from the control file
- PARENT_END
BOUNDARY_END
Because the CMS-Flow Control (Card) File contains all of the information regarding the horizontal projection, simulation time period, and output files, nothing else needs to be specified except the parent CMS-Flow simulation Card File.
Nested Water Level and Velocity Boundary Condition
CMS supports automated one-way nesting within parent CMS and ADCIRC models. When using this feature, the CMS automatically extracts the boundary condition information from the parent model solution. The user only has to specify to point to the boundary cellstring and the location and name of the parent model simulation. The user may force the CMS with either water levels or water levels and velocities extracted from the parent simulation.
If the ADCIRC simulation is 3D, it is important to export the depth- averaged current velocity file (fort.63 or *_.h5) so that this file can be used for current velocity extraction. Additional support for other models is currently in development. A description of both with examples is provided below.
Example 1: Extracting water levels and velocities from parent ADCIRC simulation
BOUNDARY_BEGIN
- NAME "Nested ADCIRC wse and velocity boundary"
- CELLSTRING "Flow_mp.h5" "PROPERTIES/Model Params/Boundary"
- WSE_BEGIN
- WSE_OFFSET 0.1 m
- TIME_INTERP_ORDER 2 !optional, temporal interpolation
- SPACE_SMOOTH_ITER 1 !optional, spatial smoothing iterations
- SPACE_SMOOTH_WIDTH 3 !optional, spatial smoothing window width
- WSE_END
- VEL_BEGIN
- VEL_END
- PARENT_BEGIN
- GRID_FILE "..\ADCIRC_Regional\fort.14"
- WSE_FILE "..\ADCIRC_Regional\fort.63"
- VEL_FILE "..\ADCIRC_Regional\fort.64"
- STARTING_DATE_TIME 2012-12-01 00:00:00 UTC
- HORIZONTAL_PROJECTION_BEGIN !Optional, assumed if not specified
- DATUM NAD83 !NAD27 | NAD83 | LOCAL
- SYSTEM GEOGRAPHIC !UTM | STATE_PLANE| GEOGRAPHIC | LOCAL
- UNITS DEGREES !METERS | FEET | DEGREES | etc.
- HORIZONTAL_PROJECTION_END
- PARENT_BEGIN
BOUNDARY_END
It is noted that since the ADCIRC simulation files do not contain information on the starting date or horizontal projection, this information should to be provided in the model input. If the horizontal projection is not specified, then it is assumed to be NAD83 Geographic in degrees.
In the example below, only the CMS Card file is specified for the parent simulation. The model automatically obtains the parent simulation starting time, horizontal projection, and output file names. The water level and velocity blocks are left empty so all of the default parameters are used.
Example 2: Interpolated water levels and velocities from parent CMS simulation
BOUNDARY_BEGIN
- CELLSTRING "Flow_mp.h5" "PROPERTIES/Model Params/Boundary"
- WSE_BEGIN
- WSE_END
- VEL_BEGIN
- VEL_END
- PARENT_BEGIN
- CONTROL_FILE "..\CMS_Regional\Flow_Reg.cmcards"
- PARENT_END
BOUNDARY_END