Question-and-Answer Resource for the Building Energy Modeling Community
 | 1 | initial version |
It sounds very strange...
You can easily reproduce this OpenStudio behavior by starting a new file (I have used version 3.7.0), drawing a simple box model (one thermal zone), applying the default ASHRAE office space type, construction set, and schedule set (including heating and cooling setpoints), activating ideal loads in the thermal zones tab, and without applying any measure (not even the default reporting measure), launch a whole-year simulation with a 6-timestep configuration.
The following code lines always appear at the end of the IDF file generated in run folder, corresponding to Output:Meter objects not configured by the user (and not present in the original OSM file):
Output:Meter:MeterFileOnly,
NaturalGas:Facility, !- Key Name
Daily; !- Reporting Frequency
Output:Meter:MeterFileOnly,
Electricity:Facility, !- Key Name
Timestep; !- Reporting Frequency
Output:Meter:MeterFileOnly,
Electricity:Facility, !- Key Name
Daily; !- Reporting Frequency
Output:Meter,
Electricity:Facility, !- Key Name
Timestep; !- Reporting Frequency
Output:Meter,
NaturalGas:Facility, !- Key Name
Timestep; !- Reporting Frequency
Output:Meter,
DistrictCooling:Facility, !- Key Name
Timestep; !- Reporting Frequency
Output:Meter,
DistrictHeating:Facility, !- Key Name
Timestep; !- Reporting Frequency
Even more, if you model a DHW system, Air-loop based HVAC system, etc., you can get a lot more Output:Meters, always in timestep reporting frequency.
In this simple box model I get the output in sql and eso files for only the Output:Meter objects corresponding to DistrictCooling:Facility and Electricity:Facility, as DistrictHeating:Facility is not supported in the last versions of EnergyPlus (now it's called DistrictHeatingWater:Facility).
Any idea on how to avoid this?
| | 2 | No.2 Revision |
It sounds very strange...
You can easily reproduce this in OpenStudio behavior by starting a new file (I have used version 3.7.0), drawing a simple box model (one thermal zone), applying the default ASHRAE office space type, construction set, and schedule set (including heating and cooling setpoints), activating ideal loads in the thermal zones tab, and without applying any measure (not even the default reporting measure), launch a whole-year simulation with a 6-timestep configuration.
The following code lines always appear at the end of the IDF file generated in run folder, corresponding to Output:Meter objects not configured by the user (and not present in the original OSM file):
Output:Meter:MeterFileOnly,
NaturalGas:Facility, !- Key Name
Daily; !- Reporting Frequency
Output:Meter:MeterFileOnly,
Electricity:Facility, !- Key Name
Timestep; !- Reporting Frequency
Output:Meter:MeterFileOnly,
Electricity:Facility, !- Key Name
Daily; !- Reporting Frequency
Output:Meter,
Electricity:Facility, !- Key Name
Timestep; !- Reporting Frequency
Output:Meter,
NaturalGas:Facility, !- Key Name
Timestep; !- Reporting Frequency
Output:Meter,
DistrictCooling:Facility, !- Key Name
Timestep; !- Reporting Frequency
Output:Meter,
DistrictHeating:Facility, !- Key Name
Timestep; !- Reporting Frequency
Even more, if you model a DHW system, Air-loop based HVAC system, etc., you can get a lot more Output:Meters, always in timestep reporting frequency.
In this simple box model I get the output in sql and eso files for only the Output:Meter objects corresponding to DistrictCooling:Facility and Electricity:Facility, as DistrictHeating:Facility is not supported in the last versions of EnergyPlus (now it's called DistrictHeatingWater:Facility).
Any idea on how to avoid this?
| | 3 | No.3 Revision |
It sounds very strange...
You can easily reproduce this in OpenStudio by starting a new file (I have used version 3.7.0), drawing a simple box model (one thermal zone), applying the default ASHRAE office space type, construction set, and schedule set (including heating and cooling setpoints), activating ideal loads in the thermal zones tab, and without applying any measure (not even the default reporting measure), launch a whole-year simulation with a 6-timestep configuration.
The following code lines always appear at the end of the IDF file generated in run folder, corresponding to Output:Meter objects not configured by the user (and not present in the original OSM file):
Output:Meter:MeterFileOnly,
NaturalGas:Facility, !- Key Name
Daily; !- Reporting Frequency
Output:Meter:MeterFileOnly,
Electricity:Facility, !- Key Name
Timestep; !- Reporting Frequency
Output:Meter:MeterFileOnly,
Electricity:Facility, !- Key Name
Daily; !- Reporting Frequency
Output:Meter,
Electricity:Facility, !- Key Name
Timestep; !- Reporting Frequency
Output:Meter,
NaturalGas:Facility, !- Key Name
Timestep; !- Reporting Frequency
Output:Meter,
DistrictCooling:Facility, !- Key Name
Timestep; !- Reporting Frequency
Output:Meter,
DistrictHeating:Facility, !- Key Name
Timestep; !- Reporting Frequency
Even more, if you model a DHW system, Air-loop based HVAC system, etc., you can get a lot more Output:Meters, always in timestep reporting frequency.
In this simple box model I get the output in sql and eso files for only the Output:Meter objects corresponding to DistrictCooling:Facility and Electricity:Facility, as DistrictHeating:Facility is not supported in the last versions of EnergyPlus (now it's called DistrictHeatingWater:Facility).
Any idea on how to avoid this?
UPDATE: You can reproduce it identically also with OpenStudio 1.5.0.
| | 4 | No.4 Revision |
It sounds very strange...
You can easily reproduce this in OpenStudio by starting a new file (I have used version OS App 1.7.0 and SDK 3.7.0), drawing a simple box model (one thermal zone), applying the default ASHRAE office space type, construction set, and schedule set (including heating and cooling setpoints), activating ideal loads in the thermal zones tab, and without applying any measure (not even the default reporting measure), launch a whole-year simulation with a 6-timestep configuration.
The following code lines always appear at the end of the IDF file generated in run folder, corresponding to Output:Meter objects not configured by the user (and not present in the original OSM file):
Output:Meter:MeterFileOnly,
NaturalGas:Facility, !- Key Name
Daily; !- Reporting Frequency
Output:Meter:MeterFileOnly,
Electricity:Facility, !- Key Name
Timestep; !- Reporting Frequency
Output:Meter:MeterFileOnly,
Electricity:Facility, !- Key Name
Daily; !- Reporting Frequency
Output:Meter,
Electricity:Facility, !- Key Name
Timestep; !- Reporting Frequency
Output:Meter,
NaturalGas:Facility, !- Key Name
Timestep; !- Reporting Frequency
Output:Meter,
DistrictCooling:Facility, !- Key Name
Timestep; !- Reporting Frequency
Output:Meter,
DistrictHeating:Facility, !- Key Name
Timestep; !- Reporting Frequency
Even more, if you model a DHW system, Air-loop based HVAC system, etc., you can get a lot more Output:Meters, always in timestep reporting frequency.
In this simple box model I get the output in sql and eso files for only the Output:Meter objects corresponding to DistrictCooling:Facility and Electricity:Facility, as DistrictHeating:Facility is not supported in the last versions of EnergyPlus (now it's called DistrictHeatingWater:Facility).
Any idea on how to avoid this?
UPDATE: You can reproduce it identically also with OpenStudio 1.5.0.App 1.5.0 (SDK 3.5.1).
| | 5 | No.5 Revision |
It sounds very strange...
You can I could easily reproduce this in OpenStudio by starting a new file (I have used version OS App 1.7.0 and SDK 3.7.0), drawing a simple box model (one thermal zone), applying the default ASHRAE office space type, construction set, and schedule set (including heating and cooling setpoints), activating ideal loads in the thermal zones tab, and without applying any measure (not even the default reporting measure), launch a whole-year simulation with a 6-timestep configuration.
The following code lines always appear at the end of the IDF file generated in run folder, corresponding to Output:Meter objects not configured by the user (and not present in the original OSM file):
Output:Meter:MeterFileOnly,
NaturalGas:Facility, !- Key Name
Daily; !- Reporting Frequency
Output:Meter:MeterFileOnly,
Electricity:Facility, !- Key Name
Timestep; !- Reporting Frequency
Output:Meter:MeterFileOnly,
Electricity:Facility, !- Key Name
Daily; !- Reporting Frequency
Output:Meter,
Electricity:Facility, !- Key Name
Timestep; !- Reporting Frequency
Output:Meter,
NaturalGas:Facility, !- Key Name
Timestep; !- Reporting Frequency
Output:Meter,
DistrictCooling:Facility, !- Key Name
Timestep; !- Reporting Frequency
Output:Meter,
DistrictHeating:Facility, !- Key Name
Timestep; !- Reporting Frequency
Even more, if you I model a DHW system, Air-loop based HVAC system, etc., you can get a lot more Output:Meters, always in timestep reporting frequency.
In this simple box model I get the output in sql and eso files for only the Output:Meter objects corresponding to DistrictCooling:Facility and Electricity:Facility, as DistrictHeating:Facility is not supported in the last versions of EnergyPlus (now it's called DistrictHeatingWater:Facility).
Any idea on how to avoid this?
UPDATE: You can I could reproduce it identically also with OpenStudio App 1.5.0 (SDK 3.5.1).
