Question-and-Answer Resource for the Building Energy Modeling Community
Get started with the Help page
Ask Your Question

Design day and Runperiod value mismatch

asked 2018-08-06 01:11:14 -0500

Siv gravatar image

updated 2018-08-06 23:04:06 -0500

This particular CSV file (Please refer the image) was obtained from an EnergyPlus Simulation. The design day for this simulation is 05/21. The run period is also 05/21. Hence, both of them are same.

I take it that the variables in the upper half of the CSV file which is enclosed in a red box, corresponds to the design day values, and the rest belongs to run period.

So, I was wondering why they both are not the same ? eventhough my run period and design day are same!

image description

edit retag flag offensive close merge delete

1 Answer

Sort by ยป oldest newest most voted

answered 2018-08-06 14:24:11 -0500

While the date is the same, the sizing period and run period use different weather data.

The DesignDay uses explicitly defined maximum/minimum temperatures and other weather variables and creates a day's worth of weather using a set of multipliers. See the EnergyPlus Reference for more details.

The run period uses the weather file data which is whatever the .epw file shows for that particular day. TMY3 files use a typical month from a 30 year average, and so it is unlikely that an average 5/21 will correspond to the design day 5/21.

Additionally, schedules for design days are usually different from the weather run period values. It's typical to have design day internal load schedules fully-saturated for cooling and zero for heating.

edit flag offensive delete link more


Thank you so much for your response.

Siv gravatar imageSiv ( 2018-08-06 23:06:39 -0500 )edit

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer


Question Tools

1 follower


Asked: 2018-08-06 01:11:14 -0500

Seen: 44 times

Last updated: Aug 06