Skip to content

update gmsh2nek.rst for input for solid mesh. #137

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
yhaomin2007 wants to merge 1 commit into
base: master
Choose a base branch
from
Open

update gmsh2nek.rst for input for solid mesh. #137

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 5 additions & 2 deletions source/tools/gmsh2nek.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -32,12 +32,15 @@ The procedure for running ``gmsh2nek`` is simpler compared to ``exo2nek``.
The expected input steps are as follows:

* It will first ask you for the dimension of the mesh (either 2 or 3).
* Next, it will ask for the input Gmsh file.
* Next, it will ask for the input fluid Gmsh file.
The ``.msh`` extension is implied and should not be included.
* Then, it will ask if you have solid mesh (0 for no, 1 for yes)
* Input solid Gmsh file name if you need.
The ``.msh`` extension is implied and should not be included.
* The tool will then begin converting the mesh and will print a summary of the boundary IDs.
* Finally, it will ask for the number of periodic boundary pairs (see :ref:`gmsh_pbound` below).
If your mesh has none, simply enter 0.
* ``gmsh2nek`` will then output a new ``.re2`` file with the same file name as the input Gmsh file.
* Finally it will ask for the name of the output file. The .re2 extension is implied and should not be included.

An example is shown below with the expected user input highlighted.

Expand Down