2 Copyright (C) 2015-2016 EDF
4 This file is part of SALOME HYDRO module.
6 SALOME HYDRO module is free software: you can redistribute it and/or modify
7 it under the terms of the GNU General Public License as published by
8 the Free Software Foundation, either version 3 of the License, or
9 (at your option) any later version.
11 SALOME HYDRO module is distributed in the hope that it will be useful,
12 but WITHOUT ANY WARRANTY; without even the implied warranty of
13 MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
14 GNU General Public License for more details.
16 You should have received a copy of the GNU General Public License
17 along with SALOME HYDRO module. If not, see <http://www.gnu.org/licenses/>.
19 #########################################
21 #########################################
23 .. |HYDROSolver| image:: /../_static/HYDROSolver.png
28 .. |eficas_04| image:: /../_static/eficas_04.png
33 .. |genereCondlim| image:: /../_static/genereCondlim.png
36 .. |eficas_01| image:: /../_static/eficas_01.png
39 .. |eficas_02| image:: /../_static/eficas_02.png
42 .. |eficas_03| image:: /../_static/eficas_03.png
45 .. |eficas_20| image:: /../_static/eficas_20.png
48 .. |eficas_21| image:: /../_static/eficas_21.png
51 .. |eficas_22| image:: /../_static/eficas_22.png
54 .. |eficas_23| image:: /../_static/eficas_23.png
57 Once the mesh is generated with the altimetry data, it remains to define the nature of the boundary condition regions,
58 the values of the flow rate and water depth boundary conditions over time and all the physical and numerical model parameters.
59 The TELEMAC manual should be consulted for the parameter definitions.
61 This information is compiled in several text files (ASCII) that are now going to be generated or manually edited.
63 **The abovementioned files will be stored in the same directory as the mesh.**
65 You must activate the HYDROSOLVER module, through the scrolling list of imodules, or its icon in the banner: |HYDROSolver|.
66 The HYDROSOLVER module supports physico-numerical data setup and calculations for codes
67 TELEMAC and MASCARET and their couplings.
69 Characterization of boundary regions
70 ====================================
72 The boundary condition regions were defined in the previous
73 steps and are incorporated by named groups of mesh elements.
75 The *condlim.bcd* file associates specific types of boundary condition (inlet, outlet, wall, etc.) to each group.
76 Four integer values define a boundary condition type.
78 The first line indicates the number of boundary conditions defined and is followed by four lines:
79 one per boundary condition. Each line contains four integers (the type) as well as the name of the group.
81 This file caan be created with de command *Edit boundary conditions file* from *HYDROSOLVER* module.
83 The path of the MED file used must be defined as input, and the file path of the boundary condition fields as output.
84 The *Boundary condition file* entry is used only to read/edit an existing file.
86 You must select the boundary condition type on the upstream, downstream, left and right bank,
87 and do not put anything on the other groups.
91 The result file looks like this:
93 .. literalinclude:: ../condlim.bcd
96 * **Note**: It is no longer necessary to create the .cli file specified in the Telemac manual,
97 which lists all the boundary condition nodes with the types associated. This file is automatically generated.
99 Values of the discharge and water elevation boundary conditions
100 ===============================================================
102 The *init.lqd* file contains the values of the flow rate and water depth boundary conditions over time.
103 Reference should be made to the Telemac manual for more precise details on the file definition.
105 .. literalinclude:: ../init.lqd
108 Physical and numerical parameters of the simulation
109 ===================================================
111 The *init.cas* file lists the other files, which must be in the same directory.
112 It then gives the different physical and numerical parameters required for the simulation (calculation case).
113 As mentioned before, the Telemac manual should be consulted for the definition of these parameters.
115 * **Note**: for version 1.0 (March 2016), the presence of a Fortran file is compulsory, even if it only contains one comment line
116 (it is necessary to force the recompilation of the TELEMAC executable). In the init.cas file,
117 the comment in front of the FORTRAN FILE keyword must be deleted and the corresponding file created.
119 .. literalinclude:: ../init.cas
122 Steering file setup through EFICAS
123 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
125 There are 2 methods to perform this, with the module *HYDROSOLVER*:
127 * **with the menus:** in HYDRO menu, click on *Edit cas file*
131 * **with the icons:** When the Hydrosolver module is activated, new buttons appear in the toolbar.
132 Right click on Edit case file
136 Click New to create a case file.
140 Complete all red items. When a sub-heading or heading is complete it changes to green.
141 Some green items are setup with the default value but the user can overwrite them.
142 Save (regularly) the created case. To do this, go to *File/Save* or *Save as*
143 or click on the icon |eficas_04|.
144 The file will be saved as *.comm* or *.jdc*.
149 In thecentral interface, at the level of the heading, in the right-hand section entitled Settings *NOM DE RUBRIQUE*,
150 optional keywords appear and can be added to the corresponding sub-heading,
151 by double-clicking the square box in front of the keyword.
153 **Example:** To add the keyword *Control_section* in *Output_Files*. Double-click on the right:
157 It appears in the *Output_Files* sub-section. In the central screen, other keywords appears in the right part under the title
158 *Control_Section*. I can add them in the same way.
162 It is also possible to have the help of the keyword. To do this, simply move the mouse over the keyword and the help appears:
166 If you click on the keyword with the mouse the help appears at the bottom left:
170 **Parameters by section and sub-section**
172 In *Computation_Environment*, by default, we find:
174 * *Initialization*: concerns input data files such as the geometry file and the boundary conditions file.
175 To take the title into account, type the desired name and enter.
177 * *Restart*: to restart from a previous computation.
179 * *Output_files*: result files, listing and their options.
181 In *Hydro*, by default, we find:
183 * *Boundary_Conditions*: boundary condition files
184 (files for liquid boundaries, stage-discharge curves, prescribed elevation or flowrate…)
186 * *Physical_Parameters_Hydro*: Physical parameters for hydrodynamics. Waves, meteo, source terms…
188 * *Numerical_Parameters_Hydro*: Numerical parameters for hydrodynamics, linear system options.
190 In *General_Parameters*, by default, we find:
192 * *Debugger*: debugger mode or not.
194 * *Time*: time step, duration…
196 * *Location*: coordinates origin…
198 In *Numerical_Parameters*, by default, we find:
200 * *Solver_Info*: solver setup
202 * *Discretizations_Implicitation*: implicitation for depth, velocity, space discretization…
206 * *Advection_Info*: mass lumping, free surface gradient compatibility…
208 * *Diffusion*: velocity diffusion, option for velocity diffusion…
210 * *Automatic_Differentiation*
212 * *Advanced*: matrix storage, matrix-vector product…
214 **Developement in progress**
216 In the end, the user can choose from pre-filled "template case files". These include:
218 * A flood model case file,
220 * A maritime model case file,
222 * A thermal case model file.
226 :ref:`ref_exempleInondation`