Jump to content

davidtinker

Members
  • Posts

    440
  • Joined

  • Last visited

Everything posted by davidtinker

  1. Intervals.icu will now prompt you for your FTP if you haven't set one before analysing all your activities. If you have an FTP set on Strava you can choose to use that or change it. This is an important fix for people who are not premium Strava subscribers. Coming soon: Editing intervals.
  2. Yes it is working. You probably don't have an FTP set. I need to add a check for that for new users before analysing all their rides. If you go to intervals.icu/settings and capture your FTP I will trigger a re-analysis of your rides tonight. Not having FTP set will also make a mess of the interval detection. I had better get on the "new user" feature.
  3. It turns out that you can use Intervals.icu without having to pay for Strava. I assumed that Strava would prevent download of power data from their API for free tier users but it seems that they do not. So you can use Intervals.icu to analyse you rides for free.
  4. Intervals.icu now supports searching for intervals based on intensity i.e. the average power for the interval as a percentage of your FTP at that time. So you can enter 100% in the power field and find all your threshold intervals.
  5. Tx. The interval search chart now supports displaying crank torque on the y-axis instead of power.
  6. Intervals.icu now has an interval search feature. You can search for intervals based on any mix of time, power, cadence and reps or just click the interval's shown with each activity. I still need to do some work on this chart to show torque and fitness and fatigue.
  7. Intervals.icu now supports displaying average, max and min speed for each interval on the ride timeline chart and the interval data table. Just click "Fields" and add what you would like to see. A new interval search feature will be landing soon to make it easier to compare interval sessions.
  8. Intervals.icu/ now has better handling for power files with zero watt drop outs (instead of nulls) so these will be less likely to break up intervals. Interval detection for very square intervals has also been improved.
  9. Intervals.icu now downloads activity data from Strava in the background using "spare" rate limit. So activities listed as "queued" on the activity calendar are likely to have been analysed by the next time you visit. This is great for the fitness chart which requires a lot of data.
  10. I had to log everyone out to fix a problem with how Strava migrates people to the new auth permissions (grrr). Next time you go to intervals.icu you will need to click connect with Stava and approve the new permissions.
  11. Tx a stack for this. I am definitely looking for feedback! I had a look at that one and the power dropouts are zeros whereas other power files I have looked at have "nulls" instead of zero. Nulls are easy to compensate for. I need to figure out how to handle the zeros. The absolute sudden drops from 280 to zero is probably something I can work with. I am going to be doing some more work on intervals.icu wed evening.
  12. Strava have changed the way auth for apps is handled. Supposedly all existing intervals.icu users should be ok but if anyone runs into problems (e.g. 404 errors loading new activities or syncing existing ones) please let me know asap on david.tinker@gmail.com. Also try logging out (from https://intervals.icu/settings) and logging in again. Its very quick if you are already logged in to Strava.
  13. Tx. You can see min and max HR for intervals. Click the "Fields" drop down under the ride timeline chart (main activity view) and select "Min HR" and "Max HR". Same thing works on the "Interval Data" page. The pages will remember your settings.
  14. Tx. This is fixed now. It was displaying in m/s. Now its km/h or mph.
  15. Tx. Could you please mail me (david.tinker@gmail.com) a link to that activity in intervals.icu so I can have a look? The algorithm does try to join work intervals separated by "short" recovery intervals but I need to do some more work in that area. Generally intervals that are varied are a challenge vs square ones. I probably need to add a combine option as you suggest. I can track how often it gets used to judge the success or otherwise of the algorithm.
  16. I just added little red dots for races. Forgot about that.
  17. Intervals.icu now has a fitness / freshness or CTL/ATL/TSB or performance management chart. IMO it does a much better job of presenting this information than Strava's fitness / freshness chart. It is based on Monitoring your training load published here on the hub by Science2Sport.
  18. Intervals.icu will now estimate training load (TSS) from rides with only heartrate data. You need to have at least 8 rides with power and HR data before the "HR only" ride and it works better if there are more. I have a powertap hub so I don't get power when using my racing wheels or for MTB. Bit annoying to do a 4h MTB race and get zero training load credit That had to be fixed!
  19. Tx. This is a side project to scratch an itch and learn some new stuff (both in technology and cycling) and the learn new stuff side is going well so far (tx John and Mike from sciencetosport!). I am a software developer and cycle so I can drink more beer and not get fat.
  20. Hmm. Looks like it should have. Could you please mail me a link to the ride (david.tinker@gmail.com) and and also a link from https://intervals.icu/followers so I can follow you and have a look at it. Tx.
  21. Intervals.icu now calculates its own weighted average power (NP) and training load (TSS) for each activity and displays these on the activity page and activity calendar with weekly total. I can't use TSS and NP since these are trademarked so I have gone with the Strava equivalent terms. My weighted average power numbers are very slightly different to Strava probably due to the way I handle power drop outs and so on. Weighted average power is calculated according to this Andrew Coggan post: https://forum.slowtwitch.com/Slowtwitch_Forums_C1/Triathlon_Forum_F1/Normalized_Power_Formula_or_Calculator..._P3097774/ Training load is calculated according to this post from Science2Sport coaching: https://www.bikehub.co.za/features/_/articles/training-nutrition/monitoring-your-training-load-r7477 (the TSS formula needs a x100)
  22. Ride names for all rides are now displayed in on the activity calendar view (used to be only for races). The ride timeline chart now displays rides with irregular time intervals (e.g. rides with only heartrate data) correctly.
  23. I have added segment names to the bottom of the ride timeline chart as the marker is moved. It tries to find the segment(s) that best fit each interval. The goal is to indicate where each work/recovery interval took place, not to display all the possible segments for that point on the chart (a 2h ride from Strava around Cape Town might have 250 segments!). This doesn't work too well for rides without intervals (no power data or recovery rides), i am working on that problem. Tx to everyone giving intervals.icu a try.
  24. I was referring to the video in the 2nd post on this thread.
Settings My Forum Content My Followed Content Forum Settings Ad Messages My Ads My Favourites My Saved Alerts My Pay Deals Help Logout