I have reason to believe the difference might be between ZONE OPERATIVE TEMPERATURE and ZONE THERMOSTAT COOLING SETPOINT TEMPERATURE or ZONE THERMOSTAT HEATING SETPOINT TEMPERATURE.

When I take the difference between ZONE THERMOSTAT AIR TEMPERATURE and the setpoint, the unmet hours are far too low. I am using the ResStock program which gives me annual sums of unmet heating hours and unmet cooling hours. I am essentially trying to code I function myself that looks at the end_use timeseries output and computes these values manually.

The unmet hours in the resstock output are in the thousands.

Comparing Zone Thermostat Air Temperature to the Setpoint (using my own code) gives me unmet hours in the 10s, far too low

Be specific on which hours not met variable or table you are looking at and I can probably find the equation.

The variable is simulation_output_report.hours_cooling_setpoint_not_met in the ResStock results.csv output

The value given by my simulation, for the building in question, is 7299.66 hrs, for the entire year. The simulation uses a temperature tolerance of 1 degree Rankine.

Taking the hour-by-hour difference between ZONE THERMOSTAT COOLING SETPOINT TEMPERATURE and ZONE OPERATIVE TEMPERATURE, comparing to this tolerance of 1 degree Rankine, and averaging over all Zones in the residential building, gives me a value of 7448.75 hrs for the entire year.

By contrast, taking the hour-by-hour difference between ZONE THERMOSTAT COOLING SETPOINT TEMPERATURE and ZONE THERMOSTAT AIR TEMPERATURE only gives me a value of 14 hrs approximately, which doesn't agree with simulation_output_report.hours_cooling_setpoint_not_met