ENF-G(1)

NAME

enf-g - convert an Elysium Neutral File (ENF) to a BRL-CAD database

On this page

SYNOPSIS
DESCRIPTION
OPTIONS
EXAMPLES
SEE ALSO
AUTHOR
COPYRIGHT
BUG REPORTS

SYNOPSIS

enf-g [-v] [-i starting_ident] [-t tolerance] [-l name_length_limit] [-n part_name_file] input_facets_file output.g

enf-g converts a tessellated input_facets_file in the Elysium Neutral File (ENF) format into a BRL-CAD output.g database. The input is expected to be the ASCII facet output produced by the Elysium enf2mxp tessellator. Each ENF part is written as a BOT primitive wrapped in a region, and the ENF assembly hierarchy is reproduced using combinations. When a part name mapping file is supplied, the original ENF part number is also recorded as a Part_No attribute on the resulting region or combination.

OPTIONS

-v: Enable verbose output, reporting each solid, region, and assembly as it is written.
-i starting_ident: Set the ident number assigned to the first region created. Each subsequent region’s ident is incremented by one. The default is 1000.
-t tolerance: Set the maximum distance (in mm) at which two vertices are treated as the same vertex. Must be greater than 0.0. The default is the BRL-CAD standard distance tolerance.
-l name_length_limit: Truncate generated BRL-CAD object names to at most this many characters. The value must be at least 5.
-n part_name_file: Read a part-number-to-name mapping from the named file. Each line holds a part number and a legal BRL-CAD object name separated by whitespace. Matching objects are renamed accordingly, while unmatched objects keep their ENF part number and trigger a warning. When this option is given, every resulting region and combination is tagged with its original ENF part number in a Part_No attribute.

EXAMPLES

Example 1. Convert an ENF facet file with a custom ident range and name mapping

enf-g -v -i 2000 -l 32 -n parts.map widget.enf widget.g

Converts widget.enf into widget.g, starting region idents at 2000, limiting object names to 32 characters, and renaming parts via the parts.map lookup table. The resulting database can then be inspected with mged(1) or rendered with rt(1).