Min heartrate in the heartrate iterator

Hi,

first of all, I am wondering whether the api documentation is wrong: I used iter.next.heartRate as stated here (click) but the simulator has thrown a symbol not found error. Saying this a call like iter.next.data works well. But now to my problem: I used iter.getMin() to get the minimum heartrate in the iteration. I got back 75 but in the simulator the heartrate is currently fixed to 80. I wondered why I get back 75 and did a:

and got back indeed different values, here are some:
80
null
84
81
76
75
79
83
85
82
78
76

I am wondering why since again, the heartrate is fixed to 80. I can also see that it the current heartrate is 80 since I show also the current heart rate. Where are the other numbers from and why are they there? I am pretty confused.

topcaser over 7 years ago

The forum software driving me nuts. Sometimes I get back error messages and my post is refused. Also the edit of the post doesn't work. Here again:
https://www.dropbox.com/s/2lonpqrd3chorky/GarminPost.JPG?dl=0

jim_m_58 over 7 years ago

It's just simulated, hard coded data in the sim. And it varies so if you are doing something like graphing it, it's not a straight line. It's the same for things like temperature, elevation and pressure in SensorHistory. The sim's data looks OK to me

Considering this on a real watch, the current could be 80, and the older samples could vary like you see in the sim. Each sample is saved every 1-2 minutes (you'll see about 4hrs of data is saved).

The null would be a case where the user took off the watch before the sample was saved. ("no reading")

topcaser over 7 years ago

Okay, this make sense. Thanks for clearing things up. Do you know why the attribute heartrate does not work as stated in the API doc?

jim_m_58 over 7 years ago

I'm not sure what you mean here.

topcaser over 7 years ago

Here (click) the API says that the attribute to get to the heartrate is "heartRate", indeed it's "data"

jim_m_58 over 7 years ago

It's heartrate if you use ActivityMonitor, and data if you use SensorHistory to get the info,

If you use ActivityMonitor, an invalid reading will be 255 ("INVALID_HEARTRATE"), while in SensorHistory, a null.

So there are a couple differences based on how you get the data. I'm thinking you use SensorHistory, based on the null in your first post.