User Guide 022: Difference between revisions

From CIRPwiki
Jump to navigation Jump to search
No edit summary
No edit summary
Line 8: Line 8:
table a1
table a1


Notes:
=Notes<nowiki>:</nowiki>=
• Directions of neighboring cells are relative to the local grid axis (i.e. positive in x = East, negative in x = West, positive in y = North, and negative in y = South).
• Indexes equal to 0 indicate the absence of a neighboring cell.
• If a cell is assigned as an inactive cell, -999
• Because the file is ASCII, the file size can be relatively large and difficult to view in WordPad or Notepad. To view the telescoping grid file, it is recommended to use a more advanced text editor such as UltraEdit or Textpad.


An example of the first 6 lines of a CMS-Flow telescoping grid file is pro-vided below. ________________________________________
:• Directions of neighboring cells are relative to the local grid axis (i.e. positive in x = East, negative in x = West, positive in y = North, and negative in y = South).
 
:• Indexes equal to 0 indicate the absence of a neighboring cell.
 
:• If a cell is assigned as an inactive cell, -999
 
:• Because the file is ASCII, the file size can be relatively large and difficult to view in WordPad or Notepad. To view the telescoping grid file, it is recommended to use a more advanced text editor such as UltraEdit or Textpad.
 
An example of the first 6 lines of a CMS-Flow telescoping grid file is pro-vided below. _


example
example
Line 22: Line 26:
matlab script
matlab script


Card (Control) File
=Card (Control) File=
Control files are used for specifying input parameters, options, and boundary conditions, initial conditions and forcing. In CMS-Flow the Control File is the *.cmcards (card) file. The ASCII file uses a simple card format to specify model input in free format. Data Input Files depend on the specific model setup, and may include but are not limited to spatially variable
 
Grid File (*_grid.h5)
Control files are used for specifying input parameters, options, and boundary conditions, initial conditions and forcing. In CMS-Flow the Control File is the *.cmcards (card) file. The ASCII file uses a simple card format to specify model input in free format. Data Input Files depend on the specific model setup, and may include but are not limited to spatially variable.
 
=Grid File (*_grid.h5)=
 
The SMS interface can save a scatter set in a binary format called the eXtensible Model Data Format (XMDF). The XMDF format (Butler et al. 2007) stores data in a much smaller file and decreases the time to load large data files, such as SHOALS or LIDAR surveys. Operation in XMDF format rather than ASCII for-mat greatly reduces time of input and output operations.
The SMS interface can save a scatter set in a binary format called the eXtensible Model Data Format (XMDF). The XMDF format (Butler et al. 2007) stores data in a much smaller file and decreases the time to load large data files, such as SHOALS or LIDAR surveys. Operation in XMDF format rather than ASCII for-mat greatly reduces time of input and output operations.
Model Parameters File (*_mp.h5)
TBC


SMS XY Series File (*.xys)
=Model Parameters File (*_mp.h5)=
TBC
<span style="color:#FF0000">TBC</span>
 
=SMS XY Series File (*.xys)=
<span style="color:#FF0000">TBC</span>
 
=SMS Time Series Data File (*.tsd)=
<span style="color:#FF0000">TBC</span>
 


SMS Time Series Data File (*.tsd)
=Note<nowiki>:</nowiki>=
TBC


Note:
:• It is recommended to use ANSI file encoding for all ASCII files. CMS has problems reading Unicode or other encodings.  
• It is recommended to use ANSI file encoding for all ASCII files. CMS has problems reading Unicode or other encodings.  
 
=CMS-Wave=
 
==CMS-Wave Spectral File (*.eng)==
<span style="color:#FF0000">TBC</span>
 
=CMS-Wave Model Parameters File (*.std)=


CMS-Wave
CMS-Wave Spectral File (*.eng)
TBC
CMS-Wave Model Parameters File (*.std)
Users can use SMS11 or higher versions, or simply edit the existing model control file *.std, to specify/select these advanced features.
Users can use SMS11 or higher versions, or simply edit the existing model control file *.std, to specify/select these advanced features.
The *.std has a maximum of 24 parameters - the first 15 parameters are more the basic ones as described in the CMS-Wave Technical Report (CHL-TR-08-13) while the remaining 9 parameters are relatively new for advanced CMS-Wave features.
The *.std has a maximum of 24 parameters - the first 15 parameters are more the basic ones as described in the CMS-Wave Technical Report (CHL-TR-08-13) while the remaining 9 parameters are relatively new for advanced CMS-Wave features.


table ?
table ?

Revision as of 20:01, 2 May 2015

11 Appendix A: Description of Input Files

CMS-Flow

Telescoping Grid File (*.tel)

The telescoping Grid File is saved in SMS 11.0 when saving a telescoping grid. The first line contains a header which says “CMS-Telescoping”. The second line contains four elements corresponding to the (1) grid orientation theta, (2) grid origin in the x-direction x0, (3) grid origin in the y-direction y0, and (4) total number of cells N (including inactive cells). Lines 3 through N+3 contain the following column data:

table a1

Notes:

• Directions of neighboring cells are relative to the local grid axis (i.e. positive in x = East, negative in x = West, positive in y = North, and negative in y = South).
• Indexes equal to 0 indicate the absence of a neighboring cell.
• If a cell is assigned as an inactive cell, -999
• Because the file is ASCII, the file size can be relatively large and difficult to view in WordPad or Notepad. To view the telescoping grid file, it is recommended to use a more advanced text editor such as UltraEdit or Textpad.

An example of the first 6 lines of a CMS-Flow telescoping grid file is pro-vided below. _

example

A simple Matlab script is provided below to read the *.tel file.

matlab script

Card (Control) File

Control files are used for specifying input parameters, options, and boundary conditions, initial conditions and forcing. In CMS-Flow the Control File is the *.cmcards (card) file. The ASCII file uses a simple card format to specify model input in free format. Data Input Files depend on the specific model setup, and may include but are not limited to spatially variable.

Grid File (*_grid.h5)

The SMS interface can save a scatter set in a binary format called the eXtensible Model Data Format (XMDF). The XMDF format (Butler et al. 2007) stores data in a much smaller file and decreases the time to load large data files, such as SHOALS or LIDAR surveys. Operation in XMDF format rather than ASCII for-mat greatly reduces time of input and output operations.

Model Parameters File (*_mp.h5)

TBC

SMS XY Series File (*.xys)

TBC

SMS Time Series Data File (*.tsd)

TBC


Note:

• It is recommended to use ANSI file encoding for all ASCII files. CMS has problems reading Unicode or other encodings.

CMS-Wave

CMS-Wave Spectral File (*.eng)

TBC

CMS-Wave Model Parameters File (*.std)

Users can use SMS11 or higher versions, or simply edit the existing model control file *.std, to specify/select these advanced features.

The *.std has a maximum of 24 parameters - the first 15 parameters are more the basic ones as described in the CMS-Wave Technical Report (CHL-TR-08-13) while the remaining 9 parameters are relatively new for advanced CMS-Wave features.

table ?