Skip to content

hfSectionVisualizer Remote Control Operation and Analysis

Operation

hfSectionVisualizer --remote [--target <id>] make-mesh [build|delete|toggle]
hfSectionVisualizer --remote [--target <id>] make-mesh --mode <build|delete|toggle>
hfSectionVisualizer --remote [--target <id>] compute-section-constants [compute|invalidate|toggle]
hfSectionVisualizer --remote [--target <id>] compute-section-constants --mode <compute|invalidate|toggle>
hfSectionVisualizer --remote [--target <id>] renumber
hfSectionVisualizer --remote [--target <id>] move <top-left|top-middle|top-right|middle-left|middle-middle|middle-right|bottom-left|bottom-middle|bottom-right|centroid|shear-center|offset> [--offset <yp,zp>]
hfSectionVisualizer --remote [--target <id>] rotate <angle-deg>
  • move offset requires --offset <yp,zp>.
  • make-mesh build builds the mesh and computes section constants together.

make-mesh

  • Builds, deletes, or toggles the active section mesh.
  • Validation: build requires section geometry. delete removes the current mesh only when one exists.
  • Behavior: build creates the mesh and then computes section constants immediately. In other words, centroid, shear-center, and other derived section constants are prepared in the same step. This matches the GUI Make Mesh action behavior.

Example:

hfSectionVisualizer --remote make-mesh build

compute-section-constants

  • Computes, invalidates, or toggles section constants for the active section mesh.
  • Validation: Requires an existing mesh.
  • Behavior: Use this command when you want to recompute or invalidate section constants for an existing mesh. make-mesh build already computes section constants by default.

Analysis

hfSectionVisualizer --remote [--target <id>] run-analysis
hfSectionVisualizer --remote [--target <id>] unlock-model
  • Requires an existing saved file path.
  • If unsaved changes exist, auto-save is attempted before analysis starts.
  • No extra CLI options are accepted. The remote command uses the same analyzer launch path as the GUI action.
  • unlock-model mirrors the GUI Unlock model action and deletes the current section-analysis result so editing returns to preprocessing mode.
  • unlock-model is available only when a result file exists or analysis results are currently loaded.

run-analysis

  • Starts section analysis in the same way as the GUI analysis action.
  • Validation: Requires a saved current file path. Fails if analysis is already running.
  • Behavior: If unsaved changes exist, the current file is saved first. Existing .xlsx result output for the current section file is removed before the new run starts.

Example:

hfSectionVisualizer --remote run-analysis

unlock-model

  • Deletes the current section-analysis result and returns the model to editable preprocessing mode.
  • Validation: Takes no positional arguments. Fails while analysis is running. Fails when no saved or loaded result exists.
  • Behavior: Removes the current .xlsx analysis-result file when present. Clears loaded analysis result data from the active session even if only in-memory results remain. GUI Unlock model also appends the same canonical unlock-model tail to Remote Control History after success.

Example:

hfSectionVisualizer --remote unlock-model