1

Massive run files

I'm working on a fairly complex Open Studio model, but some of the output files are surprisingly big. The eplusout.sql is a little over 52GB and the eplusout.eso is 22GB. Has anyone ever encountered this issue before? Any idea what might be causing it?

Thank you!

avril14's avatar
235
avril14
asked 2019-01-10 11:59:59 -0500
edit flag offensive 0 remove flag close merge delete

Comments

add a comment see more comments

1 Answer

4

Your model is probably requesting output variables in excess of what you need. Particularly, output variables of the 'Surface', 'Zone' and 'System Node' variety, with key values set to 'All' (i.e. "*") for large models will result in large amounts of data in the output files.

ericringold's avatar
10.6k
ericringold
answered 2019-01-10 12:52:48 -0500, updated 2019-01-10 12:53:16 -0500
edit flag offensive 0 remove flag delete link

Comments

Since there are so many output variables, it's easier to turn them "All Off" than turn off dozens of individual output variables. Are there any particular output variables that should remain on for the standard Energy Plus and/or Open Studio Results to properly display?

ethankheil's avatar ethankheil (2019-01-10 14:02:06 -0500) edit
1

@ethankheil there are for the OpenStudio results, but the measure that generates that report will request those variables itself, so you don't have to. The standard EnergyPlus results report does not require any user-specified time series outputs.

ericringold's avatar ericringold (2019-01-10 14:07:02 -0500) edit
add a comment see more comments