Currently, the calculation of attributes (intensive, extensive, boolean, list) for AggregatedThermalZone are always performed, even if the belonging ThermalZone instances don't have this attribute or the attribute is None. This can lead to unexpected behavior.
Currently, the calculation of attributes (intensive, extensive, boolean, list) for
AggregatedThermalZoneare always performed, even if the belongingThermalZoneinstances don't have this attribute or the attribute is None. This can lead to unexpected behavior.