Tutorial 08
Portal Frame
Goal
This tutorial combines the full workflow around a beam-based portal-frame example:
- model review
- analysis run
- render-view layout
- result review
- optional script capture
Why use a portal frame
A portal frame is a good example because the strengths of a beam model are easy to see.
- member forces and deformed shape are easy to read
- full-frame behavior can be compared quickly
- the roles of beams and columns are visually clear
Recommended sequence
- open the model
- clean up the base scene
- run the analysis
- set the result step and frame
- inspect contour and deformed shape
- split the render views if comparison is needed
Example flow
hfVisualizer --remote open D:\Work\portal_frame.h5.hdb
hfVisualizer --remote camera fit
hfVisualizer --remote representation both
hfVisualizer --remote display-control grid off
hfVisualizer --remote run-analysis
hfVisualizer --remote post-step STEP1
hfVisualizer --remote post-frame 1
hfVisualizer --remote post-plot deformed on
hfVisualizer --remote post-plot contour on
hfVisualizer --remote post-scalar S.Mises
hfVisualizer --remote post-display scalarbar on
Compare two views
For example:
r0: overall deformed shaper1: stress contour
can be assigned separate roles.
hfVisualizer --remote view add render
hfVisualizer --remote --view-id r0 camera view +z
hfVisualizer --remote --view-id r1 camera view +z
hfVisualizer --remote --view-id r1 display-control grid off
What to review
- story drift or overall frame sway
- stress concentration near beam-column connections
- differences between load-case steps
- response changes frame by frame
Save the workflow as a script
If the scene setup works well, save it.
hfVisualizer --remote script-save D:\Work\portal-review.ipc.txt
Then replay it later with:
hfVisualizer --remote script D:\Work\portal-review.ipc.txt
Summary
The portal-frame example is a good practice case for showing how beam analysis, result review, and remote-control automation connect together.