Skip to content

Tutorial 03

Beam vs Solid

Goal

Summarize the criteria for choosing between a beam model and a solid model for the same structural problem.

First questions to ask

When beam is the better choice

  • the structure is slender
  • section properties can be defined separately
  • the main goal is global displacement, reaction, or member-force review
  • fast iteration matters

When solid is the better choice

  • the 3D geometry cannot be represented well by simple section assumptions
  • local stress concentration matters
  • the internal stress distribution must be reviewed directly
  • connection or boundary geometry strongly affects the result

Cost comparison

Beam

  • faster to model
  • faster to solve
  • simpler to interpret

Solid

  • heavier to model
  • more sensitive to mesh quality
  • larger solve time and larger result files

In practice, this order works well:

  1. check the global behavior with a beam model
  2. validate boundary conditions and loads
  3. build a local solid detail model only where needed

What to compare in hfVisualizer

When comparing beam and solid results:

  • align the same step and frame
  • use the same camera view
  • start with deformed shape and reactions before detailed contour review
  • create two render views if needed and inspect both models side by side

Example:

hfVisualizer --remote view add render
hfVisualizer --remote view list
hfVisualizer --remote --view-id r0 camera view +z
hfVisualizer --remote --view-id r1 camera view +z

Conclusion

  • Beam is strong for quick decisions and global behavior review.
  • Solid is strong for detailed stress and local effects.
  • They are not competing tools so much as complementary stages of review.

Next step