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
plot_supports_and_loads_2d() load arrows do not behave as expected when the dimensions of the model are large, which occurs when inch or mm units are used. Specifically, there are two issues:
The arrowheads are deformed/practically not visible, regardless of whether the scaling factor sfac is appropriate.
The auto-calculated sfac does not seem to be in-scale.
The following model is used an example to illustrate the issues. The member lengths are defined in millimeters, so dimensions are on the order of 10^4. Similar issues exist when inch units are used, which would lead to dimensions on the order of 10^3.
Even if I set a manual sfac, the arrowheads are practically invisible:
If I let the function auto-calculate sfac, then length of the arrows become much larger than the size of the model.
However, when I redefine the member lengths in meters, neither of these issues appear.
The text was updated successfully, but these errors were encountered:
firai
changed the title
Load arrows from plot_supports_and_loads_2d() not behaving for large model dimensions
[Bug] Load arrows from plot_supports_and_loads_2d() not behaving for large model dimensions
Apr 15, 2022
plot_supports_and_loads_2d()
load arrows do not behave as expected when the dimensions of the model are large, which occurs when inch or mm units are used. Specifically, there are two issues:sfac
is appropriate.sfac
does not seem to be in-scale.The following model is used an example to illustrate the issues. The member lengths are defined in millimeters, so dimensions are on the order of 10^4. Similar issues exist when inch units are used, which would lead to dimensions on the order of 10^3.
sfac
, the arrowheads are practically invisible:sfac
, then length of the arrows become much larger than the size of the model.However, when I redefine the member lengths in meters, neither of these issues appear.
The text was updated successfully, but these errors were encountered: