302 karma · joined December 8, 2013
website: www.cbames.com email: barrett@botbuilt.com
What Force/Torque sensor do you use? Some of them are temperature sensitive and require a good warm-up period before they can be used to achieve good performance.
[0]https://www.universal-robots.com/how-tos-and-faqs/how-to/ur-...
Are you just using Jacobian transpose for force control on the neck? I ask because it seems a bit stiff, the red marks on the neck of the test subject suggested to me that maybe there's a lot of noise in your force sensing, or at least unmodeled behavior.
Due to the slow growth of test subject hair, have you found 6$ to be cheap enough to keep your test cycles short enough?
The kinematic configuration of the arm looks odd, did you pick this to maximize rank of the Jacobian or the manipulability matrix?
At one level this has to be true, if it weren't I could plop a black box on the table and say I've invented AGI it just can't interact with anyone, and you would have no recourse but accept my statement. We must necessarily define intelligence as the interaction that the agent can perform with some environment otherwise we'd have no way to know of its intelligence.
However, I suspect you're near the arm's payload limit with the clipper setup. Feel free to reach out. I get to the Bay Area every semester or so.
What arm are you using? Also what depth sensor?
A few suggestions:
It would appear that you're taking a pretty common approach to robot manipulation, sense, plan, "close your eyes" and then act. This works for stationary objects when you have high accuracy control and high accuracy sensing. Unless you're envisioning strapping people's heads down, your target is going to move. This will necessitate a closed-loop approach.
A closed-loop approach here would benefit from force control at the end effector. ATI[1] is a good source for 6-axis load cells and they've recently come out with smaller form factor load cells.
A second useful sensor would be a Time-of-Flight depth sensor. The old PMD Camboard Nano used to get up to 90 FPS and a close effective range (if I recall correctly ~3-4"). The time of flight sensors can be a bit noisy, but I've written up some of the smoothing approaches I've taken [2].
Good luck!
*I went to Vegas and built an arm with the founders.
I think limiting our analysis to one particular form of robot is probably not a good idea. As we're still trying to figure out which form is the best for whatever that "killer app" is in robotics.
Also one reason to not turn a kitchen into a robot is generality of solution. If you can have 1 robot work in 3 kitchens is cheaper than retrofitting the 3 kitchens.
All of that being said I generally agree with your sentiment, and I think we'll see robots move into places they're needed/bring more additional value than general house chores. For example, restaurants. Where they can be faster, safer with food, but still general enough to put cheese on one burger and not the next without an engineer coming in after installation.
I looked on Glassdoor not too long ago for AI/ML and there were probably 20-30 postings.