This utility constructs meshes indicating structure of local hex modification
operations developed by Tautges.

Usage: hexmodops [-h5m] [-vtk] {-ap | -foc | -fs | -cp | -tcp | -thp}

-h5m: Output results to h5m file
-vtk: Output results to vtk file

-ap: Atomic pillow operation
-foc: Face open-collapse operation
-fs: Face shrink operation
-cp: Chord push operation
-tcp: Triple chord-push operation
-thp: Triple hex-push operation

See mbconvert.man in this directory.

List all entity types defined in a file, inlucing the count of entities
statistics regarding entity sizes.

Usage: ../../para/tools/mbsize [-g] [-m] [-t|-l|-ll] <mesh file list>

Modes:
(default) : list entity measurement statistics
-t        : list tags and counts of entity types by tag
-l        : list counts of entity types
-ll       : verbose listing of every entity

Grouping:
(default) : list data for each input file
-g        : list data for each geometric topology set
-m        : list data for each material and bounary conditon set

This is a utility for generating input files for testing Mesquite
(MESh QUality Improvement Toolkit).  The CL arguments to the utilty
are a single input file and a single outpute file.  The utility
does the following:
  o Read input file
  o Find the set of all elements of the highest dimension
    (e.g. all volume elements if there are any, otherwise
     all face elements.)
  o Generate the skin of that set of elements.
  o Create an integer tag named "fixed"
  o Set the tag to zero on all interior vertices and one
    on all vertices in the skin of the mesh
  o Write out the set of elements

This utility plots the mesh of a single geometric surface projected to
a plane.  The output file is written to stdout.

Usage:
surfplot [-g|-p] <Surface_ID> <input_file>
-g           -  Write GNU Plot data file (default).
-p           -  Write encapsulated postscript file
-s           -  Write an SVG file
<Surface_ID> -  ID of surface containing mesh to export.
<input_file> -  Mesh file to read.

Usage:
tagprop <options> <input_file> <output_file>
Options:
  -t <ident_tag>[=<value>]
  -d <data_tag>[=<default>]
  -c <data_tag=type:size>[=defult]
  -w <write_tag>
  -n|-e

At least one ident_tag must be specified.  This tag will be used to
select entity sets to process.  If more than one ident_tag is
specified, entity sets that match A\bAN\bNY\bY the specified tags will
be selected (logical OR).  A tag value to match may optionally be
specified for each ident_tag.

The data_tag is the tag on the selected entity sets for which the
value should be propogated to the contained mesn entities.  If no
data_tag is specified, the value of the ident_tag will be used.  If
multiple ident_tags are specified, the data_tag must be specified
explicitly.  If the data tag is specified with the '-d' option, the
tag must exist and the optional value will be set on any entiites for
which the owning set doesn't have the data_tag defined.  If the
data_tag is specified with the '-c' option, the tag will be created.

If the write_tag is specified, the tag propogated to the mesh entities
contained in the set will be given this name.  If no write_tag is
specified, the data_tag will be used.

If -\b-n\bn is specified, the tag values will be propogated only to
nodes contained in the identified sets.  If -\b-e\be is specified, the
tags will be propogated to the contained elements.  If neither is
specified, the default is both.

The syntax for specifying tag values is as follows: Tags are specified
as <name>=[value], where the tag value is optional.  For opaque tags,
a numeric value may be specified in hexadecimal with a '0x' prefix.
If the value does not begin with the '0x' prefix, it will be treated
as a string (not a numerical value) and padded with NULL characters to
fit the tag size.

For integral types (INTEGER, BIT, and HANDLE), values are parsed as
integers with the standard 0x and 0 prefixes for hexidecimal and octal
bases, respectively.

DOUBLE types must be specified in base-10.  Exponential syntax (e) is
accepted.

If the tag is not opaque and is an array of values, the values must be
specified as a comma-separated list w/out spaces.

Tags are created with the form name=type:size[=default_value] where
type is one of {int,double,opaque,handle,bit} and size is the number
of values of the specified type, or the number of bytes if the type is
'opaque', A default value for the tag make be specified.

This tool constructs an all-hex mesh for a set of spheres embedded in
a substrate.  The sphere locations and radii are specified as a set of
vertices and tags on those vertices.  The vertices are triangulated
with a tet mesh, then each tet is subdivided such that the spherical
surface around each vertex is resolved.  The current subdivision
method used is to split each corner region (the part inside the
sphere) with four hexes, using a standard tetrahedron primitive, and
to split the remaining "interstices" region using a midpoint
subdivision on the tet with corner spheres removed.  This results in
28 hexes per tetrahedron, with 16 of those inside the 4 sphere regions
and 12 hexes in the interstices.

This directory contains miscellaneous tools built on MOAB.  Some of
them, like convert and size, are useful examples of how to write MOAB
applications.  Others, like mbzoltan, are useful both as standalone
tools and as functionality to include in other applications.

Brief description of tools below this directory:
converter: converts mesh between any two formats read/written by MOAB
hexmodops: dual-based hex meshing research support
mbchaco: static partitioner based on Sandia CHACO library
mbzoltan: static and dynamic partitioner / load balancer, based on
  Sandia Zoltan library
mcnpmit: tool to interpolate .unv meshes on MCNP meshtal files
qvdual: mesh visualization tool, based on Qt and Vtk; can visualize
  hex mesh dual, among other things
size: reads mesh and prints size by geometric owner or block/boundary
skin: computes and outputs mesh skin
spheredecomp: decompose a tet mesh into hex elements which resolve
  spheres centered at vertices
surfplot: plot the mesh of a geometric surface projected to a plane
tagprop: propagate tags from entity sets to entities in those sets
vtkMOABReader: MOAB reader plugin for VTK



There are two ways a tool can be configured by:
 1) the main MOAB configure script directly
 2) its own configure script, called by the main MOAB one



Method 1:
---------

1) Create a Makefile.am in the directory.  See converter/Makefile.am as
   an example.

2) Add a call in the main MOAB configure.in to the MB_OPTIONAL_TOOL macro
   with three arguments:
     a) The name of the tool
     b) an empty string (two brackets: [])
     c) either "[yes]" or "[no]" indicating if the tool is to be build by default

3) Add the Makefile to the list of files passed to AC_CONFIG_FILES at the
   end of the main MOAB configure.in (e.g. tools/<dir>/Makefile)

4) Add a conditional to the tools/Makefile.am file for the tool:
     if ENABLE_<name>
       SUBDIRS += <dir>
     endif
   Where <name> is the name specified in the MB_OPTIONAL_TOOL macro and
   <dir> is the subdirectory, as specified in the AC_CONFIG_FILES macro.



Method 2:
---------

1) Create makefiles, configure scripts, etc for tool.

2) Add a call in the main MOAB configure.in to the MB_OPTIONAL_TOOL macro
   with three arguments:
     a) The name of the tool
     b) The path to the tool (e.g: [tools/<dir>])
     c) either "[yes]" or "[no]" indicating if the tool is to be build by default

3) Add a conditional to the tools/Makefile.am file for the tool:
     if ENABLE_<name>
       SUBDIRS += <dir>
     endif
   Where <name> and <dir> match the values specified for the MB_OPTIONAL_TOOL
   macro.