Thoughts/suggestions? Should I move forward with this?

@shorowit @aspeake @ejhw @afontani @whiphi92

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?

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

Cool; it seems easier from a user perspective.

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.

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.

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.

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

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