<[email hidden]> wrote in message
news:[email hidden]
:: Roger Zoul wrote:
::: "John Kane" <[email hidden]> wrote in message
::: news:[email hidden]
::::: Roger Zoul wrote:
:::::: <[email hidden]> wrote in message
:::::: news:[email hidden]
:::::::: Doc O'Leary wrote:
::::::::: In article <YMmgh.481377$5R2.19648@pd7urf3no>,
::::::::: "nash" <[email hidden]> wrote:
:::::::::
:::::::::: What are your average MPH when doing a normal
:::::::::: commute or training ride?
:::::::::
::::::::: I don't bother to monitor it. When I want to get
::::::::: somewhere on a schedule, I just figure I can
::::::::: easily average 15mph and plan for the distance I
::::::::: need to go. When training, I just push myself
::::::::: harder than I normally would. Most of the people
::::::::: who get into pissing matches about speed are the
::::::::: kind of people that don't count the time they
::::::::: spend at stop lights.
:::::::::
::::::::
:::::::: That always irritates me when people claim some
:::::::: particular average or riding time for a century or
:::::::: something, and then I find out it is only "riding"
:::::::: time, not actual time.
::::::
:::::: I don't get it. Why not count riding time in an
:::::: average? Who'd want to count anything else?
:::::
::::: Well, if you're a utility cyclist average riding time
::::: is meaningless, I need to know how long the trip
::::: takes, not the time in the saddle. It is giving
::::: distances in hours which is one of my pet peeves when
::::: I hear it on the radio. Someone will say that X is an
::::: hour from Y. By what means? Car, helicopter, F18, ox
::::: cart, canoe, bicycle, walking?
:::::
::::: I really don't care what my average riding speed is. I
::::: want to know how much time it takes to go from A to B.
::::: The only time average riding speed is any important is
::::: if I know how far it is to my destination and I need
::::: to get there in specific amount of time.
:::::
::::: Tell me that it is a four hour ride from London to
::::: Toronto and this means that I can leave at 7:00 AM and
::::: still meet friends in the city for lunch at 12:00.
::::: OOPS, you forgot to mention that you need to allow an
::::: hour and a half for rest breaks. Oh well they won't
::::: mind waiting at the subway station for half an hour.
:::
::: I don't have a problem with wanting to know how long a
::: commute to work takes, with stops and traffic and all,
::: it's obvious that that's the important time. But that
::: doesn't mean that one can't also clock the average
::: speed while riding, as computers do that very well.
::: Hence, it's simply a matter of knowing what's important
::: when and making proper distinctions. Clock time or
::: riding time, big dooh.
::
:: There is no question in my mind that riding time/average
:: speed is a very important parameter. Seen by itself it
:: is not very informative about the whole picture, but it
:: is certainly something I'd like to know on a timed ride
:: like a century. It's just that I would only consider it
:: a supporting fact, not the result.
I have no problems knowing both wall time and riding time, and speed. I
want to know speed over any course I ride, as a recreational rider. Clock
time is whatever it is. Sometimes my riding is limited by clock time, but
never by riding time. If I'm really constrained by clock time, then I want
to get the higher speed possible during my riding time. The shorter, the
faster.
::
:: Joseph