When using OpenStudio Results DVIEW cannot read SQL file

asked 2022-09-24 18:57:06 -0500

GR@VT's avatar

updated 2022-09-26 13:58:27 -0500

I'm using OpenStudio Version 1.4.0+ based on SDK version 3.4.0. When using the OpenStudio Results measure it seems that it writes stuff into eplusout.sql that DVIEW cannot read and makes it silently crash (i.e. without any error code or message - just gone). Does anyone else have seen the same behavior or can replicate on a simple file? And did anyone find a work-around to use both results option at the same time? I currently run the simulation twice, removing the OpenStudio Results measure when I want to check output variables with DVIEW - not really optimal if you have to simulate a large model.

edit retag flag offensive close merge delete


@GR@VT sounds very similar to this post

Aaron Boranian's avatar Aaron Boranian  ( 2022-09-26 14:03:11 -0500 )edit

Similar, but not necessarily the same. I clearly identified the cause of the crash, which is not the same as a long loading time. This can be verified by opening DVIEW directly and then loading the SQL file. A long loading time just takes a long time but doesn't crash the DVIEW window by itself. If you do this with an sql file that had the OpenStudio Results measure running during execution, the DVIEW crashes immediately without warning. So the real questions is - what does the measure do to the .sql file that makes DVIEW crash, and which side could help fix it?

GR@VT's avatar GR@VT  ( 2022-09-26 17:54:54 -0500 )edit