jonnycowboy
Joined 18 years ago
Joined 18 years ago
That said, I’m not sure their choice of materials is the good one for a startup.
You can look up Series Elastic Actuators for more info or use this article as guidance (any spring will do as long as the force range and spring constant is adequate).
https://www.sciencedirect.com/science/article/pii/S240589631...
1st a voice setup with Alexa or similar can really help.
With regards to phone use, some of our users have an attachment to put the phone close to their head and use their nose to "click/select" (they can move their head).
Eye tracking technology is really impressive these days (can be as fast as using a mouse). I've recently demoed a system with a Tobii sensor (https://www.tobii.com/) that was hooked up to a laptop, very impressive when combined with appropriate software (it handles scrolling, keyboard shortcuts, etc in a custom interface). I'm not sure with regards to phone/tablet use how well they integrate.
Ping me on Linkedin if you'd like to talk more.
I have friends who have been looking after legacy applications for an airline running on Unisys. The core apps for reservation, Cargo booking and weight/balance were written in FORTRAN. In recent times, the front end was written in Java to give web access. They tried to rewrite the core apps but it was impossible to do so and get the performance.
One point I noticed not mentioned yet is that the images used for training are only 64x64! In the original google "grasping" research, the images were 472 × 472, 54 times bigger! I think they are looking for "minimum visual information" required to trigger the required learning. This will help in mobile applications (ie: robotics, smartphones, etc) where processing power is severely limited.
- automated cities & robotic workers - HARC working on the interfaces for the "workers" - basic income to replace minimum wage earners' incomes
Would love to work on this path!
Montreal, Canada