Set Output Table to IP Units

asked 2018-01-11 09:02:47 -0500

Matt Koch
1998 ●2 ●17

updated 2018-10-29 18:32:21 -0500

Upon trying to run the "Set Output Table to IP Units" EnergyPlus measure in OpenStudio, I get the following error (sorry, I do not know how to format this). Does anyone know what might be wrong? The "eplustbl.html" file in the "run" directory does seem to show IP units after all.

  [08:23:01.914749 WARN] IP units were provided, SI units were expected. Leave EnergyPlus tabular results in SI units to     run this report.
 [08:23:01.928749 ERROR] Optional not initialized
    C:/Users/MattK/AppData/Local/Temp/OpenStudioApp.A12740/resources/measures/OpenStudioResults/measure.rb:276:in `get'
    C:/Users/MattK/AppData/Local/Temp/OpenStudioApp.A12740/resources/measures/OpenStudioResults/measure.rb:276:in `run'
    :/ruby/2.2.0/gems/openstudio-workflow-1.3.1/lib/openstudio/workflow/util/measure.rb:454:in `apply_measure'
    :/ruby/2.2.0/gems/openstudio-workflow-1.3.1/lib/openstudio/workflow/util/measure.rb:74:in `block in apply_measures'
    :/ruby/2.2.0/gems/openstudio-workflow-1.3.1/lib/openstudio/workflow/util/measure.rb:32:in `each_index'
    :/ruby/2.2.0/gems/openstudio-workflow-1.3.1/lib/openstudio/workflow/util/measure.rb:32:in `apply_measures'
    :/ruby/2.2.0/gems/openstudio-workflow-1.3.1/lib/openstudio/workflow/jobs/run_reporting_measures.rb:85:in `perform'
    :/ruby/2.2.0/gems/openstudio-workflow-1.3.1/lib/openstudio/workflow/run.rb:261:in `step'
    :/ruby/2.2.0/gems/openstudio-workflow-1.3.1/lib/openstudio/workflow/run.rb:210:in `run'
    :/openstudio_cli.rb:804:in `execute'
    :/openstudio_cli.rb:620:in `execute'
    :/openstudio_cli.rb:1517:in `<main>'
    eval:85:in `eval'
    eval:85:in `require_embedded_absolute'
    eval:70:in `block in require'
    eval:64:in `each'
    eval:64:in `require'
    eval:2:in `<main>'
[08:23:01.929749 ERROR] :/ruby/2.2.0/gems/openstudio-workflow-1.3.1/lib/openstudio/workflow/util/measure.rb failed with message Runner error :/ruby/2.2.0/gems/openstudio-workflow-1.3.1/lib/openstudio/workflow/util/measure.rb failed with Optional not initialized, C:/Users/MattK/AppData/Local/Temp/OpenStudioApp.A12740/resources/measures/OpenStudioResults/measure.rb:276:in `get'
C:/Users/MattK/AppData/Local/Temp/OpenStudioApp.A12740/resources/measures/OpenStudioResults/measure.rb:276:in `run'
:/ruby/2.2.0/gems/openstudio-workflow-1.3.1/lib/openstudio/workflow/util/measure.rb:454:in `apply_measure'
:/ruby/2.2.0/gems/openstudio-workflow-1.3.1/lib/openstudio/workflow/util/measure.rb:74:in `block in apply_measures'
:/ruby/2.2.0/gems/openstudio-workflow-1.3.1/lib/openstudio/workflow/util/measure.rb:32:in `each_index'
:/ruby/2.2.0/gems/openstudio-workflow-1.3.1/lib/openstudio/workflow/util/measure.rb:32:in `apply_measures'
:/ruby/2.2.0/gems/openstudio-workflow-1.3.1/lib/openstudio/workflow/jobs/run_reporting_measures.rb:85:in `perform'
:/ruby/2.2.0/gems/openstudio-workflow-1.3.1/lib/openstudio/workflow/run.rb:261:in `step'
:/ruby/2.2.0/gems/openstudio-workflow-1.3.1/lib/openstudio/workflow/run.rb:210:in `run'
:/openstudio_cli.rb:804:in `execute'
:/openstudio_cli.rb:620:in `execute'
:/openstudio_cli.rb:1517:in `<main>'
eval:85:in `eval'
eval:85:in `require_embedded_absolute'
eval:70:in `block in require'
eval ...

(more)

edit retag flag offensive close merge delete

add a comment

2 Answers

Sort by » oldest newest most voted

answered 2018-01-11 09:32:47 -0500

ericringold

10512 ●30 ●8 https://www.nrel.gov/b...

updated 2018-01-11 09:33:55 -0500

The OpenStudio Results measure needs the EnergyPlus output to be in SI to do its unit conversion to IP.

To not receive that error, don't include the OS Results measure with your run, and just do the EnergyPlus unit conversion measure.

See here, here, and related discussion here.

edit flag offensive delete link

Comments

That's it. Thanks.

Matt Koch ( 2018-01-11 09:54:00 -0500 )edit

add a comment

answered 2018-10-29 17:26:28 -0500

Dan Johnson
51 ●5

updated 2018-11-05 13:39:00 -0500

OK, so how can we get both EnergyPlus results in IP units, AND OpenStudio results in IP units? If we run the "Energyplus output to IP" measure, the OS results will fail. If we omit this measure and run only the OpenStudio Results measure, then we get no IP Energyplus results, just the SI version. How to get both?

This is even more puzzling because my coworker IS getting both. He's running both of these measures listed above, and it's not failing, and it's reporting both E+ and OS results in IP format. How is this possible? Something about his computing environment, because he runs my failing files and they work for him. I run his working (=reporting in dual IP) files, and they fail for me (= OS results fails on E+ IP units). We're both running OS v2.6.1 on Windows 10.

Update 1: So the answer is: my coworker is running a personal-library OLD VERSION of the OpenStudio Results measure, which doesn't crash upon receiving E+ results that have been converted to IP. His version is 10/24/2016. The newer version that is current on the BCL will fail and crash if it receives E+ results in IP.

These old and new measures have the same name, and they are indistinguishable to the user, unless you can find and read the actual Ruby text. To make this more difficult, one is saved in C:...User/Name/BCL and the other in C:...User/Name/Openstudio/Measures, yet they both appear as the same thing in the OS interface. One has the "BCL" brand and the other has the "My" brand, respectively. It's only by the grace of goddess that my coworker's measure was downloaded and saved offline, so it wasn't erased/synced to the current BCL version that is broken.

edit flag offensive delete link

Comments

Update 2: This older measure that worked in 2.6.1 is now broken in 2.7.0. No way to get IP units from both EnergyPlus results and Openstudio Results. Fix please.

Dan Johnson ( 2018-11-05 13:39:45 -0500 )edit

@Dan Johnson this doesn't seem to be an answer to the original question, but a new question expanding on the topic. If that is the case, check if someone else has already created a post for your specific question. If not, then feel free to create a new post for your question.