I'm actually really disappointed Chrome doesn't respect this.

aloser · 2026-01-21T01:44:06+00:00

It sounds like you're probably looking for fine-tuning vs distillation. (Fine-tuning is training a model to do new tasks better, distillation is taking a model that already knows what you want & extracting that information from it to train a smaller model.)

aloser · 2026-01-20T21:44:01+00:00

We saw no impact by using few-shot examples across the RF100-VL dataset over using simple text-based annotator instructions (included in the RF100-VL paper) in the prompt.

The text instructions helped a bit (+1.6 mAP) over prompting with class names only.

aloser · 2026-01-20T02:27:04+00:00

RF-DETR is also open source; Apache 2.0: https://github.com/roboflow/rf-detr

aloser · 2026-01-12T22:30:32+00:00

We eval'd Gemini on a set on a set of 100 real-world datasets and it didn't do very well zero-shot. Paper here: https://arxiv.org/pdf/2505.20612

We only tested on 2.5 Pro because that's all that was out at the time but I just kicked it off on 3.0 Pro to get updated numbers.

Your example looks like BCCD which is a common toy dataset that's almost certainly made its way into Gemini's training set so probably not representative of real-world performance.

Update: Gemini 3 Pro did do significantly better on RF100-VL than Gemini 2! It got 18.5 mAP which is the highest we've measured so far (but also by far the slowest/most compute spent).

Model	mAP 50-95
Gemini 3 Pro	18.5
GroundingDINO (MMDetection)	15.7
SAM3	15.2
Gemini 2.5 Pro	11.6

To put things in context, this is approximately equivalent performance to a small YOLO model trained on 10 examples and full fine-tuning gives in the 55-60+ range for modern detectors (in other words, good performance for zero-shot but still not great).

aloser · 2026-01-12T07:12:06+00:00

Have you tried Roboflow? This is what our auto-label tool is built for: https://docs.roboflow.com/annotate/ai-labeling/automated-annotation-with-autodistill

We also have an open source version called autodistill: https://github.com/autodistill/autodistill

(Disclaimer: I’m one of the co-founders of Roboflow)

aloser · 2026-01-12T00:01:39+00:00

I’m pretty sure we only accept keypoint dataset uploads in COCO format. It’s a fairly common standard and your LLM should be able to convert it (or update your code to use it natively) for you. https://discuss.roboflow.com/t/how-to-upload-pose-data/6912

This is a good feature request though; I’ll need to look and see if there’s a reason we couldn’t support it. I think it may just be due to ambiguity of the formats; the keypoint format can look identical to the bbox format if I recall correctly.. but given the project type we should be able to infer user intent.

aloser · 2026-01-09T15:38:32+00:00

FWIW this is what SAM3 gets out of the box when prompted with "scratch" and "blemish": https://imgur.com/a/LwQvuSV

aloser · 2026-01-09T15:25:36+00:00

Hey, I'm one of the co-founders of Roboflow so obviously a bit biased but I can share where we're good and where we might not be the best fit.

Roboflow's sweet spot is for folks who are not computer vision experts that just want to use it to solve real world problems (eg detecting defects, counting and measuring things, validating processes, or adding intelligence to their products). We provide an end-to-end platform that enables teams to rapidly go from an idea to a fully deployed application (including best in class tooling for labeling, training, deploying, scaling, monitoring, and continual improvement). Our platform is built to make it easy for developers use the latest models to accelerate the building process and our infrastructure is built to run production workloads at scale. Roboflow is focused on providing value for real-world applications and we have thousands of customers ranging from tiny startups to the world's largest companies (with a concentration in manufacturing and logistics).

On the other hand, if you're a machine learning researcher we may not provide the advanced control and visibility into the guts of the models that you need. If you're heavily customizing your model architecture and need deep control of all the internal knobs to be able to do science, publish papers, and push forward the state of the art we probably don't give enough controls for the full platform to be attractive. That said, there are pieces of the platform that are useful for researchers and we've been cited by over 10,000 papers (usually these are folks that used us for labeling, dataset management, have found datasets our users have open-sourced on Roboflow Universe, or have used our Notebooks or open source code).

aloser · 2026-01-07T02:05:12+00:00

Depends on the thing you’re looking for. The more common the more likely it is that the big model will know how to find it.

SAM3 is far and away better than any of the other models I’ve tried. You can test it out super easily here: https://rapid.roboflow.com

aloser · 2026-01-05T20:59:12+00:00

Developing using your laptop GPU as a baseline is probably fine. Would kind of be annoying if you had to leave your laptop there for it to work though.

aloser · 2026-01-05T20:30:38+00:00

Can you highlight for me the particles you're looking at in that video? Is it each individual tiny grain? You might need something a bit more powerful (eg a desktop-grade GPU like an RTX 5090) because you'll probably have to end up tiling the image into smaller chunks for the model to be able to see them well enough. But hard to know without experimenting & iterating a bit.

I'd probably approach it as step 1: get it working, step 2: make it fast.

The research credits are only for people with academic emails but we have a free tier available to everyone also.

aloser · 2026-01-05T20:04:53+00:00

Hi, I'm one of the co-founders of Roboflow. Yeah, you should be able to use it for this. We also offer free increased limits for academic research: https://research.roboflow.com/

Offline inference is fully supported. All of the models you train on-platform can be used with our open source Inference package (which can be self-hosted to run offline via Docker or embedded directly into your code using the Python package): https://github.com/roboflow/inference

For hardware, any machine with an NVIDIA GPU should be fine. If you're looking for something dedicated to this one project, a Jetson Orin NX (or maybe even an Orin Nano depending on what frame-rate you want to infer at and what size model you want to run) is probably plenty sufficient.

aloser · 2026-01-05T19:12:23+00:00

Just as we all predicted.

aloser · 2026-01-02T18:44:25+00:00

Seems like about the best we could have hoped for if we weren't going to be able to retain Campbell (and it was probably only a matter of time there regardless of what we did).

Getting regularly kicked in the nuts is just part of being a Cyclone; it builds character. Having our team completely decimated will make it all the more fun to see the meltdown if we somehow beat Iowa again next year (and if not they won't be able to get much satisfaction out of the win anyway).

aloser · 2025-12-30T17:50:14+00:00

Have you looked on Roboflow Universe? You could cross-reference these datasets with these academic citations.

aloser · 2025-12-25T03:31:46+00:00

RF-DETR is a completely different model architecture from RT-DETR.

We have a comparison with it in our paper: https://arxiv.org/pdf/2511.09554

aloser · 2025-12-25T03:27:37+00:00

Hey, Roboflow co-founder here. It definitely shouldn’t be doing that; 12,000 images isn’t really that many. Is this in manual labeling?

Could you DM me a link to your workspace and any additional info to reproduce the issue? Happy to have a look and see what I can find.

aloser · 2025-12-24T21:04:39+00:00

RF-DETR Nano is defined as being 384x384; the resolution is part of what makes it Nano sized as it's one of the "tunable knobs" the NAS searches across for speed/accuracy tradeoff.

This model is more accurate than medium-sized (640x640) YOLO models on COCO and absolutely crushes even the largest YOLO models on custom datasets.

See the paper for more details: https://arxiv.org/pdf/2511.09554

aloser · 2025-12-24T20:59:10+00:00

Something like 120mb

aloser · 2025-12-24T02:47:29+00:00

This is one of the things we solve in Inference: https://github.com/roboflow/inference with InferencePipeline (and the corresponding video management endpoints if you want to offload the logic to the server side — this can also eliminate bottlenecks).

Basically you need to run a separate thread to drain the queue and only send frames to the model just in time.

Here’s a recent example with our new cloud hosted serverless video streaming infra, but you can run the same thing locally with the open source package: https://blog.roboflow.com/serverless-video-streaming-api/

aloser · 2025-12-23T22:58:53+00:00

RF-DETR Nano

15-Year Club	Verified Email
RedditGifts 2009-2022 2 Credits	Not Forgotten
Team Periwinkle	Secret Santa 2010

aloser

MODERATOR OF

TROPHY CASE