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
This is basically a followup for issue #724. When importing ReduceSpaceInfiltrationByPercentage, the first input _ApplytheMeasuretoaSpecificTypeortotheEntireModel is to choose a space type to apply the measure. When validating the inputs, the valid values taken from the xml file is a GUID in a curly bracket, which will lead a warning for invalid input and throw an error because of input being None. This is the reason for the breakdown in Elliot's follow-up post. Similar bugs will also occur in several other measures where the valid values for inputs are GUIDs. I feel like it is hard to fix this perfectly, so maybe it is possible to just detect when GUID is used and assign the value to the inputs anyway even if it is invalid to prevent such breakdown. I can help to fix it if you want. Let me know how it goes. Thanks!
The text was updated successfully, but these errors were encountered:
Larry7707
changed the title
importOSMeasure error when valid inputs are choices taken from .osmimportOSMeasure error when valid inputs are choices taken from os model
Jul 9, 2019
This is basically a followup for issue #724. When importing
ReduceSpaceInfiltrationByPercentage
, the first input_ApplytheMeasuretoaSpecificTypeortotheEntireModel
is to choose a space type to apply the measure. When validating the inputs, the valid values taken from the xml file is a GUID in a curly bracket, which will lead a warning for invalid input and throw an error because of input beingNone
. This is the reason for the breakdown in Elliot's follow-up post. Similar bugs will also occur in several other measures where the valid values for inputs are GUIDs. I feel like it is hard to fix this perfectly, so maybe it is possible to just detect when GUID is used and assign the value to the inputs anyway even if it is invalid to prevent such breakdown. I can help to fix it if you want. Let me know how it goes. Thanks!The text was updated successfully, but these errors were encountered: