RapDaddyo said:
I'm writing something for this. I'll send it to you when I have it working to get your thoughts. The only issue is defining the rules for inclusion and how to treat "intervals within intervals" -- maybe a larger problem for me than you because I don't do traditional intervals but rather adapt intensity to the course.
You know about the workout file maker I made for this purpose, don't you?
Currently I eyeball my .wko graphs for periods of 'notable' intensity. I'll admit to counting NP rather than AP for L4 if hills force me to drop the AP a little. My cutoff times are just based on Andy's original guidelines ... no thinking on my part
For overlapping intervals - I do it manually and simply log what feels logical based on the type of ride. But if I had to code it I suspect I would count (or highlight) the highest power section and ask the user to confirm that interval should be logged as such.
What I was thinking of re CPS is roughly:
1. Allow the user to enter a search power range (or select L3/4/5/6 from their profile).
2. Allow the user to enter an 'effective duration' (or select from a drop-down, durations would default to 30min, 15min, 3min, 30sec if Levels were selected in #1).
3. Search the file for periods of Sustained AP that meets or exceed the user's specs.
4. Highlight the sections that fulfill the specs and display total duration and TSS. Allow the user to name the intervals or just log the duration/interval TSS and discard them.
If I were using this feature, I would start at the highest power range of interest for that ride .. for example L5. Search params would be AP>1.05FT for >3min. I'd log total time in L5/TSS from the highlighted intervals.
I'd then select L4. Search params would be >0.90FT for >15min and I'd note/log as before.
Finally I'd select L3. Search params would be >0.75FT for >30min. Often that would be the entire darn ride so the benefit lessens as one drops in power. But if I were doing L2 rides as I did back in 2003/2004, this could still be useful in picking out 'significant' L3 o/o that data.
I'd log the data as duration/TSS in the three levels with the proviso that the Higher Level overrules. For instance, let's say there was a hilly circuit with a nice 5-min climb. An hour may have averaged 0.95FT which would ostensibly be L4 but the 'real' story is the the 6 hard climbs at say 1.15FT. I'd log the 6x5 or 30min in L5 and not the hour L4.
I would NOT want to try & code something comprehensive for this. I'd be happy if CPS just had the nice specifiable power-range or Level search with the effective duration filter added. I don't mind logging manually.
Finally before someone mentions the Fast Find - it's a start but what I want is AVERAGE POWER > XX Watts for YY Minutes ... not to specify an Entry/Exit power as per that feature. I guess F/F would work just fine for L7 though as durations are quite short anyway.
RD, re the file maker, my primary log has been in Excel for year (plus my big picture stuff) so I wouldn't really use that. Sounds like a nice idea for those who use CPS as the main repository of training data.
rmur