Skip to content

hfVisualizer Remote Control Sensor

sensor

hfVisualizer --remote [--target <id>] sensor <Point|Line|TrackTwist> <name> (--content <text> | --content-file <file>)
  • Creates or updates one *Sensor, TYPE=<type>, Name=<name> definition.
  • Exactly one of --content or --content-file is required.
  • sensor runs only in preprocessing mode.
  • <type> and <name> must not be empty.
  • Supported sensor types are:
  • Point
  • Line
  • TrackTwist
  • Content is passed directly to readSensorModification() after the IPC layer prepends the *Sensor keyword line.
  • Inside --content, use \n for line breaks. \\n stays literal.
  • Empty content is rejected.
  • After a successful apply, the created or updated sensor becomes the current sensor selection, matching the GUI Define Sensor widget.
  • Validation follows the existing sensor reader rules:
  • Point: first data line must be <field>, <hostElset>, later lines are id, x, y, z, dx, dy, dz
  • Line: first data line must be <field>, <hostElset>, <spline>[, <startId>]
  • TrackTwist: single data line must be <line1Elset>, <line2Elset>, <spacing>, <advance>[, <startId>]

Example:

hfVisualizer --remote sensor Point SG1 --content "Strain, girder\n1, 1, 0.0, 0, 1, 0, 0"
hfVisualizer --remote sensor Line LVDT1 --content-file D:\Work\line-sensor.txt
hfVisualizer --remote sensor TrackTwist TW1 --content "leftRail, rightRail, 3, 0.5, 1"

sensor-rename

hfVisualizer --remote [--target <id>] sensor-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 sensor 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 sensor-rename ... tail.

Example:

hfVisualizer --remote sensor-rename SG1 SG_MAIN

sensor-delete

hfVisualizer --remote [--target <id>] sensor-delete <name>
  • Available only in preprocessing mode.
  • name must be non-empty and must resolve to an existing sensor.
  • The command uses the same delete path as ModelTree delete, so related output requests and post targets are cleaned up together.
  • Successful execution is recorded by script-save as a canonical sensor-delete ... tail.

Example:

hfVisualizer --remote sensor-delete SG_MAIN