CMS-Flow Boundary Conditions/WSE Nesting: Difference between revisions

From CIRPwiki
Jump to navigation Jump to search
(Created page with "=Extracted Water Levels from a Parent Simulation= CMS supports automated one-way nesting within parent CMS and ADCIRC models. When using this feature, the CMS automatically e...")
 
mNo edit summary
Line 3: Line 3:
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.


Example 3: Extracting water levels from parent ADCIRC 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.
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
  NAME      "Nested Boundary"
:NAME      "Nested Boundary"
  CELLSTRING "Flow_mp.h5" "PROPERTIES/Model Params/Boundary"
:CELLSTRING "Flow_mp.h5" "PROPERTIES/Model Params/Boundary"
  WSE_BEGIN !All settings for wse at the boundary set here
:WSE_BEGIN !All settings for wse at the boundary set here
    OFFSET                0.1 m  !optional, positive is upwards
::OFFSET                0.1 m  !optional, positive is upwards
    TIME_INTERP_ORDER    2      !optional, temporal interpolation
::TIME_INTERP_ORDER    2      !optional, temporal interpolation
    SPACE_SMOOTH_ITER    1      !optional, spatial smoothing iterations
::SPACE_SMOOTH_ITER    1      !optional, spatial smoothing iterations
    SPACE_SMOOTH_WIDTH    3      !optional, spatial smoothing window width
::SPACE_SMOOTH_WIDTH    3      !optional, spatial smoothing window width
  WSE_END
:WSE_END
  PARENT_BEGIN !All settings for parent simulation set here
:PARENT_BEGIN !All settings for parent simulation set here
    GRID_FILE            "..\ADCIRC_Regional\fort.14"
::GRID_FILE            "..\ADCIRC_Regional\fort.14"
    WSE_SOL_FILE          "..\ADCIRC_Regional\fort.63" !Optional
::WSE_SOL_FILE          "..\ADCIRC_Regional\fort.63" !Optional
    STARTING_DATE_TIME    2012-12-01 00:00:00 UTC
::STARTING_DATE_TIME    2012-12-01 00:00:00 UTC
    HORIZ_PROJ_BEGIN !Optional, assumed if not specified
::HORIZ_PROJ_BEGIN !Optional, assumed if not specified
      DATUM        NAD83        !NAD27 | NAD83 | LOCAL
:::DATUM        NAD83        !NAD27 | NAD83 | LOCAL
      SYSTEM        GEOGRAPHIC    !UTM | STATE_PLANE| GEOGRAPHIC | LOCAL
:::SYSTEM        GEOGRAPHIC    !UTM | STATE_PLANE| GEOGRAPHIC | LOCAL
      UNITS        DEGREES      !METERS | FEET | DEGREES | etc.
:::UNITS        DEGREES      !METERS | FEET | DEGREES | etc.
    HORIZ_PROJ_END
::HORIZ_PROJ_END
  PARENT_END
:PARENT_END
BOUNDARY_END
BOUNDARY_END


Example 4: Extracting water levels from parent CMS simulation.
==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.
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
  NAME      "Nested CMS Boundary"
:NAME      "Nested CMS Boundary"
  CELLSTRING "Flow_mp.h5" "PROPERTIES/Model Params/Boundary"
:CELLSTRING "Flow_mp.h5" "PROPERTIES/Model Params/Boundary"
  WSE_BEGIN
:WSE_BEGIN
    WSE_SOLUTION          PARENT !required
::WSE_SOLUTION          PARENT !required
    WSE_OFFSET            0.1 m  !optional, positive is upwards
::WSE_OFFSET            0.1 m  !optional, positive is upwards
    TIME_INTERP_ORDER    2      !optional, temporal interpolation
::TIME_INTERP_ORDER    2      !optional, temporal interpolation
    SPACE_SMOOTH_ITER    1      !optional, spatial smoothing iterations
::SPACE_SMOOTH_ITER    1      !optional, spatial smoothing iterations
    SPACE_SMOOTH_WIDTH    3      !optional, spatial smoothing window width
::SPACE_SMOOTH_WIDTH    3      !optional, spatial smoothing window width
  WSE_END
:WSE_END
  PARENT_BEGIN
:PARENT_BEGIN
    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
:PARENT_END
 
BOUNDARY_END
BOUNDARY_END

Revision as of 21:38, 3 January 2014

Extracted Water Levels from a 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.

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

Retrieved from "https://cirpwiki.info/index.php?title=CMS-Flow_Boundary_Conditions/WSE_Nesting&oldid=10351"