Question-and-Answer Resource for the Building Energy Modeling Community
Get s tarted with the Help page
Ask Your Question
2

Simulation fails at initialization, empty .err file

asked 2021-10-20 04:42:07 -0600

Kmech gravatar image

updated 2021-10-20 09:53:14 -0600

Hello guys. I am working on my thesis and when I try to run a simulation it fails just after initializing. Problem is that the .err file comes up empty. This is the .osm file.

edit retag flag offensive close merge delete

Comments

1

I don't have an answer, but can replicate what you are seeing running IDF exported from your OSM with EnergyPlus 9.5 CLI. Anyone familiar with Seg fault 11?

EnergyPlus Starting
EnergyPlus, Version 9.5.0-de239b2e5f, YMD=2021.10.22 17:26
Could not find platform independent libraries <prefix>
Could not find platform dependent libraries <exec_prefix>
Consider setting $PYTHONHOME to <prefix>[:<exec_prefix>]
Adjusting Air System Sizing
Adjusting Standard 62.1 Ventilation Sizing
Initializing Simulation
Segmentation fault: 11
David Goldwasser gravatar image David Goldwasser  ( 2021-10-22 18:27:42 -0600 )edit
1

Not the cause for the seg fault but one issue in your model is the lack of surface matching. As a result an additional 35 surfaces that should not, are exposed to outside conditions. On top of that since all of those spaces are assigned to the same thermal zone the zone surfaces are nothing like a manifold geometry and isn't something EnergyPlus is accepting, could impact floor area, volume or other calculations. I had hoped this was causing the crash, but I saw same seg fault after running surface matching on your model.

With more testing seems related to Cycling PTAC DX Clg Elec Htg

David Goldwasser gravatar image David Goldwasser  ( 2021-10-22 18:48:44 -0600 )edit

David thank you so much for taking the time and helping me with this one.

Indeed when I removed Cycling PTAC DX Clg Elec Htg and instead added ideal loads to the model the simulation run normally.

If anyone knows about Segmentation fault: 11 please let me know because I still need to add some equipment for heating and cooling.

Kmech gravatar image Kmech  ( 2021-10-25 09:34:54 -0600 )edit

1 Answer

Sort by ยป oldest newest most voted
3

answered 2021-10-26 02:38:47 -0600

I upgraded your file to E+ 9.6.0 and it doesn't segfault there. I'll paste the log below, but I know what's going on.

Please add DesignDays to your OpenStudio model. Without design days added to your OSM, there isn't a Sizing:Zone object that is written to the IDF file. Yet, your PTAC has an autosized DX cooling coil. My guess is that E+ 9.5.0 did not properly catch that condition to handle it gracefully and segfaults as a result. 9.6.0 does it though.

I added design days to your OSM model to check, and it runs perfectly fine with them.


For completeness, in the ForwardTranslator (which translates the OSM to an IDF), a check is done in ForwardTranslateThermalZone.cpp, and a Sizing:Zone object is only added if: * The ThermalZone has at least one hvac equipment or Uses the IdealAirLoads * There is at least one SizingPeriod:DesignDay in your model


The interesting part of the E+ 9.6.0 eplusout.err is this one:

** Warning ** CalculateZoneVolume: 1 zone is not fully enclosed. For more details use:  Output:Diagnostics,DisplayExtrawarnings; 
** Warning ** GetInternalHeatGains: People="PEOPLE 13", Activity Level Schedule Name values
**   ~~~   ** fall outside typical range [70,1000] W/person for Thermal Comfort Reporting.
**   ~~~   ** Odd comfort values may result; Schedule="LOBBY ACTIVITY".
**   ~~~   ** Entered min/max range=[0.0,] W/person.125.0
** Warning ** GetInternalHeatGains: People="PEOPLE 7", Activity Level Schedule Name values
**   ~~~   ** fall outside typical range [70,1000] W/person for Thermal Comfort Reporting.
**   ~~~   ** Odd comfort values may result; Schedule="CORRIDOR ACTIVITY".
**   ~~~   ** Entered min/max range=[0.0,] W/person.160.0
** Severe  ** For autosizing of ZoneHVAC:PackagedTerminalAirConditioner CYCLING PTAC DX CLG ELEC HTG, a zone sizing run must be done.
**   ~~~   ** No "Sizing:Zone" objects were entered.
**   ~~~   ** The "SimulationControl" object did not have the field "Do Zone Sizing Calculation" set to Yes.
**  Fatal  ** Program terminates due to previously shown condition(s).
edit flag offensive delete link more

Comments

I added a .ddy file and it worked. Thank you so much!

Kmech gravatar image Kmech  ( 2021-10-27 04:54:38 -0600 )edit

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

 

Question Tools

1 follower

Stats

Asked: 2021-10-20 04:42:07 -0600

Seen: 76 times

Last updated: Oct 27