Cadence anomaly Forerunner 255 + Running Dynamics Pod

[David_Baak]

First of all, I am very happy with this platform!
I am using a Garmin Forerunner 255 and a Running Dynamics Pod. The cadence on Stava and Garmin Mobile Connect is correct (around 180 spm when running). Intervals displays the number 90, so half the spm.
Strava

Intervals

[MedTechCD]

Intervals started as a cycling app and in cycling cadence is based on revolutions. In running it is steps. @david already has this on the todo list.

[David_Baak]

Aha, that explains the exact division by 2!

[nichalam]

Hi,

I am having the same issue on Forerunner 955 + Running Dynamics Pod. So it’s not hardware related right? Just a fix from David’s side correct?

[david]

Yes this needs a fix in Intervals.icu.

[Povedano]

In the meantime, I have a custom activity field and a custom interval field. The only problem is the lack of the graphic, but for me it is ok with the total and interval average.

Activity field

cadences = streams.get("cadence").data
times = streams.get("time").data

cadence=0
totalCadence=0

for (let i=0; i<times.length; i++) {
  cadence=cadences[i]*2
  totalCadence+=cadence
  //console.log(cadence)
}

finalCadence = totalCadence/times.length

Interval field

cadences = streams.get("cadence").data

totalCadence=0
count=0

for (let i=interval.start_time; i<interval.end_time; i++){
  count++
  totalCadence+=cadences[i]*2
}

finalCadence = totalCadence/count

[david]

Tx. You can do it a little easier using activity.average_cadence * 2 and interval.average_cadence * 2.

Also with your interval code you need to use interval.start_index and interval.end_index for this sort of thing. The times will only work if there is 1 second per tick and no missing data points.