More nuanced detection of furnace/AC run #32

Closed
opened 2017-11-24 22:53:38 -06:00 by mattbk · 2 comments
mattbk commented 2017-11-24 22:53:38 -06:00 (Migrated from github.com)

Following #30 and #31, what if you're in a shoulder season? Maybe check monotonicity as well as rate of increase/decrease of temperature.

Following #30 and #31, what if you're in a shoulder season? Maybe check monotonicity as well as rate of increase/decrease of temperature.
mattbk commented 2017-11-27 16:45:12 -06:00 (Migrated from github.com)

#34 is pretty close, but there are long stretches of what look like "increase and then constant" temperatures that throw off calculations. Example would look like [60.1, 60.4, 60.4, 60.4, 60.4, 60.4], which would pass both the "increasing or constant?" and the "are they all the same?" tests and get included.

E.g.,
image

#34 is pretty close, but there are long stretches of what look like "increase and then constant" temperatures that throw off calculations. Example would look like [60.1, 60.4, 60.4, 60.4, 60.4, 60.4], which would pass both the "increasing or constant?" and the "are they all the same?" tests and get included. E.g., ![image](https://user-images.githubusercontent.com/3729038/33293362-24b3871a-d392-11e7-9eb9-a183382115e0.png)
mattbk commented 2017-11-27 16:46:55 -06:00 (Migrated from github.com)

It's probably okay to not include constant values--it might lose a minute or so when flat in between increases in temperature (and break streaks into multiple streaks), but would avoid the issue in the previous comment.

It's probably okay to not include constant values--it might lose a minute or so when flat in between increases in temperature (and break streaks into multiple streaks), but would avoid the issue in the previous comment.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: matt/pi-temp#32
No description provided.