Hourly Mean Air Temperature for Whole Building

savecancel

@mther, OpenStudio output variables are simply activating (then reading) EnergyPlus output variables (one-to-one match). Allowable variables are listed in the run/eplusout.rdd file, which by default would include:

Output:Variable,*,Zone Mean Air Temperature,hourly; !- Zone Average [C]
Output:Variable,*,Zone Air Temperature,hourly; !- HVAC Average [C]

... yet unavailable at the building level. Unavailable in EnergyPlus? Unavailable in OpenStudio.

In other circumstances, a Meter:Custom object might do the trick ... but that doesn't work for state variables like temperature.

There are also multiple ways of averaging state variables, e.g.:

• arithmetic mean air temperature
• zone volume-weighted average
• zone floor area-weighted

You may have some particular preference, so maybe post-processing is not a bad idea. You can always automate a solution (e.g. Ruby, Python), instead of doing it by hand.

If I'm reading this right, this measure (m_1) calculates the average zone volume-weighted air temperature for the whole building. The repo is 7-years old, yet the measure worked like a charm using OpenStudio Application v1.6.0 (SDK 3.6.1) - nice! From the generated run/eplusout.eso file ... I'm summarizing:

449,1,EMS,Weighted Average Building Zone Air Temperature [C] !TimeStep
...
449,15.76152511059765
449,16.004443655183326
449,16.02198703086131
449,15.464527023851538
449,15.985402203220058
449,16.02115237358896
449,16.023248413329345
449,15.358156264258898
...

The tested model has an unconditioned attic (US DOE SmallOffice), and I ran it for a very cold climate - hence the cold average temperatures in January. A head's up if using the measure with unconditioned spaces.

In any case, if that measure suits your needs, I think you're good to go. Hope this helps.