Files
ThirdParty-6/scotch_6.0.6/man/man1/mmk_m2.1
Henry Weller 95d9c7802c scotch: Upgraded to latest version
Avoids problems compiling with MPI-3.0
See https://bugs.openfoam.org/view.php?id=3216
2019-04-08 10:58:53 +01:00

56 lines
1.5 KiB
Groff
Raw Permalink Blame History

This file contains invisible Unicode characters

This file contains invisible Unicode characters that are indistinguishable to humans but may be processed differently by a computer. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

." Text automatically generated by txt2man
.TH mmk_m2 1 "August 03, 2010" "" "Scotch user's manual"
.SH NAME
\fBmmk_m2, mmk_m3 \fP- create source meshes
\fB
.SH SYNOPSIS
.nf
.fam C
\fBmmk_m2\fP [\fIoptions\fP] [\fB-g\fP\fIcfile\fP] \fIdimX\fP \fIdimY\fP [\fIofile\fP]
.PP
\fBmmk_m3\fP [\fIoptions\fP] [\fB-g\fP\fIcfile\fP] \fIdimX\fP \fIdimY\fP \fIdimZ\fP [\fIofile\fP]
.fam T
.fi
.SH DESCRIPTION
The \fBmmk_\fP* programs create source mesh files for some common,
regular topologies.
.PP
\fBmmk_m2\fP creates a 2D regular mesh of \fIdimX\fP times \fIdimY\fP elements and
(\fIdimX\fP+1) times (\fIdimY\fP+1) nodes, such that element (i,j) is
connected to nodes (i,j), (i,j+1), (i+1,j) and (i+1,j+1).
.PP
\fBmmk_m3\fP creates a 3D regular mesh of \fIdimX\fP times \fIdimY\fP times \fIdimZ\fP
elements and (\fIdimX\fP+1) times (\fIdimY\fP+1) times (\fIdimZ\fP+1) nodes,
such that element (i,j,k) is connected to nodes (i,j,k), (i,j,k+1),
(i,j+1,k), (i,j+1,k+1), (i+1,j,k), (i+1,j,k+1), (i+1,j+1,k) and
(i+1,j+1,k+1).
.SH OPTIONS
.TP
.B
\fB-g\fP\fIcfile\fP
Output graph vertex coordinates (that is, geometry data to be used by
\fBgout\fP(1)) in file \fIcfile\fP.
.TP
.B
\fB-h\fP
Display some help.
.TP
.B
\fB-V\fP
Display program version and copyright.
.SH EXAMPLE
Create a mesh of 5x7 elements, along with its geometry:
.PP
.nf
.fam C
$ mmk_m2 5 7 -g/tmp/m5x7.xyz /tmp/m5x7.msh
.fam T
.fi
.SH SEE ALSO
\fBmord\fP(1), \fBmtst\fP(1), \fBgmk_msh\fP(1).
.PP
Scotch user's manual.
.SH AUTHOR
Francois Pellegrini <francois.pellegrini@labri.fr>