Changing setpoints with measure files

edit

You might try adding the following to the .idf file:

Output:Variable,*,Zone Air Temperature,hourly; !- HVAC Average [C] 
Output:Variable,*,Zone Thermostat Air Temperature,hourly; !- HVAC Average [C]
Output:Variable,*,Zone Thermostat Heating Setpoint Temperature,hourly; !- HVAC Average [C]
Output:Variable,*,Zone Thermostat Cooling Setpoint Temperature,hourly; !- HVAC Average [C]

You can then open the eplusout.sql file with DView to see zone temperature vs. setpoints. Is that what you are looking for?

Thank you for the suggestion, Matt! This is actually a way that I can test that the setpoint changing measure files to work correctly.

I can put my main question at a higher level, though. Is there any method, other than the Ruby-based measure files, that I can change setpoints in certain hours automatically?

As you're likely running OpenStudio (re: measures), you can activate the output variables Matt suggested directly in the App (or through the SDK). In addition to plotting setpoint vs sensed temperatures, you could also do a diff between .osm files (before vs after running the measure), as well as checking the eplusout.err file ... i.e., is the measure inadvertently doing more than expected?

What do you mean by "changing setpoints at certain hours automatically"? Dynamically e.g., based on runtime variable outputs? If so, EMS would be well suited for this (which you can also define via the SDK).

Thanks for the details, Denis. I mean for the setpoint to be set during certain hours (which is already known as an exogenous output) through a series of scripts (similar to what the measure intends to do). As I am facing issue doing it with the measure files, I'm thinking of finding an alternative method.