Related
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Can I delete or edit wrist heart rate data before or after it gets sent to Firstbeat Technology analytics platform?

mikegreiwe
over 4 years ago

Hi All,

Yesterday, I went out for a run, and I forgot to use my Garmin chest strap heart rate monitor.  This resulted in an abnormally elevated heart rate average for the run and erroneous input to the Firstbeat analytics software to determine today's activity and my current VO2max (which went down due to the heart rate error).  Today's activity says rest and realistically, I should be doing a workout.

I'd like to be able to do the following:

  • Delete or Edit the heart rate data that is going to Firstbeat Technology 
  • Delete or edit the heart rate data before it gets saved.

Can these two features be implemented? Is there a work-around?

Thank you,

Mike

  • 0 over 4 years ago

    Unfortunately, metrics are calculated on saving, so there is no opportunity to edit the HR after the event.

    High HR data suggests the watch is moving on your wrist. Try tightening the band - I find I have to have the band 1-2 notches tighter for accurate HR while running than I do for 24/7 monitoring. Wrist HR doesn't work for everyone, but my suggestion would be to start here first.

    If you get to the start of your run, and realize you have forgotten your chest strap, you can record it using the Trail Run activity - this will not calculate a VO2Max.

    If you are part way through a run, and realize the data is coming from the wrong source because you have forgotten the strap, you could just turn the HR sensor off.

  • 0 over 4 years ago in reply to mcalista

    Thanks .

    That was super helpful.

  • 0 over 4 years ago in reply to mcalista

    That is super helpful also from my side; add a little request of advice; I often run hilly tracks, and I always find my Vo2 max worsened after these runs because hr is high, but of course, speed is not, due to uphills...do you think switching to trail run is the solution? What other implication will I have recording a run with trail run settings?

  • 0 over 4 years ago in reply to afarnedi

    This is what I do on many of my runs that involve snow/ice, ridiculous amounts of winter gear, hungover, etc.  Works well, still get a training effect score.  If you do it too much... then you will not have an updated vo2max score for system to give trend info on. 

  • 0 over 4 years ago in reply to NickMN

    Just going to leave this article here for anyone viewing looking for help with VO2 Max questions. Top VO2 Max. Estimate FAQs

    Nick Regarding your usage I agree. I would think the most people could get away with doing it on three days a week. Tempo day, speed day, and long run day. 

    Using my weekly schedule, I think I will be changing it up a bit for this year. The more reading I've done the more I think this might lead to the most useful training status information. Really what I am interested in is on a week to week basis am I getting more fit. To your point about not using it too much, as long as you get 2 runs a week with a VO2 Max estimate, it will be able to maintain your Training Status. 

  • 0 over 4 years ago in reply to Garmin-Brooks

    I am wondering if the underlying issue is similar to what I experience when I use the optical HR on my Garmin watch when running. My running cadence is typically in the 170spm to 190spm range and what happens is OHR slowly creeps up and locks onto the cadence value and stays in sync. This then screws up the Firstbeat calculations. 

    This is a portion of highlighted text (especially the section in green) from a DC Rainmaker article testing an OHR device which leads me to believe it is a fundamental issue with how OHR and cadence work. I have seen a few of my runner buddies have this experience too:
    'If we look closely at these four core 800m intervals (before the sprints later on), there’s virtually no lag at all this time. Why? Well, most optical HR sensors look at running cadence via the accelerometer as a supporting factor for figuring out intensity shifts. So in this case, it sees my cadence naturally increase as I increase intensity, allowing the algorithm to consider that a valid increase.....;
    I would be interested in your thoughts