Suunto app Forum Suunto Community Forum
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    Cycling Power Estimator

    Scheduled Pinned Locked Moved SuuntoPlus™ Sports Apps
    34 Posts 7 Posters 2.5k Views 9 Watching
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • B Offline
      bubuche @mickywickyftw
      last edited by

      @mickywickyftw I owe you a feedback on previous changes (not the 13th July one): far better in descents. They are still some spikes (above 450W), when the road suddenly changes (from negative to positive grade for example). I still used 3s for the power average. I’ll switch to 10s for next moves.

      1 Reply Last reply Reply Quote 1
      • B Offline
        bubuche @mickywickyftw
        last edited by

        @mickywickyftw unfortunately, there are regressions in the last update. My feeling is that power is overestimated in descents (and is now almost as high as power in ascents). Just my feeling, as I do not have a real power meter to validate this. I would say that power should somehow be related to heart rate.

        B 1 Reply Last reply Reply Quote 0
        • B Offline
          bubuche @bubuche
          last edited by

          24f3e24d-d82a-4b1e-804c-43df40a37ca5-image.jpeg

          mickywickyftwM 1 Reply Last reply Reply Quote 0
          • mickywickyftwM Offline
            mickywickyftw Bronze Member @bubuche
            last edited by mickywickyftw

            The power estimator calculates the mechanical force required to move at a given speed on a given slope (with weight, terrain, etc. taken into account).
            Heart rate correlates with power over longer efforts but diverges significantly in short bursts (because it reacts more slowly) on descents (because you don’t have to push as hard to produce the same acceleration), and in heat (for obvious reasons). The power model doesn’t see fatigue, cardiac drift, or how hard your legs feel. But that is not its purpose either.

            The spikes are a known issue caused by the grade estimation model. They happen at grade transitions, e.g. when the road flips from downhill to uphill. Grade snaps from the descent average to the ascent average in a single second, simultaneously with the acceleration that naturally occurs there. That combination can briefly produce very high values. Difficult to work around for now, and given the altimeter’s 20cm granularity, it may not be achievable, but I’m still looking.

            Descent overestimation: I thought this might be the case. Without a cadence sensor the model has no way to detect coasting, since it cannot tell whether you’re pedalling or freewheeling. So it has to assume by comparing your speed to terminal velocity, which is calculated using… the grade estimation. So we’re back to that limitation.

            On the topic of the grade estimation used by Suunto for NGP, that algo seems to suffer the same issues.

            1 Reply Last reply Reply Quote 0
            • B Offline
              bubuche
              last edited by

              @mickywickyftw I’m aware that the model has some limitations (especially due to grade variations and without cadence sensor), but getting the same power estimation (~ 220/250W) in both a 10 minutes descent and ascent is quite unexpected (at 100bpm and 140bpm, respectively). Same position on bike. As far as I remember, I did not observe this on previous versions (I switched to 10s window today though, so not exactly same settings).

              mickywickyftwM 1 Reply Last reply Reply Quote 0
              • mickywickyftwM Offline
                mickywickyftw Bronze Member @bubuche
                last edited by

                @bubuche 200-250W is very high for a descent, true. Too high for the model as it should be I think.

                Can you help narrow it down, as I have not observed this myself?
                Zoom in on the downhill section, and note:

                • % grade
                • distance
                • start and end elevation
                • Avg power
                • Avg speed
                • Your total weight as configured in the settings (bike + rider + pack)

                If you can zoom to just that section, overlay speed and power, that might give us a clue.

                mickywickyftwM 1 Reply Last reply Reply Quote 0
                • mickywickyftwM Offline
                  mickywickyftw Bronze Member @mickywickyftw
                  last edited by

                  I think I’ve worked it out - it was a typo! Please try the latest build.
                  It meant that terminal velocity was ignored when going downhill without a sensor - resulting in those high power readings.
                  Let me know, as I cannot test this for a couple of weeks now.

                  B 2 Replies Last reply Reply Quote 1
                  • B Offline
                    bubuche @mickywickyftw
                    last edited by bubuche

                    @mickywickyftw said:

                    I think I’ve worked it out - it was a typo!

                    Ok, I’ll try in a few days 😅

                    1 Reply Last reply Reply Quote 1
                    • B Offline
                      bubuche @mickywickyftw
                      last edited by

                      @mickywickyftw said:

                      I think I’ve worked it out - it was a typo!

                      Changing a + to à - helped a lot 😅
                      This is far better in descents.

                      In a previous post, you requested the avg speed and power on a section. How? I can only get this for segments of 1/5/10 km.

                      mickywickyftwM 1 Reply Last reply Reply Quote 0
                      • mickywickyftwM Offline
                        mickywickyftw Bronze Member @bubuche
                        last edited by

                        @bubuche I would use Runalyze or another external platform for that.
                        Now I‘ve been using the latest updates for a bit, I think we‘re there.
                        I thought about using predicted wind from the weather app, but you end up losing accuracy as soon as buildings are involved.
                        I will look at using the accelerometer perhaps, but felt it was overkill when I started with this app. It might solve the grade latency issue though. I‘ll play around with it at some point.

                        1 Reply Last reply Reply Quote 0

                        Hello! It looks like you're interested in this conversation, but you don't have an account yet.

                        Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.

                        With your input, this post could be even better 💗

                        Register Login
                        • First post
                          Last post

                        Suunto Terms | Privacy Policy