Openstudio fails without stating errors found and blank eplusout.err file
Openstudio (1.1.0 and 3.1.0) fails just after starting simulation of a 20 story office block with 4 basements without showing the normal "program terminated energyplus terminated--error(s) detected". It just gives the red FAILED and if I open the eplusout.err file it's completely blank. Before this state it would show me some warnings in the error file but it was abruptly cut off at the end of the file, there also wasn't any severe errors only warnings.
I've already did diagnostic in sketchup, then the surface matching diagnostic in OS, both was successful. I don't know what to check anymore, can someone take a look at my file maybe?
Are you running any measures, other than OpenStudio Results, as part of the workflow? Look in the
out.oswfile and look to see if any measures have errors which you can find by searching forstep_errors. Looking at this file can also see the last measure that completed. Also try throwing away the run directory. I'm interested to see ifeplusout.erris still being generated or if that is from prior attempt at run.Only running Add Output Diagnostics but it completes successfully. I have used the VRFDOAS measure earlier (I realised afterwards its an old measure) and it ran successfully, but I'm not seeing any errors (when there were errors) relevant to the HVAC system. Created a new run directory after I deleted it.
If I run in Energyplus the only error I see is the following: EOF encountered during read of ESO header records
probable energyplus error condition -- check eplusout.err (but it's blank)
Could be something has changed related to Add Output diagnostics. If you remove that measure do you still have the same issue?
Yes, exactly the same. I actually saw a couple more warnings when I added Add output diagnostics, but when I fixed them it went blank again. I have simplified and redid the model in sketchup but still ends the same.
Could this happen if spaces were drawn upside down by accident?
No, that wouldn't do this. Most common cause might be OpenStudio failing for forward translate OSM to IDF, although then the eplousout.err file would not even be made. Could also be EnergyPlus crashing. I still want to see what happens if you just don't add that measure at all. It seems like you ran it one way (and maybe got a measure) ten changed it and that error appear to go away but it may have resulted in a corrupted file. I would like you to try to just skip that measure. If it runs fine, then we know that measure is introducing the problem.
Just tried it and still an early fail, I also think EnergyPlus is failing. Also deleted 'run' folder prior to the simulation, it was created again.
If you can't share your model here can you email the OSM and the weather file to me? a few other things to try in addition to not running the measure - From the OpenStudio Application try to export to an IDF to confirm forward translation is working. - If you are using a custom weather file try using a standard DOE provide weather file.
Thanks a lot here is the download link: https://we.tl/t-WjzdTD9ypA Weather file is from climate.onebuilding.org, it worked on other simulations IDF exports and does the same on energyplus
Thanks for the files. When I run that I get 65 of these severe errors for
Zone has no surfacesin the eplusout.err file. I'm using a mac with 10.15.7. What operating system and version are you using? It is strange that you are not seeing the same errors. Instead of using or file in place, (with a directory matching the OSM name, take the same files you gave me and open and save that, and try to run it. It will be a fresh OSW that would like just like what I ran.I just tried it and it gives me the same blank file. I did try to download and use the OS 1.1.1 alpha release but it was also blank. If I run an older, but smaller, project it works fine. I'm on windows 10 Home version 20H2 and OS app as above.
Just deleted all the thermal zones and it ran! But then it stoppped again after I edited some things. it must be a glitch somewhere for it not to show the errors.
Yes, narrowing down what you edited and having an example IDF file that E+ team can replicate this with would be helpful.
Got it going again, there was a space without surfaces that was assigned a thermal zone again. I checked my first version of the file I used and it also had a thermal zone without surfaces. Should I send an IDF to you or would you be able to use the one I sent you?
When you say you got it going do you mean EnergyPlus is now populating eplousout.err file? There may be many issues creating errors in a successful simulation, but I think the focus of this post was something unexpectedly halting the simulation leaving an empty eplousout.err file that I can't reproduce on mac.
Yes, as soon as I removed the spaces without surfaces and the thermal zones linked to spaces like that it started working like normal. I didn't get any other severe errors so it simulated and completed successfully.