CMS-PTM: Difference between revisions

From CIRPwiki
Jump to navigation Jump to search
No edit summary
No edit summary
Line 14: Line 14:
The CMS calculates water levels, currents and waves through the coupling of a hydrodynamic model, CMS-Flow and a wave spectral model, CMS-Wave.  CMS-Flow is driven by time-dependent water surface elevation at the offshore open boundaries, and wind forcing over the surface boundary. Directional wave data for input to CMS-Wave are available from the National Data Buoy Center (NDBC, http://www.ndbc.noaa.gov) and Coastal Data Information Program (CDIP, http://cdip.ucsd.edu). The wave conditions are specified at the seaward boundaries.  
The CMS calculates water levels, currents and waves through the coupling of a hydrodynamic model, CMS-Flow and a wave spectral model, CMS-Wave.  CMS-Flow is driven by time-dependent water surface elevation at the offshore open boundaries, and wind forcing over the surface boundary. Directional wave data for input to CMS-Wave are available from the National Data Buoy Center (NDBC, http://www.ndbc.noaa.gov) and Coastal Data Information Program (CDIP, http://cdip.ucsd.edu). The wave conditions are specified at the seaward boundaries.  


CMS-Flow requires three input files and CMS-Wave requires six input files through the SMS. Each of CMS-Flow and CMS-Wave simulations will generate its own output file (Figure 2).  
CMS-Flow requires three input files and CMS-Wave requires six input files through the SMS. Each of CMS-Flow and CMS-Wave simulations will generate its own output file (Figure 2). The CMS-Flow input and output files are required, while the CMS-Wave output files are optional for setting up a CMS-PTM simulation. After loading the required hydrodynamic and/or wave files, users can follow the steps below to set up the CMS-PTM simulation for the Noyo application.
 
{{Image|Slide2.png|150px|'''Figure 2. CMS files.'''}}  
{{Image|Slide2.png|150px|'''Figure 2. CMS files.'''}}  
* '''Native Sediment Dataset'''  CMS-PTM requires spatially varying native bed sediment data specified as datasets, including the grain size information of d35, d50, and d90 for each cell, in the CMS-Flow grid.
* '''Native Sediment Dataset'''  CMS-PTM requires spatially varying native bed sediment data specified as datasets, including the grain size information of d35, d50, and d90 for each cell, in the CMS-Flow grid.

Revision as of 20:21, 15 November 2010

Case Studies / Sample Problems

The following tutorials may be helpful for learning to use CMS-PTM in SMS:

Noyo Nearshore Sediment Placement Pilot Study

Noyo Harbor and Noyo River are located on the northern California coast. Every year about 30,000-40,000 cy of beach-quality sediment is dredged from the Noyo River Federal Navigation Channel. The USACE San Francisco District (SPN) and the Coastal and Hydraulics Laboratory (CHL), U.S. Army Engineer Research and Development Center are presently collaborating with the Noyo Harbor District and stakeholders in a pilot study to investigate a potential candidate site for nearshore placement of dredged sediment. Upland disposal sites used in the past will soon be exceeded. The pilot study proposes a dispersive nearshore site 3 to 8 miles north of Noyo Bay along the northern California coast (Figure 1).

Figure 1. CMS domain, grid, and bathymetry.

To evaluate the potential impacts of nearshore placement, the CMS and CMS-PTM were applied to simulate sediment transport for combined waves and currents under various ambient conditions and project alternatives. The model results will provide the technical information necessary to evaluate a demonstration site that is economically feasible for the optimum sediment placement location.

CMS-PTM

The CMS calculates water levels, currents and waves through the coupling of a hydrodynamic model, CMS-Flow and a wave spectral model, CMS-Wave. CMS-Flow is driven by time-dependent water surface elevation at the offshore open boundaries, and wind forcing over the surface boundary. Directional wave data for input to CMS-Wave are available from the National Data Buoy Center (NDBC, http://www.ndbc.noaa.gov) and Coastal Data Information Program (CDIP, http://cdip.ucsd.edu). The wave conditions are specified at the seaward boundaries.

CMS-Flow requires three input files and CMS-Wave requires six input files through the SMS. Each of CMS-Flow and CMS-Wave simulations will generate its own output file (Figure 2). The CMS-Flow input and output files are required, while the CMS-Wave output files are optional for setting up a CMS-PTM simulation. After loading the required hydrodynamic and/or wave files, users can follow the steps below to set up the CMS-PTM simulation for the Noyo application.

Figure 2. CMS files.
  • Native Sediment Dataset CMS-PTM requires spatially varying native bed sediment data specified as datasets, including the grain size information of d35, d50, and d90 for each cell, in the CMS-Flow grid.
  1. Select and open the CMS-Flow control file, “flow-exist-Alt2.cmcards” (Figure 2),
  2. Choose Data | Data Calculator in the CMS-Flow menu,
  3. Name the first dataset, d35, in the Output data set name and specify a constant value, 0.1 mm in the Calculator,
  4. Click Compute to generate the dataset,
  5. Repeat steps iii) and iv) to generate the datasets for d50 and d90 (Figure 3), (for the Noyo simulation, d50=0.2 mm and d90=0.4 mm)
  6. Click Done to exit Data Calculator,
  7. Highlight the datasets, d35, d50, and d90, right-click, and select Export Datasets (Figure 4),
  8. Select XMDF file in the File Type, check All time steps in the Time Steps, and click the Filename to save the file “NativeSediments.h5” in the present working folder.