New ResStockArgumentsPostHPXML measure

[joseph-robertson]

Update the workflow to accommodate writing detailed schedule csv files. This will support:

• Detailed HVAC setpoints (GEB) #852
• Water heater GEB #921

Proposal:

BuildExistingModel (and ApplyUpgrade) calls, in order:

• ResStockArguments
• BuildResidentialHPXML
• BuildResidentialScheduleFile
• ResStockArgumentsPostHPXML
  • Input:
    • hpxml_path
    • output_csv_path (for schedules.csv generated by BuildResidentialScheduleFile)
    • New arguments from options_lookup.tsv
  • Output:
    • schedules2.csv (updates hpxml_path's <SchedulesFilePath>)
• HPXMLtoOpenStudio
• ReportSimulationOutput
• ...

[joseph-robertson]

Thoughts/suggestions? Should I move forward with this?

@shorowit @aspeake @ejhw @afontani @whiphi92

[ejhw]

I defer to Scott on whether this is a good method. Can the setpoint schedules be appended to the existing schedules.csv or is there a reason they need to be separate?

[joseph-robertson]

I think, yes, we could append new schedules to the existing schedules.csv.

[ejhw]

Cool; it seems easier from a user perspective.

[shorowit]

Note that appending new schedules will have a runtime performance impact because you have to read in the entire CSV, add the columns, and then write it back out. Might check how much time that takes for a 10-min or 1-min simulation.

[shorowit]

I guess we're having to read the entire CSV either way to find the occupied/unoccupied hours for use in the HVAC setpoint generation. But writing to disk is the expensive operation.

[ejhw]

Thanks. I'm fine with separate files if we think it is worth the time savings. cc @afontani in case he has an opinion on this.

[joseph-robertson]

Are we going to be able to create new setpoint TSV files that avoid htg_stpt > clg_stpt? Or do we need to build/use the same type of "averaging" approach that OS-HPXML uses?

@ejhw

[ejhw]

@joseph-robertson I don't think we do anything special to handle that now.