Sunday, July 3, 2016

Don't Blame the (Tesla) AutoPilot !

Most of you must have seen the amply-broadcast and highlighted story about a fatal accident involving a Tesla in autopilot mode. Most commentators have been quick to blame, chastise, or at least question, Tesla's autopilot software. The government watchdog NHTSA is investigating Tesla (http://www.theverge.com/…/tesla-autopilot-car-crash-death-a…). There is every possibility of a knee-jerk reaction that will force Tesla to "recall" the software, and for Tesla drivers to lose this feature. But before we fall into that trap I would like to offer a perspective. 

1) Augment vs Replace: Tesla AutoPilot, like many other “artificial intelligence” (AI) tools, aims to augment the human, not replace him or her. This “augmentation” idea has been a cornerstone of AI work for decades. For example, I find the auto-pilot feature immensely useful - it lets my eye scan the environment around, front of, and behind me - and be alert for unforeseen things which I would have missed if I were intensely focused on keeping the car in lane. It doesn’t replace me - there are a lot of things I can anticipate, predict, and respond to a lot better - but it definitely helps me while I’m in the car. The particular scenario that occurred - big truck crossing perpendicular to your lane, in front of you - perfectly illustrates the value of augmentation. A driver with autopilot would be far more likely to notice the truck than one without.

2) Beta status and Correct use: Tesla is very clear about conditions under which autopilot should be used ("standard" freeways, no construction, and evidently no intersections for cross-traffic). I find myself pushing these boundaries, but all the time ready to take over in the blink of an eye. In this particular case, I am not sure but it appears to me this event might have occurred outside the "correct use" condition.

3. Tradeoff and probabilities: Even if points number 1 and 2 were not valid in this case (which they are), one still should be clear of what to expect from an AI tool : it may not be perfect, but if it is "better on average" (i.e., reduces probability of an accident) it is still worthwhile.

Most importantly, look at how items #1 and #3 combine. Not only does autopilot perform better on average, it generally performs well on where the human is weak (e.g., losing attention on a long boring drive; drifting across lanes; unsafe lane shifting) - and while it certainly will fail in some cases where the human would have done fine - that totally reiterates the point that in this case 1+1 = 3 or more.

At the end of the day, Autopilot software is in a sense not so different from, say, a rear-view mirror. You use it to get a sense of the objects behind you. But sometimes you turn your head and try to look behind. And you certainly don’t blame it if you back into a wall.

So, I hope you will all not be scared of, or against, autopilot technology. And please spread the word !

Monday, January 25, 2016

A Hike in Blue Ridge / Stebbins Canyon, Winters, CA

Jan 17, 2016

After several days of rains, a beautiful morning in Davis, with puffy clouds and blue skies. In other words, a perfect day for a hike. I start the 30-minute drive to the Blue Ridge Stebbins Canyon trail, adjacent to Lake Berryessa. This is the first visit in months, and after the Summer 2015 forest fire that burnt about 8,000 acres near here. Here’s a picture of my destination.



Inspired by monochrome pictures taken by a friend, I stop in Winters to click the bare almond groves in their Winter sadness. 



A few minutes and some beautiful winding roads later I’m near the trailhead. But, wait, not a single car here! That’s odd. Is the trail closed? A little sign in the parking area suggests so. 


This could be due to the recent abundant rainfall. I sense some hope - the sign seems flipped out to the side and it hasn’t really rained that hard! Sadly, my doubts are erased as I approach the trailhead. 



But I’ve waited too long and come too far to give up on this. Sorry, law, trail beckons. 



The main trail is a 5-mile loop, which ascends steeply to the top, then provides beautiful vistas of Lake Berryessa and Napa valley along the ridge, before diving into the canyon and crossing a creek towards the end. I was especially looking forward to seeing a fully-flowing creek, after years of dryness from our recent droughts. But, today, not quite sure if I should even be here, I realize I can only head to the top and turn back down. As for the creek, just a peek of it while starting the hike.




As I begin the hike, the reason for the closure dawns on me. This region was not just near the summer fire - it was right in it! The landscape has changed. Trees are shorter, and bereft of branches or leaves. The ground is black. Around me lingers the smell of fire - and surely, some death - trees, plant life and wild life?








Still, some things are not that different. Our version of El Capitan is majestic, marking the start of the ridge.







 The scenery around me is beautiful, down into the valley where I parked, and beyond towards Winters and Davis in the East. 







Some more climbling brings me to the Eastern end of the ridge top, which opens up a view of the South end of Lake Berryessa.





The trail continues along the ridge, leaking evidence of the fire and devastation.  Below it, the lake is calm and beautiful!





The muscular hills on the South side remind me of Big Sur. The East side is also a beautiful green at this time of year. 





 Overcoming a desire to carry on along the ridge and then down into the canyon, I decide to turn around after spending a few minutes to enjoy the scenery. The descent is speedy but on the way down I notice signs of new life amid the blackness and devastation.





The new life and fresh green makes for a nice end to a memorable hike. As for the trail closures, I resolve to join the volunteer group working on restoration of this area.  Hope you enjoyed reading this, and perhaps you can hike here this summer.

https://www.facebook.com/events/1539429586336123/permalink/1539429589669456/