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 changes in #563 have caused some issues with DirectModel as it used in SasView (and probably peoples scripts).
The text of #563 says its only an error that will occur outside of SasView and just requires different parameter names, but SasView is affected. Whilst changing the names does remove the error, it results in calculations that are incorrect (in parallelepiped at least, a -> length_a etc).
The text was updated successfully, but these errors were encountered:
Having an incorrect parameter name in a call (e.g., a rather than length_a) will cause the correct parameter name to assume the default value and ignore the incorrect parameter value.
Checking for unused parameters protects us from typos in the call. It seems strictly better to catch these errors rather than unexpectedly using the default values.
What are the cases where parameters are being passed that should not be used? Can the problem be addressed in that code instead?
The changes in #563 have caused some issues with DirectModel as it used in SasView (and probably peoples scripts).
The text of #563 says its only an error that will occur outside of SasView and just requires different parameter names, but SasView is affected. Whilst changing the names does remove the error, it results in calculations that are incorrect (in parallelepiped at least,
a
->length_a
etc).The text was updated successfully, but these errors were encountered: