You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Problem: right now you can only use one model runPeriod.
Solution: Add ability to have several runPeriods.
Context: It’s extremely useful during iterative changes or troubleshooting. You might want to have for example a run for three days: one in winter (january), one in summer (july) and one in shoulder season (april). That would allow short runtime while still seeing different load conditions.
Also, I could also see a case where you’d run for a week in each month (reduce runtime but without sacrificing the accuracy too much). The good thing about using several runPeriods in EnergyPlus (rather than launching a parametric analysis where you do 12 individual runs) is that the sizing only happens once, AND all the runs end up in the SAME SQL file, which makes aggregation of the results much easier. That would allow easier creation of measures for new workflows such as this one.
Problem: right now you can only use one model
runPeriod
.Solution: Add ability to have several runPeriods.
Context: It’s extremely useful during iterative changes or troubleshooting. You might want to have for example a run for three days: one in winter (january), one in summer (july) and one in shoulder season (april). That would allow short runtime while still seeing different load conditions.
Also, I could also see a case where you’d run for a week in each month (reduce runtime but without sacrificing the accuracy too much). The good thing about using several runPeriods in EnergyPlus (rather than launching a parametric analysis where you do 12 individual runs) is that the sizing only happens once, AND all the runs end up in the SAME SQL file, which makes aggregation of the results much easier. That would allow easier creation of measures for new workflows such as this one.
Migrated from UserVoice
The text was updated successfully, but these errors were encountered: