1

Long waiting time when openning eso file in Designbuilder Result Viewer

Hi, this is my first time posting a question.

It takes me sometimes 2 minutes to open an eso file in designbuilder Result viewer. I would like to know what are the problems causing this and how can I do to hopefully accelerate this process.

Thank you very much for your reply in advance.

richardhl's avatar
11
richardhl
asked 2023-05-09 22:38:32 -0500
Aaron Boranian's avatar
14.1k
Aaron Boranian
updated 2023-05-10 10:41:00 -0500
edit flag offensive 0 remove flag close merge delete

Comments

2

Did you try Timestep link text ? Recently I have opened 18GB .eso/sql file in this and it was way faster.

Javed's avatar Javed (2023-05-11 01:41:29 -0500) edit
add a comment see more comments

1 Answer

3

DesignBuilder just released a new version (v4), which might be faster. I have also experienced long waits for opening files (with v3). My workarounds are to:

  • limit the quantity of output variables by providing a separate "additional IDF" and de-selecting the hourly / daily / etc options before running the simulation
  • run the simulation for a design week or single season.
Jim Dirkes's avatar
3.5k
Jim Dirkes
answered 2023-05-11 05:40:47 -0500
edit flag offensive 0 remove flag delete link

Comments

Thank you vewry much, sorry for the late rely. limite the quantity really help

richardhl's avatar richardhl (2023-07-04 05:05:18 -0500) edit
add a comment see more comments
2

I have experienced the same, usually when hourly or sub-hourly results are selected for the simulation. At hourly, with 8760 outputs for each variable, this is just a significant amount of data that needs to be opened by resultsviewer, and it just takes time. I suggest being careful about selecting only the outputs you need, to limit the size of the .eso file.

If you need to work at hourly detail, there are other ways to post process the results to extract only the outputs for variables you need. An example is using eplusout python scripting, and connecting to the SQLite database, and extracting the result to csv using the 'to_csv' function. This can bypass the need to open the .eso file. See link here for details.

Also, another perhaps simpler solution is when in the simulation output options, check 'allow custom outputs' and uncheck all other outputs. Then, using the scripts module add in only the outputs you need. This should speed resultsviewer loading up a bit. Designbuilder Help has a good section on this here.

matbla's avatar
61
matbla
answered 2023-05-10 16:33:08 -0500, updated 2023-05-13 22:44:35 -0500
edit flag offensive 0 remove flag delete link

Comments

Thank you very much for your reply.

richardhl's avatar richardhl (2023-07-04 05:06:04 -0500) edit
add a comment see more comments