Contents
 Welcome
 Getting Started
    System Requirements
    Cycling Equipment Requirements
    Training Knowledge Requirements
    Registration
    Creating Power Zones/Interval Specifications
    Creating Heart Rate Zones
    Training Load Settings
    Logging In
    Interval Detection & Selection Overview
 Rides
    Uploading A Ride
       Handling Missing Seconds
       Wahoo Cloud Sync
       Garmin Connect Sync
       Ride Backfill Request Utility
       Ride Load Status Checker
    Adding A Manual Ride
    Finding Rides
    Deleting Rides
    Exporting Rides
    Ride Feed
    Ride Calendar
    The Ride Page
       Ride Header
       Map
       Ride Graph
       Intervals
       Heart Rate Zone Distribution
       Power Zone Distribution
       Cadence Distribution
       Power Curve
       Stats
       Laps
       Training Progress
       Edit Ride
       Comments
       Zwift Workout Generator
       Workout Performance Report
    KPower
       Uploading KPower Rides
       Curating KPower Source Rides
 Reports
    Race Readiness Graph
    Power Curves
    Rider Stats Year Over Year
    Personal Records
       Personal Records Overview
       Personal Records Report
       Personal Records - Workload Correlations
    Ride Summary Charts
    Critical Power
       Overview
       Generating A CP Graph
       Critical Power History
       Critical Power History Backfill
    Fitness Signature
    Hammer Score Leaderboard
    Training Effectiveness
    Rider Assessment
    Plan Strategy
 Workouts
    Workout Builder Screen
    Adding A Workout
    Adding A Block
    Adding A Component To The Workout Graph
    Deleting A Block
    Insertion Points
    Fixing A Block Mistake
    Multi Select Blocks
       Building
       Saving As A Component
       Removing Multi Select
    Finding Workouts
    Editing Workouts
    Deleting A Workout
    Generating A Zwift Workout
    Components
    Downloading Workouts
    Workout Projections
    Scheduling A Workout
       Rescheduling A Workout
    Deleting A Workout From The Schedule
    Viewing A Workout Performance Report
    Importing A Workout
    Interval Advisor
       Saving A Recommendation
       Adaptive Workouts
    Curating Interval Advisor Source Rides
 Other Functions
    Changing General Settings
    Changing Rider Assessment Settings
    Changing Power Zones/Interval Specifications
    Changing Heart Rate Zones
    Changing Training Load Settings
    Coaches And Friends
    Viewing The Terms Of Service
    Viewing The Privacy Policy
    Logging Out
    Evaluating Progress
    Changing Advanced Settings
    Notifications
       Insights
          Critical Power AWC Check
          Training Effectiveness
          Interval Workload Levels
       Warnings
          FTP CP Mismatch Warning
    Changing Bicycle Settings
 FAQ
    General FAQ
  
Index

Home > Getting Started > Interval Detection & Selection Overview

Interval Detection & Selection Overview

KOM Informatics is, as far as the writer knows,  the first cycling analytics system to detect and display the most important and relevant intervals based on training zones, accomplished on a ride. Coupled with many other informative and useful tools the system is a must have for those cyclists who are looking to optimize their training gains.

It turns out that it is relatively easy to detect all of a ride's intervals. But even a short TT of under an hour can yield over 1.5 million intervals, many of which are very similar to one another. Displaying that many  on a web page is not going to make anyone happy!

KOM Informatics utilizes a heuristic algorithm to distill what can be a potentially large numbers of intervals into the most powerful and important ones generated on your ride.

KOM Informatics detects intervals in 2 different contexts. The first context is dependent upon minimum durations that you supply for each of your power zones that you want to set up.  The minimum wattage detected is the lowest wattage for a zone.  The objective of this type of detection is to find the most energy intensive intervals, which almost always tend to be at the lowest wattage/longest duration intervals per grouping. The system detects these intervals when you upload a ride.  The results of this type of detection provide a basis for understanding the composition of your training.  When the system aggregates the data in various reports, you'll get to know how much time you spent at interval intensity for each of your zones for a given training period.  If you set a PR, or attain strong results in a race you'll be able to tell the exact mix of training which produced that PR or results.

The second context is searching for highest wattage intervals for a ride based on minimum wattages, durations and quantities that you supply on a form located on the intervals tab of the Ride page.  After providing your selections and clicking go, the system will return the highest wattage intervals that meet your search criteria, along with averages.  If you do the same workouts on a regular basis, comparing the output of this search across rides can be a useful way to gauge progress.   

Zone based intervals are used to create an Interval Zone Distributions (IZD) for each ride. This is a rollup of the time and kilojoules spent at or above interval minimum duration in each power zone.  An individual second only counts in the highest power zone in which it occurs for the IZD.  In real life though,  it is frequently the case that  intervals are "stacked" (an individual second can belong to intervals in multiple zones).  Say for example you do a Zone 5 (VO2Max) effort that's 8 minutes long.  Further, let's suppose you've defined your Zone 4 (Threshold) minimum duration at 10 minutes.  Under these conditions KOM Informatics will detect a Zone 4 Interval underneath the Zone 5 effort you intended. This detected Zone 4 effort will start a minute or so before the Zone 5 effort, and end a minute or so afterwards.  KOM Informatics will display the Zone 4 interval on the Ride Graph, but it likely will not be included in the Interval Zone Distribution for the ride.  This is because the system analyzes the quality of all lower zone intervals that are covered by a higher zone interval. It looks at the average watts of the uncovered seconds.  If those seconds don't average at least 90% of the minimum wattage for the zone, the interval won't count towards the Interval Zone Distribution. Also, if a lower zone interval is completely covered by a higher zone interval, the lower zone interval won't count towards the IZD




This image is clipped from the Ride Graph of a KOM Informatics ride page.  The ride is from the NJBA's 2017 Silvermine TT which was a "full gas" effort  34:41 for this rider.  Each layer of the intervals depicted represents efforts in descending zones, starting from Z6(Anaerobic), Z5(VO2Max), TT(Upper Threshold), and Z4(Threshold Zones). It's pretty easy to see that every second on this ride is involved in multiple intervals, hence the term "stacked intervals".

>

This image is clipped from the same ride page as the one above. The table to the left lists the individual intervals accomplished. The  pie chart is the Interval Zone Distribution for the ride.  The right hand side of the image shows the Find Most Powerful Intervals form where you can search for a ride's most powerful intervals based on your minimum wattages and durations.

By looking at the intervals table in conjunction with the Interval Zone Distribution (IZD) pie chart you can see how individual intervals contribute to the IZD.

  • The Z4 (Threshold) interval (duration 34:41) doesn't count at all since it is completely covered by a TT (Upper Threshold) interval. The IZD Inclusion column in the table for the interval is not checked.
  • The TT (UpperThreshold) interval (duration 34:41) does participate in the IZD. The system has checked those seconds of the interval that are not shared with higher zone intervals and found them to average at least 90% of the minimum wattage defined for the TT zone.  Not all of the 34:41 counts towards the IZD because some of it occurs in the presence of higher zone intervals. The IZD Inclusion column in the table for the interval is checked indicating it does contribute to the IZD.
  • The 3 Z5 (VO2Max) intervals all participate in the IZD.  The system has checked those seconds that are not shared with higher zone intervals for each of the Z5's and found them  to average at least 90% of the average for the Z5 zone.  Not all of the Z5 seconds count towards the IZD, as at least some of those seconds also participate in a Z6 higher zone interval. The IZD Inclusion column in the table for the intervals are checked indicating they do contribute to the IZD.
  • All of the Z6 intervals participate in the IZD. Because there is significant overlap between some of the Z6's you can't just add up the duration of each of them to come up with the total in the IZD. The system counts each of the shared seconds between intervals which occur in the same zone only once.  The IZD Inclusion column in the table for the intervals are checked indicating they do contribute to the IZD.

See also

  
HelpConsole 2007 - Standard

Copyright © 2004 - 2007 Extreme Ease Software Inc. All Rights Reserved.