Missing eplusout.sql after running PAT

Hi, I've launched into using PAT both locally and on the amazon cloud, after having run my sims in OS for some time. Albeit the .sql output files are large, I appreciated viewing them in Results Viewer to help me troubleshoot, as well as all the helpful .html output files from various reporting measures. However, unlike OS, after every run (local or remote) eplusout.sql is missing amid the abundance of eplusout.* files and other .htmls in my PAT project folder! I've looked long and hard to find the database in my directories, and have carefully compared output files between OS and PAT, but cannot find it -- but I concede that it is possible that I could have missed something somewhere ...
Since I had been using OS 2.1.0 with associated PAT 0.0.1, I thought it might be a version issue, so I upgraded my OS on my mac (10.12 sierra) yesterday to OS 2.2.0 with associated PAT 0.0.1 ... (also I'm a little confused on the version/iteration naming, since most online documentation/tutorials etc. refer to PAT 2.0.) But with the upgrade, still no sign of eplusout.sql. In tutorials showing PAT results on an earlier version of PAT (different anyway from the version that comes with OS 2.2.0), I've spotted that when they open their data_point directory, eplusout.sql is indeed there! Has this option since been removed from PAT?
I would love to sort this out -- any suggestions would be greatly appreciated! Thanks so much!

The eplusout.sql file will be in the datapoint's Run directory. If you ran locally these will be on your computer. If you're running in the cloud these are NOT downloaded automatically due to potential file size. You can download the datapoint from within PAT or download the datapoint zip file from OS Server on the cloud. If the datapoint completed successfully you should have an eplusout.sql file. That behavior has not changed between 1.x and 2.x. Note that there is an updated PAT 2.x tutorial here.

image description

3.8k

ljbrackney

answered 2017-09-27 09:47:32 -0500, updated 2017-09-27 09:50:36 -0500

edit flag offensive 0 remove flag delete link

Comments

When running on the cloud, there is a file size limitation at which point the file is excluded from the datapoint.zip. I think it may be 100MB? It's possible for the sql file to be larger than this.

shorowit (2017-09-27 10:15:38 -0500) edit

Thanks for your quick response, especially the screenshot. Whether I run locally or after downloading results from the cloud, the .sql file is missing from my output list. Running the same measures in OS always produced .sql's. Could it be that the following warning from the OSResults measure could have anything to do with it? "Warning: Model Summary section failed and was skipped because: Optional not initialized." (followed by an extensive list of paths to ruby files and line numbers of the warnings, but cryptic to me) ... oops, I think I may have inadvertently opened up another question!

pep4life (2017-09-27 10:18:44 -0500) edit

Do you have other eplusout files? The OSResults Measure runs after all the eplusout stuff gets generated, so it sounds like there may be a problem with the datapoint(s).

ljbrackney (2017-09-27 11:25:14 -0500) edit

Yes, I have all the eplusout.* files in my data_point directory as per your screenshot above, except .sql and .eso. The .sql must be somewhere, since the Initial Condition on the OSResults measure (last in my list of measures) reads: "Gathering data from EnergyPlus SQL file and OSM model".

pep4life (2017-09-27 11:47:26 -0500) edit

For what it's worth, I found the code that filters out files that are too large from the datapoint zip: https://github.com/NREL/OpenStudio-wo...

shorowit (2017-10-11 15:00:32 -0500) edit

add a comment see more comments

Question-and-Answer Resource for the Building Energy Modeling Community

Missing eplusout.sql after running PAT

Comments

1 Answer

Comments

Missing eplusout.sql after running PAT edit

Comments

1 Answer

Comments

Missing eplusout.sql after running PAT