First time here? Check out the Help page!

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

OpenStudio - DView showing wrong simulation dates

asked Jul 18

Olamide's avatar

updated Feb 3

I simulated an OpenStudio building model with simulation dates set to Aug 4 - Aug 11 (8 days). When I view the results in DView, it shows the simulation start date as Jan 1, so all results are displayed for Jan 1 - Jan 8. I see that the question was asked a while ago here, but there was no resolution. I deleted the DDY weather file, but there is no change. I would appreciate any suggestions on what I can do differently. Thank you.

Simulation settings

IDF file: image description

Preview: (hide)

Comments

The link you've posted leads to this bug report, which appears to be inactive for well over a year. I would venture that this is strictly a WEX/DVIEW issue, and that this has likely little to do with the OpenStudio Application. But to be sure, can you check if the requested "August 4 to 11" run period is well translated in the generated IDF file (i.e. run/in.idf)? This would help narrow down the issue.

Denis Bourgeois's avatar Denis Bourgeois  ( Jul 19 )

Thank you @Denis Bourgeois. I checked, and the selected run period is in the IDF file. I have added a screenshot of it to the original post.

Olamide's avatar Olamide  ( Jul 19 )

OK. Thanks @Olamide. This confirms that the issue is unrelated to the OpenStudio Application per se. Hopefully a fix to WEX/DVIEW is in the works in the near future.

Denis Bourgeois's avatar Denis Bourgeois  ( Jul 19 )

@Denis Bourgeois thank you so much for the clarification. I will add a note to that old bug report.

Olamide's avatar Olamide  ( Jul 19 )

1 Answer

Sort by » oldest newest most voted
2

answered Jul 19

Craig Simmons's avatar

updated Jul 19

DView always starts with Midnight, Jan 1 unless a data file specifies otherwise. The output data files for E+ and OS (eplusout.sql) do not transmit the specific run period to DView. That information is contained in a separate reference table within the SQL file and currently DView is not sophisticated enough to interpret those cross references. Maybe that bug report will get picked up but I think it has been a long time since DView saw updates.

It is possible to export your data to a CSV file (from DView) and add the appropriate information to the header lines of that file if you really want to use DView. Information on doing that can be found here.

There is also at least one Python package to parse the SQL file (including timeseries) https://github.com/michaelsweeney/epp.... I've also had good luck using PowerBI, although it takes some work to get used to the table relationships and some comparisons are difficult to display due to the structure of the reference tables.

Preview: (hide)
link

Comments

@Craig Simmons thanks a lot for the explanation and additional resources!

Olamide's avatar Olamide  ( Jul 19 )

Your Answer

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

Add Answer

Training Workshops

Careers

Question Tools

1 follower

Stats

Asked: Jul 18

Seen: 236 times

Last updated: Jul 19 '24