Module Sand - Revision history

Paulochambel: /* Connect the bed load transport */

2011-07-13T17:33:11Z

‎Connect the bed load transport

Paulochambel at 02:59, 15 March 2011

2011-03-15T02:59:44Z

Paulochambel at 02:21, 15 March 2011

2011-03-15T02:21:34Z

Paulochambel at 02:20, 15 March 2011

2011-03-15T02:20:24Z

Paulochambel at 13:30, 8 March 2011

2011-03-08T13:30:32Z

Paulochambel at 13:22, 8 March 2011

2011-03-08T13:22:43Z

Luisfernandes: /* Maps (HDF5 format) */

2011-03-08T11:58:55Z

‎Maps (HDF5 format)

Luisfernandes: /* Time series */

2011-03-08T11:58:31Z

‎Time series

Luisfernandes: /* Advanced options */

2011-03-08T11:57:32Z

‎Advanced options

Luisfernandes: /* Main options */

2011-03-08T11:54:08Z

‎Main options

← Older revision		Revision as of 17:33, 13 July 2011
Line 28:		Line 28:

	SAND_TRANSPORT : 1		SAND_TRANSPORT : 1
		+
		+	If the user choose bed load transport formulations dependent of wave parameters needs also to define the follow keywrods:
		+
		+	WAVETENSION : 1
		+
		+	<begin_waverugosity>
		+	DEFAULTVALUE : 0.002
		+	<end_waverugosity>
		+

	The user needs also to add the follow keywords in the bathymetry file (see - [[Bathymetry]]). Keyword EVOLUTION used to activate the ability of the [[Module GridData]] to write the bathymetry evolution in a [[HDF5]] file and read also from a [[HDF5]] (important for the hot start runs). The keyword EVOLUTION_FILE is used to define the [[HDF5]] filename. The keyword PROPERTY_NAME is used to associate a name to the bathymetry array to be stored in the [[HDF5]] file.		The user needs also to add the follow keywords in the bathymetry file (see - [[Bathymetry]]). Keyword EVOLUTION used to activate the ability of the [[Module GridData]] to write the bathymetry evolution in a [[HDF5]] file and read also from a [[HDF5]] (important for the hot start runs). The keyword EVOLUTION_FILE is used to define the [[HDF5]] filename. The keyword PROPERTY_NAME is used to associate a name to the bathymetry array to be stored in the [[HDF5]] file.

@@ Line 1: / Line 1: @@
 == Overview ==
-Module Sand was the result of the accumulated experience gain by Hidromod in the framework of many engineering projects [http://www.hidromod.pt]. Many of the projects were done with a old MOHID version programmed in F77. More recently Hidromod develop a new Module using the present [[Mohid Programming]] philosophy. The concepts of this module were described an tested in detail by Carmo (2005) see [http://www.mohid.com/PublicData/products/Thesis/TFC_miguelcarmo.pdf]. However, if the user wants to know exactly what this module is doing it can take a look at the source code (see - [http://mohid.codeplex.com/SourceControl/changeset/view/63225#1208126]).
+Module Sand was the result of the accumulated experience gain by Hidromod in the framework of many engineering projects [http://www.hidromod.pt]. Many of the projects were done with a old MOHID version programmed in F77. More recently Hidromod develop a new Module using the present [[Mohid Programming]] philosophy. The concepts of this module were described an tested in detail by Carmo (2005) (see [http://www.mohid.com/PublicData/products/Thesis/TFC_miguelcarmo.pdf] in Portuguese). However, if the user wants to know exactly what this module is doing it can take a look at the source code (see - [http://mohid.codeplex.com/SourceControl/changeset/view/63225#1208126]).
 === Algorithm  ===
 From a conceptual point of view this module is very simple. The bed load fluxes are computed in a Arakawa-C grid [http://en.wikipedia.org/wiki/Arakawa_grids#Arakawa_C-grid]. In each centre cell (Z point) the transport flow is computes. In order to compute the transport flows the user can choose from a set of formulations presented below. In a second step the Zonal (or X) component flows are interpolated to the U points and the meridional (or Y) components are interpolated to the V points.

@@ Line 94: / Line 94: @@
   SAND_MIN : 0.01
-The field properties D90, D50, D35 and bed rock are defined using the options available in [[Module Fillmatrix]].
+The field properties D90, D50, D35 and bed rock are defined using the options available in [[Module FillMatrix]].
 == Advanced options ==

@@ Line 23: / Line 23: @@
 Bailard (1981,1984)
 Dibajnia (1992)
 == Main options ==
 In this section the available options in Module Sand are briefly described. The different options provided by the module can be defined through an input data file, similarly to other MOHID modules. The name of the Module Sand for run number x is Sand_x.dat (see [[Mohid GUI]])
@@ Line 37: / Line 49: @@
   BATHYM_EVOLUTION : 1
   BATIM_DT         : 60.
 Regarding keywords used to define boundary conditions, the keyword BOUNDARY is used to define the open boundary condition. The options are 1 (null gradient) and 2 (cyclic boundary - used in academic studies mainly). The keyword DISCHARGES is used to activate a set of sinks or sources of sediments (0 - OFF, 1 - ON). These sinks/sources of sediments are defined in the discharge_x.dat input file see [[Module Discharges]]. To define a set of sinks/sources of sediments see [[How to create discharges in MOHID]].

@@ Line 1: / Line 1: @@
 == Overview ==
-Module Sand was the result of the accumulated experience gain by Hidromod in the framework of many engineering projects. Many of the projects were done with a old MOHID version programmed in F77. More recently Hidromod develop a new Module using the present [[Mohid Programming]] philosophy. The concepts of this module were described an tested in detail by Carmo (2005) see [http://www.mohid.com/PublicData/products/Thesis/TFC_miguelcarmo.pdf]. However, if the user wants to know exactly what this module is doing it can take a look at the source code (see - [http://mohid.codeplex.com/SourceControl/changeset/view/63225#1208126]).
+Module Sand was the result of the accumulated experience gain by Hidromod in the framework of many engineering projects [http://www.hidromod.pt]. Many of the projects were done with a old MOHID version programmed in F77. More recently Hidromod develop a new Module using the present [[Mohid Programming]] philosophy. The concepts of this module were described an tested in detail by Carmo (2005) see [http://www.mohid.com/PublicData/products/Thesis/TFC_miguelcarmo.pdf]. However, if the user wants to know exactly what this module is doing it can take a look at the source code (see - [http://mohid.codeplex.com/SourceControl/changeset/view/63225#1208126]).
 === Algorithm  ===
 From a conceptual point of view this module is very simple. The bed load fluxes are computed in a Arakawa-C grid [http://en.wikipedia.org/wiki/Arakawa_grids#Arakawa_C-grid]. In each centre cell (Z point) the transport flow is computes. In order to compute the transport flows the user can choose from a set of formulations presented below. In a second step the Zonal (or X) component flows are interpolated to the U points and the meridional (or Y) components are interpolated to the V points.

@@ Line 110: / Line 110: @@
   TAU_MAX = 10.
-To help improve the model performance it the concept of lateral transport was implemented (SMOOTH_SLOP : 0 - OFF, 1 - ON). In this case, it is assumed that when the bathymetry gradient perpendicular to the main bed load flow is above a critical slope (CRITICAL_SLOP) there is a flow in this direction. This bed load flow is equal to a percentage (FLUX_SLOP) of the main flow. This perpendicular bed load flow tend to smooth the slopes. This is important in river flows where the bathymetry gradients perpendicular to the main flow can be very steep.
+To help improve the model performance it the concept of lateral transport was implemented (SMOOTH_SLOPE : 0 - OFF, 1 - ON). In this case, it is assumed that when the bathymetry gradient perpendicular to the main bed load flow is above a critical slope (CRITICAL_SLOPE) there is a flow in this direction. This bed load flow is equal to a percentage (FLUX_SLOPE) of the main flow. This perpendicular bed load flow tend to smooth the slopes. This is important in river flows where the bathymetry gradients perpendicular to the main flow can be very steep.
-  SMOOTH_SLOP : 0
+  SMOOTH_SLOPE : 0
-  CRITICAL_SLOP : 0.1
+  CRITICAL_SLOPE : 0.1
-  FLUX_SLOP : 0.1
+  FLUX_SLOPE : 0.1
 == Outputs ==

@@ Line 139: / Line 139: @@
 === Maps (HDF5 format) ===
-The user can also do output of the most signifcant properties fields related with bed load following the standard methodology used in the other MOHID modules (see [[OUTPUT TIME]]).
+The user can also make outputs of the most significant properties fields related with bed load following the standard methodology used in the other MOHID modules (see [[OUTPUT TIME]]).
-For example, if a user wants field results every hour starting from the beginning of the run it needs to define the follow (time is seconds).
+For example, if a user wants field results every hour starting from the beginning of the run it needs to define the following (time is seconds).
    OUTPUT_TIME : 0. 3600.

@@ Line 131: / Line 131: @@
 === Time series ===
-The user can also do output of the most signifcant properties in a point related with bed load following the standard methodology used in the other MOHID modules (see [[Module TimeSerie]]).
+The user can also make outputs of the most significant properties in a point related with bed load following the standard methodology used in the other MOHID modules (see [[Module TimeSerie]]).
-For example, if a user wants to activate the output time series option needs to add to the input file (Sand_x.dat) the follow keyword:
+For example, if a user wants to activate the output time series option needs to add to the input file (Sand_x.dat) the following keyword:
    TIME_SERIES : 1

@@ Line 92: / Line 92: @@
 == Advanced options ==
-The follow keywords are used to convert sediments from mass per sqaure meter in meters (POROSITY - porosity and DENS_SAND - sand density).
+The following keywords are used to convert sediments from mass per square meter in meters (POROSITY - porosity and DENS_SAND - sand density).
   POROSITY : 0.1
   DENS_SAND : 2650.
-The follow keywords are used to smooth the solution. The transport formulas are highly non-linear and tend to generate very noisy solutions. Keyword - FILTER_SCHEME, options: No Filter (filter OFF), Modify Lax (filter ON). This filter distributes 50% of the bathymetry evolution in the adjecent cells. The keyword FILTER_RADIUS is used to define the radius (in number of cells) that is used to define the adjcent areas under the effect of sediment redistribution.
+The following keywords are used to smooth the solution. The transport formulas are highly non-linear and tend to generate very noisy solutions. Keyword - FILTER_SCHEME, options: No Filter (filter OFF), Modify Lax (filter ON). This filter distributes 50% of the bathymetry evolution in the adjacent cells. The keyword FILTER_RADIUS is used to define the radius (in number of cells) that is used to define the adjacent areas under the effect of sediment redistribution.
   FILTER_SCHEME : No Filter
   FILTER_RADIUS : 4
+Another option is to use a factor to speed up morphodynamic processes. This factor must be used with caution. This factor multiplies by the transport loads
   TRANSPORT_FACTOR : 1.
-The maximum limit for the bottom shear stress used in the Meyer Peter formula can be defined with the follow keyword:
+The maximum limit for the bottom shear stress used in the Meyer Peter formula can be defined with the following keyword:
   TAU_MAX = 10.
-To help improve to model performance it was implemented the concept of lateral transport (SMOOTH_SLOP : 0 - OFF, 1 - ON). In this case is assumed when the bathymetry gradient perpendicular to the main bed load flow is above a critical slop (CRITICAL_SLOP) there is a flow in this direction. This bed load flow is equal to a percentage (FLUX_SLOP) of the main flow. This perpendicular bed load flow tend to smooth the slopes. This is important in river flows where the bathymetry gradients perpendicular to the main flow can be very steep.
+To help improve the model performance it the concept of lateral transport was implemented (SMOOTH_SLOP : 0 - OFF, 1 - ON). In this case, it is assumed that when the bathymetry gradient perpendicular to the main bed load flow is above a critical slope (CRITICAL_SLOP) there is a flow in this direction. This bed load flow is equal to a percentage (FLUX_SLOP) of the main flow. This perpendicular bed load flow tend to smooth the slopes. This is important in river flows where the bathymetry gradients perpendicular to the main flow can be very steep.
   SMOOTH_SLOP : 0

@@ Line 25: / Line 25: @@
 == Main options ==
-In this section it is briefly described the options available in Module Sand. The different options provided by the module can be defined through an input data file, similarly to other MOHID modules. The name of the Module Sand for run number x is Sand_x.dat (see [[Mohid GUI]])
+In this section the available options in Module Sand are briefly described. The different options provided by the module can be defined through an input data file, similarly to other MOHID modules. The name of the Module Sand for run number x is Sand_x.dat (see [[Mohid GUI]])
-Keyword TRANSPORT_METHOD  is used to choose from the list presented above the transport formula the user wants to test. The options are: no transport, MeyerPeter, Ackers, VanRijn1, VanRijn2, Bailard, Dibajnia, Bijker. Keyword SAND_DT is the time step used to compute the transport formula by default is equal to the global model time step (see - [[Choose the model time step]]). The keyword OLD (0 - OFF; 1 - ON) is ON when the user wants to do a hot start (OFF - cold start).
+Keyword TRANSPORT_METHOD is used to choose the transport formula the user wants to test from the list presented above. The options are: no transport, MeyerPeter, Ackers, VanRijn1, VanRijn2, Bailard, Dibajnia, Bijker. Keyword SAND_DT is the time step used to compute the transport formula and by default it is equal to the global model time step (see - [[Choose the model time step]]). The keyword OLD (0 - OFF; 1 - ON) is ON when the user wants to do a hot start (OFF - cold start).
   TRANSPORT_METHOD : MeyerPeter
@@ Line 33: / Line 33: @@
   OLD              : 0
-The user can choose if the compute bed loads change or not the bathymetry and consequently the hydrodynamics. If the user wants to take in consideration the effect of bathymetry changes in the other Mohid modules than BATHYM_EVOLUTION : 1. The keyword BATIM_DT is used to define the frequency of actualization of the model bathymetry by default is equal to the global model time step (see - [[Choose the model time step]]).
+The user can choose if the compute bed loads change or not the bathymetry and consequently the hydrodynamics. If the user wants to take in consideration the effect of bathymetry changes in the other Mohid modules then the keyword BATHYM_EVOLUTION : 1 must be defined. The keyword BATIM_DT is used to define the update frequency of the model bathymetry and by default is equal to the global model time step (see - [[Choose the model time step]]).
   BATHYM_EVOLUTION : 1
   BATIM_DT         : 60.
-If the bathymetry evolution option is ON the user needs to add the follow keywords in the bathymetry file (see - [[Bathymetry]]). Keyword EVOLUTION used to activate the ability of the [[Module GridData]] to write the bathymetry evolution in a [[HDF5]] file and read also from a [[HDF5]] (important for the hot start runs). The keyword EVOLUTION_FILE is used to define the [[HDF5]] filename. The keyword PROPERTY_NAME is used to associate a name to the bathymetry matrixes to be store in the [[HDF5]] file.
+If the bathymetry evolution option is ON the user needs to add the follow keywords in the bathymetry file (see - [[Bathymetry]]). Keyword EVOLUTION used to activate the ability of the [[Module GridData]] to write the bathymetry evolution in a [[HDF5]] file and read also from a [[HDF5]] (important for the hot start runs). The keyword EVOLUTION_FILE is used to define the [[HDF5]] filename. The keyword PROPERTY_NAME is used to associate a name to the bathymetry array to be stored in the [[HDF5]] file.
   EVOLUTION      : 1
@@ Line 44: / Line 44: @@
   PROPERTY_NAME  : Bathymetry
-Keywords to define the boundary condtions. The keyword BOUNDARY is used to define the open boundary condition. The options are 1 (null gradient)and 2 (cyclic boundary - used in academic studies mainly). The keyword DISCHARGES is use to activate a set of sinks or sources of sediments (0 - OFF, 1 - ON). These sikns/sources of sediments are define in the discharge_x.dat input file see [[Module Discharges]]. To define a set of sinks/sources of sediments see [[How to create discharges in MOHID]].
+Regarding keywords used to define boundary conditions, the keyword BOUNDARY is used to define the open boundary condition. The options are 1 (null gradient) and 2 (cyclic boundary - used in academic studies mainly). The keyword DISCHARGES is used to activate a set of sinks or sources of sediments (0 - OFF, 1 - ON). These sinks/sources of sediments are defined in the discharge_x.dat input file see [[Module Discharges]]. To define a set of sinks/sources of sediments see [[How to create discharges in MOHID]].
   BOUNDARY : 1
@@ Line 50: / Line 50: @@
   DISCHARGES : 0
-The follow keywords are used to define the sediments diameter. This are one of the main inputs of transport formulas.
+The following keywords are used to define the sediments diameter. These are one of the main inputs of transport formulas.
   <beginD90>
@@ Line 59: / Line 59: @@
   FILENAME              : D90Field.dat
   <endD90>
   <beginD50>
   NAME                  : D50
@@ Line 66: / Line 67: @@
   FILENAME              : D50Field.dat
   <endD50>
   <beginD35>
   NAME                  : D35
@@ Line 74: / Line 76: @@
   <endD35>
-The follow keywords are used to define the sediments availability (bed rock concept). The SAND_MIN keyword is to define the limit (in meters) below which the transport stops to avoid sediment negative thicknesses.
+The following keywords are used to define the sediments availability (bed rock concept). The SAND_MIN keyword is to define the limit (in meters) below which the transport stops to avoid sediment negative thicknesses.
   <beginrock>
@@ Line 83: / Line 85: @@
   FILENAME              : BedRock.dat
   <endrock>
   SAND_MIN : 0.01
 The field properties D90, D50, D35 and bed rock are defined using the options available in [[Module Fillmatrix]].
 == Advanced options ==