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
The method update_arguments_if_invalid_input checks if the values kmod and gamma_m are correctly given by the user. A check is performed to see if the given kmod value is equal to the value it should be by using a dictionary with material IntEnum and corresponding kmod values. In this check however, the user inputed kmod value is compared to the value it should be by using an if not statement. This statement checks if the memory location of both values is the same and does not check if the values are equal. I believe an != statement should be used instead. The same holds for the check of gamma_m_value.
As an example I created a DSheetPiling Model and inputted a kmod value of 1.0. Upon debugging I found that the inputted kmod value was 1.0 and the value corresponding to the sheetpilingelementmaterialtype.value was also equal to 1.0 but still a warning was raised.
The text was updated successfully, but these errors were encountered:
The method update_arguments_if_invalid_input checks if the values kmod and gamma_m are correctly given by the user. A check is performed to see if the given kmod value is equal to the value it should be by using a dictionary with material IntEnum and corresponding kmod values. In this check however, the user inputed kmod value is compared to the value it should be by using an if not statement. This statement checks if the memory location of both values is the same and does not check if the values are equal. I believe an != statement should be used instead. The same holds for the check of gamma_m_value.
As an example I created a DSheetPiling Model and inputted a kmod value of 1.0. Upon debugging I found that the inputted kmod value was 1.0 and the value corresponding to the sheetpilingelementmaterialtype.value was also equal to 1.0 but still a warning was raised.
The text was updated successfully, but these errors were encountered: