More info on ZoneConditioning

docs/tables/conditioning.csv

@@ -1,23 +1,23 @@
 "Setting", "Description", "Units", "Default Value"
-":ref:`cond_heating`","Description"," "," "
-":ref:`cond_h_setpoint`","Description"," "," "
-":ref:`cond_h_schedule`","Description"," "," "
-":ref:`cond_h_limit_type`","Description"," "," "
-":ref:`cond_h_max_cap`","Description"," "," "
-":ref:`cond_h_max_cap`","Description"," "," "
-":ref:`cond_h_max_flow`","Description"," "," "
-":ref:`cond_h_cop`","Description"," "," "
-":ref:`cond_c_setpoint`","Description"," "," "
-":ref:`cond_c_schedule`","Description"," "," "
-":ref:`cond_c_limit_type`","Description"," "," "
-":ref:`cond_c_max_cap`","Description"," "," "
-":ref:`cond_c_max_flow`","Description"," "," "
-":ref:`cond_c_cop`","Description"," "," "
-":ref:`cond_mech_vent`","Description"," "," "
-":ref:`cond_mv_schedule`","Description"," "," "
-":ref:`cond_min_freshair_area`","Description"," "," "
-":ref:`cond_min_freshair_pers`","Description"," "," "
-":ref:`cond_econ_type`","Description"," "," "
-":ref:`cond_hr_type`","Description"," "," "
-":ref:`cond_hr_eff_latent`","Description"," "," "
-":ref:`cond_hr_eff_sensible`","Description"," "," "
+":ref:`cond_heating`"," "," "," "
+":ref:`cond_h_setpoint`"," "," "," "
+":ref:`cond_h_schedule`"," "," "," "
+":ref:`cond_h_limit_type`"," "," "," "
+":ref:`cond_h_max_cap`"," "," "," "
+":ref:`cond_h_max_cap`"," "," "," "
+":ref:`cond_h_max_flow`"," "," "," "
+":ref:`cond_h_cop`"," "," "," "
+":ref:`cond_c_setpoint`"," "," "," "
+":ref:`cond_c_schedule`"," "," "," "
+":ref:`cond_c_limit_type`"," "," "," "
+":ref:`cond_c_max_cap`"," "," "," "
+":ref:`cond_c_max_flow`"," "," "," "
+":ref:`cond_c_cop`"," "," "," "
+":ref:`cond_mech_vent`"," "," "," "
+":ref:`cond_mv_schedule`"," "," "," "
+":ref:`cond_min_freshair_area`"," ","m3/s-m2","0.0003"
+":ref:`cond_min_freshair_pers`"," ","m3/s-person","0.0025"
+":ref:`cond_econ_type`"," "," ","NoEconomizer"
+":ref:`cond_hr_type`"," "," ","None"
+":ref:`cond_hr_eff_latent`"," "," ","0.65"
+":ref:`cond_hr_eff_sensible`"," "," ","0.70"

docs/template-info/Zone-Information/conditioning.rst

@@ -25,17 +25,23 @@ This checkbox field defines whether or not this component is available to operat
 Heating setpoint
 ````````````````
 
-The temperature below which zone heating is turned on.
+The temperature below which zone heating is turned on. Umi controls the temperature in the zone using a ThermostatSetpoint:DualSetpoint object. This would be for heating and cooling thermostat where both a heating and cooling setpoint can be scheduled for any given time period. The setpoint can be scheduled and varied throughout the simulation for both heating and cooling.
+
+.. Note::
+   In this version of umi, the heating setpoint can only be scheduled as a constant.
 
 .. index:: Heating schedule
 .. _cond_h_schedule:
 
 Heating schedule
 ````````````````
 
-Schedule for when the heating system is available. Winter only enables the heating system when the outdoor temperature is less than 5 °C.
+The name of a schedule (ref: Schedule) that denotes whether heating is available. A schedule value greater than 0 (usually 1 is used) indicates that heating and humidification are available. A value less than or equal to 0 (usually 0 is used) denotes that heating and humidification are not available. If blank, heating and humidification are always available.
+
+.. Note::
+
+   Schedule for when the heating system is available. Winter only enables the heating system when the outdoor temperature is less than 5 °C.
 
-.. todo:: to confirm
 
 .. index:: Heating limit type
 .. _cond_h_limit_type:
@@ -75,19 +81,32 @@ Efficiency of heating system. This value is used in deriving total heating energ
 Cooling
 ```````
 
+This checkbox field defines whether or not this component is available to operate. If this field is unchecked, the :ref:`cond_c_schedule` field will be forced to the generic schedule name *Off*.
+
+
 .. index:: Cooling setpoint
 .. _cond_c_setpoint:
 
 Cooling setpoint
 ````````````````
 
+The temperature above which zone heating is turned on. Umi controls the temperature in the zone using a ThermostatSetpoint:DualSetpoint object. This would be for heating and cooling thermostat where both a heating and cooling setpoint can be scheduled for any given time period.
+
+.. Note::
+   In this version of umi, the heating setpoint can only be scheduled as a constant.
+
+
 .. index:: Cooling schedule
 .. _cond_c_schedule:
 
 Cooling schedule
 ````````````````
 
-Schedule for when the cooling system is available. Summer only enables the cooling system when the outdoor temperature is greater than 8 °C below the cooling setpoint.
+The name of a schedule (ref: Schedule) that denotes whether cooling is available. A schedule value greater than 0 (usually 1 is used) indicates that cooling and dehumidification are available. A value less than or equal to 0 (usually 0 is used) denotes that cooling and dehumidification is not available. If blank, cooling and dehumidification are always available.
+
+.. Note::
+
+   Schedule for when the cooling system is available. Summer only enables the cooling system when the outdoor temperature is greater than 8 °C below the cooling setpoint.
 
 .. todo:: to confirm
 
@@ -105,6 +124,8 @@ The input must be either **LimitFlowRate**, **LimitCapacity**, **LimitFlowRateAn
 Max cooling capacity
 ````````````````````
 
+The maximum allowed total (sensible plus latent) cooling capacity in Watts per square meter if Cooling Limit is set to LimitCapacity or LimitFlowRateAndCapacity. If :ref:`cond_c_limit_type` is set to **NoLimit** or **LimitFlowRate**, this field is ignored.
+
 .. index:: Max cool flow
 .. _cond_c_max_flow:
 
@@ -127,12 +148,16 @@ Performance factor of cooling system. This value is used in deriving the total c
 Mechanical ventilation
 ``````````````````````
 
+Mechanical Ventilation affects building energy consumption by forcing Fresh Air into the zones, air that needs to be treated. If **on**, an outdoor air quantity for use by the model will be calculated.
+
 .. index:: Mechanical ventilation schedule
 .. _cond_mv_schedule:
 
 Mechanical ventilation schedule
 ```````````````````````````````
 
+This field is the reference to the schedule that defines how outdoor air requirements change over time. The schedule values are multiplied by the outdoor air flow rate defined by the next two fields. The schedule values must be between 0 and 1, inclusive. For example, if users specify the same schedule as the OccupancySchedule, this means that the current occupancy level will be used when computing the minimum outdoor air flow rate based on the next two fields.
+
 .. index:: Min fresh air per area
 .. _cond_min_freshair_area:
 
@@ -151,7 +176,7 @@ The design outdoor air volume flow rate per square meter of floor area (units ar
 Min fresh air per person
 ````````````````````````
 
-Outdoor fresh air supply relative to current occupancy.
+The design outdoor air volume flow rate per person for this zone in cubic meters per second per person. The default is 0.00944 (20 cfm per person). An outdoor air flow rate is calculated based on the total number of people for all People statements assigned to the zone. Occupancy schedule values are not applied during sizing calculations and are applied during the remainder of the simulation. This input is used if Outdoor Air Method is one of Outdoor Air Flow per Person, Sum, or Maximum.
 
 .. index:: Economizer type
 .. _cond_econ_type:

docs/template-info/Zone-Information/ventilation.rst

@@ -29,7 +29,7 @@ Infiltration rate
 Natural ventilation
 ```````````````````
 
-For this model, the ventilation air flow rate is a function of wind speed and thermal stack effect, along with the area of the opening being modeled. This object can be used alone or in combination with :ref:`vent_schduled`. This model is intended for simplified ventilation calculations as opposed to the more detailed ventilation investigations that can be performed with the AirflowNetwork model. Using the “Wind and Stack with Open Area” model, the natural ventilation flow rate can be controlled by a multiplier fraction schedule applied to the user-defined :ref:`windows_operable_area` and through the specification of minimum, maximum and delta temperatures. The temperatures can be either single constant values for the entire simulation or schedules which can vary over time.
+Natural ventilation is assumed to be air movement/exchange as a result of openings in the building façade and will not consume any fan energy. For this model, the ventilation air flow rate is a function of wind speed and thermal stack effect, along with the area of the opening being modeled. This object can be used alone or in combination with :ref:`vent_schduled`. This model is intended for simplified ventilation calculations as opposed to the more detailed ventilation investigations that can be performed with Energy+'s AirflowNetwork model. Using the “Wind and Stack with Open Area” model, the natural ventilation flow rate can be controlled by a multiplier fraction schedule applied to the user-defined :ref:`windows_operable_area` and through the specification of minimum, maximum and delta temperatures. The temperatures are taken as single constant values for the entire simulation.
 
 .. Note::
 
@@ -69,6 +69,8 @@ Defines the dehumidifying relative humidity setpoint, expressed as a percentage
 Natural ventilation schedule
 ````````````````````````````
 
+This field is the name of the schedule (:ref:`schedule`) which ultimately modifies the Opening Area value (see previous field). In its current implementation, any value greater than 0 will consider, value above The schedule values must be any positive number between 0 and 1 as a fraction. 
+
 .. index:: Natural ventilation zone temperature setpoint
 .. _vent_nat_zone_temp_setpoint: