Question-and-Answer Resource for the Building Energy Modeling Community
 | 1 | initial version |
According this diagram from the timestep model formulation documentation, the timestamp represents the end of the timestep.
This depends on value of the Reporting Frequency field of the Output:Variable or Output:Meter used to generate the output. According to the documentation, there are several options:
Field: Reporting Frequency
This field specifies how often the variable will be listed in the output file. “Detailed” will list the value each calculation step (i.e. Zone or HVAC). “Timestep” will be the same as “Detailed” for Zone valued variables and will be aggregated to the Zone timestep (i.e. Timestep in Hour value) for HVAC variables. “Hourly” will aggregate the value to the hour. “Daily” will aggregate to the day (i.e. one value per day). “Monthly” will aggregate to the month (i.e. one value per month). “RunPeriod” will aggregate to the runperiod specified (each Design Day is a runperiod as is each runperiod object). Default for this field if left blank or omitted is Hourly.
Generally, there are two ways to figure this out:
The first way is to look at the documentation for the object's outputs. So for Zone Mean Air Temperature, we can see that the value is an average.
Zone Mean Air Temperature [C]
From the code definition, the zone mean air temperature is the average temperature of the air temperatures at the system timestep. Remember that the zone heat balance represents a “well stirred” model for a zone, therefore there is only one mean air temperature to represent the air temperature for the zone.
The second way is to look in the .rdd file that is generated after you run a simulation. This file lists all of the Output:Variables available for this model. You will notice that although Zone Mean Air Temperature is an average at the specified frequency, some of the other variables are a sum across the specified frequency. A sum really makes sense when you are looking at how much something (energy, water, etc.) was used during that period.
Output:Variable,*,Water Heater Mains Water Volume,hourly; !- HVAC Sum [m3]
Output:Variable,*,Zone Mean Air Temperature,hourly; !- Zone Average [C]
Output:Variable,*,Zone Operative Temperature,hourly; !- Zone Average [C]
| | 2 | No.2 Revision |
According this diagram from the timestep model formulation documentation, the timestamp represents the end of the timestep.
This depends on value of the Reporting Frequency field of the Output:Variable or Output:Meter used to generate the output. According to the documentation, there are several options:
Field: Reporting Frequency
This field specifies how often the variable will be listed in the output file. “Detailed” will list the value each calculation step (i.e. Zone or HVAC). “Timestep” will be the same as “Detailed” for Zone valued variables and will be aggregated to the Zone timestep (i.e. Timestep in Hour value) for HVAC variables. “Hourly” will aggregate the value to the hour. “Daily” will aggregate to the day (i.e. one value per day). “Monthly” will aggregate to the month (i.e. one value per month). “RunPeriod” will aggregate to the runperiod specified (each Design Day is a runperiod as is each runperiod object). Default for this field if left blank or omitted is Hourly.
Generally, there are two ways to figure this out:
The first way is to look at the documentation for the object's outputs. So for Zone Mean Air Temperature, we can see that the value is an average.
Zone Mean Air Temperature [C]
From the code definition, the zone mean air temperature is the average temperature of the air temperatures at the system timestep. Remember that the zone heat balance represents a “well stirred” model for a zone, therefore there is only one mean air temperature to represent the air temperature for the zone.
The second way is to look in the .rdd file that is generated after you run a simulation. This file lists all of the Output:Variables available for this model. You will notice that although Zone Mean Air Temperature is an average at the specified frequency, some of the other variables are a sum across the specified frequency. A sum really makes sense when you are looking at how much something (energy, water, etc.) was used during that period.
Output:Variable,*,Water Heater Mains Water Volume,hourly; !- HVAC Sum [m3]
Output:Variable,*,Zone Mean Air Temperature,hourly; !- Zone Average [C]
Output:Variable,*,Zone Operative Temperature,hourly; !- Zone Average [C]
