Page 465 of 522
1 463 464 465 466 467 522

Robots and jobs

Will a robot take my job?
Media headlines often speculate about robots taking our jobs. We’re told robots will replace swaths of workers from taxi drivers to caregivers. While some believe this will lead to a utopian future where humans live a life of leisure provided for by robots, the dystopian view sees automation as a risk to the very fabric of society. Such hopes and fears have preceded the introduction of new technologies for centuries – the Luddites for example destroyed weaving machines in the 19th century to protest the automation of their sector. What we see, time and time again, is that technology drives productivity and wealth, which translates to more and better jobs down the line. But can we expect the same to happen with robots, or is this time different?

What do the numbers say?
Studies looking at the impact of robots on the job market have contradictory findings. A paper released by the National Bureau of Economic Research concludes that every robot introduced between 1990 and 2007 coincided with the elimination of 6.2 jobs within the commute area and a slight drop in wages. The International Federation of Robotics however found that from 2010 to 2015, the US industry installed around 135,000 new industrial robots, mainly in the car industry. During this same period, the number of employees in the automotive sector increased by 230,000, which suggests a positive impact on jobs.

Examples of this can also be seen in Amazon warehouses where the introduction of more than 100,000 warehouse robots did not lead to a dip in human labor. In fact, Amazon has added 113,500 people to its company worldwide in the past year.

Other studies have tried to estimate the number of jobs that could be automated in the future, and there again, the numbers vary widely. An Oxford report from 2013 estimated that 47% of U.S. jobs were at risk of automation. The OECD however has said that “14% of jobs in developed countries were highly automatable, with a further 32% likely to experience significant changes to the way they were carried out.”

So which is it, do robots create or destroy jobs? The answer may be “it’s complicated”. Certain professions may disappear in a local community, while the overall number of jobs may increase globally. In any case, the nature of work will most likely change.

Robots perform tasks, not jobs
Most jobs require workers to have more than one skill. Building a fully automated solution would therefore require a robot that masters many different tasks. Making robots is hard however, so they tend to be highly specialised. Imagine all the tasks a cleaner can do, yet it took Dyson 12 years of research just to make a vacuum cleaning robot. The reality is that robots perform tasks, not jobs. It therefore makes sense to think of robots as tools that can be used by people in their workplace, ideally helping with the dull, dirty, or dangerous tasks and boosting productivity. This has spurred a new area of collaborative robots, or cobots, that are easy to work with. ColRobot for example is a European project focussed on building an integrated system for collaborative robotics.

Skills for the new economy
The jobs of today are different from the ones of tomorrow. There is a pressing need to train a new generation of roboticists. This workforce will need to be diverse to ensure the best tools are being built for everyone. Inspiring the future generation is the goal of the European Robotics Week, which hosts more than 1000 events all over Europe. Training is further needed at all levels from school for young children to graduate education programs. But not everyone needs to be a roboticist, being technology literate is the first step towards building environments where humans and robots can work together. And while robots help us with the menial tasks, we have a chance to be “more human”. A carebot won’t replace a caregiver, it will give the caregiver time to have a coffee with their patient. Ultimately, we have the opportunity to focus on the jobs we enjoy most. Creative sectors, and those requiring emotional intelligence and empathy will also be in high demand in the future.

Technology that benefits all
One risk with automation is that wealth is concentrated in the hands of those that design or have access to the technology. Such a winner-takesall scenario would lead to growing inequality between large technology companies and workers. Wages have also stagnated, even though productivity has increased, which is another marker of inequality. At the same time these technologies are becoming increasingly accessible, meaning that non-experts should feel empowered to use them in their own industries and lives. The European Union and individual European governments are actively preparing for a change in labour markets with dedicated commissions and reports, as well as ground work to ensure the robot revolution benefits all. Solutions discussed include taxing automation, providing for a universal basic income, or boosting education, research, and entrepreneurship.

This article is part of a series of briefing documents published on www.eu-robotics.net/sparc. This project has received funding from the European Union’s Horizon 2020 Programme under grant agreement n° 688441

Waymo’s left turns frustrate other drivers

This week’s hot story was again from Amir at The Information and there is even more detail in the author’s Twitter thread.

The short summary: Amir was able to find a fair number of Waymo’s neighbours in Chandler, Arizona who are getting frustrated by the over-cautious drive patterns of the Waymo vans. Several used the words, “I hate them.”

A lot of the problems involve over-hesitation at an unprotected left turn near the Waymo HQ. The car is just not certain when it can turn. There is also additional confirmation of what I reported earlier, that operation with no safety driver is still very rare, and on limited streets.

Unprotected turns, especially left ones, have always been one of the more challenging elements of day-to-day driving. You must contend with oncoming traffic and pedestrians who may be crossing as well. You may have to do this against traffic that is moving at high speed.

While I am generally not surprised that these intersections can be a problem, I am a little surprised they are one for Waymo. Waymo is the only operating car which features a steerable, high resolution long range LIDAR on board. This means it can see out 200m or more (in a narrower field of view.) This lets it get a good look at traffic coming at it in such situations. (Radar also sees such vehicles but with much less resolution.)

For Waymo, this is not a problem of sensors but one of being too timid. One reason they are operating in Phoenix is it’s a pretty easy area to be timid in. The instinct of all teams is to avoid early risks that lead to early accidents. That became even stronger in Arizona after the Uber fatality, which used up a lot of the public’s tolerance for such errors. As such, the “better safe than sorry” philosophy which was already present in Waymo and most teams has been strengthened.

The problem is, it needs to eventually be weakened. Timid drivers won’t make it in the real world. They won’t make it far at all in the non-tame places like Boston. Thus you look at a nasty trade-off:

  • The more timid you are, the more problems you have and the more people driving behind you that you annoy.
  • The less timid you are, the greater the risk of a mistake and an accident.

That leaves only a few options. The other drivers must adapt better to a timid driver, or the public must get more tolerant of a slightly higher (but still better than human) accident risk.

Hype around self-driving cars has pushed some into the public to expect computerized perfection. That’s not coming.

Changing how people react?

Believe it or not, it is not as impossible to change the behaviour of other drivers as you might think. In Manhattan not that may years ago, two things were very common. Endless honking, and gridlock. Both were the result of well ingrained aggressive habits of New York drivers. The city decided to crack down on both, and got aggressive with fines. It worked, and those things are both vastly reduced.

It’s less possible to adjust the patterns of pedestrians. Some recent articles have gotten a lot of attention from people suggesting this must happen. I think some of it will happen, but much less than hoped, and that will be the subject of another article.

A robocar should eventually get very good at driving decisions which involve physics, because computers are very good at physics. Unlike humans which have difficulty precisely timing when an oncoming car will get to them, robots could in theory do it with a very frightening precision, making turns through gaps that seem tiny to humans. This would frighten other drivers and cause problems, so it’s not something we’ll see today.

This isn’t the last story we’ll see of robocars frustrating other drivers. That’s particularly true if we unwisely keep them at the speed limit. My long term belief is that most of the traffic code should be eliminate for robocars and be replaced by, “it’s legal if you can do it safely and without unfairly impeding traffic.” The whole idea of a traffic code only makes sense for humans. With robots, since there will never be more than a few dozen different software stacks on the road, you can just get all the designers together in a room and work out what should be done and what is safe. Traffic codes and other laws are there to deal with humans who can’t be trusted to know the rules or even obey the rules they know. While companies can’t be trusted to do anything but look after their own interests, you can easily make it in their interests to follow the rules.

Rapid prototyping of the strider robot – smoother, stronger, faster

This summer we used our Strider optimizer coupled with rapid prototyping in LEGO to refine its 10-bar linkage.

In a tiny fraction of the time it took us to refine TrotBot’s linkage in our garage, we explored numerous variations of Strider’s linkage and their trade-offs, and were able to significantly improve its performance in these categories:

Gait Efficiency. To be energy efficient, walking gaits should be smooth and not cause the robot to rise and fall – think how much more tiring it is to do lunges than it is to simply walk. The feet should also move at constant speed – try walking while changing how quickly your feet sweep across the ground and your leg muscles will quickly complain! Strider Ver 3 was optimized for both of these features, and it’s the only mechanism that we’ve tested which can walk with a 1:1 gear ratio without the LEGO motors stalling:

Rugged Terrain. Like with TrotBot, we wanted Strider to be able to walk on rugged terrain, otherwise why not just use wheels? But, mechanical walkers are blind and dumb, and they can’t lift their feet to avoid tripping on obstacles. So we designed Strider’s foot-path to mimic how you would walk blindfolded on a path crisscrossed by roots: lift your feet high and keep them high until stepping back down to the ground, like this:

Here’s a rugged terrain test an 8-leg build:

Strength. Walkers stress frames more than wheeled vehicles, so we increased the frame’s rigidity with more triangles. Also, the leverage of long legs can put a tremendous amount of force on the leg’s joints, especially when turning them tank-style. We strengthened Strider’s leg joints by sandwiching them between beams like in the image below, which also reduces how quickly friction wears down the lips of the frictionless pins.

Here’s a test of Strider’s strength with a 10 pound load:

We made these changes while keeping Strider simple – it’s still our easiest walker to build. We also (hopefully) made our building instructions more clear. We learned how bad we are at creating building instructions from Ben’s experience teaching his walking robots class last spring. In the past when users would email us about something confusing in the instructions, we’d simply add more pictures to clarify things. This backfired in Ben’s class, since more build pictures resulted in the students getting more confused, and caused them to skim thru the pictures more quickly, and to make more mistakes. As we learned, less is more!

We also separated the leg and frame instructions to make it easier to build different versions of Strider, and we designed the frame to make it easy to swap between the battery box/IR controller, or the EV3 brick. You can find the instructions here. Here’s an example build with the EV3 brick mounted underneath – but it would probably work with the brick mounted on top as well.

For the bold, we also posted a half dozen new variations of the Strider linkage for you to try building here, along with an online optimizer for the even bolder to create their own versions of the Strider linkage. We’ve also optimized Klann’s and Strandbeest’s linkages for LEGO, and you can find their online optimizers here. (jeez, I guess we’ve been busy)

Here’s a final teaser to encourage you (or your students) to take on the challenging task of replacing wheels with mechanical legs:

UTSA enters Guinness World Records with smallest medical robot

It can't be seen with a human eye. It doesn't look anything like C-3PO or R2-D2, or even BB-8. But, nevertheless, it is a robot (all 120nm of it) and its creators from The University of Texas at San Antonio (UTSA) are now world record holders in the Guinness World Records for creating the Smallest Medical Robot.

Robots in Depth with Søren Peter Johansen

In this episode of Robots in Depth, Per Sjöborg speaks with Søren Peter Johansen from DTI about implementing robotic solutions.

Søren talks about how he got into robotics by starting to tinker with any electronic he could get his hands on. He worked in a mechanical workshop and added automation to the machines in the shop. As robots became more and more available, he then included them in his work.

Søren also discusses examples of successful human robot collaboration and how software and hardware both are essential elements of robot development.

We also get to hear about how he went to the Danish Technological Institute because he saw an opportunity to work with lots of interesting robots.

This interview was recorded in 2016.

The AI driving olympics (the duckies go to NIPS!)

We are excited to announce the AI Driving Olympics (AI-DO), a new competition focused around AI for self-driving cars. The first edition is going to be at NIPS 2018; the second edition will be at ICRA 2019.

The competition comprises challenges of increasing complexity for self-driving cars, from lane following to fleet management, all on the Duckietown platform.

We are excited because AI-DO at NIPS 2018 is going to be the first robotic competition at a machine learning conference, and in a way that is completely reproducible: you send your code — we run it on our robots. Or, you can get a Duckiebot for yourself through the Kickstarter run by our newly-established non-profit Duckietown foundation.

For all details and rules about AI-DO see here.

The AI Driving Olympics is presented in collaboration with 6 academic institutions: ETH Zürich (Switzerland), Université de Montréal (Canada), National Chiao Tung University (Taiwan), Toyota Technological Institute at Chicago (USA), Tsinghua University (China) and Georgia Tech (USA), as well as two industry co-organizers: nuTonomy (a self-driving car company) and Amazon Web Services (AWS).

Uber might sell its robocar division, Nuro opens first delivery pilot in Scottsdale

The newsletter The Information reports Uber’s investors are pushing Uber to sell its self-drive division to some other large player. The division has, of course, been nothing but trouble for Uber, and as I have noted several times, Uber is one of the few large players in this space that doesn’t have to build their own tech. They have the #1 brand in selling rides, and selling rides is what the robotaxi business is all about.

At the same time, Uber recruited a great team (though it has lost many of them.) First they recruited many of the best around CMU for their Pittsburgh ATC headquarters. CMU and Stanford are where most of the stars of the robocar world have come from. Then they “paid” $680M in stock for Otto, which was really an acqui-hire in many ways, at least if you believe court documents. Because that stock payout required certain milestones that weren’t met, the Otto stockholders did not get their money, but Uber had to make a large stock payout to Waymo as a result of the lawsuit over Anthony Levanowski’s actions.

So they have this team, but the team and the Uber name are tarnished by the fatality. But the right pickings from the team are still valuable to somebody who is falling behind, if you eliminate the factors that led to the fatality and take the Uber name off it.

At the same time, Uber gets a pledge that the car the team makes will be usable in the Uber network. They get guaranteed access to tech (if the new owner succeeds) though not the deep control that comes with owning it. They don’t need the deep control. In fact, it’s now better if they can stick another famous brand on it.

Nuro starts a delivery pilot

Aside from Starship (which I am involved in) the company to watch in the delivery space is Nuro. Nuro has started a delivery pilot in Scottsdale with Fry’s groceries. The pilot will be done with regular Prius and Leaf cars with Nuro’s self drive tech, and a safety driver, not with the small no-seat delivery pod Nuro is trying to build. That pod isn’t ready for the real streets, even the easy streets of Scottsdale.

Nuro is the company to watch in on-road delivery because its founders were among the top members of Google/Waymo’s team. I worked with them regularly when I was there and they are the best. They have also raised lots of money.

Driving on the road is much harder than the sidewalk, though. A road robot must be able to handle any situation on its own and get to a safe state if there is a problem no matter what. A sidewalk robot can stop in 30cm. If it encounters something it doesn’t understand, it can just stop and request help from HQ. Safety is very unlikely to be an issue, while a road robot could really hurt somebody in a mistake.

The $6 price for delivery in the pilot is strange, since that’s a common price for human driven delivery.

Page 465 of 522
1 463 464 465 466 467 522