Assign detailed schedules using the lookup

[joseph-robertson]

Pull Request Description

Adds ResStockArguments arguments:

• heating_setpoint_schedule
• cooling_setpoint_schedule
• water_heater_setpoint_schedule
• battery_schedule

Update ResStockArguments measure to populate schedules_filepaths based on the contents of these new arguments. Update an arbitrary Battery option to assign battery_schedule. Only the testing project samples battery options.

Checklist

Not all may apply:

• Tests (and test files) have been updated
• Documentation has been updated
  • If related to resstock-estimation, checklist includes data dictionary, source report, options saturation, options_lookup.
• Changelog has been updated
• openstudio tasks.rb update_measures has been run
• No unexpected regression test changes on CI (checked comparison artifacts)

[joseph-robertson]

This PR has identified a bug in how OS-HPXML calculates detailed utility bills for homes with modeled batteries. The fix is here: NREL/OpenStudio-HPXML#1554.

[shorowit]

Seems unlikely that you could ever use a single schedule across all buildings in the housing stock. Maybe it should be like detailed utility rates, where you can point to files based on a specified parameter?

[joseph-robertson]

Seems unlikely that you could ever use a single schedule across all buildings in the housing stock. Maybe it should be like detailed utility rates, where you can point to files based on a specified parameter?

Yeah, I thought about that too. I think the idea in using the options_lookup, is that the schedule could differ by option for a given parameter. That's essentially the same approach used for detailed utility rates, except that the mapping is pulled out into its own lookup so as to support multiple scenarios.

[shorowit]

True, I guess you can always create a new TSV parameter for use in options_lookup to ensure you apply the desired schedule to a given building.