You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
.# Generate the mesh now that we've defined all the openings. Pynite automatically generates all
.# meshes when analyzing, but generating it early with give us the chance to work with it prior to
.# analysis.
Other examples have similar comments.
But if I remove the calls the .generate() in my code, the meshes seem to not exist: they're not rendered, calls to max_shear() and max_moment() return None, and the displacements of involved nodes change.
I've put the .generate() calls back in my code and this works for me, but it seems like at a (documentation?) bug.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
The shear wall example contains this comment:
.# Generate the mesh now that we've defined all the openings. Pynite automatically generates all
.# meshes when analyzing, but generating it early with give us the chance to work with it prior to
.# analysis.
Other examples have similar comments.
But if I remove the calls the .generate() in my code, the meshes seem to not exist: they're not rendered, calls to max_shear() and max_moment() return None, and the displacements of involved nodes change.
I've put the .generate() calls back in my code and this works for me, but it seems like at a (documentation?) bug.
Beta Was this translation helpful? Give feedback.
All reactions