AI Engineer World's Fair 2025
Vision AI in 2025 — Peter Robicheaux, Roboflow
Read the talk
Vision AI in 2025: Better Features, Harder Benchmarks
Real-time perception needs more than object recognition: it needs detailed visual features, architectures that can use them, and benchmarks that test unfamiliar domains.
From a talk by Peter Robicheaux
Before you start: Familiarity with embeddings, pretraining, and object detection will help; the article explains the relevant differences between vision and vision-language models.
Seeing quickly enough to act
How can a system interact with the physical world if it cannot reliably see what is happening? Built environments depend on visual information. Peter Robicheaux, introducing himself as Roboflow’s ML lead, argues that the gap between human and computer vision remains larger than the corresponding gap in speech.
Vision also imposes a different engineering constraint: perception has to arrive in time to affect a decision. Recognizing motion requires processing successive frames, multiple times per second. Sending every frame to a central computing hub can add enough latency to undermine the resulting decisions. That makes edge execution a practical requirement for many vision systems, rather than merely a deployment preference.
Suggest correction
This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.
What familiar benchmarks fail to demand
Looking back at a version of this discussion at NeurIPS, Robicheaux identifies saturated evaluations as a central problem. In his diagnosis, ImageNet and COCO largely reward pattern matching. If an evaluation can be solved without richer visual understanding, it supplies little incentive to build that understanding through larger pretraining. Language provides the motivating comparison: broad pretraining produces representations that many downstream applications can reuse.
There are two separate limitations here. Representation quality concerns what a pretrained vision model actually preserves about an image. Downstream transfer concerns whether another model can use those features effectively. Better embeddings alone do not guarantee a better detector; a more capable detector architecture cannot recover information its embeddings never retained. Robicheaux’s criticism addresses both sides of that relationship.
Suggest correction
This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.
Knowing about watches is not reading their hands
A watch makes the distinction concrete. In Robicheaux’s reported Claude 3.5 example, the model recognizes the kind of object it is looking at but supplies an incorrect time. Reading a watch requires a more precise chain of perception: locate the hands, distinguish their positions, and relate those positions to the dial’s numbers. Conceptual knowledge of watches does not establish that spatial fidelity.
His updated Claude 4 example also fails. He identifies the displayed time as 10:10 and points out that this is a common arrangement in watch imagery. These examples illustrate a failure on the presented inputs, rather than a comprehensive evaluation of either model: fluent knowledge about an object can coexist with an inability to read its visible state.
Suggest correction
This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.
The visual distinctions captions leave out
The MMVP benchmark tests similarly basic visual distinctions. In the school-bus example, GPT-4 is asked whether the image shows the front or back of the bus. The displayed image shows the front, but the response claims that the bus faces away and invents details to support that answer. The explanation sounds coherent even though its visual premise is wrong.
The construction of MMVP helps explain why this can happen. Robicheaux describes selecting image pairs that are close in CLIP embedding space but far apart in DINOv2 space. CLIP learns through contrastive image–text training; DINOv2 learns visual representations through self-supervision. A pair that CLIP treats as similar but DINOv2 separates exposes a distinction that the two representations preserve differently.
In the talk’s simplified account of CLIP training, the model must match images with their corresponding captions. But consider the dog examples: one dog faces the camera, while another faces away. An ordinary caption may describe both without mentioning orientation. If the training objective does not reward that distinction, the model has less reason to preserve it. Caption alignment can succeed while detailed visual discrimination fails. This explains a possible weakness in image–text supervision without requiring every vision-language model to use the same encoder.
Suggest correction
This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.
Preserving visual structure while aligning with language
DINOv2 offers evidence that visual pretraining can discover useful structure. Robicheaux presents a principal-component analysis, or PCA, visualization of its learned features. He highlights not only the dog’s separation from a green background, but also distinctions between parts of its body. The visualization exposes structure in pretrained features; it is not itself a supervised segmentation result.
He also points to analogous features for dog and human legs. The interesting possibility is a representation that preserves meaningful parts across different subjects. That leads to the unresolved problem: how can those detailed visual features become aligned with language and usable by a vision-language model without losing their fidelity?
Suggest correction
This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.
The detector determines the payoff from pretraining
Even when useful visual features exist, downstream models must be able to exploit them. Object detection makes that second limitation visible. Robicheaux uses a comparison from LW-DETR to contrast the convolutional YOLOv8n detector with transformer-based detectors. The question is how much each benefits from pretraining before evaluation on COCO.
The talk reports the following gains in mean average precision, or mAP, for the comparison shown:
| Detector | Architecture | Reported COCO gain with pretraining |
|---|---|---|
| YOLOv8n | Convolutional | About 0.2 mAP points |
| LW-DETR variants | Transformer | About 5–7 mAP points |
The YOLOv8n figure is a point increase, not a relative percentage increase. These results concern the displayed models and training recipes; they do not establish that every convolutional detector is unable to benefit from pretraining.
The architectural implication is that pretraining value depends on the model receiving it. Robicheaux describes Objects365 pretraining here as using about 1.6 million images—already considered large in this detection setting, but modest compared with the scale associated with language pretraining. The opportunity is both to improve visual representations and to build detectors that can make better use of them.
Suggest correction
This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.
Bringing DINOv2 into real-time detection
RF-DETR is Roboflow’s response to that opportunity. Robicheaux describes taking the LW-DETR detector design and replacing its backbone with a pretrained DINOv2 backbone. The goal is to carry the benefits of visual pretraining into real-time object detection.
The resulting COCO improvement does not put RF-DETR first in the comparison presented: Robicheaux places it behind D-FINE. That is the historical comparison in this talk; the maintained RF-DETR repository now includes later releases. The more interesting result for his argument is the larger benefit on RF100-VL, a benchmark designed to test adaptation across domains.
COCO’s familiar classes, such as people and coffee cups, can make recognition relatively easy while leaving precise bounding-box placement as the main source of improvement. Better iterative refinement of box coordinates can raise a detector’s score without demonstrating much broader visual knowledge. RF100-VL is intended to make the richness of the underlying features matter more.
Suggest correction
This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.
Testing unfamiliar viewpoints and imaging domains
RF100-VL collects 100 object-detection datasets from Roboflow Universe. Robicheaux loosely estimates that the source collection contained about 750,000 datasets at the time. Curation combined community engagement with a search for difficult domains, rather than simply selecting more examples of familiar natural-image categories.
The resulting diversity changes what a detector must handle:
- Camera viewpoint: Aerial images require recognizing objects from positions uncommon in COCO.
- Imaging modality: Microscopy and X-rays introduce visual appearances unlike ordinary photographs.
Robicheaux proposes this breadth as a more comprehensive test of learned features. It is a benchmark for broader transfer, not an established universal measure of visual intelligence.
Suggest correction
This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.
A class name gets its meaning from the domain
RF100-VL also tests the connection between language and localization. A class name is not always a self-contained description of what to detect. In a volleyball dataset, block denotes an action; recognizing it requires interpreting the word in the context of the sport.
Other examples extend the same requirement:
- Cable defects:
thunderboltnames a defect appearance. Searching for literal lightning would miss the intended target. - Scientific concepts:
fibrosisrequires specialized knowledge beyond familiar categories such as dogs and cats. - Imaging context: The appearance of a target depends on the modality in which it is observed.
The benchmark therefore supplies visual descriptions and annotator instructions for finding the objects. This is its vision-language component: language helps specify the detection task within a domain. It does not mean that the RF-DETR architecture introduced earlier is itself a general conversational VLM.
Suggest correction
This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.
A few visual examples can beat a large VLM
Robicheaux reports that YOLOv8 trained on about ten examples per class outperforms Qwen2.5-VL-72B in the RF100-VL setting discussed. The striking comparison is between a detector adapted with a small amount of visual supervision and a much larger vision-language model. It should not be read as a comparison under identical training or prompting conditions.
His interpretation separates linguistic generalization from visual generalization. A VLM may handle unfamiliar language well while struggling when the images themselves depart from familiar domains. RF100-VL is intended to make that weakness visible and encourage research on the visual side of VLMs. The prepared talk closes by returning to pretrained features: Robicheaux reports that stronger embeddings improve DETR’s RF100-VL performance beyond what embeddings learned on Objects365 alone provide.
Suggest correction
This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.
Running locally and accessing the data
The first audience question returns to edge deployment. After briefly asking whether the question concerns Qwen, Robicheaux understands it as running the detector locally and answers affirmatively. He cites roughly 20 million parameters for the small detector. That size is not a latency measurement or a hardware prescription, and it does not describe the large Qwen model.
The dataset is publicly available. Robicheaux points readers to the RF100-VL project site for the paper and download utilities, and also mentions availability on Hugging Face.
Medical and biological datasets enter the collection through research use of Roboflow. Robicheaux describes offering researchers free access to labeling tools in exchange for contributing their data openly. He says some contributions come from research associated with papers cited in Nature. This explains the community contribution model behind the collection, rather than establishing the provenance or licensing of each constituent dataset.
Suggest correction
This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.
The missing capability is combining all the inputs
An audience member raises the physical differences between natural images and biological or medical imaging. Robicheaux responds by emphasizing the benchmark’s range of imaging and prediction modalities, then identifies the few-shot track as especially interesting. Its canonical ten-shot splits supply three kinds of information: a class name, annotator instructions explaining how to find it, and visual examples. The original paper defines the ten-shot budget as ten object instances per class, not necessarily ten distinct images.
The desired behavior is that these inputs complement one another. The class name supplies a concept, the instructions clarify its meaning in the dataset, and the examples show its visual appearance. Robicheaux’s talk-time assessment is that no model they had found could combine all three to achieve higher mAP than it could obtain with one of those inputs removed. The weakness is not simply missing language or missing images; it is failure to turn their combination into better detection.
The final question contrasts generalist models with specialists such as SAM and Grounding DINO. Robicheaux says specialists currently perform best and describes evaluations of Grounding DINO both without adaptation and after fine-tuning.
His rounded Q&A figures and the original paper’s results differ:
| RF100-VL setting | Spoken average mAP | Original paper average mAP |
|---|---|---|
| Grounding DINO, zero-shot | About 19 | 15.7 |
| YOLOv8n, ten-shot | About 25 | 20.1; 21.6 with Federated Loss |
The original paper averages across 100 datasets using pycocotools with maxDets=500. These are different reported results, not interchangeable rounded versions of the same scores. In the spoken comparison, Robicheaux describes YOLOv8n as trained from scratch on the ten-shot examples.
Robicheaux then reports that fine-tuning Grounding DINO with Federated Loss produces their highest-performing model on the dataset. The zero-shot score above does not describe that fine-tuned result. Yet specialist performance is only part of the goal. A generalist should be able to use annotator instructions, ten-shot examples, and class names together—and become more accurate because each contributes information the others lack. That is the capability the benchmark is meant to demand.
Suggest correction
This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.
Resources
From the talk
Benchmark design, evaluation protocols and original zero-shot and few-shot detection results.
Project overview, dataset exploration and links to benchmark materials.
Utilities for downloading full and few-shot datasets; the documented workflow requires a free Roboflow API key.
Research on CLIP-blind image pairs and basic visual distinctions multimodal models miss.
Real-time transformer detector architecture, pretraining recipe and COCO comparisons.
Self-supervised visual backbones and examples for using pretrained features.
Updates since the talk
Maintained RF-DETR implementation with training resources and model variants added after the talk.
Read the complete timestamped transcript
- 0:00
[upbeat music] I'm gonna be giving a sh- quick presentation about the state of the union regarding AI vision.
- 0:21
Um, so I'm Peter Robicheaux. I'm the ML lead at Roboflow, which is a platform for building and deploying vision models. Um, so a lot of people are really interested in LLMs these days, so I'm trying to pitch why computer vision matters.
- 0:40
Uh, so if you think about systems that interact with the real world, they have to use vision as one of their primary inputs because the w- the built world is sort of built around vision as a fundamental primitive.
- 0:53
Um, and there's a big gap between where human vision is and where computer vision is, uh, I, I would argue a bigger gap than exists currently for human speech and, uh, computer speech.
- 1:10
Uh, computer vision has like, uh, its own set of problems that are very distinct from the problems that need to be solved by LLMs. Latency usually matters. You need to-- If you want to perceive motion, you have to be running your process multiple frames per second.
- 1:26
Uh, you usually wanna run at the edge. You can't have, like, one big hub where you do all of your computation because you would introduce too much latency to make decisions based off that computation.
- 1:39
Um, and so I sort of gave, uh, a version of this talk, uh, at Latent Space podcast at NeurIPS. Um, and retrospectively, I think we identified a few problems with, uh, the field of vision in twenty twenty-four, one of them being evals are saturated.
- 1:57
So vision evals like ImageNet and COCO, they're mostly like pattern matching. They measure your ability to match patterns and sort of like don't require much visual intelligence to solve.
- 2:10
Uh, consequently, I think vision models don't leverage big pre-training the way that, uh, language models do. So right now you can take a language model, unleash it on the internet and get something incredibly smart.
- 2:23
Some of the best vision models are cert-- are moving in that direction. But because you don't need that level of like knowledge and intelligence to solve the evals, there's kind of no incentive to do so.
- 2:37
Uh, and I think that part of that-- So there's sort of two dimensions here. One is that vision doesn't leverage big pre-training. So you can think of, like, if you're building an application with language right now, you probably wanna use the smartest model to get an embedding that works really well for you.
- 2:52
And right now we don't have-- Like, there are downstream applications that make really good use of the pre-training and the embeddings that they get from large language models. But there aren't really good vision models that can leverage these embeddings.
- 3:07
And the, the corollary to this is that th-there are-- the quality of big pre-trained models just isn't the same in vision as it is in language. And so my, my underlying conclusion is vision models aren't smart.
- 3:20
That's the, the takeaway. And I can prove it to you. So last year when Claude Three point five was happening, you could give it an image of a watch and it just guesses-- You ask it what time it is, and it'll just guess a random time.
- 3:32
And that's because this model, it has a good conceptual abstract idea of what a clock is or what a watch is, but when it comes to actually identifying the location of watch hands and finding the numbers on the watch, it's hopeless.
- 3:45
Uh, and updated for Claude Four, still has no idea what time it is. And this is even like a, a, an egregious failure because ten ten is like the stock time on like all watches.
- 3:56
So the fact that it couldn't even get like the most common time is, uh, pretty telling.
- 4:02
Uh, there's-- So there's this really cool d-- uh, dataset that's trying to measure this inability of LLMs to see, uh, called MMVP, which basically you can see an example here where they ask this question that seems incredibly obvious.
- 4:18
And the model-- So in this case, they ask the model, which is like ChatGPT Four, uh, which direction the school bus is facing. Are we seeing the front or the back of the school bus?
- 4:29
And the model com-- gets it completely wrong and then hallucinates details to support its claim. And again, I think this is evidence that large language models, which are maybe the most intelligent models that we have, like cannot see.
- 4:42
And that is due to a lack of visual features that they can perceive with. And so the way that th-this dataset was created is they went and they found pairs of images that were close in CLIP space, but far in DINOv2 space.
- 4:56
So CLIP is a, is a vision-language model that was c- sort of contrastively trained on the whole internet. DINOv2 is just a pure vision model that was, uh, trained in a self-supervised way on the whole internet, right?
- 5:07
And so what this is showing is that CLIP is not discriminative enough to tell these two images apart, right? So according to CLIP, these two images basically look the same.
- 5:17
And what that's pointing to is like a failure in vision-language pre-training. And so the way CLIP is trained is basically you come up with a big dataset of captioned images, and you, you ask the model to-- You scramble the captions and scramble the images and ask the model to pair the image with the caption.
- 5:37
But the thing is, is if you go back and look at these two images, what is a caption that would distinguish these two images, right? It's like the peculiar pose of the dog.
- 5:46
In one, in one image it's facing the camera, in one it's facing away. But these are sort of details that aren't included in the caption. So if your loss function can't tell these two images apart, then why would your model be able to, right?
- 5:58
So vision-only pre-training kind of works, is, is the claim. So DINOv2 is this really cool model that-- So what you're seeing right now is a visualization of its PCA'd features that have been self-discovered by pre-training on the whole internet.
- 6:13
Um, so what's really cool is not only, like, does it find the mask of the dog, obviously, that's sort of easy 'cause it's highly contrasted with the green background, but it also finds the segments of the dog, and it finds even analogous segments.
- 6:28
So if you look at the, these principle components, you compare the legs of a dog, it'll be in the same sort of feature space as the legs of a, of a human.
- 6:35
And so the, eh, there's sort of this big open question, which is like, how do we get vision features that are well-aligned with language features and usable by VLMs that don't suck [chuckles] and like have visual fidelity?
- 6:51
Um, cool. So, so that's part of the story. The other part of this, the question that needs to be answered is, given that we have some sort of semi-working large pre-training, uh, of vision models, why aren't we leveraging these vision models?
- 7:07
And I would answer that, at least in the object detection space, the answer is mostly in the distinction between convolutional models and transformers. So this is from LW-DETR, which is one of the top-performing, uh, detection transformers that currently exists.
- 7:24
Uh, if you look at this graph, if you look at YOLOv8, YOLOv8n, which is a convolutional object detector on the edge, with and without pre-training on Objects365, it gains like 0.2 mAP, which is like the main accuracy metric for object detectors.
- 7:39
So Objects365, which is a big million, 1.6 million image dataset, uh, pre-training on it leads almost no performance improvements on, on COCO. Whereas for LW-DETR, which is a transformer-based model, you can see that without...
- 7:56
If you look at this column mAP without pre-training, and you look at the column mAP with pre-training, you can see that you're getting like five mAP improvements across the board, sometimes even seven mAP improvements, which is like a gigantic amount, right?
- 8:07
And so basically, the-- while the language world knows that transformers are able to leverage big pre-trainings and, and yield decent results, the vision world is sort of just now catching up.
- 8:21
Uh, and you can see this from the scale of the big pre-training. In the image world, pre-training on Objects365 with 1.6 million images is considered a large pre-training. That would be like a tiny like challenge dataset for like, for like undergrads in the LLM world.
- 8:38
So [chuckles] I wanna announce Roboflow's special new model called R- RF-DETR, which leverages the DINOv2 pre-trained backbone and, uh, perform or uses it in a real-time object detection context. So this is sort of our answer to the, the, the hole that we see in the field of like why aren't we leveraging big pre-trainings for visual models.
- 9:03
Um, and so here are some of the metrics. You can see that, um,
- 9:09
basically what we did is we took the LW-DETR backbone, and we like kinda swapped it out with the DINOv2 backbone, and we get like a decent improvement on COCO.
- 9:17
Um, and we're still not SOTA, uh, compared to on COCO compared to DeFine, which is the current SOTA. We're like second SOTA. Um, but I think what's really interesting is there's this other dataset called RF100-VL, which we created to measure the sort of domain adaptability of this model.
- 9:35
And you can see massive yields from using the DINOv2 pre-trained backbone, which basically is pointing to the fact that, number one, COCO is too easily solvable. Uh, it basically has common classes like humans and like coffee cups and stuff like this, so it's not a good measure of the intelligence of your model.
- 9:53
More so the way that you optimize COCO is by like really nailing the precise location of a bounding box or something, really having good iterative refinement of your like locations that you're guessing.
- 10:04
Um, whereas we posit RF100-VL, this new dataset, is a better measure of the intelligence of a visual model. Um, so we're introducing a new dataset, RF100-VL, which is a collection of 100 different object detec- detection datasets that were pulled from our open source collection of datasets.
- 10:26
We have something like, I don't know, it's something like 750,000 datasets or whatever on Roboflow Universe, and we hand-curated the 100 best, I guess, by some metrics. So like we sorted by community engagement, and we tried to find very difficult domains.
- 10:44
So you'll notice, for instance, we have different, uh, camera poses that are common fr- in COCO. So we have, uh, like aerial camera, camera positioning, uh, which requires your model to sort of understand different views of an object in order to, to do well.
- 11:01
We have different visual imaging domains. Like you can see like microscopes and X-rays and all this sort of things. Uh, so yeah, we think that this dataset can measure the, the richness of features that are learned by object detectors in a much more comprehensive way than COCO.
- 11:20
Uh, and h- here's-- So the, the other fun thing about this is that it is a visual language model, so we are able to benchmark a bunch of different models on RF100-VL, being able to ask them things like using, contextualizing the class name in the context of this dataset, where, where is this action happening, for instance.
- 11:39
So for-- So if you look at the top left, we have this class which is block, which is representing an action, a volleyball block, but you have to be smart enough to contextualize this like word embedding of block within the context of volleyball to be able to detect that.
- 11:53
Same thing with this thunderbolt-type, uh, defect in this cable here. If you just ask a, a, a dumb vision-language model to detect thunderbolts in the image, it will find nothing.
- 12:02
But if it contextualizes it in the context of a cable defect, then it'll be able to find more things. And it also increases the breadth of classes. So if you only look at COCO, you're basically asking your model, "Hey, can you find a dog?
- 12:16
Can you find a cat?" But like, "Can you find fibrosis?" Now your model needs to have like a lot more information around the world, about the world to solve that problem.
- 12:25
Same thing with different imaging domains. Um, so it is a vision-language benchmark, so it, we also have, um, visual descriptions, uh, and sort of instructions on how to find, uh, the objects that are present in this image.
- 12:40
And basically, what we found is like you take a COCO or you take a YOLOv8 model and you train it on like 10 examples per class, it does better than like QwenV2 72- Qwen 2.5VL 72B, like state-of-the-art gigantic vision-language model.
- 12:57
So the vision-language models are really good right now at generalizing out of distribution in the vis- in the linguistic domain, but absolutely hopeless when it comes to generalizing in the visual domain.
- 13:08
And so we hope that this benchmark can sort of drive that part of the, the research and make sure that the visual parts of VLMs don't get left behind.
- 13:20
Uh, and yeah, basically by leveraging like stronger embeddings, uh, a DETR model does much, much better on RF100VL than just leveraging embeddings learned on Objects365, which makes sense. And that's my talk.
- 13:36
Thank you. Yes.
- 13:38
Can you, can you fine-tune it to run it at the edge?
- 13:41
Fine-tune Qwen on the edge?
- 13:44
On the edge. You know, run it yourself.
- 13:45
Oh, yeah, yeah, yeah. It, it's, it's like 20 million parameters at the small size, yeah. Cool. Any other questions? Thanks, Wicks.
- 13:58
Yeah. Is the dataset, uh, publicly available now?
- 14:00
Yeah, it's publicly available. It's on ... Maybe I can-- If you go to rf100vl.org, you can find our archive paper as well as the code utilities to help download the dataset.
- 14:11
It's also like on Hugging Face somewhere. Yeah.
- 14:15
Is that including the [inaudible]
- 14:18
Yeah. So Roboflow kinda has a pretty unique strategy when it comes to our platform. So we make our platform freely available to all researchers basically. And so we have like a ton of people who use our platform to label medical data and biological data for their own papers and their own research, and then our only ask is
- 14:39
that they then contribute that data back to the community and make it open source. And so a lot of this data comes from like papers cited in Nature and stuff like that.
- 14:48
For natural images, there's not a between image pattern matching versus like distortion, tiger type of thing in ImageNet. For like a lot of the images in biology and medical images, a lot of the distortion are kind of not necessarily down to the pattern, but it's physical.
- 15:09
Even though a lot of those are not just kind of natural-
- 15:14
Yeah. So the dataset is kind of measuring the performance of like a bunch of different imaging modalities or predictive modalities, I guess. So, so I think the most interesting tract of the dataset is the few-shot tract.
- 15:29
So basically, we've constructed like, uh, canonical 10-shot splits. So we provide the model the class name, uh, annotator instructions on how to find that class, as well as 10 visual examples per class.
- 15:45
And if a model-- Basically, no model exists that can leverage those three things and get higher mAP than if you just deleted one of those like options. I th- I see that as one of the big shortcomings of vision-language models right now.
- 15:59
In terms of multi modality, there's like a more generous kind of thing like a model that is like can be more branded versus more specialist like a SAM using-
- 16:10
Yeah
- 16:11
... very similar like Grounding DINO.
- 16:16
Yeah.
- 16:16
So then what do you think about the like using like models in terms of these are two directions, which do you think is more important?
- 16:23
Yeah. So, so currently the specialists are by far the best.
- 16:27
Yes.
- 16:27
Uh, we benchmarked Grounding DINO specifically-
- 16:30
Okay
- 16:30
... both zero-shot and fine-tune. So zero-shot Grounding DINO got like 19 mAP average on RF100VL, which is like kinda good, kinda bad. So if you take like a YOLOv8 Nano and you train it from scratch on the 10-shot examples, which is not a lot of data obviously, it gets something like 25 mAP.
- 16:46
So like to, to be worse than fine-tuning a YOLO from scratch is, is sort of bad. But if you then fine-tune the Grounding DINO with Federated Loss, that's the highest performing model we have on the dataset.
- 16:57
However, that being said, like I think that the point of the dataset should be, hey, like you should be able to leverage these annotator instructions, the 10-shot examples, and the class names, and come up with something more accurate, which requires a generalist model.
- 17:12
But okay, I think I'm super over time. So yeah, thanks for the questions.
- 17:16
Yeah. Thanks a lot.
- 17:16
Cool. Thanks everyone. [outro music]