Originally Posted by RapDaddyo .
Well, the parsing app won't just spit out a number. It takes the defined ride schema (intensity and duration) and breaks down a ride into the component pats by duration and TSS. So, if you define an L7 as minimum *** watts and xx sec duration, then it'll find those segments in the ride file and include them as L7s. If you define an L7 as YYY watts and yy secs duration, it'll find those. So, it finds what you tell it to look for.
As to why it matters, you could apply the question to the application as a whole, not just L7s. Does it matter to know what a given workout consisted of in terms of a training schema? Does it matter to know what a week consisted of? A month? I think it does. I plan a ride or a week of rides in terms of targets for time and TSS by training level. IOW, I consciously attempt to manage the mix of my training efforts in addition to total time and TSS. So, if I am going to parse a ride file, I would just as soon try to get it right rather than just throw a dart and hope for the best. Everything else is straightforward except for differentiating between L6s and L7s. Hence the question.