Question-and-Answer Resource for the Building Energy Modeling Community
 | 1 | initial version |
DView always starts with Midnight, Jan 1 unless a data file specifically 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 (includeing timeseries) https://github.com/michaelsweeney/epparse. 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.
| | 2 | No.2 Revision |
DView always starts with Midnight, Jan 1 unless a data file specifically 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 (includeing timeseries) https://github.com/michaelsweeney/epparse. 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. tables.
| | 3 | No.3 Revision |
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 (includeing (including timeseries) https://github.com/michaelsweeney/epparse. 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.
