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
When using solve_for_reaciton_loads in the wrong way in the beam class the output will be IndexError: tuple index out of range. It doesn't matter what the problem is. The user doesn't know what went wrong when trying to calculate the reaction loads.
when the wrong *reactions are given as input
There are probably a lot more possible ways to get the same error message.
As stated in this comment this method can be improved by adding some try and except statements to give more detailled error messages. This will make it easier for the user to find the problem in their code.
The text was updated successfully, but these errors were encountered:
As also described in this comment.
When using
solve_for_reaciton_loads
in the wrong way in the beam class the output will beIndexError: tuple index out of range
. It doesn't matter what the problem is. The user doesn't know what went wrong when trying to calculate the reaction loads.The line that outputs this message is:
The error message will be the same when:
*reactions
given as input*reactions
are given as inputThere are probably a lot more possible ways to get the same error message.
As stated in this comment this method can be improved by adding some
try
andexcept
statements to give more detailled error messages. This will make it easier for the user to find the problem in their code.The text was updated successfully, but these errors were encountered: