MGED Tutorial

%

Start a “/bin/sh” shell process for the user. The mged prompt will be replaced by a system prompt for the shell, and the user may perform any legal shell commands. The mged process waits for the shell process to finish, which occurs when the user exits the shell. This only works in a command window associated with a tty (i.e., the window used to start mged in classic mode).

Examples:

mged> %

3ptarb [arb_name x1 y1 z1 x2 y2 z2 x3 y3 z3 x|y|z coord1 coord2 thickness]

Build an ARB8 shape by extruding a quadrilateral through a given thickness. The arguments may be provided on the command line; if they are not, they will be prompted for. The x1, y1, and z1 are the coordinates of one corner of the quadrilateral. x2, y2, z2, and x3, y3, z3 are the coordinates of two other corners. Only two coordinates of the fourth point are specified, and the code calculates the third coordinate to ensure all four points are coplanar. The x|y|z parameter indicates which coordinate of the fourth point will be calculated by the code. The coord1 and coord2 parameters supply the other two coordinates. The direction of extrusion for the quadrilateral is determined from the order of the four resulting points by the right-hand rule; the quadrilateral is extruded toward a viewer for whom the points appear in counter-clockwise order.

Examples:

mged> 3ptarb

?

Provide a list of available mged commands. The ?devel, ?lib, help, helpdevel, and helplib commands provide additional information on available commands.

Examples:

mged> ?

?devel

Provide a list of available mged developer commands. The ?, ?lib, help, helpdevel, and helplib commands provide additional information on available commands.

Examples:

mged> ?devel

?lib

Provide a list of available BRL-CAD library interface commands. The ?, ?devel, help, helpdevel, and helplib commands provide additional information on available commands.

Examples:

mged> ?lib

B [-R -A -o -s C#/#/#] <objects | attribute name/value pairs>

Clear the mged display of any currently displayed objects, then display the list of objects provided in the parameter list. Equivalent to the Z command followed by the command draw <objects>. The -C option provides the user a way to specify a color that overrides all other color specifications including combination colors and region id-based colors. The -A and -o options allow the user to select objects by attribute. The -s option specifies that subtracted and intersected objects should be drawn with solid lines rather than dot-dash lines. The -R option means do not automatically resize the view if no other objects are displayed. See the draw command for a detailed description of the options.

Examples:

mged> B some_object

E [-s] <objects>

Display objects in an evaluated form. All the Boolean operations indicated in each object in objects will be performed, and a resulting faceted approximation of the actual objects will be displayed. Note that this is usually much slower than using the usual draw command. The -s option provides a more accurate, but slower, approximation.

Examples:

mged> E some_object

M 1|0 xpos ypos

Send an mged mouse (i.e., defaults to a middle mouse button) event. The first argument indicates whether the event should be a button press (1) or release (0). The xpos and ypos arguments specify the mouse position in mged screen coordinates between -2047 and +2047. With the default bindings, an mged mouse event while in the viewing mode moves the view so that the point currently at screen position (xpos, ypos) is repositioned to the center of the mged display (compare to the center command). The M command may also be used in other editing modes to simulate an mged mouse event.

Examples:

mged> M 1 100 100

Z

Zap (i.e., clear) the mged display.

Examples:

mged> Z

adc [-i] [subcommand]

This command controls the angle/distance cursor. The adc command with no arguments toggles the display of the angle/distance cursor (ADC). The -i option, if specified, causes the given value(s) to be treated as increments. Note that the -i option is ignored when getting values or when used with subcommands where this option makes no sense. You can also control the position, angles, and radius of the ADC using a knob or the knob command. This command accepts the following subcommands:

vars

Returns a list of all ADC variables and their values (i.e., var = val).

draw [0|1]

Set or get the draw parameter.

a1 [angle]

Set or get angle1 in degrees.

a2 [angle]

Set or get angle2 in degrees.

dst [distance]

Set or get radius (distance) of tick in local units.

odst [distance]

Set or get radius (distance) of tick (+-2047).

hv [position]

Set or get position (grid coordinates and local units).

xyz [position]

Set or get position (model coordinates and local units).

x [xpos]

Set or get horizontal position (+-2047).

y [ypos]

Set or get vertical position (+-2047).

dh distance

Add to horizontal position (grid coordinates and local units).

dv distance

Add to vertical position (grid coordinates and local units).

dx distance

Add to x position (model coordinates and local units).

dy distance

Add to y position (model coordinates and local units).

dz distance

Add to z position (model coordinates and local units).

anchor_pos [0|1]

Anchor ADC to current position in model coordinates.

anchor_a1 [0|1]

Anchor angle1 to go through anchorpoint_a1.

anchor_a2 [0|1]

Anchor angle2 to go through anchorpoint_a2.

anchor_dst [0|1]

Anchor tick distance to go through anchorpoint_dst.

anchorpoint_a1 [x y z]

Set or get anchor point for angle1 (model coordinates and local units).

anchorpoint_a2 [x y z]

Set or get anchor point for angle2 (model coordinates and local units).

anchorpoint_dst [x y z]

Set or get anchor point for tick distance (model coordinates and local units).

reset

Reset all values to their defaults.

help

Print the help message.

Examples:

mged> adc

ae [-i] azimuth elevation [twist]

Set the view orientation for the mged display by rotating the eye position about the center of the viewing cube. The eye position is determined by the supplied azimuth and elevation angles (degrees). The azimuth angle is measured in the xy plane with the positive x direction corresponding to an azimuth of 0˚. Positive azimuth angles are measured counter-clockwise about the positive z axis. Elevation angles are measured from the xy plane with +90˚ corresponding to the positive z direction and -90 corresponding to the negative z direction. If an optional twist angle is included, the view will be rotated about the viewing direction by the specified twist angle. The -i option results in the angles supplied being interpreted as increments.

Examples:

mged> ae -90 90

analyze [arb_name]

The “analyze” command displays the rotation and fallback angles, surface area, and plane equation for each face of the ARB specified on the command line. The total surface area and volume and the length of each edge are also displayed. If executed while editing an ARB, the arb_name may be omitted, and the ARB being edited will be analyzed.

Examples:

mged> analyze arb_name

animmate

The “animmate” command starts the Tcl/Tk-based animation tool. The capabilities and correct use of this command are too extensive to be described here, but there is a tutorial available.

apropos keyword

The “apropos” command searches through the one-line usage messages for each mged command and displays the name of each command where a match is found.

Examples:

mged> apropos region

aproposdevel keyword

The “aproposdevel” command searches through the one-line usage messages for each mged developer command and displays the name of each command where a match is found.

Examples:

mged> aproposdevel region

aproposlib keyword

The “aproposlib” command searches through the one-line usage messages for each BRL-CAD library interface command and displays the name of each command where a match is found.

Examples:

mged> aproposlib mat

arb arb_name rotation fallback

The “arb” command creates a new ARB shape with the specified arb_name. The new ARB will be 20 inches by 20 inches and 2 inches thick. The square faces will be perpendicular to the direction defined by the rotation and fallback angles. This direction can be determined by interpreting the rotation angle as an azimuth and the fallback angle as an elevation as in the ae command.

Examples:

mged> arb new_arb 35 25

arced comb/memb anim_command

The objects in a BRL-CAD model are stored as Boolean combinations of primitive shapes and/or other combinations. These combinations are stored as Boolean trees, with each leaf of the tree including a corresponding transformation matrix. The “arced” command provides a means for directly editing these matrices. The first argument to the “arced” command must identify the combination and which member s matrix is to be edited. The comb/memb argument indicates that member memb of combination comb has the matrix to be edited. The remainder of the “arced” command line consists of an animation command to be applied to that matrix. The available animation commands are:

Examples:

mged> arced body/head matrix rot 0 0 45

area [tolerance]

The “area” command calculates an approximate presented area of one region in the mged display. For this command to work properly, a single BRL-CAD region must be displayed using the E command. The tolerance is the distance required between two vertices in order for them to be recognized as distinct vertices. This calculation considers only the minimum bounding polygon of the region and ignores holes.

Examples:

mged> Z

arot x y z angle

The “arot” command performs a rotation about the specified axis (x y z) using screen units (-2048 to +2048). The amount of rotation is determined by angle, which is in degrees. Exactly what is rotated and how it is rotated are dependent on MGED s state as well as the state of the display manager. For example, in normal viewing mode, this command simply rotates the view. However, in primitive edit mode, it rotates the shape being edited.

Examples:

mged> arot 0 0 1 10

attach [-d display_string] [-i init_script] [-n name] [-t is_toplevel] [-W width] [-N height] [-S square_size] win_type

The “attach” command is used to open a display window. The set of supported window types includes X and ogl. It should be noted that attach no longer releases previously attached display windows (i.e., multiple attaches are supported). To destroy a display window, use the release command.

Examples:

mged> attach ogl

attr get|set|rm|append|show object_name [arguments]

The “attr” command is used to create, change, retrieve, or view attributes of database

objects. The arguments for “set” and “append” subcommands are attribute name/value pairs. The arguments for “get,” “rm,” and “show” subcommands are attribute names. The “set” subcommand sets the specified attributes for the object. The “append” subcommand appends the provided value to an existing attribute, or creates a new attribute if it does not already exist. The “get” subcommand retrieves and displays the specified attributes. The “rm” subcommand deletes the specified attributes. The “show” subcommand does a “get” and displays the results in a user readable format. Note that the attribute names may not contain embedded white space, and if attribute values contain embedded white space, they must be surrounded by “{}” or double quotes.

Examples:

region_1 comment

mged> attr set region_1 comment {This is a comment for region_1}

– Assign an attribute named “comment” to region_1, its value is "This is a

comment for region_1"

mged> attr show region_1 comment

– List all the attributes for region_1

autoview

The “autoview” command resets the view_size and the view center such that all displayed objects are within the view.

Examples:

Autoview

mged> autoview

– Adjust the view to see everything displayed.

bev [-t] [-P#] new_obj Boolean_formula

The “bev” command performs the operations indicated in the Boolean_formula and stores the result in new_obj. The new_obj will be stored as an NMG shape (it may be converted to a polysolid by using the nmg_simplify command). If the -t option is specified, then the resulting object will consist entirely of triangular facets. The default is to allow facets of any complexity, including holes. The -P option specifies the number of CPUs to use for the calculation (however, this is currently ignored). Only simple Boolean_formulas are allowed. No parentheses are allowed and the operations are performed from left to right with no precedence. More complex expressions must be expressed as BRL-CAD objects using the r, g, or c commands and evaluated using the facetize or ev commands.

Examples:

mged> bev -t triangulated_lens sphere1 + sphere2

cat <objects>

The “cat” command displays a brief description of each item in the list of objects. If the item is a primitive shape, the type of shape and its vertex are displayed. If the item is a combination, the Boolean formula for that combination including operands, operators, and parentheses is displayed. If the combination is flagged as a region, then that fact is also displayed along with the region s ident code, air code, los, and GIFT material code.

Examples:

mged> cat region_1 region_2

center [x y z]

The “center” command positions the center of the mged viewing cube at the specified model coordinates. This is accomplished by moving the eye position while not changing the viewing direction. (The lookat command performs a related function by changing the viewing direction, but not moving the eye location.) The coordinates are expected in the current editing units. In case the coordinates are the result of evaluating a formula, they are echoed back. If no coordinates are provided, the current center coordinates (in current editing units, not mm) are printed and can be used in subsequent calculations.

Examples:

mged> center

color low high r g b str

The “color” command creates an entry in the database that functions as part of a color lookup table for displayed regions. The ident number for the region is used to find the appropriate color from the lookup table. The low and high values are the limits of region ident numbers to have the indicated rgb color (0-255) applied. The str parameter is intended to be an identifying character string, but is currently ignored. The current list of color table entries may be displayed with the prcolor command, and the entire color table may be edited using the edcolor command. If a color lookup table exists, its entries will override any color assigned using the mater command.

Examples:

mged> color 1100 1200 255 0 0 fake_string

comb combination_name <operation object>

The “comb” command creates a new combination or extends an existing one. If combination_name does not already exist, then it will be created using the indicated list of operations and objects. If it does exist, the list of operations and objects will be appended to the end of the existing combination. The <operation object> list is expected to be in the same form as used in the r command. The c command may also be used to create a combination.

Examples:

mged> comb abc u a - b + c

comb_color combination_name r g b

The “comb_color” command assigns the color rgb (0-255) to the existing combination named combination_name.

Examples:

mged> comb_color region1 0 255 0

copyeval new_primitive path_to_old_ primitive

Objects in a BRL-CAD model are stored as Boolean trees (combinations), with the members being primitive shapes or other Boolean trees. Each member has a transformation matrix associated with it. This arrangement allows a primitive to be a member of a combination, and that combination may be a member of another combination, and so on. When a combination is displayed, the transformation matrices are applied to its members and passed down through the combinations to the leaf (primitive shape) level. The accumulated transformation matrix is then applied to the primitive before it is drawn on the screen. The “copyeval” command creates a new primitive object called new_ primitive by applying the transformation matrices accumulated along the path_to_old_primitive to the leaf primitive shape object at the end of the path and saving the result under the name new_ primitive. The path_to_old_ primitivemust be a legitimate path ending with a primitive shape.

Examples:

mged> copyeval shapeb comb1/comb2/comb3/shapea

copymat comb1/memb1 comb2/memb2

The “copymat” command copies the transformation matrix from a member of one combination to the member of another.

Examples:

mged> copymat comb1/memb1 comb2/memb2

cp from_object to_object

The “cp” command makes a duplicate of an object (shape or combination). If from_object is a shape, then it is simply copied to a new shape named to_object. If from_object is a combination, then a new combination is created that contains exactly the same members, transformation matrices, etc., and it is named to_object.

Examples:

mged> cp comb1 comb2

cpi old_tgc new_tgc

The “cpi” command copies old_tgc (an existing TGC shape) to a new TGC shape (new_tgc), positions the new TGC such that its base vertex is coincident with the center of the top of old_tgc, and puts mged into the primitive edit state with new_tgc selected for editing. This command was typically used in creating models of wiring or piping runs; however, a pipe primitive has since been added to BRL-CAD to handle such requirements.

Examples:

mged> cpi tgc_a tgc_b

d <objects>

The “d” command deletes the specified list of objects from the mged display. This is a synonym for the erase command. Only objects that have been explicitly displayed may be deleted with the “d” command (use the who command to see a list of explicitly displayed objects). Objects that are displayed as members of explicitly displayed combinations cannot be deleted from the display with this command (see dall or erase_all). Note that this has no effect on the BRL-CAD database itself. To actually remove objects from the database, use the kill command.

Examples:

mged> d region1 shapea

dall <objects>

The “dall” command deletes the specified list of objects from the mged display. This is a synonym for the erase_all command. This command will allow the user to delete objects that have not been explicitly displayed (unlike the d command). Note that this has no effect on the BRL-CAD database itself. To actually remove objects from the database, use the kill command.

Examples:

mged> dall region1 shapea

db command [args…]

The “db” command provides an interface to a number of database manipulation routines. Note that this command always operates in units of millimeters. The command must be one of the following with appropriate arguments:

Examples:

mged> db match *.s

db glob

db_glob cmd_string

Globs cmd_string against the MGED database resulting in an expanded command string.

Examples:

mged> db_glob “l r23\[0-9\]”

dbconcat [-s/-p] [-t] [-u] [-c] database_file [affix]

The “dbconcat” command concatenates an existing BRL-CAD database to the database currently being edited. If an affix is supplied, then all objects from the database_file will have that affix added to their names. The -s option indicates that the affix is a suffix, while the -p option (default) indicates that the affix is a prefix. Note that each BRL-CAD object must have a unique name, so care must be taken not to “dbconcat” a database that has objects with names the same as objects in the current database. The dup command may be used to check for duplicate names. If the dup command finds duplicate names, use the prefix option to both the dup and dbconcat commands to find a prefix that produces no duplicates. If duplicate names are encountered during the “dbconcat” process, and no affix is supplied, computer-generated prefixes will be added to the object names coming from the database_file (but member names appearing in combinations will not be modified, so this is a dangerous practice and should be avoided). If the -t option is specified, then the title of the database_file will become the new title of the current BRL-CAD database. If the -u option is specified, the units of the current database will be set to that of the database_file being concatted. The -c option specifies that the region color table in the concatted database_file should replace any region color table in the current BRL-CAD database.

Examples:

mged> dbconcat model_two.g two_

mged> dbconcat -s model_two.g

mged> dbconcat -c -p model_two.g two_

debugbu [hex_code]

The “debugbu” command allows the user to set or check the debug flags used by libbu. With no arguments, the debugbu command displays all the possible settings for the bu_debug flag and the current value. When a hex_code is supplied, that value is used as the new value for bu_debug. Similar debug commands for other BRL-CAD libraries are debuglib for librt and debugnmg for the NMG portion of librt. Other debugging commands include debugmem and debugdir.

Examples:

mged> debugbu

Examples:

mged> debugdir

debuglib [hex_code]

The “debuglib” command allows the user to set or check the debug flags used by librt. With no arguments, the debuglib command displays all the possible settings for the librt debug flag and the current value. When a hex_code is supplied, that value is used as the new value for the flag. Similar debug commands for other BRL-CAD libraries are debugbu for libbu and debugnmg for the NMG portion of librt. Other debugging commands include debugmem and debugdir.

Examples:

mged> debuglib

debugmem

The “debugmem” command prints a list of all the memory blocks that have been allocated and recorded in the memdebug table. Memory allocation is not normally recorded in the memdebug table, but executing the debugbu2 command will turn on the <MEM_CHECK> flag, and as long as that flag is set, all memory allocation will be recorded.

Examples:

mged> debugmem

debugnmg [hex_code]

The “debugnmg” command with no options displays a list of all possible debug flags available for NMG processing. If the command is invoked with a hex number argument, that value is used as the new value for the NMG debug flag. Similar debug commands for other BRL-CAD libraries are debuglib for librt and debugbu for libbu. Other debugging commands include debugmem and debugdir.

Examples:

mged> debugnmg 100

decompose NMG_shape [prefix]

The “decompose” command processes an NMG shape and produces a series of new NMG shapes consisting of each maximally connected shell in the original NMG shape. If an optional prefix is supplied, the resulting NMG shapes will be named by using the prefix and adding an underscore character and a number to make the name unique. If no prefix is supplied, the default prefix “sh” will be used.

Examples:

mged> decompose shape.nmg part

delay seconds microseconds

The “delay” command provides a delay of the specified time before the next command will be processed.

Examples:

mged> delay 5 0

dm subcommand [args]

The “dm” command provides a means to interact with the display manager at a lower level. The dm command accepts the following subcommands:

set [var [val]]

The “set” subcommand provides a means to set or query display manager-specific variables. Invoked without any arguments, the set subcommand will return a list of all available internal display manager variables. If only the var argument is specified, the value of that variable is returned. If both var and val are given, then var will be set to val.

size [width height]

The “size” subcommand provides a means to set or query the window size. If no arguments are given, the display manager s window size is returned. If width and height are specified, the display manager makes a request to have its window resized. Note that a size request is just that, a request, so it may be ignored, especially if the user has resized the window using the mouse.

m button x y

The “m” subcommand is used to simulate an M command. The button argument determines which mouse button is being used to trigger a call to this command. This value is used in the event handler to effect dragging the faceplate scrollbars. The x and y arguments are in X screen coordinates, which are converted to MGED screen coordinates before being passed to the M command.

am <r | t | s> x y

The “am” subcommand effects mged s alternate mouse mode. The alternate mouse mode gives the user a different way of manipulating the view or an object. For example, the user can drag an object or perhaps rotate the view while using the mouse. The first argument indicates the type of operation to perform (i.e., r for rotation, t for translation, and s for scale). The x and y arguments are in X screen coordinates and are transformed appropriately before being passed to the knob command.

adc <1 | 2 | t | d> x y

The “adc” subcommand provides a way of manipulating the angle distance cursor while using the mouse. The first argument indicates the type of operation to perform (i.e., 1 for angle 1, 2 for angle 2, t for translate, and d for tick distance). The x and y arguments are in X screen coordinates and are transformed appropriately before being passed to the adc command (i.e., not “dm adc”).

con <r | t | s <x | y | z> xpos ypos

This form of the “con” subcommand provides a way to effect constrained manipulation of the view or an object while using the mouse. This simulates the behavior of sliders without taking up screen real estate. The first argument indicates the type of operation to perform (i.e., r for rotation, t for translation, and s for scale). The <x | y | z> argument is the axis of rotation, translation, or scale. The xpos and ypos arguments are in X screen coordinates and are transformed appropriately before being passed to the knob command.

con a <x | y | 1 | 2 | d> xpos ypos

This form of the “con” subcommand provides a way to effect constrained manipulation of the angle distance cursor while using the mouse. This simulates the behavior of sliders without taking up screen real estate. The first argument indicates that this is to be applied to the angle distance cursor. The next argument indicates the type of operation to perform (i.e., x for translate in the x direction, y for translate in the y direction, 1 for angle 1, 2 for angle 2, and d for tick distance). The xpos and ypos arguments are in x screen coordinates and are transformed appropriately before being passed to the knob command.

Examples:

mged> dm set

draw [-R -A -s -o -C#/#/#] <objects | attribute name/value pairs>

Add <objects> to the display list so that they will appear on the MGED display. The e command is a synonym for draw.

Examples:

mged> draw object1 object2

dup file [prefix]

The “dup” command checks the specified file (which is expected to contain a BRL-CAD model) for names that are the same as those in the current model. If a prefix is included on the command line, all names in the specified file will have that prefix added to their names before comparison with the current model. This command is often used prior to invoking the dbconcat command to ensure that there are no name clashes.

Examples:

mged> dup other_model.g

e [-R -A -o -s -C#/#/#] <objects| attribute name/value pairs>

The “e” command adds the objects in the argument list to the display list so that they will appear on the MGED display. This is a synonym for the draw command; see that entry for a full list of options. The -C option provides the user a way to specify a color that overrides all other color specifications including combination colors and region-id-based colors. The -A and -o options allow the user to select objects by attribute. The -s specifies that subtracted and intersected objects should be drawn with solid lines rather than dot-dash lines. The -R option means do not automatically resize the view if no other objects are displayed.

Examples:

mged> e object1 object2

eac <aircodes>

The “eac” command adds all the regions in the current model that have one of the aircodes in the argument list to the display list so that they will appear on the MGED display. Regions that have nonzero ident numbers will not be listed by this command. The whichair command will perform the same search, but just lists the results.

Examples:

mged> eac 1 2 3

echo text

The “echo” command merely echos whatever text is provided as an argument on the command line. This is intended for use in MGED scripts.

Examples:

mged> echo some text goes here

edcodes <objects>

The “edcodes” command puts the user into an editor to edit a file that has been filled with the ident, air code, material code, LOS, and name of all the regions in the specified objects. The user may then modify the entries (except for the names). The editor used is whatever the user has set in the environment variable EDITOR. If EDITOR is not set, then /bin/ed is used.

Examples:

mged> edcodes object1 object2

edcolor

The “edcolor” command puts the user into an editor to edit a file that has been filled with the ident based color lookup table. The entire table may be seen with the prcolor command, and entries may be added using the color command. The editor used is whatever the user has set in the environment variable EDITOR. If EDITOR is not set, then /bin/ed is used.

Examples:

mged> edcolor

edcomb combname R|G regionid air_code los [material_code]

The “edcomb” command allows the user to modify the attributes of a combination. The combname is the name of the combination to be modified. An R flag indicates that the region flag should be set; otherwise, the region flag is unset. If the region flag is not being set, then the remainder of the attributes are ignored. If the region flag is being set, then the region_id, aircode, los, and material_code are set according to the arguments supplied.

Examples:

mged> edcomb comb1 R 1001 0 50 8

edgedir [x y z]|[rot fb]

The “edgedir” command allows the user to set the direction of an edge by specifying a direction vector in the form of x, y,andz components or via rotation and fallback angles. This can only be done while moving an edge of an ARB.

Examples:

mged> edgedir 0 1 0

edmater <combinations>

The “edmater” command places the user in an editor ready to edit a file filled with shader arguments for the combinations listed on the command line. The arguments placed in the file for editing are the shader name and its own arguments, RGB color, RGB_valid flag, and the inheritance flag. The editor used is whatever the user has set in the environment variable EDITOR. If EDITOR is not set, then /bin/ed is used.

Examples:

mged> edmater comb1 comb2

eqn A B C

The “eqn” command allows the user to rotate the face of an ARB shape by providing the coefficients of an equation of the desired plane for the face. The coefficients A, B, and C are from the plane equation:

Examples:

mged> eqn 0 0 1

em [ -C#/#/#] value [value value . . .]

The “em” command displays all regions that a MUVES_Component attribute that is set to any of the specified value arguments. The C option specifies a color to draw the regions.

Examples:

Examples:

mged> em engine pilot

– Display all regions that have_muves_Component attributes equal to engine or pilot.

mged> em C0/255/0 hydraulics

– Display all regions that have_muves_Component attributes equal to hydraulics in green.

– Display all regions that have_muves_Component attributes equal to hydraulics in green.

erase <objects>

The “erase” command deletes the specified list of objects from the MGEDdisplay. This is a synonym for the d command. Only objects that have been explicitly displayed may be deleted with the “erase” command (use the who command to see a list of explicitly displayed objects). Objects that are displayed as members of explicitly displayed combinations cannot be deleted from the display with this command (see dall or erase_all). Note that this has no effect on the BRL-CAD database itself. To actually remove objects from the database, use the kill command.

Examples:

mged> erase region1 shapea

erase_all <objects>

The “erase_all” command deletes the specified list of objects from the MGED display. This is a synonym for the dall command. This command will allow the user to delete objects that have not been explicitly displayed (unlike the d or erase commands). Note that this has no effect on the BRL-CAD database itself. To actually remove objects from the database, use the kill command.

Examples:

mged> erase_all region1 shapea

ev [-dfnrstuvwST] [-P#] [-C#/#/#] <objects>

The “ev” command evaluates the objects specified by tessellating all primitive shapes in the objects and then performing any Boolean operations specified in the objects. The result is then displayed in the MGED display according to the specified options:

Examples:

mged> ev region1 shapea

exit

The “exit” command ends the MGED process. This is a synonym for the quit command.

Examples:

mged> exit

eye_pt x y z

The “eye_pt” command positions the eye point to the given x, y, and z coordinates (specified in mm).

Examples:

mged> eye_pt 100 0 0

e_muves MUVES_component1 MUVES_component2 …

The “e_muves” command displays the BRL-CAD regions that are part of the indicated MUVES components. The internal list of MUVES components must have been created earlier by the read_muves command. The MUVES components listed on the command line must not use any wildcards (the expansion will result in BRL-CAD objects, not_muves components).

Examples:

mged> e_muves fuel transmission

facedef #### [a|b|c|d parameters]

The “facedef” command allows the user to redefine any face of an ARB8 shape. The user must be in Primitive Edit Mode with an ARB selected for editing. The optional parameters may be omitted, and MGED will prompt for the missing values. The options are:

Examples:

mged> facedef 1234 a 1 0 0 20

facetize [-ntT] [-P#] new_object old_object

The “facetize” command creates new_object as a BOT shape by tessellating all the primitive shapes in old_object and then performing any Boolean operations specified in old_object. The -T option indicates that all faces in the new_object should be triangulated. The -n option specifies that the resulting shape should be saved as an NMG shape. The -t option is to create TNURB faces rather than planar approximations (this option is still under development). The -P option is intended to allow the user to specify the number of CPUs to use for this command, but it is currently ignored.

Examples:

mged> facetize region1.nmg region1.r

find <objects>

The “find” command displays all combinations that have any of the objects specified as a member.

Examples:

mged> find shapea

fracture NMG_shape [prefix]

The “fracture” command creates a new NMG shape for every “face” in the specified NMG_shape. The new shapes will be named by adding an underscore and a number to the prefix. If no prefix is specified, then the NMG_shape name provided is used in place of the prefix.

Examples:

mged> fracture shape1.nmg f

g groupname <objects>

The “g” command creates a special type of combination often referred to as a group. This builds a combination by unioning together all the listed objects. If groupname already exists, then the list of objects will be unioned to the end of it. (Note that an existing groupname is not restricted to being a group; any combination is legal.) Other commands to build combinations are c, r, or comb.

Examples:

mged> g shape1.nmg f

garbage_collect

The “garbage_collect” command eliminates unused space in a BRL-CAD database file.

Examples:

mged> garbage_collect

gui [-config b|c|g] [-d display_string] [-gd graphics_display_string] [-dt graphics_type] [-id name] [-c -h -j -s]

This command is used to create an instance of MGED s default Tcl/Tk graphical user interface (GUI). The following options are allowed:

help [command]

The “help” command returns a list of available MGED commands along with a one-line usage message for each. If a command is supplied as an argument, the one-line usage message for that command is returned. The helpdevel, helplib, ?, ?devel, and ?lib commands provide additional information on available commands.

Examples:

mged> help ae

helpdevel [command]

The “helpdevel” command returns a list of available developer commands along with a one-line usage message for each. If a command is supplied as an argument, the one-line usage message for that command is returned. The help, helplib, ?, ?devel,and ?lib commands provide additional information on available commands.

Examples:

mged> helpdevel winset

helplib [command]

The “helplib” command returns a list of available library commands along with a one-line usage message for each. If a command is supplied as an argument, the one-line usage message for that command is returned. The help, helpdevel, ?, ?devel, and ?lib commands provide additional information on available commands.

Examples:

mged> helplib mat_trn

i obj_name comb_name [operation]

The “i” command adds obj_name to the end of the combination named comb_name. The operation may be “+,” “-,” or “u.” If no operation is specified, “u” is assumed. If comb_name does not exist, it is created.

Examples:

mged> i region3 group5

idents file_name <objects>

The “idents” command places a summary of the regions in the list of objects specified in the file specified. If any regions include other regions, then only the first encountered region in that tree will be listed. The resulting file will contain two lists of regions, one in the order encountered in the list of objects, and the other ordered by ident number. The data written for each region includes (in this order) a sequential region count, the ident number, the air code, the material code, the LOS, and the path to the region.

Examples:

mged> idents regions_file group1 group2 region3

ill obj_name

The “ill” command performs the function of selecting an object after entering solid(i.e., primitive)illuminate or object illuminate mode. In solid illuminate mode, this command selects the specific shape for editing. In object illuminate mode, this command selects the leaf object for the object path, then the user may use the mouse to select where along the object path the editing should be applied. In both modes, the ill command will only succeed if the specified obj_name is only referenced once in the displayed objects; otherwise a multiply referenced message will be displayed. If the ill command fails, the user must resort to either using the mouse to make the selection, or using aip and M 1 0 0.

Examples:

mged> ill shapea

in [-f] [-s] new_shape_name shape_type <parameters>

The “in” command allows the user to type in the arguments needed to create a shape with the name new_shape_name of the type shape_type. The command may be invoked with no arguments, and it will prompt the user for all needed information. The -s option will invoke the primitive edit mode on the new shape immediately after creation. The -f option does not draw the new shape, and therefore the -s option may not be used in conjunction with -f. The possible values for shape_type are:

Examples:

mged> in new1 raw 0 0 0 0 0 1 1 0 0 0 1 0

inside [outside_shape_name new_inside_shape_name <parameters>]

The “inside” command creates a new shape that is inside an existing shape. This command is typically used to create an inside shape that can be subtracted from the original shape to produce a hollow shell. The command is typically used with no arguments, and it prompts the user for all needed information; however, all the parameters may be supplied on the command line. If MGED is in primitive edit mode when the “inside” command is issued, then the shape currently being edited will be used as the “outside_shape.” Similarly, if MGED is in matrix edit mode when the “inside” command is executed, then the current key shape will be used as the outside shape.

Examples:

mged> inside out_arb in_arb 1 1 1 1 1 1

item region_name ident_number [air_code [material_code [LOS]]]

The “item” command sets the values of ident_number, aircode, material_code, and LOS for the specified region.

Examples:

mged> item region_1 1137 0 8 100

journal [-d] [journal_file_name]

The “journal” command starts or stops the journaling of MGED commands to a file. If executed with no arguments, the command stops journaling. If journal_file_name is provided, that file will become the recipient of the journaling. If a -d option is also provided, the journaling will include the delays between commands. Journaling is off by default.

Examples:

mged> journal journal_file

keep keep_file <objects>

The “keep” command copies the objects specified to the keep_file. If keep_file does not exist, it is created. If keep_file does exist, the objects are appended to it. The keep_file is a BRL-CAD database file. The objects in the list must exist in the current database.

Examples:

mged> keep sample.g sample1 sample2

keypoint [x y z | reset]

The “keypoint” command without any options displays the current keypoint setting. If a point is specified, then that point becomes the keypoint. If reset is specified, then the default keypoint is restored. The keypoint is used as the center of rotation and scaling in primitive edit or matrix edit (formerly known as object edit) modes. This command has no effect when used in nonediting modes.

Examples:

mged> keypoint 10 20 30

kill [-f] <objects>

The “kill” command deletes the specified objects from the current database. This command affects only the objects actually listed on the command line. If a combination is killed, its members are not affected. If the -f option is specified, then kill will not complain if some, or all, of the objects specified do not actually exist in the database. Note that the objects are killed immediately. There is no need for a “write file” command in MGED, and there is no “undo” command. Use this command with caution. Other commands that remove objects from the database are killall and killtree.

Examples:

mged> kill group1 region2 shapeb

killall <objects>

The “killall” command deletes the specified objects from the current database and removes all references to them from all combinations in the database. Note that the objects are killed immediately. There is no need for a “write file” command in MGED, and there is no “undo” command. Use this command with caution. Other commands that remove objects from the database are kill and killtree.

Examples:

mged> killall group1 region2 shapeb

killtree <objects>

The “killtree” command deletes the specified objects from the current database and recursively deletes all objects referenced by any of those objects. If one of the objects listed is a combination, then that combination as well as any objects that are members of that combination will be deleted. If a member of that combination is itself a combination, then all of its members will also be destroyed. This continues recursively until the primitive shapes are reached and destroyed. Note that the objects are killed immediately. There is no need for a “write file” command in MGED, and there is no “undo” command. Use this command with extreme caution. Other commands that remove objects from the database are kill and killall.

Examples:

mged> killtree group1 region2 shapeb

knob [-e -i -m -v] [-o v|m|e|k] [zap|zero|(id [val])]

The “knob” command is used internally by MGED in the processing of knob input devices and is not recommended for users. The knob command provides a method for simulating knob input. With no options, it will display the current values for the knobs. With the zap or zero command provided, all the knob values will be reset to zero. If an id and value are provided, the specified knob setting will be simulated. If the -i option is specified, then the value provided will be used as an increment to be applied to the indicated knob. The knobs have different functions depending on the current mode. For example, if in primitive or matrix edit mode and a rotation or translation function is selected, the knob effects are applied to the edited object by default. However, the -v (view coordinates) and -m (model coordinates) options may be used to adjust the view without modifying primitives or matrices. The -e option allows the knob effects to be applied to the edited object when they would normally be applied to the view. The -o option allows the origin of rotation to be specified with v, m, e, and k, indicating view, model, and eye and keypoint, respectively. The units for value are degrees for rotation and local units for translation. The available knob ids are:

Examples:

mged> knob y 1

l [-r] <objects>

The “l” command displays a verbose description about the specified list of objects. If a specified object is a path, then any transformation matrices along that path are applied. If the final path component is a combination, the command will list the Boolean formula for the combination and will indicate any accumulated transformations (including any in that combination). If a shader and/or color has been assigned to the combination, the details will be listed. For a region, its ident, air code, material code, and LOS will also be listed. For primitive shapes, detailed shape parameters will be displayed with the accumulated transformation applied. If the -r (recursive) option is used, then each object on the command line will be treated as a path. If the path does not end at a primitive shape, then all possible paths from that point down to individual shapes will be considered. The shape at the end of each possible path will be listed with its parameters adjusted by the accumulated transformation.

Examples:

mged> l region1

labelvert <objects>

The “labelvert” command labels the vertices of the indicated objects with their coordinate values in the MGED display window. The objects must have already been displayed using e, E, ev, B, or any other command that results in the display of an object.

Examples:

mged> labelvert shapeb

listeval [path]

Combinations may include transformation matrices to be applied to their members. A path through a series of combinations and ending with a primitive shape represents that primitive shape with the transformations accumulated through the path applied to it. The “listeval” command displays primitive shape parameters after applying the accumulated transformations from the indicated path. If the specified path does not end at a primitive shape, then all possible paths from the indicated path to any primitive shape will be evaluated and displayed.

Examples:

mged> listeval group1/region1/shapeb

lm [-l] [values]

The “lm” command with no values argument lists the name of every region in the database (in alphabetical order), except for those marked as hidden with the hide command. If the values argument is supplied, only those regions with a “MUVES_Component” attribute having one of the values are listed. The l option specifies to use a long format showing object name, object type, major type, minor type, and length.

Examples:

-

mged> lm engine

–List all regions with “MUVES_Component” attribute having a value of “engine”.

-

mged> lm 1 engine pilot

–List all regions with “MUVES_Component” attribute having a value of “engine” or “pilot,” and use the long format.

-

loadtk

The “loadtk” command loads the initialization for the Tk window library. This is normally done automatically when the user attaches any display manager for MGED. If no display manager is attached, then the user must execute loadtk prior to using any Tk facilities.

Examples:

mged> loadtk

lookat x y z

The “lookat” command adjusts the current view in MGED such that the eye is looking in the direction of the given coordinates, but does not move the eye point nor change the view_size. This is similar to just rotating the viewers head to look at the specified point, putting that point in the center of the MGED display. The center command performs a similar function, but moves the eye_pt without changing the viewing direction.

Examples:

mged> lookat 10 20 30

ls [-A -o -a -c -r -s -p -l] [objects]

The “ls” command with no object argument lists the name of every object in the database (in alphabetical order) except for those marked as hidden with the hide command. If the object argument is supplied, only those objects are listed. The object argument may include regular expressions. If the -A option is used, then the arguments are expected to be a list of attribute name/value pairs, and objects having attributes that match the provided list are listed. By default, an object must match all the specified attributes in order to be listed; however, the -o flag indicates that an object matching at least one attribute name/value pair should be listed. See the attr command for information on how to set or get attributes. Regular expressions are not supported for attributes. The following options are also allowed: