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

Revision history [back]

I see the simulation failing in 1.14 with the 'Set Output Table to IP Units' measure, but it's not (directly) that measure's fault. The eplustbl.html is still created with IP units. The failure is with the OpenStudio Results measure, at line 254:

annual_peak_electric_demand_kw = OpenStudio.convert(sql_file.execAndReturnFirstDouble(annual_peak_electric_demand_k_query).get, 'W', 'kW').get

The measure is attempting a query of the SQL file that fails, because the lookup units are now wrong. The comments above explain:

# adding additional runner.registerValues needed for project scripts in 2.x PAT
# note: these are not in begin rescue like individual sections. Won't fail gracefully if any SQL query's can't be found

Paging @David Goldwasser.

Re: modifying the report script, there's some discussion on that here (the measure has changed somewhat since v1.9, but the concept should be the same).

I see the simulation failing in 1.14 with the 'Set Output Table to IP Units' measure, but it's not (directly) that measure's fault. The eplustbl.html is still created with IP units. The failure is with the OpenStudio Results measure, at line 254:

annual_peak_electric_demand_kw = OpenStudio.convert(sql_file.execAndReturnFirstDouble(annual_peak_electric_demand_k_query).get, 'W', 'kW').get

The measure is attempting a query of the SQL file that fails, because the lookup units are now wrong. The comments above that line explain:

# adding additional runner.registerValues needed for project scripts in 2.x PAT
# note: these are not in begin rescue like individual sections. Won't fail gracefully if any SQL query's can't be found

Paging @David Goldwasser.

Re: modifying the report script, there's some discussion on that here (the measure has changed somewhat since v1.9, but the concept should be the same). same).

I see the simulation failing in 1.14 with the 'Set Output Table to IP Units' measure, but it's not (directly) that measure's fault. The eplustbl.html is still created with IP units. The failure is with the OpenStudio Results measure, at line 254:

annual_peak_electric_demand_kw = OpenStudio.convert(sql_file.execAndReturnFirstDouble(annual_peak_electric_demand_k_query).get, 'W', 'kW').get

The measure is attempting a query of the SQL file that fails, because the lookup units are now wrong. The comments above that line explain:

# adding additional runner.registerValues needed for project scripts in 2.x PAT
# note: these are not in begin rescue like individual sections. Won't fail gracefully if any SQL query's can't be found

Paging @David Goldwasser.

Re: modifying the report script, there's some discussion on that here (the measure has changed somewhat since v1.9, but the concept should be the same).

same). The measure currently checks the energyplus output units with the if statement at line 164. To get the measure to work with IP units you'd need to use that check to then change all the places where the measure calls OpenStudio.convert in 'os_lib_reporting.rb'.