great idea! Now, you are running into the same issue Google Trends had to solve: term disambiguation. For instance, "atom" is ambiguous in a comparison of editors like this: https://hackernewstrends.com/?q=sublime&q=atom&q=vscode. Given LLMs it might be possible to use an embedding vector (with context) instead of a text string for indexing, and if you do, this problem might go away.
Almost definitely 100% teleoperated -- the robot might move between places autonomously, but all the manipulation tasks, i.e., the actual cleaning, is not something anyone yet knows how to do autonomously reliably. And that's OK. However I'd like to know whether the data you gather from these cleanings is shared with other companies (who would be willing to pay a lot of money for it in order to train their own physical AI models).
What a silly idea. Technology moves 20x faster than the legislature. There is no point in even trying this. By the time any suggestions would get implemented and (all?) signs replaced, they would already no longer be necessary -- like, 15 years past being necessary.
Makes a lot of sense, and seems better executed than AWS's pathetic RoboMaker attempt 8 years ago or whenever that was.
Was looking for the team but there is no linkedin link on your page.
The problem is not that there is no standard -- there is, it's called ROS. The problem is that manufacturers are not interested in opening their robots up to that degree.
Also, REST is a terrible idea for interacting with robots. REST is call-response based. But with Robots a pub/sub (like ROS or MQTT) or a blackboard data architecture (like what we used in Transitive Robotics) is much more efficient and natural.
Foxglove is not the only name in town. There are many, Transitive Robotics, the company I'm building is one of them. Different from Foxglove we are much more focused on live-remote monitoring and control, e.g., we have a pretty popular remote teleoperation module: https://transitiverobotics.com/caps/transitive-robotics/remo...
You can find all the other modules we're currently offering here: https://transitiverobotics.com/caps/
The platform itself is and remains open-source.
We are thrilled to announce a new major version of Transitive, the open-source framework for full-stack robotics. Version 2.0 adds significant new integrations and features: storage of historic and time-series data in ClickHouse, visualization in Grafana, and custom alerting via Alertmanager. Some of our capabilities, like the free Health Monitoring capability, already use these features, providing significant added value to robotics companies with growing fleets.
This is absolutely awesome. Thanks for sharing! I would love to chat more with you. For context: we make a remote teleoperation solution for robotics. It's mostly used for mobile robots, but we've been getting a lot of inquiries regarding teleoperation for manipulation, so I've been learning more about this, in particular regarding the question of speed. I really appreciate these results!
"the funding all these startups are getting should allow them to scale their methods 10x-100x.." .. "Therefore, we might soon see a ChatGPT moment in robotics" -- I don't think so and no, the second statement is NOT entailed by the first. Why would it? Because 100 is a big number? Do you have any idea how much more data LLM needed to be trained for a GPT3 level compared to the data available for robot training right now, and how low dimensional the space is in which LLMs operate compared to robots?
"My intuition is there's 40% chance we will see it this year" -- again, why? Don't you realize that people have been working in robotics for 65 years, and these people don't live under a rock either. They knew about GPT3 because 2023. So why is it NOW less then 10 month you think that this breakthrough will happen?
How can you seriously state that as a positive? Are you trying to exemplify the new AI-patent-generation-mill? No one in their right mind can expect a person to make 10 meaningful inventions in 4 days.
Working with nine different robotics companies over the course of 10 years has taught us a thing or two about designing robotic full-stack architectures. All this experience went into the design of Transitive, the open-source framework for full-stack robotics. In this new mini-series of blog posts we dive into the three core concepts of the framework.
We think that once you've experienced the magic of full-stack encapsulation, you'll not want to go back to the old ways of writing distributed code, esp. in robotics.