**FATAL:IP: Errors occurred on processing IDF file. Preceding condition(s) cause termination.

asked 2014-12-12 15:34:11 -0500

updated 2016-09-22 00:52:03 -0500

flag of United Kingdom of Great Britain and Northern Ireland

I am a user with very little experience of simulation software trying to predict the thermal behaviour of a large office building with the aid of the Energy Plus plugin for Open Studio (1.5.0 version). I am doing this as a part of my master degree. Firstly, I have tried to build a basic model and the simulation runs without any errors. At the present moment, I have tried to run the simulator for the large building but thats not possible as it interrupts every single time with the following message:

ExpandObjects Started.
No expanded file generated.
ExpandObjects Finished. Time:     0.256
Script executing from: /private/var/folders/1l/f4r9s0ms40n666jxcnnj7m2w0000gn/T/OpenStudio.dd4423/resources/run/3-UserScript-0
Found argument 'measures_json' with value '[{"arguments":{},"measure":"/Applications/OpenStudio 1.5.0/OpenStudio.app/Contents/share/openstudio-1.5.0/pat/Measures/StandardReports/measure.rb"}]'.
Found UserScript 'Report Request'.
Processed 1 base script and 0 merged scripts
 Missing Energy+.ini
 EnergyPlus Starting
 EnergyPlus-Darwin-64 8.1.0.009, YMD=2014.12.12 23:27
 Processing Data Dictionary
 Processing Input File
 **FATAL:IP: Errors occurred on processing IDF file. Preceding condition(s) cause termination.
 EnergyPlus Run Time=00hr 00min  1.39sec

Can anyone please help me with that? I really can't tell what the problem might be. Can anyone please explain the error and what might causes it?

Thank you, Despina

edit retag flag offensive close merge delete

Comments

@Despina_pol - please update your question with the specific error causing the simulation to fail. See the eplusout.err file.

MatthewSteen ( 2014-12-16 08:48:31 -0500 )edit

@Despina_pol - please see the ERR file and rename your question with the specific error. See comments below. Thanks!

MatthewSteen ( 2015-01-06 11:54:55 -0500 )edit

add a comment

2 Answers

Sort by » oldest newest most voted

answered 2014-12-12 16:06:49 -0500

Benjamin
1145 ●1 ●10 http://ca.linkedin.com...

updated 2014-12-12 16:07:53 -0500

You'll need to provide more information from E+.

In OpenStudio, on the "Run Simulation" tab, click on the "Tree" tab at the top, and expand the tree. It's going to show you a lot of files - you are looking for the eplusout.err file. You may also want to check the *stderr file...

This file will detail all the errors & warnings in your model, and can be opened with any text editor. Once you find the file and open it, do a search for the word "Fatal" and this should direct you to the error that is causing your simulation to crash.

Unfortunately, without the error messages in your eplusout.err file, we can't help you diagnose the problem.

edit flag offensive delete link

Comments

@Benjamin @MatthewSteen @Archmage @Julien Marrec @Neal Kruis I suggest adopting a convention of changing questions with the name "**FATAL:IP: Errors occurred on processing IDF file. Preceding condition(s) cause termination." to the name of the actual error once the person posts the .err file text like I did for this question. Thoughts?

aparker ( 2014-12-15 09:32:24 -0500 )edit

We definitely need to do something about it, those messages are cryptic. I think what you've done is fine, but I'm wondering if we shouldn't remove the special characters like so: "Severe Error in Object=ZONEINFILTRATION:DESIGNFLOWRATE - Field [Schedule Name] is required but was blank" instead of "* Severe ...Error in Object=ZONEINFILTRATION:DESIGNFLOWRATE... ~~~ * Field [Schedule Name] is required but was blank"

Julien Marrec ( 2014-12-15 09:57:05 -0500 )edit

I like it. More specific to the EP error. @Michael J. Witte might like to know as well. Also related, I suggest using the tag error instead of trouble-shooting since that's what this site is all about.

MatthewSteen ( 2014-12-15 09:57:27 -0500 )edit

Also, while we're at it, the "code" function isn't working great, especially with E+ error messages. The "*" for example are understood as bold symbols sometimes... Is there something that could be done for that?

Julien Marrec ( 2014-12-15 09:58:38 -0500 )edit

Should probably leave one such generic fatal question, with a generic answer to find the severe(s) that caused the fatal.