Question-and-Answer Resource for the Building Energy Modeling Community
 | 1 | initial version |
OpenStudio does have an SI/IP switch for model input but currently all output is in SI. In the OpenStudio application simulation results are shown using a reporting measure that makes an HTML file. It would be very easy for someone to update those to be SI Instad of IP. Here I a link](https://bcl.nrel.gov/node/39420) to the standard report on BCL. Unfortunately it isn't so easy for PAT. We do eventually want to have customizable PAT, but I don't have a timeline for either that or native unit switching for reporting measures.
Here is one work around. While our reporting measures generally write to HTML, you can write to csv and other formats. You could write a reporting measure to gather what you want from each simulation and then combine then in Excel to create a custom analysis report.
| | 2 | No.2 Revision |
OpenStudio does have an SI/IP switch for model input but currently all output is in SI. In the OpenStudio application simulation results are shown using a reporting measure that makes an HTML file. It would be very easy for someone to update those to be SI Instad of IP. Here I a link](https://bcl.nrel.gov/node/39420) to the standard report on BCL. Unfortunately it isn't so easy for PAT. We do eventually want to have customizable PAT, but I don't have a timeline for either that or native unit switching for reporting measures.
Here is one work around. While our reporting measures generally write to HTML, you can write to csv and other formats. You could write a reporting measure to gather what you want from each simulation and then combine then in Excel to create a custom analysis report.
Updated content below:
I should add that in general, writing a measure in SI will actually be easier than in IP. The OSM model, just like an IDF model stores everything in SI units. So when you see a measure with IP argument units and also IP output, we had to do unit conversion on both ends of the measure. It needs to be SI during the body of the measure because that's what the API expects you to pass in for an object value, and that is what will be returned if you do something like building.floorArea is an SI value.
You will see a lot of code like what is shown below. You could remove these if you want to stay in IP throughout the entire process. This page shows some example unit strings for the convert method.
value_ip = OpenStudio::convert(value_si,"m^2","tft^2").get
| | 3 | No.3 Revision |
OpenStudio does have an SI/IP switch for model input but currently all output is in SI. In the OpenStudio application simulation results are shown using a reporting measure that makes an HTML file. It would be very easy for someone to update those to be SI Instad of IP. Here I a link](https://bcl.nrel.gov/node/39420) to the standard report on BCL. Unfortunately it isn't so easy for PAT. We do eventually want to have customizable PAT, but I don't have a timeline for either that or native unit switching for reporting measures.
Here is one work around. While our reporting measures generally write to HTML, you can write to csv and other formats. You could write a reporting measure to gather what you want from each simulation and then combine then in Excel to create a custom analysis report.
Updated content below:
I should add that in general, writing a measure in SI will actually be easier than in IP. The OSM model, just like an IDF model stores everything in SI units. So when you see a measure with IP argument units and also IP output, we had to do unit conversion on both ends of the measure. It needs to be SI during the body of the measure because that's what the API expects you to pass in for an object value, and that is what will be returned if you do something like building.floorArea is an SI value.
You will see a lot of code like what is shown below. You could remove these if you want to stay in IP throughout the entire process. This page shows some example unit strings for the convert method.
value_ip = OpenStudio::convert(value_si,"m^2","tft^2").get
OpenStudio::convert(value_si,"m^2","ft^2").get
| | 4 | No.4 Revision |
OpenStudio does have an SI/IP switch for model input but currently all output is in SI. In the OpenStudio application simulation results are shown using a reporting measure that makes an HTML file. It would be very easy for someone to update those to be SI Instad instead of IP. Here I is a link](https://bcl.nrel.gov/node/39420) to the standard report on BCL. Unfortunately it isn't so easy for PAT. We do eventually want to have customizable PAT, but I don't have a timeline for either that or native unit switching for reporting measures.
Here is one work around. While our reporting measures generally write to HTML, you can write to csv and other formats. You could write a reporting measure to gather what you want from each simulation and then combine then in Excel to create a custom analysis report.
Updated content below:
I should add that in general, writing a measure in SI will actually be easier than in IP. The OSM model, just like an IDF model stores everything in SI units. So when you see a measure with IP argument units and also IP output, we had to do unit conversion on both ends of the measure. It needs to be SI during the body of the measure because that's what the API expects you to pass in for an object value, and that is what will be returned if you do something like building.floorArea is an SI value.
You will see a lot of code like what is shown below. You could remove these if you want to stay in IP throughout the entire process. This page shows some example unit strings for the convert method.
value_ip = OpenStudio::convert(value_si,"m^2","ft^2").get
