symmetry_use_file

frame.symmetry_use_file(p0: str) → int

Sets whether a periodic matchfile will be used for specification of the rotational or translational symmetry.

Since modification of frame symmetry attributes typically need more than one attribute change before being able to properly perform the option, one typically should encase the attribute lines between frame: modify_begin and frame: modify_end commands.

If no matchfile is used, the rotational angle and number of instances (for rotational symmetry) or the translational deltas and number of instances (for translational symmetry) must be set in the user interface. Also, node hashing will be done in an attempt to eliminate duplicate nodes at the boundaries of instances. If a matchfile is used, the matchfile must follow the prescribed format, which contains the angle or delta, and the list of paired nodes that match at the instance boundaries. The number of instances still comes from the user interface.

Args:

p0:

‘toggle’

• ON

• OFF

Examples:

ensight.frame.select_begin(1)
ensight.frame.modify_begin()
ensight.frame.symmetry_type("rotational")
ensight.frame.symmetry_rinstances(5)
ensight.frame.symmetry_use_file("ON")
ensight.frame.symmetry_file("/usr/tmp/model.trn_match")
ensight.frame.modify_end()

Returns:

zero on success, non-zero on error