Question-and-Answer Resource for the Building Energy Modeling Community
 | 1 | initial version |
Looking at the error log, it seems like the coolingCapacityFunctionOfTemperature() curve on a ChillerElectricEIR object is deleted before the ChillerElectricEIR. What happens is that when ChillerElectricEIR is deleted it tries to delete it's children (curves) and the way the coolingCapacityFunctionOfTemperature() function is written, if it doesn't find its associated curve it will crash.
A common cause of this issue (and one i've had happen to me as well) is if you share curves between objects. You should never use a curve on more than one object or even for different fields in the same object. Curves do not behave like Schedules in OpenStudio. This will for sure cause the above error.
What happens is that an object will delete itself and all curves, regardless if that curve is used elsewhere. Then when you go to delete a different object that was using that same curve, it tries to delete that curve again but it is no longer valid and will crash OpenStudio.
If you are using the GUI only, this kind of error should never happen and is definitely a bug if it does. If you are using measures and the API then it is possible and likely for this crash to happen if you are not careful.
If you are not sharing curves between objects then something else in your measure it deleting the curve before the ChillerElectricEIR is deleted. Without seeing the measure it is hard to know for sure.
| | 2 | No.2 Revision |
Looking at the error log, it seems like the coolingCapacityFunctionOfTemperature() curve on a ChillerElectricEIR object is deleted before the ChillerElectricEIR. What happens is that when ChillerElectricEIR is deleted it tries to delete it's children (curves) and the way the coolingCapacityFunctionOfTemperature() function is written, if it doesn't find its associated curve it will crash.
A common cause of this issue (and one i've had happen to me as well) is if you share curves between objects. You should never use a curve on more than one object or even for different fields in the same object. Curves do not behave like Schedules in OpenStudio. This will for sure cause the above error.
What happens is that an object will delete itself and all curves, regardless if that curve is used elsewhere. Then when you go to delete a different object that was using that same curve, it tries to delete that curve again but it is no longer valid and will crash OpenStudio.
If you are using the GUI only, this kind of error should never happen and is definitely a bug if it does. If you are using measures and the API then it is possible and likely for this crash to happen if you are not careful.
If you are not sharing curves between objects then something else in your measure it is deleting the curve before the ChillerElectricEIR is deleted. Without seeing the measure it is hard to know for sure.
