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
I worked on two days about this issue. Can you please help me. This is very important. How to fix this Value error. When we using reaction force this value error came. axial, bending, deflection forces working. Can you please help me. show_reaction_force(show=True) is working when we did not used load combinations.
Notes from investigating this: This is closely related to the fact that get_element_results() on the "combination" results works correctly, but get_nodal_results_system() just gives you a bunch of zeros for everything.
Basically, in a normal solve without load cases and combinations, anaStruct creates an initial set of nodes that it uses to create the FEA matrices, and then the solver overwrites those nodes with new ones once it has results. That is for example, before you solve node.Fx represents applied loads, but after the solve, nodes.Fx represents loads or reactions.
When anaStruct calculates the "combination" results, it's not doing a solve - it's just adding together load cases - which means that that overwriting the nodes step never happens correctly. I need to dig more, but I think there are correct results in system.element_map[].node_map[]. However, that node_map is separate from the system.node_map[] which is what the nodal results are actually pulled from by the postprocessing code.
Hi @ritchie46 & @lukaszlaba & @rodrigo1392 ,
I worked on two days about this issue. Can you please help me. This is very important. How to fix this Value error. When we using reaction force this value error came. axial, bending, deflection forces working. Can you please help me. show_reaction_force(show=True) is working when we did not used load combinations.
The text was updated successfully, but these errors were encountered: