Skip to content

hfVisualizer Remote Control CoordinateSystem

coordinatesystem

hfVisualizer --remote coordinatesystem <type> <name> (--content <text> | --content-file <file>)
  • Creates or updates one *CoordinateSystem, TYPE=<type>, Name=<name> definition.
  • Exactly one of --content or --content-file is required.
  • coordinatesystem runs only in preprocessing mode.
  • Supported coordinate-system types are User, Orientation, and Beam.
  • <name> must be non-empty and uses the same single-token normalization as GUI edits.
  • The command builds the keyword header first and applies the remaining lines as the block body.
  • Names created here can be referenced later by commands such as element-update --beam-cs and element-update --orientation-cs.
  • Successful execution is recorded by script-save as a canonical coordinatesystem ... --content ... tail.

Example:

hfVisualizer --remote coordinatesystem User girder_cs --content "1, 0, 0\n0, 0, 1\n0, 1, 0"

coordinatesystem-rename

hfVisualizer --remote coordinatesystem-rename <old-name> <new-name>
  • Available only in preprocessing mode.
  • Both names must be non-empty and use the same single-token normalization as GUI edits.
  • The source name must exist.
  • The target name must not collide with another coordinate system unless it normalizes to the same name, in which case the command succeeds as a no-op.
  • Successful execution is recorded by script-save as a canonical coordinatesystem-rename ... tail.

Example:

hfVisualizer --remote coordinatesystem-rename girder_cs girder_local

coordinatesystem-activate

hfVisualizer --remote [--view-id <rN>] coordinatesystem-activate <name|none>
  • Sets the named User coordinate system as the checked/active user coordinate system in the target render view.
  • Activating one User coordinate system automatically clears any previously active User coordinate system in that render view.
  • The command is available whenever the current model and target render view exist; it is not limited to preprocessing mode.
  • Only User coordinate systems are valid. Orientation and Beam coordinate systems return an error.
  • Use none to clear the active User coordinate system in the target render view.
  • --view-id <rN> targets a specific render view. Without it, the active render view is used.
  • The command follows the same render-view path as the TreeMenu check state and uncheck state, so it changes or clears the active UCS / 2D datum target for that render view only.
  • Successful execution is recorded by script-save as a canonical coordinatesystem-activate ... tail.

Example:

hfVisualizer --remote coordinatesystem-activate girder_local

hfVisualizer --remote coordinatesystem-activate none

coordinatesystem-delete

hfVisualizer --remote coordinatesystem-delete <name>
  • Available only in preprocessing mode.
  • <name> must be non-empty and must resolve to an existing coordinate system.
  • The command uses the same delete path as ModelTree, so the same reference cleanup is applied to loads, constraints, beam assignments, and the active user coordinate system.
  • Successful execution is recorded by script-save as a canonical coordinatesystem-delete ... tail.

Example:

hfVisualizer --remote coordinatesystem-delete girder_local