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

OS 2.5.1 Baseline Measure Error

asked 2018-06-20 10:53:20 -0600

Tim Johnson gravatar image

updated 2018-06-20 12:09:46 -0600

I am having further issues beyond what was discussed here and here with the OpenStudio 2.5.1 updates. The error says it is unable to find the eplusout.sql file in my local temp folder. I don't understand how this folder fits into the measure, but I do know the I have an eplusout.sql file in my run folder that seems to work fine though it is nearly 200 MB. Here is the error from the baseline measure log:

ERROR Results for the run couldn't be found here: C:/Users/timj/AppData/Local/Temp/OpenStudioApp.MS1964/ApplyMeasureNow/run/000_6c1da0f7-8c62-40b0-a0e2-d327568f89c5/output/SR1/run/eplusout.sql.

This is a fairly large model at 320k sf and 120 or so zones. The OSM runs, but takes over 3 hours with no major red flags that I can see. This particular ECM is a 2012 IECC code compliance model that needs to be adapted to 2010 Appendix G. I have my .osm located here for reference. It doesn't seem to matter if I apply the 2010 or 2013 measure.

Any help on this would be appreciated as I have struggled to get the baseline measure to run on these larger OpenStudio models.

edit retag flag offensive close merge delete


I think this measure does a sizing run and sets the hard-sized equipment values. How many design days do you have? What system are you running it on?

mdahlhausen gravatar image mdahlhausen  ( 2018-06-20 12:05:40 -0600 )edit

1 Answer

Sort by ยป oldest newest most voted

answered 2018-06-20 12:10:09 -0600

updated 2018-06-20 13:04:01 -0600

So, the first sizing run is failing. If you look in the ".../output/SR1/run" folder you can find the eplusout.err file that shows this error message:

** Severe  ** <root>[Coil:Heating:Fuel][Gas Htg Coil] - Missing required property 'air_inlet_node_name'.
**  Fatal  ** Errors occurred on processing input file. Preceding condition(s) cause termination.

which looks like an orphaned gas heating coil. Sure enough, in your osm there's a 'Gas Htg Coil' not connected to anything. I don't know how the osm was running outside of the measure (I didn't try). But if you open the osm in a text editor and delete the following, the measure should run (at least, it's still chugging away as I type this).

  {20baa5ee-74eb-43b5-8d2f-a017b2bbb242}, ! Handle
  Gas Htg Coil,                           ! Name
  {92ae2cbe-524f-4de3-95e0-21fb86f6bbc3}, ! Availability Schedule Name
  0.80000000000000004,                    ! Gas Burner Efficiency
  AutoSize,                               ! Nominal Capacity {W}
  {5c3f4c02-4057-4af2-9dc8-85af02137315}, ! Air Inlet Node Name
  {be53c99a-af78-4876-a074-60e8ffc42986}, ! Air Outlet Node Name
  ,                                       ! Temperature Setpoint Node Name
  0,                                      ! Parasitic Electric Load {W}
  ,                                       ! Part Load Fraction Correlation Curve Name
  0;                                      ! Parasitic Gas Load {W}

  {64921020-54d3-41f6-82e9-c1acf3fbde83}, !- Handle
  Node 859,                               !- Name
  {be53c99a-af78-4876-a074-60e8ffc42986}, !- Inlet Port
  ;                                       !- Outlet Port

  {5c3f4c02-4057-4af2-9dc8-85af02137315}, !- Handle
  {56e6e93e-9f7d-420c-b0c6-708a020972b4}, !- Name
  ,                                       !- Source Object
  3,                                      !- Outlet Port
  {20baa5ee-74eb-43b5-8d2f-a017b2bbb242}, !- Target Object
  5;                                      !- Inlet Port

  {be53c99a-af78-4876-a074-60e8ffc42986}, !- Handle
  {41dff33c-b880-4a29-a0e7-1ea24a92b139}, !- Name
  {20baa5ee-74eb-43b5-8d2f-a017b2bbb242}, !- Source Object
  6,                                      !- Outlet Port
  {64921020-54d3-41f6-82e9-c1acf3fbde83}, !- Target Object
  2;                                      !- Inlet Port

EDIT: after that change, it still fails with an 'Optional not initialized' error, here. This is happening at this step in the 'create baseline' method, so after the new baseline fans have been created and existing HVAC removed. However, looking at the in.osm file in /SR2/run, it appears there are some Fan:VariableVolumes in that osm that are not referenced by anything, and are likely orphaned in the original osm, thus causing this error (since the script can't find any sizing info for them in the sql file). Find those fans and delete them from the original model and you should get past this error.

edit flag offensive delete link more



Eric, thanks for the help, that did the trick. When I applied other HVAC measures, they must have left some pieces. I'll be looking for that in the future. Thanks!

Tim Johnson gravatar image Tim Johnson  ( 2018-06-20 15:06:36 -0600 )edit

Your Answer

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

Add Answer

Training Workshops

Question Tools

1 follower


Asked: 2018-06-20 10:53:20 -0600

Seen: 256 times

Last updated: Jun 20 '18