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.