Incorporate codes/programs in BuildResidentialHPXML measure

[shorowit]

We could make it easier to create an HPXML that conforms to various codes or efficiency programs (e.g., IECC, ENERGY STAR, DENH (ZERH), etc.) by creating options in the BuildResidentialHPXML measure that use the climate zone to apply the appropriate performance values.

For example, instead of these window options that require the user to look up the correct U/SHGC values for a given climate zone and code year, we could have options that are "IECC 2015", "IECC 2021", etc., and the corresponding U-factors & SHGCs could be looked up automatically in the measure.

[joseph-robertson]

This sort of reminds me of how we handle/map enclosure arguments in URBANopt.

[shorowit]

There could be two ways to implement this:

1. Allow codes/programs on a technology by technology basis (e.g., windows, walls, ducts, etc.), or
2. Allow a top-level input that somehow applies the code/program for all technologies

Option 2 might be simpler for most use cases, but Option 1 allows deviating from a given code (say, for a local code that amends IECC).