Revision history [back]

@Matt Koch, If only that section is failing, I don't think it is anything work worry about, assuming you have interior lights in the model. My first guess is that one or more lights object names has a special character that is breaking the query in the tabular SQL data. You can look at the EnergyPlus HTML file to confirm the values for lights are as expected. If you don't have special character names then you can email the model to openstudio@nrel.gov and I can take a look at the cause.

@Matt Koch, If only that section is failing, I don't think it is anything work worry about, assuming you have interior lights in the model. My first guess is that one or more lights object names has a special character that is breaking the query in the tabular SQL data. You can look at the EnergyPlus HTML file to confirm the values for lights are as expected. If you don't have special character names then you can email the model to openstudio@nrel.gov and I can take a look at the cause.

@Matt Koch, If only that section is failing, I don't think it is anything work worry about, assuming you have interior lights in the model. My first guess is that one or more lights object names has a special character that is breaking the query in the tabular SQL data. You can look at the EnergyPlus HTML file to confirm the values for lights are as expected. If you don't have special character names then you can email the model to openstudio@nrel.gov and I can take a look at the cause.

@Matt Koch, If only that section is failing, I don't think it is anything work worry about, assuming you have interior lights in the model. My first guess is that one or more lights object names has a special character that is breaking the query in the tabular SQL data. You can look at the EnergyPlus HTML file to confirm the values for lights are as expected. If you don't have special character names then you can email the model to openstudio@nrel.gov and I can take a look at the cause.

Updated Below after reviewing test model:

@Matt Koch, thanks for sending the test model. Below is a bit more of the error

Interior Lighting Summary section failed and was skipped because: Optional not initialized. Detail on error follows. ["/private/var/folders/83/rcnbz4dd5qqgf7rpc69354_x0g1kng/T/OpenStudioApp.s93602/resources/measures/openstudio_results/measure.rb:278:in `eval'\n/private/var/folders/83/rcnbz4dd5qqgf7rpc69354_x0g1kng/T/OpenStudioApp.s93602/resources/measures/openstudio_results/resources/os_lib_reporting.rb:3307:in `block in interior_lighting_section'\n/private/var/folders/83/rcnbz4dd5qqgf7rpc69354_x0g1kng/T/OpenStudioApp.s93602/resources/measures/openstudio_results/resources/os_lib_reporting.rb:3306:in

Line 3307, shown below is in a loop through spaces in the model and is finding the thermal zone. thermal_zone = space.thermalZone.get
space.thermalZone is an optional, as spaces in a model do not have to have a zone, although they typically do all have thermal zones by the time you run a simulation, so we didn't write a check in this code. code to see if the optional was initialized. The model you sent has a few spaces (mechanical, elevators, and plenums) that are not assigned to thermal zones.

Spaces that are not assigned to a thermal zone, are not passed forward translated to the IDF file. It won't necessarily stop the model from running, but it will be missing elements.

@Matt Koch, If only that section is failing, I don't think it is anything work worry about, assuming you have interior lights in the model. My first guess is that one or more lights object names has a special character that is breaking the query in the tabular SQL data. You can look at the EnergyPlus HTML file to confirm the values for lights are as expected. If you don't have special character names then you can email the model to openstudio@nrel.gov and I can take a look at the cause.

Updated Below after reviewing test model:

@Matt Koch, thanks for sending the test model. Below is a bit more of the error

Interior Lighting Summary section failed and was skipped because: Optional not initialized. Detail on error follows. ["/private/var/folders/83/rcnbz4dd5qqgf7rpc69354_x0g1kng/T/OpenStudioApp.s93602/resources/measures/openstudio_results/measure.rb:278:in `eval'\n/private/var/folders/83/rcnbz4dd5qqgf7rpc69354_x0g1kng/T/OpenStudioApp.s93602/resources/measures/openstudio_results/resources/os_lib_reporting.rb:3307:in `block in interior_lighting_section'\n/private/var/folders/83/rcnbz4dd5qqgf7rpc69354_x0g1kng/T/OpenStudioApp.s93602/resources/measures/openstudio_results/resources/os_lib_reporting.rb:3306:in

Line 3307, shown below is in a loop through spaces in the model and is finding the thermal zone. thermal_zone = space.thermalZone.get
space.thermalZone is an optional, as spaces in a model do not have to have a zone, although they typically do all have thermal zones by the time you run a simulation, so we didn't write a check in this code to see if the optional was initialized. The model you sent has a few spaces (mechanical, elevators, and plenums) that are not assigned to thermal zones.

Spaces that are not assigned to a thermal zone, are not passed forward translated to the IDF file. It won't necessarily stop the model from running, but it will be missing elements.elements. There is a warning related to this in the output for the simulation, but doesn't make it into that HTML file, so it is easily missed. I may add new measure, or more likely a new section of the end of this to create table of warnings. Not just from this measure, but from any upstream measures that were run as part of the workflow. "step_warnings" : [ "EnergyPlus reported area is 1093 (m^2). OpenStudio reported area is 1156 (m^2).", "Interior Lighting Summary section failed and was skipped because: Optional not initialized. Detail on error follows.",