Interesting, thanks for reporting! We haven’t encountered this issue yet. Will have some engineers investigate this next week.
Thank you!
Looks great. Thank you for the initial steps.
Rather than basing TSS from RPE, could you include a run FTP option so that those using a power meter don’t have to use estimated TSS?
2 Likes
The days of manually entering data or using TrainingPeaks instead are over. It took a while, but nonetheless - thank you!
1 Like
Great to see this first installment of run and multisport dropping.
Looking forward to testing it out tomorrow.
1 Like
I understand that the elevation accuracy varies but it seems run elevations are way off or at least for me. Here are the elevation gain from different platforms for the same run:
TR: 1,401m
Strava: 230m
Garmin: 299m
TrainingPeaks: 788m
Stryd: 550m
3 Likes
Loving the feature. Just curious to know about privacy options; would it be possible to make sure the map of my run can be hidden? Just want to know whats the best way to do that for my own peace of mind.
At last - thanks for doing this. Swimming and other sports such as kayaking / rowing next please along with analysis of such sports and integration into training plans etc. #MakeTrainerRoadFullyMultiSport 
Al.
Just make your account privacy “private” under the account area and no one can see your activities, etc.
Edit; at least I think that still works.
I’ve done so but I was curious if there was an options specifically to just turn off maps. Maybe a planned option for the future?
The best way to ensure privacy would be to set your account as private. Run activities will have the same restrictions as cycling activities
1 Like
Very briefly, I saw a Running Records tab (words to that effect) under Career on the web app. I only saw it prior to uploading my first run workout, and never again so I didn’t see the content, but looking forward to some form of pace PRs graph etc. in future iterations.
My first run was uploaded manually and interestingly it generated power data in TR, even though the .fit file didn’t have any power data (Log In to TrainerRoad private - for ref for TR). This wasn’t replicated in auto-syncs from Strava/Garmin which have only generated pace data. This almost suggests that TR has a pace, acceleration, weight & gradient to power algorithm lurking in the background being tested. Or something much more benign.
In all the conversations about TSS above, I bet everyone is basing their TSS comparison numbers from Training Peaks rTSS (run) which is a Normalized Graded Pace (NGP) calculated field. This seems like a fairly simple thing to calculate, being similar to Normalized Power in concept. Then, to calculate rTSS would require a threshold pace. Which could just be a self-input number. I would be interested to learn whether a run TSS from NGP is the next logical step. Because manually amending/tracking the TSS in TR is going to be a fairly arduous process in the long term.
I had a run with a significant series of pauses in the middle as I spectated a race. The RPE-calculated TSS came up with a crazy high number, as if it was using some pause time in the calculation or some other oddity. Log In to TrainerRoad
I have a Tri plan loaded in my Calendar. Runs are syncing to the Web and associating with planned runs. However, as mentioned in the release notes, runs aren’t viewable in the Windows app/mobile app at present. This results in a slightly odd situation where none of my runs in the Windows app are marked as completed. So far, AT hasn’t changed anything (adapted future runs), but visually and brain-wise this is causing dissonance. Would be interesting to hear whether I should just leave them unmarked, mark as complete in Windows or some other action to prevent any buggy behaviour.
I was looking at my Career TSS history. I’m pretty new to TR. So, before April 2022, my TSS is cycling-only imports from Strava. April-June, breaks out TR specific stress as I was on a cycling only plan. Then I switched to a Tri plan. So now my TSS includes a mess of manually marked runs and swims (if I mark as completed and bother to complete the estimated TSS, all of which comes from Training Peaks anyway). Therefore, it’s not easy to look at TSS history and take much use of it.
Key request: Be able to filter the TSS chart by sport which would help even existing flip-flopping Triathletes/cyclists as well as Early Adopters of Run imports.
I reported at least three of these points via the Early tester feedback mechanism as well.
Anyway, looking forward to seeing where this progresses.
1 Like
Thanks for taking the time to provide all your feedback.
For the power issue, I’ll DM you for some more details on that. If the .fit file doesn’t contain power data, it shouldn’t be displaying it.
TSS is definitely less standard in running and something we knew would be a topic of conversation. Our initial iteration was to keep athletes with the functionality they had previously and iterate from there.
There shouldn’t be any issues marking your runs complete on the Apps. Apps will be our next focus after addressing the issue discovered in Early Access.
Noting your feature requests as well!
I have inspected the .fit file and it contains power data! I suspect that it is injected by Sauce for Strava, the export tool of which I used to export the .fit file before uploading to TR. So it’s been “polluted” with non-original data. My fault. Sorry.
With regards marking runs complete in Windows app, I am able. However, I would prefer not to have to do this, when they are being associated on the Web app. Or if I do this, does it cause problems with the association when the two systems are aligned? I hope I’m making myself clear.
This is something that will be taken into consideration when we are adding Runs into the apps and will also need to be top of mind for us when we are completing a backfill of Runs. Your concern is a valid one, we should have you covered marking them as complete though
Hi,
I just manually uploaded a run from last week (just enabled the feature today), and it uploaded fine. I was able to associate it with the scheduled run in my calendar (following a Garmin 5k run plan - can’t wait until TR has separate run plans!).
I ran into an issue when I tried to rename the workout from ‘Evening Run’ to what the name of the workout was. I ended up getting the ‘Oops’ error page.
I’m trying to remane the title of my latest imported run but keep getting the “Ouch! We’ve taken a nasty spill!” error message.
I can see the issue on Calendar, is this also happening when trying to change the name from the detail view?
I found I would get that if I edited from from the pencil icon but if I go into the run and edit via the three dots it doesn’t 
1 Like
This seems to be the same issue as harrissilver posted above. Is it isolated to the Calendar for you? Or can you edit the name successfully from the Run Detail View?
1 Like