Refactor HTAP (.options, .choices, substitute-h2k.rb)

[fergusoa]

Dream up a better way to organize this data, including:

• How we track and compare multiple .options files for different projects.
• Do we need options files as they exist now or is a new format better
• Some of the options only require a single input and, perhaps, can be specified only in a choice file

[jblake59]

Proposal 1

Replace "HOT2000.options" files with a spreadsheet for ease-of-maintenance.

1. Tabs for "Envelope", "Heat/Cool", "Ventilation" and "Renewables"
2. Each tab contains associated attributes (tags) in columns (Header Row: OptionName, TagSetType, Cost, Tag1, Tag2. ..., TagN). Where: OptionName: Name of option (e.g., "UsrSpecR40") TagSetType: Type of the tag set (e.g., "Opt-Ceilings") Cost: The cost of this option Tag1 ... TagN: Tag variable values (different number for different tag types)
3. Each tab contains associated option sets in rows.
4. One spreadsheet tab will contain a lookup table for the relationship between tag numbers and the tag attribute names. For example, "Opt-Ceilings" tag1 has the name "Opt-Ceiling" and tag2 has the name "OPT-H2K-EffRValue"
5. Allow backwards compatibility in substitute-h2k.rb so that "old" .options files can be used.

Note: If the grouping of multiple tag types (i.e., different ceilings, walls, basements, etc.) in the same spreadsheet tab table (i.e., 1-4 above) seems too difficult to maintain, we could simply make each spreadsheet tab a separate option.

[fergusoa]

Closed - HTAP-options.json realizes most of these goails)