Mistral's Robostral Navigate: a state of the art robotics navigation model
21–30 of 117 posts
Re: Mistral's Robostral Navigate: a state of the art robotics navigation model
#22Producing specific niche models for 100 year old industries that have mountains of data and warehouses full of folders will be the european take on AI. It may come late but it‘ll be safe and reliable. It also requires a lot of OCR.
Re: Mistral's Robostral Navigate: a state of the art robotics navigation model
#23Re: Mistral's Robostral Navigate: a state of the art robotics navigation model
#24Frontier labs are realizing that software/models themselves don’t have real moats and move to embodied ai. SOTA 80% means a practically useless robot. What are they really imagining their ICP to be here?
Re: Mistral's Robostral Navigate: a state of the art robotics navigation model
#25Re: Mistral's Robostral Navigate: a state of the art robotics navigation model
#26How long until Tesla buys Mistral?
I imagine the EU would block any attempted takeover of Mistral given recent Anthropic and US govt actions.
Re: Mistral's Robostral Navigate: a state of the art robotics navigation model
#27Earlier quoted context omitted.
The Niche model story is still fairly week. Evidence points to general models being equally capable to niche models at a more attractive capex (risk is spread across multiple verticals rather than concentrated in a single model capability)
It seems like a stronger story for robotics, since smaller models can always react to the environment faster than large models at a given hardware budget. Also because robots that keep their models local for latency or reliability aren't going to be carrying many kilowatts of inference capacity.
Unless you are in military robotics or automotive of course :)
Re: Mistral's Robostral Navigate: a state of the art robotics navigation model
#28Producing specific niche models for 100 year old industries that have mountains of data and warehouses full of folders will be the european take on AI. It may come late but it‘ll be safe and reliable. It also requires a lot of OCR.
The Niche model story is still fairly week. Evidence points to general models being equally capable to niche models at a more attractive capex (risk is spread across multiple verticals rather than concentrated in a single model capability)
Costs of simple tasks grow extensively: OCR with "Mistral OCR" at $4 per 1000 pages vs OCR with Opus 4.8 at sometimes¹ $1 per "page".
Or just the immense costs when burning tokens in an unoptimized agentic coding environment costing tens of dollars for a few simple classes or functions versus a highly optimized "autocomplete" model costing under $10 for thousands of such classes and functions.
Or the, over ten dollars worth of tokens when some "agent" using a general model, tries to perform the task I gave it to "read the event on example.com/event/1337 and put it in my calendar", include commute time as well"
The "general models" currently only become smarter by growing bigger and having larger context windows - by becoming exponentially more expensive to train and to run and to interact with. Whereas "Niche" models can do the things that "normal code" cannot do, and improve by tuning and tweaking only that. Their goal is then to fill in gaps that traditionally are hard or impossible with normal software. Wheras the goal of a general model (with agentic reasoning)is to replace that entire "normal software".
One example: I am not interested in "chatting with my calendar". I'm interested in a calendar because it is a well known view (UI) of my planning and tasks, but I see a lot of opportunities where AI can improve my working with this calendar. I may be interested in a smarter screen when I hit "+ Add event"; one that has knowledge of my previous events and patterns (some RAG vector db maybe). One that maybe has access to content I just copied, or read (though: privacy?) or can open my camera to let me shoot a pic of something that has the event info on it. In such a set-up, Niche LLMs perform dedicated tasks: determine patterns (he always books a Yoga class on wednesday or thursday, two days in advance, so lets suggest a yoga class), determine existing content (event is planned 100Km from his home, so lets suggest the commute based on previous commutes like this). Or an OCR model. Or an autocomplete model. Relatively simple, niche models, called from within software to aid me when "calendaring". Not replace the entire calendar with some chat.
¹Edit: This was a rather unscientific research of mine, where I compared some models to read from photographs, compared purely on costs and timing. "Opus" or other generic LLMS with image input capabilities commonly did better on "performance" esp with difficult input such as a picture of a poster of some rock event.
Re: Mistral's Robostral Navigate: a state of the art robotics navigation model
#29Re: Mistral's Robostral Navigate: a state of the art robotics navigation model
#30Earlier quoted context omitted.
It seems like a stronger story for robotics, since smaller models can always react to the environment faster than large models at a given hardware budget. Also because robots that keep their models local for latency or reliability aren't going to be carrying many kilowatts of inference capacity.
remote inference should be sufficient for most robotics applications with potentially a small model for safety critical actions running locally. Unless you are in military robotics or automotive of course :)
I'm also skeptical that you can cleanly differentiate between "safety critical actions" and "actions", though this is less of a practical concern given how laissez-faire some manufacturers are. For context, I work on safety critical robotics (in automotive).