Closed mjwitte closed 7 years ago
Output:Variable,*,Plant Demand Side Lumped Capacitance Temperature,hourly; !- HVAC Average [C]
Output:Variable,*,Plant Supply Side Lumped Capacitance Temperature,hourly; !- HVAC Average [C]
Output:Variable,*,Plant Demand Side Lumped Capacitance Heat Transport Rate,hourly; !- HVAC Average [W]
Output:Variable,*,Plant Supply Side Lumped Capacitance Heat Transport Rate,hourly; !- HVAC Average [W]
Output:Variable,*,Plant Demand Side Lumped Capacitance Heat Storage Rate,hourly; !- HVAC Average [W]
Output:Variable,*,Plant Supply Side Lumped Capacitance Heat Storage Rate,hourly; !- HVAC Average [W]
Output:Variable,*,Plant Demand Side Lumped Capacitance Excessive Storage Time,hourly; !- HVAC Sum [hr]
Output:Variable,*,Plant Supply Side Lumped Capacitance Excessive Storage Time,hourly; !- HVAC Sum [hr]
Regarding component schedules, the general rule (which probably isn't stated anywhere in the documentation) is don't schedule anything except the supply fan and the corresponding availability manager(s). Beyond that, everything should always be available and let the controls determine what runs or doesn't run. This gets most confusing when using a night cycle manager - if a component schedule other than the supply fan it won't run even when night cycle turns on the system.
for unitary systems, don't use the night cycle manager. Use a scheduled availability manager and let the system be always on. then use the Supply Air Fan Operating Mode Schedule Name in the unitary system to switch between continuous fan (for ventilation) during occupied periods and switch to cycling fan for unoccupied. The system will cycle on as the thermostat requests, and this way it will run just enough to meet the load - no need for a minimum cycle time.
[x] I/O Ref, WindowMaterial:Shade, numeric fields 5 and 6 in the IDD are:
N5 , \field Infrared Hemispherical Emissivity N6 , \field Infrared Transmittance
In the I/O Ref, the names are Thermal Hemispherical Emissivity and Thermal Transmittance. Not sure which name is batter (check other similar fields) but they should be the same, of course.
Nigusse added: Changed "Infrared" to "Thermal" to make it consistent with I/O Ref and will add notes as well as needed. Here is the note: " \note Thermal means the long-wave radiation or sometimes it is also defined as the \note the Infrared wave-length range radiation."
Changed in the following objects (both in I/O Ref and IDD): WindowMaterial:Blind, WindowMaterial:Glazing, WindowMaterial:Glazing:RefractionExtinctionMethod, WindowMaterial:Shade:EquivalentLayer, WindowMaterial:Drape:EquivalentLayer, WindowMaterial:Screen:EquivalentLayer, WindowMaterial:Glazing:EquivalentLayer,
I have not located the offending text yet.
BN added: Also added I/O Ref section to AirTerminal:SingleDuct:VAV:NoReheat. Adopted from AirTerminal:SingleDuct:VAV:Reheat
Also need to clarify this sentence describing the equation in text. We should change this sentence to read:
"The output of this curve is multiplied by the reference EIR (inverse of the reference COP) and the Energy Input to Cooling Output Ratio Function of Temperature Curve to give the energy rate (power) at the specific temperature and part-load ratio at which the chiller is operating."
@mjwitte The "Zhang-Huang Solar Model" in Section 5.1.4.3 of the Eng. Ref (V8.6) or develop version does not mention direct/diffuse split. But the following paragraph in Section 5.1.5 "Perez Direct/Diffuse Splitting Model" discusses splitting global horizontal radiation. However, this two section are not related. My be the confusion is caused because the two sections are next to each other. I also checked the I/O Ref but found nothing offending text. So there is nothing to address here.
@JasonGlazer I am looking at "Add all the native variables related to time of use to the list under UtilityCost:Tariff under the Time Of Use Period Schedule Name" documentation issue.
Looking at the I/O Ref, some of the native variables such as: IsWinter, IsNotWinter, IsSpring, IsNotSpring, IsSummer, IsNotSummer, IsAutumn, IsNotAutumn, may need to go into "Season Schedule Name" field, I think. I am not sure if all the native variables go into "Time Of Use Period Schedule Name" input field.
@Nigusse Looking further down in the original bldg-sim message, there is a link to this section of the Auxiliary Programs Doc:
However, many data sources may not have any solar radiation components. A study was undertaken to find an appropriate solar model to fill in missing solar data for weather files. The goal was to determine one or more possible solar models to use in the weather conversion/creation process. One model seemed better overall with the usual given data from the sources than others. The model, termed Zhang-Huang, has been used in a variety of locations and data creations, including the upcoming IWEC2 data. The model uses a simplistic approach of recent drybulb temperatures, sky cover, global solar constant and solar position. This model is only used when all solar values are missing from the incoming data. When global radiation is available, then a different model (Perez split) is used to split the global into direct normal and diffuse horizontal values.
I would take the last sentence about Perez out of this paragraph and add it to the paragraph that comes before this, so the progression of this section would be: a) If you have two components, then you can easily compute the third b) If you have global horizontal then Perez is used for the direct/diffuse split. c) If you have no solar data, then Zhang-Huang is used to estimate global horizontal, and Perez is used to split that into direct and diffuse.
@Nigusse I just want to make sure all the native variables that show up in the Tariff Report are documented. If they are listed in two places, some language that leads the user that is reading either field description that other variables are described in the other field would be needed.
@mjwitte Ok. updated the Auxiliary Programs text. Thanks.
@JasonGlazer Will follow the IO Ref document and the Tariff Report to make determination where to document the variables. Thanks.
Addressed all items listed in this issue. Waiting for the CI machine run for verification.
Closed via #5996