Revision history [back]

A few points...

• There technically isn't a 90.1-2018, only 2016 and 2019.
• The OpenStudio _App_ 1.0 has the resources folder with OSMs to load as a library
• The OpenStudio _SDK_ 3.0 does not have a resources folder because it's no the GUI

A few suggestions...

• You can generate a 90.1-2016 baseline, which follows 90.1-2004, by removing the comment character (#) on line 27 of the Create Baseline Building measure, i.e. the standard_chs << 90.1-2004 below.

``` # Define the arguments that the user will input. def arguments(model) args = OpenStudio::Measure::OSArgumentVector.new

# Make an argument for the standard
standard_chs = OpenStudio::StringVector.new
# standard_chs << '90.1-2004'
standard_chs << '90.1-2007 BETA'
# 1.13.1 onward supports 90.1-2010
if model.version > OpenStudio::VersionString.new('1.13.0')
  standard_chs << '90.1-2010 BETA'
end
standard_chs << '90.1-2013'
# standard_chs << 'India ECBC 2007'
standard = OpenStudio::Measure::OSArgument.makeChoiceArgument('standard', standard_chs, true)
standard.setDisplayName('Standard')
standard.setDefaultValue('90.1-2013')
args << standard

```

• You can use any of the available templates to generate a functioning model and then apply measures during run time to match 90.1-2016/2019 performance. These are the ones that come to mind...

  • Set Exterior Wall Assembly to User Input U Value
  • Set Exterior Roof Assembly to User Input U Value
  • Replace Exterior Window Constructions with a Different Construction from the Model (required you to create a new construction first)
• Set Lighting Loads by LPD

A few points...

• There technically isn't a 90.1-2018, only 2016 and 2019.
• The OpenStudio _App_ 1.0 has the resources folder with OSMs to load as a library
• The OpenStudio _SDK_ 3.0 does not have a resources folder because it's no a standalone product and not the GUI

A few suggestions...

• You can generate a 90.1-2016 baseline, which follows 90.1-2004, by removing the comment character (#) on line 27 of the Create Baseline Building measure, i.e. the standard_chs << 90.1-2004 below.

``` `

# Define the arguments that the user will input.
 def arguments(model)
   args = OpenStudio::Measure::OSArgumentVector.new
 
OpenStudio::Measure::OSArgumentVector.new

   # Make an argument for the standard
 standard_chs = OpenStudio::StringVector.new
 # standard_chs << '90.1-2004'
 standard_chs << '90.1-2007 BETA'
 # 1.13.1 onward supports 90.1-2010
 if model.version > OpenStudio::VersionString.new('1.13.0')
   standard_chs << '90.1-2010 BETA'
 end
 standard_chs << '90.1-2013'
 # standard_chs << 'India ECBC 2007'
 standard = OpenStudio::Measure::OSArgument.makeChoiceArgument('standard', standard_chs, true)
 standard.setDisplayName('Standard')
 standard.setDefaultValue('90.1-2013')
 args << standard
 
``` 
 
You can use any of the available templates to generate a functioning model and then apply measures during run time to match 90.1-2016/2019 performance. These are the ones that come to mind...
 
 
Set Exterior Wall Assembly to User Input U Value
 
Set Exterior Roof Assembly to User Input U Value
 
Replace Exterior Window Constructions with a Different Construction from the Model (required you to create a new construction first)
 
 
Set Lighting Loads by LPD