The surfins2d and surfins3d executables take additional
arguments to specify the surface to insert and how to insert it. There
are more possible variations in 2D here than in 3D.
- [-z filename] Specify a file from which to read curve
data. This file is a .bdry file, like those read by tri.
- [-s string] Specify options for surface insertion. Similar
to the -O optimization string, this string is parsed internally.
- Anisotropic insertion.
- To use GRUMMP's anisotropic insertion
capabilities, include 'a' in the string.
- Quasi-structured mesh.
- If the 'q' flag is given, curve sampling
will take the quasi-structured nature of the initial background mesh
- Surface offsetting.
- Offset surfaces can be specified by a single
curve and offset distances, or by a sequence of curves. In either
variant, mesh points on the originally inserted curve are projected
onto nearby curves. Attempting projection with incompatible curves
will cause failure, so take care!
- This option uses a single curve and computes the
location of offset curves based on a given offset vector and number
of offset curves to produce. Use ``o curveIndex x dx
y dy n num''. Here, curveIndex tells which curve
in the file to use, (dx, dy) is an offset vector between
curves, and num gives the number of offset curves to add. Spaces
are optional, provided the string is enclosed in quotes on the command
- Given curves.
- This option selects among multiple curves within
the single .bdry file read. For example, p3c0c1c1c2c2c3 specifies
that the curves 0, 1, 2, and 3 in the input will be inserted using
projection of mesh points from curve 0 onto 1, 2, and 3.
- [-z filename] Specify a file from which to read surface
data. This file can be either an STL file or a file containing a list
of STL files (preceded by the number of files; see examples/3D/surfaceInsertion/offset_file.txt
for an example of the latter).
- [-s string] Specify options for surface insertion. The
only currently active possible contents for this string is: ``p#1s#2s#3...'',
where the letters are literals, and #1 etc represent integers. #1
tells how many surface pairs there are for which mesh topology from
one surface is projected to the next. Subsequent numbers give the
indices of pairs of surfaces in the list of STL files in the file
given by the -z option. Note that surfaces can be chained together:
the topology of surface 1 can be projected to surface 2 and then on
to surface 3 by specifying: -s ``p2s1s2s2s3'' on the command line.