Today's Forum Topics
Set as homepage
|
View
New Forum Topics Today's Forum Topics Set as homepage |
 |
|
|||||||
Welcome to CyclingForums.com You are currently viewing our website as a guest which gives you limited access to view most discussions. You will have to register before you can post to this thread. By joining our free online community you will have access to post new topics, communicate privately with other cyclingforums.com members (PM), respond to polls, upload photos and access other special features like product reviews and classifieds. |
 |
|
|
Thread Tools | Search this Thread | Display Modes |
15-11.-2006, 09:36 PM
|
#1 |
|
Registered User
Join Date: Mar 2006
Location: Sydney, Australia
Posts: 1,736
|
Parsing Time (& TSS)
I am currently a beta tester for a new application designed to parse power meter files into segments based on descriptive training schema (i.e. identifies sections of a ride which the meet minimum intensity and duration criteria to be considered an L4 effort, L5 etc). These segments can then be totalled for time and TSS at each level.
Any schema can be used such as Andy Coggan's levels based on FTP, or Ric Stern's levels based on MAP. As we know they are fundamentally similar schema in terms of the intensity and minimum duration applicable, just some variances in the number of levels and "bandwidth" of each level. I thought I would share some charts developed as a result of the output of this data. This is by no means the only way of looking at the parsed workout data but I thought it may provide some insights which perhaps didn't previously exist in a visual format. There will no doubt be debate over the validity of the file parsing approach so certainly interested in what forums members make of this lot.... The setting of levels is arbitrary (you define lower limits for duration and intensity), so there is some interpretation as to what the limits are. This approach also tends to make you focus on levels as being discrete in their physiological impact, when in fact we all know this isn't the case, indeed this in itself is probably the biggest challenge to overcome when translating our "analogue" bodies' response into a "digital" display. Nevertheless, this provides one way of visualising the mix of workout types from all rides, in particular non-structured rides. The charts cover my own training since 1 August. All road and track riding, nothing on trainer/rollers (except for the odd short warm up before a race). Chart 1 shows weekly ride time in minutes parsed into "levels" based on Ric's MAP based levels. Chart 2 shows weekly ride TSS parsed based on same "levels" and plotted with CTL attained at end of week. Thoughts? Alex |
|
|
|
16-11.-2006, 12:09 AM
|
#2 |
|
Registered User
Join Date: Mar 2003
Location: Cape Town
Posts: 534
|
Re: Parsing Time (& TSS)
Alex - those graphs are great.
I am testing too - would love to get my hands on a templat to produce those graphs from my data - can you send me anything ? (I am very poor on creating graphical output) Thanks |
|
|
|
|
16-11.-2006, 12:48 AM
|
#3 | |
|
Registered User
Join Date: May 2005
Location: Las Vegas, NV
Posts: 4,115
|
Re: Parsing Time (& TSS)
Quote:
|
|
|
|
|
|
16-11.-2006, 12:55 AM
|
#4 | |
|
Registered User
Join Date: Mar 2003
Location: Cape Town
Posts: 534
|
Re: Parsing Time (& TSS)
Quote:
Isn't he just  I think he is just showing off..  |
|
|
|
|
|
16-11.-2006, 01:49 AM
|
#5 |
|
Registered User
Join Date: Dec 2004
Location: Johannesburg
Posts: 189
|
Re: Parsing Time (& TSS)
I've got a question about this approach.
Let's say I do a ride L3 for x minutes, L4 for y minutes, L3 for x minutes. where x < min L3 duration, y > min L4 duration, x + y + x > L3 minimum duration. What are the results going to be? In other words, since L4 is greater intensity than L3, does it count towards L3, and should it? So, would I get: L3 = x + y + x L4 = y Looking at Coggans table of physiological adaptions, things get a bit complicated for L4/L5/L6, however, the rapid decline in time spent at these levels probably doesn't introduce much of an error. Last edited by Bruce Diesel : 16-11.-2006 at 01:58 AM. |
|
|
|
|
16-11.-2006, 01:59 AM
|
#6 | |
|
Registered User
Join Date: Mar 2003
Location: Cape Town
Posts: 534
|
Re: Parsing Time (& TSS)
Quote:
I am very glad you put the "in other words" part in... It filters the data so that all data runs through a check to see if it fulfills your preset criteria for the various zones - it starts with the highest intensity and works down so that no data segment can be a member of more than one zone. In other words .. L4 does not count towards L3 etc. I am sure Rap will explain this better (it is his app after all) |
|
|
|
|
|
16-11.-2006, 02:01 AM
|
#7 | |
|
Registered User
Join Date: Dec 2004
Location: Johannesburg
Posts: 189
|
Re: Parsing Time (& TSS)
Quote:
So, what you are saying is that the results of my example would be L4 = y L3 = 0 |
|
|
|
|
|
16-11.-2006, 02:09 AM
|
#8 | |
|
Registered User
Join Date: Aug 2005
Location: Canada
Posts: 1,234
|
Re: Parsing Time (& TSS)
Quote:
"Nested levels" switch that can be turned on and off. Personally, I'd turned it to on, meaning that I prefer total time per level to be higher than the total workout time. |
|
|
|
|
|
16-11.-2006, 02:14 AM
|
#9 | |
|
Registered User
Join Date: May 2005
Location: Las Vegas, NV
Posts: 4,115
|
Re: Parsing Time (& TSS)
Quote:
|
|
|
|
|
|
16-11.-2006, 02:17 AM
|
#10 | |
|
Registered User
Join Date: May 2005
Location: Las Vegas, NV
Posts: 4,115
|
Re: Parsing Time (& TSS)
Quote:
L4 = y L3 = 2x This is what I was referring to as "nested segments," in which there is one long L3 segment (x + y + x) with a nested L4 segment (y) in the middle. The L4 segment would be "lifted out" and the remainder of the long L3 segment (x+x) is what's left. |
|
|
|
|
|
16-11.-2006, 02:29 AM
|
#11 | |
|
Registered User
Join Date: Dec 2004
Location: Johannesburg
Posts: 189
|
Re: Parsing Time (& TSS)
Quote:
|
|
|
|
|
|
16-11.-2006, 02:33 AM
|
#12 | |
|
Registered User
Join Date: May 2005
Location: Las Vegas, NV
Posts: 4,115
|
Re: Parsing Time (& TSS)
Quote:
Technically, the app gives both results (i.e., "gross" and "net"). |
|
|
|
|
|
16-11.-2006, 02:48 AM
|
#13 |
|
Registered User
Join Date: Dec 2004
Location: Johannesburg
Posts: 189
|
Re: Parsing Time (& TSS)
A further conclusion therefore, is a segment at a certain intensity level that does not meet the duration criterion, is demoted to a lower level.
To illustrate: I ride at L3 for x, and L4 for y, where x < L3minduration and y < L4minduration but x + y > L3minduration I would get: L4 = 0 L3 = x + y But, should y > L4minduration I would get: L4 = y L3 = 0 Sorry, I'm a programmer at heart and I love testing algorithms! |
|
|
|
|
16-11.-2006, 02:48 AM
|
#14 | |
|
Registered User
Join Date: Aug 2005
Location: Canada
Posts: 1,234
|
Re: Parsing Time (& TSS)
Quote:
|
|
|
|
|
|
16-11.-2006, 02:51 AM
|
#15 | |
|
Registered User
Join Date: Mar 2003
Location: Cape Town
Posts: 534
|
Re: Parsing Time (& TSS)
Quote:
Stop being a propeller head and testing algorithms and start training .. |
|
|
|
|
Linear Mode
