xara 0.0.34
Python 3.11, Windows 10
Installed via pixi/pip
Description:
For a Joint2D element under nonzero load (confirmed via the surrounding structure's real, nonzero internal forces), querying the element's own response — "force", "deformation", or "defoANDforce" — returns a correctly-sized but all-zero vector. This happens identically whether queried through:
model.recorder("Element", "-file", ..., "-ele", tag, "force") (and "deformation", "defoANDforce")
model.eleResponse(tag, "force") called live during the analysis loop
By contrast, querying the element's internal materials directly works correctly and returns real, physically sensible, time-varying values:
model.eleResponse(tag, "material", "1", "stress")
model.eleResponse(tag, "material", "1", "strain")
This suggests the bug is in Joint2D's own getResponse()/setResponse() handling of the aggregate force/deformation/defoANDforce response IDs specifically — the per-material response path is unaffected.
Reproduction: (attach script)
Expected: force/deformation/defoANDforce should return the same nonzero values as the underlying materials show (transformed to the element's basic system).
Actual: All zero, regardless of applied load magnitude or step.
xara 0.0.34
Python 3.11, Windows 10
Installed via pixi/pip
Description:
For a Joint2D element under nonzero load (confirmed via the surrounding structure's real, nonzero internal forces), querying the element's own response — "force", "deformation", or "defoANDforce" — returns a correctly-sized but all-zero vector. This happens identically whether queried through:
model.recorder("Element", "-file", ..., "-ele", tag, "force") (and "deformation", "defoANDforce")
model.eleResponse(tag, "force") called live during the analysis loop
By contrast, querying the element's internal materials directly works correctly and returns real, physically sensible, time-varying values:
model.eleResponse(tag, "material", "1", "stress")
model.eleResponse(tag, "material", "1", "strain")
This suggests the bug is in Joint2D's own getResponse()/setResponse() handling of the aggregate force/deformation/defoANDforce response IDs specifically — the per-material response path is unaffected.
Reproduction: (attach script)
Expected: force/deformation/defoANDforce should return the same nonzero values as the underlying materials show (transformed to the element's basic system).
Actual: All zero, regardless of applied load magnitude or step.