Coach is wrong. It’s hallucinating a bit - we are working hard to help AI Coach get back on track. Apologies for suboptimal feedback. You did great on your session!
I know how many hills there are in Oslo! Dipping a little bit into l3 is ok, but you can consider walking up the hills if need be. The difference in SE and Aerobic is that undulating terrain you’re working on sports specific strength going up the hills (need to watch that HR so you don’t go too hard), while aerobic sessions, you can choose flatter terrain to run a little bit faster at aerobic internal intensity.. I used to love run along Frognerkilen and Bygdøy - flatter area and good for mental health to run by Oslofjord.
Enjoy spring running
MJ
My nickname when I lived in Oslo was “Marka” because I loved to spend time in the forests around Oslo, especially Nordmarka ..
I hope we get the coach back on track soon! I’m always getting a Total Load that is way too high, because I spend supposedly too much time in the wrong zones - which was not the case.
The zones for heart rate a probably correct and maybe I had some time in pace zone 3a, too (slight downhills). But I definitly did not spend time in the zones above, what probably leads to the high Total Load.
I have this problem with every run and I’m beginning to doubt whether the coach isn’t creating my training plan based on incorrect data - and therefore whether I can trust him. I hope you get this solved soon.
Hi, yes, we are about to release the major AI Coach changes in the next few days. Here is what it is going to look like:
Your recent run session aimed at enhancing aerobic endurance was spot on! With an RPE of 3 and an amazing feeling of 5 out of 5, it’s clear you listened to your body and maintained the right intensity. The goal is to focus on those low zones (Z1 and Z2), and you’re doing just that. Your ability to keep the stress low while still feeling great is a testament to your understanding of the training process—way to go! Looking at your compliance, it seems you’re extremely above the load recommendations, which is impressive. However, with minor distress reported in your recovery status, it might be wise to monitor how your body responds as you taper. Load compliance is vital, but what matters most is how you feel—keep that balance in mind, and don’t hesitate to take it easy if needed. Keep this momentum going; your awareness of your body will help optimize your training for that upcoming half marathon!
It is warning you about the high load because indeed it sees non-optimal recovery status on a taper week and a load (which is pace-based) is almost twice as the prescribed one. This can be due to elevation affecting paces, although it was so little that it should not have mattered. Can you please tell us if the paces you see in the session graph correspond to truth? We are trying to figure out the best solution here. Thanks a lot for your feedback!
I agree, there’s some data discrepancy here. My Garmin chart for yesterday looks perfect, nice and consistent, but AI coach is yelling about 174% compliance and the zone graph shows time in 3, 4, 5, and 7 even though my Garmin data says I never once exceeded zone 2 pace.
My heart rate data is also wrong in Athletica. The graph for that same (very easy aerobic) run shows an intended large chunk in HRZ 1, but the workout is prescribed entirely in the aerobic range up to and including HRZ 2. That particular problem came through with the synced workout on my Garmin, beacause the cool down segment had a broken heart rate zone (it came through as 130-130 rather than 91-150).
Every run is this way now.
If I weren’t already improvising this taper around an injury, I’d also be really worried my plan was not accurately reflecting my training. Very frustrating.
My half-marathon is going to happen in less then 4 weeks. I am using Athletica to prepare myself for it and managing around a busy (family) life
But somehow, I am not super confident that I am going to be well prepared for the half-marathon. The good thing, it is not a competition, so if it does not work out as expected - I just give it another try in a couple of month
Anyhow, since the day I started to pay for the service, I do have “compliance” issues. At the beginning it was indicated that the HRM on my watch could be the issue, now I have a Polar H9 HRM with chest strap to figure out - there is a bigger underlying problem.
As a paying customer - hmm - this is somehow annoying - especially after I did not like the Garmin Training Plans / Coaches - now I am struggling here too.
I hope the new update brings the suggested relief. For now, I tried to adjust my Paces manually to match the HR zones in Athletica to get a little closer to the compliance needed, but this should not be needed at all.
I don’t know if you’ve done anything yet, but my feedback from the coach has actually been super positive for the past two days. If not, maybe I’m just getting better at adhering to the prescribed workout
My feedback from last night’s workout (admittedly, a custom one) also looks better. The zone time chart still has some issues (still showing Z7 time where there was none at all) but the AI coach feedback seems to be interpreting the data reasonably.
Sort of same for me. The AI coach seemed much more positive in tone and positive that I did work across zones 1 through 7. The issue still exists that I didn’t actually do any work in zones 5, 6 or 7 though.
Thanks for the great feedback – we’re glad to hear the latest AI Coach updates have been useful!
We wanted to share a quick update regarding two ongoing areas we’re actively working on:
Compliance Algorithm Optimization
We’re continuing to refine this behind the scenes to improve accuracy and performance.
Running Pace Accuracy
We’ve received reports around discrepancies in running pace data. To clarify, this is a separate issue from the AI Coach feedback – which simply responds to the data it receives.Currently, our pace calculations rely on GPS coordinates (latitude/longitude) to compute distances, divided by the time differences between recorded timestamps. This method has shown some inconsistencies compared to devices like Garmin. While it might seem straightforward to use Garmin’s paces directly, we’re not yet certain if those are already grade-adjusted or processed in other ways, so we need to analyze this carefully before adopting them.
Until this is resolved, AI Coach will temporarily focus its running-related feedback primarily on heart rate zones rather than pace metrics.
We understand this may be frustrating and appreciate your patience. We’re juggling multiple feature releases at the moment, but this remains a priority and we’ll dive deeper into a long-term fix as soon as we can.
