#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.,
#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.,

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.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Following #30 and #31, what if you're in a shoulder season? Maybe check monotonicity as well as rate of increase/decrease of temperature.
#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.,

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.