Closed Myoldmopar closed 8 years ago
$ EnergyPlus --version
EnergyPlus, Version 8.6.0-fc5b8c5c90
$ EnergyPlus -x -r -d /tmp/myoutput -w /Applications/EnergyPlus-8-6-0/WeatherData/USA_IL_Chicago-OHare.Intl.AP.725300_TMY3.epw /Applications/EnergyPlus-8-6-0/ExampleFiles/HVACTemplate-5ZoneBaseboardHeat.idf
ExpandObjects Started.
Begin reading Energy+.idd file.
Done reading Energy+.idd file.
ExpandObjects Finished. Time: 0.037
EnergyPlus Starting
EnergyPlus, Version 8.6.0-fc5b8c5c90, YMD=2016.09.25 07:05
Processing Data Dictionary
****SNIP****
Starting Simulation at 07/07 for Chicago Ohare Intl Ap IL USA TMY3 WMO#=725300
Writing tabular output file results using HTML format.
Writing final SQL reports
ReadVarsESO program starting.
Requested ESO file=eplusout.eso
does not exist. ReadVarsESO program terminated.
ReadVarsESO program terminated.
ReadVarsESO program starting.
Requested ESO file=eplusout.mtr
does not exist. ReadVarsESO program terminated.
ReadVarsESO program terminated.
EnergyPlus Run Time=00hr 00min 0.79sec
I think that's about all I will do on Mac. I'll test Linux later.
EnergyPlus itself worked well. I tried to run IDFVersionUpdater, but ran into issues. Went back to Mac install and had trouble there as well. I may try to fix the issues, but then again, I may just spend another 2 or 3 days making my own IDFVersionUpdater tool like with EP-Launch-Lite, and release it separately after the release. That's my current plan. So this won't hold up the release. @mjwitte as you have time, could you put it through the rigors on Windows? Thanks!
Can you post an issue related to IDFVersionUpdater?
I have been checking out the windows x64 version, on a polluted Win10 OS. IDFVersionUpdater worked.
@EnergyArchmage #5873 is not ready but could be if it is important for this release
Tested on Win10 with lots of other EnergyPlus version installed. Ran various example files (including params, HVACTemplate, basement, delight, ep-macro), ran transition, opened outputs, opened IDF Editor, IDF Version Updater (transitioned v8.2 5ZoneAirCooled to v8.6) - no problems found.
I just ran IDFVersionUpdater on a Mac OS X Yosemite (10.10.5) and it transitioned files from 8.3, 8.4 and 8.5 just fine. @Myoldmopar could you describe what was failing?
Also EP-Launch-Lite does not seem to be launching. Could it be the PreProcess directory?
OK, I anticipate pushing the button today, hopefully this morning.
Seems like we need to fill this in with one more person to determine if it is just a fluke or something else:
Application | Works for @myoldmopar | Works on @jasonglazer | Works for third party |
---|---|---|---|
IDFVersionUpdater | NO | YES | ? |
EP-Launch-Lite | YES | NO | ? |
@RKStrand Has a Mac, yes?
@Myoldmopar what is weird about EP-Launch-Lite is that the version I tested just the other day is working fine. But when I try the version with the installer, it shows up for a moment in the dock and then disappears. No window opens or anything. Did you change anything when you integrated it with EnergyPlus 8.6.0 installer?
I don't believe so, @JasonGlazer. And directly launching the one from my 8.6 installer works fine. Gremlins...
OK, I was able to reproduce the EP-Launch-Lite problem on a coworker machine. I think I know the problem. I'm updating that now. I also have the performance folder removed, and the README updated. Do you plan on doing the LCC 2016 change @JasonGlazer? I hope to wrap this up before lunch.
I think I will wait until the next release on the LCC update.
Dumb. OK, I found the EP-Launch-Lite problem. The py2app application bundles up some blobs deep inside the .app/ folder, and some of those were being ignored by our .gitignore file, and so they weren't getting committed to the repo, and thus the program wouldn't run. I was able to reproduce it locally, fixed it and it runs now. I think we are done. I am tagging develop right now as v8.6.0.
Hmm, just noticed the comments above about DataCenter failing and the documentation version numbers. OK, almost there...
As for the data center file, it runs in Denver, and fails elsewhere due to the coil design conditions. Error file is clear about this. It won't hold the release. File a ticket if necessary.
As for the documentation, I updated the date and version number and merged it in. NOW I'm tagging develop as v8.6.0
A place to keep a checklist of things to do before callling 8.6.0 done