SMS:CMS-Flow Files

CMS-Flow creates a number of files during the model run. These are summarized in the tables below

• For more information on these files see pages 224 and 242 of the manual.

Required Input/Project Files (SMS 13.3+)

Name	Description
DB3	dBASE III
MAP	Grid and Projection Information
MATERIALS	Material Values
_UGrid.h5	UGrid representation of grid (XMDF)
XMC	UGrid representation of grid (ASCII)

Output/Export files from SMS for CMS

Name	Description	Type of file
.cmcards	CMS paramter/card Settings	ASCII
.tel	Grid definition/connectivity	ASCII
_datasets.h5	Cell-based Dataset values (i.e., Mannings)	XMDF
_diag.h5	Diagnostic Solutions (debugging)	XMDF
_mp.h5	Model Parameters	XMDF

Output files from CMS

Name	Description	Type of file
CMS_Diag.txt	Summary and Output from model	ASCII
SingleHotStart.h5 AutoHotStart_#.h5	Information for hot starting	XMDF
<solution type>	Solution information for different processes	XMDF

<Solution type> above can be any of the following types.

• _wse.h5 - Water surface elevation solution
• _vel.h5 - Current velocity solution
• _visc.h5 - Eddy viscosity solution
• _sed.h5 - Sediment solutions (concentration/capacity, etc.)
• _morph.h5 - Sediment morphology solution
• _trans.h5 - Transport rate solution
• _wave.h5 - Wave solution mapped to flow grid.
• A few other types are available as well.

Hot Start File

In the CMS-Flow Model Control, it is possible to specify a previously saved hot start file to be used as initial conditions or instruct CMS-Flow to save hot start files for future use.

To create a hot start file, either select Write Hot Start output file and select an output time, or select Automatic recurring Hot Start file and choose an output interval.

• Choosing to write the hot start file at a specific output time will create the following file:
  • SingleHotStart.h5 This file has the simulation data including elevations and velocities.

• Choosing automatic recurring hot start files will create the following files:
  • AutoHotStart_#.h5 (where "#" can be '1' or '2') These files have the simulation data including elevations and velocities and CMS iterates between two versions of this file so the user will have two saved records to choose from.

Once the hot start files are created, they can be read into CMS-Flow. Open the CMS-Flow Model Control and check the Initial conditions file check box, then select the hot start file to be used.

When using a hot start file, No parameters need to be changed. CMS reads the appropriate information from the hot start file and will start as needed.

Again, the following parameters should not be changed:

• Start Date: no change
• Start Time: no change
• Simulation Duration: no change
• Boundary Conditions: no change

Save Point File

Storing Save Points in the *.cmcards File

When saving the SMS project, the save points get stored in the *.cmcards file. An example looks like this:

Save Points

HYDRO_OUTPUT_INTERVAL        5.0 MINUTES 
SEDIMENT_OUTPUT_INTERVAL     5.0 MINUTES 
SALINITY_OUTPUT_INTERVAL     5.0 MINUTES 
WAVE_OUTPUT_INTERVAL         5.0 MINUTES 

The SAVE_POINT is formatted [name][x location][y location][hydro (if on)][sediment (if on)][salinity(if on)][wave(if on)]

SAVE_POINT        "6, 61" -2867.5 2022.0 HYDRO SEDIMENT WAVE
SAVE_POINT        "20, 59" -2517.5 1966.0 HYDRO 
SAVE_POINT        "10, 31" -2767.5 1182.0 SEDIMENT 
SAVE_POINT        "11, 31" -2742.5 1182.0 SEDIMENT 
SAVE_POINT        "10, 32" -2767.5 1210.0 SALINITY 
SAVE_POINT        "11, 32" -2742.5 1210.0 WAVE

*.sp/*.spx File for Reading in Save Point Information

Simulation output data gets stored in *sp and *.spx file. The *.sp file is and individual output file. The 8.spx file simply identifies all of the *.sp files that should be loaded for a simulation. An *.sp file looks something like this:

SAVE_POINT_OUTPUT    eta
REFERENCE_TIME       2001/01/01 00:00 -0000 GMT
CREATION_DATE        2012/05/28 09:02 -0600 GMT
CMS_VERSION          4.00.11
TIME_UNITS           HOURS
OUTPUT_UNITS         'm'       
NUMBER_POINTS        2


NAME_BEGIN
  '6, 61'
  '20, 59'
NAME_END


XY_BEGIN
  -2867.5000   2022.0000
  -2517.5000   1966.0000
XY_END


SCALAR_TS_BEGIN
      0.0000   0.0000E+00   0.0000E+00
      0.0333   1.7545E-09   1.7434E-09
      0.0667   1.4042E-08   1.3971E-08
      0.1000   4.6679E-08   4.6524E-08
      0.1333   1.1143E-07   1.1117E-07

Sms will read in a *.sp file and create a CMS-Flow save point coverage with the points.

Projection Cards

CMS-Flow uses a local coordinate system in which all vector values are positive along the I and J axis. All output vector arrays are specified in the local coordinate system. Any input that is specified on the local grid must be specified in the local coordinate system (e.g. initial condition for currents, interpolated wave forcing, etc). If input vector arrays are specified on a different grid then the vectors are assumed to follow the coordinate system of their native grid. The grid is always created in SMS with the origin is by default always at the lower left hand corner of the grid.

Below are two examples of CMS Flow projection cards:

HORIZONTAL_PROJECTION_BEGIN                  !Optional 
  DATUM                             NAD83    !NAD27|NAD83|LOCAL 
  SYSTEM                            UTM      !UTM|STATE_PLANE|GEOGRAPHIC|LOCAL 
  UNITS                             METERS   !METERS|FEET|DEGREES 
  ZONE                              15       !Only if necessary 
HORIZONTAL_PROJECTION_END            

VERTICAL_PROJECTION_BEGIN            
  DATUM                             LOCAL    !NGVD29|NAVD88|LOCAL 
  UNITS                             METERS   !METERS|FEET 
  OFFSET                            2.0 m    !Positive is upwards 
VERTICAL_PROJECTION_END

Related Topics

• CMS-Flow
• CMS-Flow Model Control