Question-and-Answer Resource for the Building Energy Modeling Community
 | 1 | initial version |
I ran your model (OS v1.9.0) and the run failed. The stderr file in the job folder (right click the job that errors in the tree view and click 'Open Directory' to get to the temp directory for that job) contains the following:
C:/Users/ericr_000/AppData/Local/Temp/OpenStudio.e10744/resources/run/6-UserScript-0/user_script.rb:155:in `eval': Optional not initialized (RuntimeError)
from C:/Users/ericr_000/AppData/Local/Temp/OpenStudio.e10744/resources/run/6-UserScript-0/resources/os_lib_reporting.rb:2087:in `block (2 levels) in design_day_table'
This points to this line in the v1.9.0 version of the standard reporting measure. The error message is indicating that the sql query for information about the design days is returning an empty 'optional' value. I can't identify what is wrong about the design days, but trying the model with the Victoria file yields the same error. Since you mentioned the model runs fine with Seattle design days, there might be something about Canadian weather files that causes the error. @DavidGoldwasser
Note: if you update to the latest major release (OS v1.11.0) the simulation will not fail, however in the standard report you will see the error message. So whatever it is is still a problem, just not an OS run-killing problem:
| | 2 | No.2 Revision |
I ran your model (OS v1.9.0) and the run failed. The stderr file in the job folder (right click the job that errors in the tree view and click 'Open Directory' to get to the temp directory for that job) contains the following:
C:/Users/ericr_000/AppData/Local/Temp/OpenStudio.e10744/resources/run/6-UserScript-0/user_script.rb:155:in `eval': Optional not initialized (RuntimeError)
from C:/Users/ericr_000/AppData/Local/Temp/OpenStudio.e10744/resources/run/6-UserScript-0/resources/os_lib_reporting.rb:2087:in `block (2 levels) in design_day_table'
This points to this line in the v1.9.0 version of the standard reporting measure. The error message is indicating that the sql query for information about the design days is returning an empty 'optional' value. I can't identify what is wrong about the design days, but trying the model with the Victoria file yields the same error. Since you mentioned the model runs fine with Seattle design days, there might be something about Canadian weather files that causes the error. @DavidGoldwasser
Note: if you update to the latest major release (OS v1.11.0) the simulation will not fail, however in the standard report you will see the error message. So whatever it is is still a problem, just not an OS run-killing problem:
Which points to the same line in the latest standard report measure.
| | 3 | No.3 Revision |
I ran your model (OS v1.9.0) and the run failed. The stderr file in the job folder (right click the job that errors in the tree view and click 'Open Directory' to get to the temp directory for that job) contains the following:
C:/Users/ericr_000/AppData/Local/Temp/OpenStudio.e10744/resources/run/6-UserScript-0/user_script.rb:155:in `eval': Optional not initialized (RuntimeError)
from C:/Users/ericr_000/AppData/Local/Temp/OpenStudio.e10744/resources/run/6-UserScript-0/resources/os_lib_reporting.rb:2087:in `block (2 levels) in design_day_table'
This points to this line in the v1.9.0 version of the standard reporting measure. The error message is indicating that the sql query for information about the design days is returning an empty 'optional' value. I can't identify what is wrong about the design days, but trying the model with the Victoria file yields the same error. Since you mentioned the model runs fine with Seattle design days, there might be something about Canadian weather files that causes the error. @DavidGoldwasser@David Goldwasser
Note: if you update to the latest major release (OS v1.11.0) the simulation will not fail, however in the standard report you will see the error message. So whatever it is is still a problem, just not an OS run-killing problem:
Which points to the same line in the latest standard report measure.
| | 4 | No.4 Revision |
I ran your model (OS v1.9.0) and the run failed. The stderr file in the job folder (right click the job that errors in the tree view and click 'Open Directory' to get to the temp directory for that job) contains the following:
C:/Users/ericr_000/AppData/Local/Temp/OpenStudio.e10744/resources/run/6-UserScript-0/user_script.rb:155:in `eval': Optional not initialized (RuntimeError)
from C:/Users/ericr_000/AppData/Local/Temp/OpenStudio.e10744/resources/run/6-UserScript-0/resources/os_lib_reporting.rb:2087:in `block (2 levels) in design_day_table'
This points to this line in the v1.9.0 version of the standard reporting measure. The error message is indicating that the sql query for information about the design days is returning an empty 'optional' value. I can't identify what is wrong about the design days, days the measure isn't agreeing with, but trying the model a run with the Victoria file yields the same error. Since you mentioned the model runs fine with Seattle design days, there might be something about Canadian weather files that causes the error. @David Goldwasser
Note: if you update to the latest major release (OS v1.11.0) the simulation will not fail, however in the standard report you will see the error message. So whatever it is is still a problem, just not an OS run-killing problem:
Which points to the same line in the latest standard report measure.
| | 5 | No.5 Revision |
I ran your model (OS v1.9.0) and the run failed. The stderr file in the job folder (right click the job that errors in the tree view and click 'Open Directory' to get to the temp directory for that job) contains the following:
C:/Users/ericr_000/AppData/Local/Temp/OpenStudio.e10744/resources/run/6-UserScript-0/user_script.rb:155:in `eval': Optional not initialized (RuntimeError)
from C:/Users/ericr_000/AppData/Local/Temp/OpenStudio.e10744/resources/run/6-UserScript-0/resources/os_lib_reporting.rb:2087:in `block (2 levels) in design_day_table'
This points to this line in the v1.9.0 version of the standard reporting measure. The error message is indicating that the sql query for information about the design days is returning an empty 'optional' value. I can't identify what about the design days the measure isn't agreeing with, but trying a run with the Victoria file yields the same error. Since you mentioned the model runs fine with Seattle design days, there might be something about Canadian weather files that causes the error. @David Goldwasser
Note: if you update to the latest major release (OS v1.11.0) the simulation run will not fail, however in the standard report you will see the error message. So whatever it is is still a problem, just not an OS run-killing problem:
Which points to the same line in the latest standard report measure.
