Including an update on the 2K all out parsing issue.
I manually parsed the 2K section of the C2 .csv file to get average split, average HR, and average power and presented the results to the AI coach, transcript below. My prompts to the coach are in bold, all other text are the responses.
As I suspected, my training zones are quite a bit off. The AI coach provided new training zones which is very helpful. Overall, I am fine with response but I would appreciate it if support can take a look at this issue. I was going to just re-row my 2K but the AI coach suggest not to do that and work with support to get this result into the system. Also, this may help identify a bug or issue with parsing sessions like this one.
I plan to use the cheat sheet the AI coach provided for my sessions next week.
I have also included a screen shot of how the session displays in the Concept2 logbook with the 2K session clearly defined.
I did a 2K that this week that Athletica did not parse properly. My split was 1:55/500m, Average HR was 163, and my Average Power in watts was 223W.
AI Coach
AI Coach
1:39 PM
Asking the knowledge agentâŚ
Frank, thatâs a strong 2K effortâespecially with an average split of 1:55/500m and 223W! Hereâs how you can use these results for immediate training guidance and your next performance:
1. Training Zone Implications:
Your 2K average power of 223W is well above your previous training prescription (\~173W threshold). This suggests your true threshold and high-intensity zones may need to be recalibrated upwards.
Given your average heart rate (163 bpm), you likely paced well; if this wasnât your absolute max, you could even push slightly harder next time.
These numbers indicate your intervals and MIT sessions can be done at higher power, and your target VO2 should likely be set above 223W.
2. Pacing for Future 2K Efforts:
Take your recent result as your new 2K benchmark. For your next 2K, aim to start at the same split or with a slight negative split (e.g., 1:56/500m first 500m, then 1:55 or faster in the final 500m if feeling strong).
Use the 223W as your primary target power: try to stay between 223â230W.
Watch HR, but use power as the primary guide. HR lag will always occur, but if youâre holding higher power and feeling in control, your conditioning is improving.
3. Training Application:
For threshold training: Intervals (8â20 min) can now be set at 210â215W.
For VO2 work: Intervals (1â6 min) can now be targeted at 230â250W, as tolerated.
MIT sessions: Base these off 190â200W to ensure strong but sustainable aerobic stimulus.
You should expect Athletica to recalculate your training zones once an all-out effort like this gets recognized as a test. If it isnât parsed, mark the session explicitly as a âtestâ next time or insert it as a stand-alone effort in your calendar.
4. What To Do Next:
If Athletica didnât automatically update your zones, you may need to manually tag your session as a test or await a platform update.
Continue to build around this new baseline. If you want pacing and split breakdowns for different intervals or session types, just ask!
Let me know if youâd like a session-by-session cheat-sheet using your new 2K reference, or tips on marking future tests for Athletica zone recalibration.
The session is marked as a test with an aerobic session at the in the beginning with a 2â minute rest before the 2K and a few minutes rest after the 2K. It is clearly shown as a defined interval in the data. The test session is titled Aerobic + 2K All Out as well. I also submitted a support request to resolve but still nothing from support.
Frank, youâve done everything rightâmarking the session as a test, titling it clearly (âAerobic + 2K All Outâ), ensuring a defined interval, and submitting a support request. Itâs understandable to be frustrated when a maximal effort test isnât being parsed for zone recalibration.
Hereâs what you should know and some practical next steps:
Why This Happens Occasionally:
Even when a test is marked and executed as prescribed, sometimes the system logic might miss the recalibration triggerâoften due to:
How intervals are parsed (rest periods, interval boundaries, or small data gaps can occasionally affect auto-recognition)
Software update lag or technical backlog on support tickets
What You Can Do While You Wait:
Double-check that your test interval in the activity file is 2,000 meters, continuous, and not âinterruptedâ by any erroneous pause, lap mark, or data glitch.
Tag or annotate the session (âTestâ or âMax Effortâ) in your notes so that when support audits your case, your intention is crystal clear.
Keep all raw files from your device in case support requests them (e.g., .fit or .csv exports from Concept2 Logbook).
Your Training in the Meantime:
Use your new benchmark values for effort and pacing until zone recalibration is triggered:
Threshold work: Use 210â215W
Intervals/VO2: 230â250W
MIT/tempo: 190â200W
Thereâs no need to retest until the system updates. Continue your program at these effort levels.
When the recalibration goes through, Athletica will automatically update your zonesâpast sessions will be reanalyzed if needed.
If Delays Continue:
Periodically check for Athletica app updates or patch notes, as these sometimes improve interval recognition and test handling.
If support still hasnât responded after a reasonable period, you can ânudgeâ your support ticket or ask here for interim training zone advice (always happy to help you bridge that gap).
Youâre handling your training and data management in a textbook fashion, Frank. Stick with the stronger power targets your 2K now supports, and trust that your program will catch up with your progress soon. If you want, I can prep a session-by-session cheat-sheet using these recalibrated training zones for you to follow while the system update is pendingâjust let me know!
