Double check setback component in Honeybee

[mostaphaRoudsari]

http://www.grasshopper3d.com/group/ladybug/forum/topics/thermostat-setbacks

[mostaphaRoudsari]

I will check this after addressing #126.

[mostaphaRoudsari]

This is happening because the josn file doesn't have the key for setback schedules. I'm not sure why is that. Here is the available schedules :

'lighting_pri_spc_type',
'infiltration_sch',
'cooling_setpoint_sch',
'occupancy_per_area',
'elec_equip_per_area',
'rgb',
'lighting_w_per_person',
'ventilation_ach',
'lighting_standard',
'ventilation_standard',
'lighting_sec_spc_type',
'gas_equip_per_area',
'infiltration_per_area_ext',
'ventilation_pri_spc_type',
'occupancy_activity_sch',
'lighting_sch',
'occupancy_sch',
'ventilation_per_area',
'lighting_w_per_area',
'ventilation_sec_spc_type',
'ventilation_per_person',
'elec_equip_sch',
'gas_equip_sch',
'heating_setpoint_sch'

[mostaphaRoudsari]

Regardless of the warning the component looks to be working fine and generates the schedule. I think we can close this but I think it's better to have more people looking at this before I close it

[chriswmackey]

@mostapharoudsari ,

In the year or so that I have been applying this component, it has always worked as intended for the simulation but I have never completely understood the warnings that I get every time that I input vales into the setback. For this reason, I changed the warnings to cments a couple of months ago.

The way I am explaining it to myself right now, there are some setpoint schedules that govern the typical operation if the zone and others for design day conditions. The design day schedules never have setbacks and this is why the component complains.

Let me know if this is making sense.

-Chris

[mostaphaRoudsari]

Since this is working fine I change the lable to enhancement and I will check it later.

[chriswmackey]

Now that I have gone 2 years with using this feature, I feel confident that it's all working correctly. I'm going to close it out!