First time here? Check out the Help page!
1 | initial version |
I am adding the answer by Harshul after a discussion with David Goldwasser on unmet hours slack.
According to David "Everything in OSM and IDF files are stored in SI units, and any API methods that alter OpenStudio objects also expect SI units. Most measures have user input in IP, then convert internally to SI to run. Then at the tail end convert back to IP for reporting.
You can change this val_si = OpenStudio.convert(val_in_fahrenheit,"F","C")
to
val_si = OpenStudio.convert(val_in_fahrenheit,"C","C")"
If you change your user argument to expect an SI value vs. an IP value. There is some work involved in this, and if we update the measures you may be out of sync with what NREL is developing as most measures are developed to take ip units.
2 | No.2 Revision |
I am adding to the answer by Harshul after a discussion with David Goldwasser on unmet hours slack.
According to David "Everything in OSM and IDF files are stored in SI units, and any API methods that alter OpenStudio objects also expect SI units. Most measures have user input in IP, then convert internally to SI to run. Then at the tail end convert back to IP for reporting.
You can change this val_si = OpenStudio.convert(val_in_fahrenheit,"F","C")
to
val_si = OpenStudio.convert(val_in_fahrenheit,"C","C")"
If you change your user argument to expect an SI value vs. an IP value. There is some work involved in this, and if we update the measures you may be out of sync with what NREL is developing as most measures are developed to take ip units.