How to get the Join value correct? The value in the Join app is different with the value in Intervals.icu.
Sorry, have not been on this forum for a long time. I am still using the script but the public version seems to have disappeared (but shared again by dvkoko above). Important that FTP, weight and CTL are the same in both Join and Intervals.
It seems that when a new activity is uploaded to intervals, the parameter âactivity.icu_ctlâ does not take into account the contribution of the newly uploaded activity and thereby underestimates current CTL. The simple solution is to go to the activity, âfieldsâ, âjoin scoreâ and run the script again (or re-analyze a batch of activities). Keep in mind that it is a reverse-engineered analytical approximation so there will be a small deviation.
Any long term reviews?
no long term reviews of Join but I have been trialing it for a few weeks and might use it for a few months to traing for a 2 day gravel stage race. Iâve used TrainerRoad in the past.
Join is a bit more relaxed than TrainerRoad, a bit of a laissez faire feel compared to TrainerRoadâs more clinical feel. And TrainerRoad definitely leans on intensity where I think Join leans more towards more volume.
Joinâs flexibility is simple. Set your training hours for the week and you can swap workouts or rides as you go along and Join will adjust. TrainerRoad has a lot adjustability but there are a lot of adjustment knobs to turn. Or at least it feels that way.
TrainerRoad is definitely data heavy which is what lots of bike nerds might like. Join just seems much more laid back you donât feel like a failure for missing or changing a workout.
Whether that means performance wise, one is better than the other, itâs hard to say. I can see the appeal of Join for people who just want a bit of structure but also want more flexibility. TrainerRoad really wants you to stick to their structure. Thatâs not a bad thing but it can make you feel like youâre constantly screwing up.