<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p><br>
</p>
<p><br>
</p>
<div class="moz-cite-prefix">On 15/05/2020 13:00, Peter Bishop
wrote:</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">-<snip>-<br>
</div>
<blockquote type="cite"
cite="mid:772b62a6-6cdb-d612-2b44-373d8bcf12c7@adelard.com">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<p>So there is a lot of mileage (excuse the pun) in *assisting*
the driver rather than replacing him/her, e.g. <br>
</p>
<p>-detecting driver inattention/sleepiness/drunkenness <br>
-blocking misuse of mobile phones<br>
-vision enhancement (infra-red / radar imaging / all round view
cameras)<br>
-collision detection / emergency braking</p>
<p>Such driver assistance could feasibly reduce the fatal accident
rate by an order of magnitude<br>
- a challenging target for a fully autonomous vehicle.</p>
</blockquote>
<p>Indeed, and more to the point, providing better driver assistance
is well within the current capabilities of automotive software
engineering (apart, arguably, from execrably bad HMI design skills
- I've already griped about the Ford C-Max on this list - the
speed limiter and cruise control are <b>still</b> giving me
jolting surprises after almost a year of ownership).</p>
<p>The resources required to realise better driver assistance would
be modest (if not minuscule) in comparison with what it would take
to get autonomous vehicles right. And this is quite part from the
costs of the infrastructure improvement that would be needed to
achieve anything approaching safe use of AVs.<br>
</p>
<p>As we curmudgeons say:</p>
<p>1. Don't try to run before you can walk.</p>
<p>2. Don't try to walk before you can crawl.</p>
<p>3. If you're still crawling, don't expect others to share your
expansive vision of the future.</p>
<p><br>
</p>
<p>Ho, hum ...</p>
<p>Olwen<br>
</p>
<p><br>
</p>
<br>
</body>
</html>