Re: Helmet efficacy test

cyclintom <cyclintom@yahoo.com> wrote:

On Wed Mar 26 20:40:23 2025 Roger Merriman  wrote:

cyclintom <cyclintom@yahoo.com> wrote:

On Wed Mar 26 18:51:39 2025 Roger Merriman  wrote:

cyclintom <cyclintom@yahoo.com> wrote:

On Tue Mar 25 23:15:20 2025 Frank Krygowski  wrote:

On 3/25/2025 12:36 PM, cyclintom wrote:

On Tue Mar 25 10:36:01 2025 Frank Krygowski  wrote:

 
First, I don't know that's true. Based on your claims here, I think my
typical riding speed is faster than yours. I'm sure I couldn't keep up
with Zen or Mark, but I suspect most of us old guys here would ride at
similar speeds. I know that on the club rides I attend (I'm typically
the oldest of the attendees) I usually finish in the front half of the
group, and often first. Not that they're races. I just enjoy speeding up
at times.
 
Not that it matters. I dispute the implication that faster riders
naturally crash more. It takes miles of riding to get fast, and people
with miles of experience tend to be more skillful.
 
You may be an exception.

 
 
 
 
Frank, obviously you do not ride with a Garmin and believe that my
claim of riding an average soeed of 11 mph is slow.

 
You're right. I don't use a Garmin. I still use ordinary cyclometers - a
couple Avocets that I've managed to keep running, and a couple Cateyes,
etc. They give me average speed. 11 mph _is_ slow. I don't think I've
ever averaged that slow unless on a recreation ride with my wife,
grandkids or a good friend who is quite slow.

 
 
 
 
Those meters only sverage moving speed. You are supposed to be an
engineer and you don't understand the effects of stop lights and a 30-45
minute pause at a coffee shop on a meter that measures average speed from
total time from turning the meter on? All I can say is that you're
some kind of engineer.
 

 
As do Garmin connect and Strava ie doesn?t count the stationary time, aka
waiting at traffic lights or time at the cafe or so on.

 
 
 
 
I have an 830 and a 1030 and neither one of those has an autostop
feature. And if you push "stop" on the clock, when you restart, they
restart the mileage from zero. Now it has saved the previous ride and you
can downlooad the same total mileage. But if you leave it, it measures
the time from start to finish regardless of speed.
 

It?s called auto pause and within each activity profile, I leave it off as
don?t want it paused during slow speed tricky MTB stuff as Strava and
indeed Garmin connect will make average speed calculations ie remove the
cafe stops and so on.
 
Unless your riding has no cafe stops? Or no waiting for mates to ride
together or no traffic lights or stops in general, it?s a very poor way of
displaying average speed, for example I often do a gravel ride to the pub
on a Wednesday, and spend a hour or more with mates there.
 
If you have a the Garmin set to no auto pause or don?t use Garmin Connect
or Strava to process the rides and calculate average speed etc, all your
doing is measuring cafe stops and other non performance metrics which is
isn?t remotely relevant!
 
Your averages on Garmin connect will be much more accurate as they don?t
measure faff and cafe time, ie how fast or not your riding.

 
 
 
 
Of course I agree with you but that doesn't make Garmin measure it any differently.
 

It absolutely does, turn on auto pause or use Strava or similar that
applies that sort of thing, post ride.

But click The 3 dashes to the bottom left of your screen, click one of the
activity profiles (I have Commute/Gravel/MTB) and then auto features one of
which is auto pause, which if you enable will give a more accurate average
speed, assuming you have cafe stops or traffic lights!

I personally find that 3rd parties are much better at presenting the data
than just on the device.

Roger Merriman