User had analysis results with odd outcomes that saturated at very low recovery times. The model had several custom components with ID's that were not proper regex syntax in the damage_states_attributes_mapping file. This caused their components to be skipped without realizing this was happening.
Solution
- Update the documentation to clearly state the regex_id column on damage_state_attribute_mapping should be regex (particular that special characters like "." need to be escaped
- Add a stronger warning to users that components are not being included (consider throwing an exception)
Additionally, the user noted that structural_system_id and associated fields could use a better definition (including what specific IDs mean)
User had analysis results with odd outcomes that saturated at very low recovery times. The model had several custom components with ID's that were not proper regex syntax in the damage_states_attributes_mapping file. This caused their components to be skipped without realizing this was happening.
Solution
Additionally, the user noted that structural_system_id and associated fields could use a better definition (including what specific IDs mean)