roboflow-100-benchmark VS sahi

> Their SKILL tool involves a set of algorithms that make the process go much faster, they said, because the agents learn at the same time in parallel. Their research showed if 102 agents each learn one task and then share, the amount of time needed is reduced by a factor of 101.5 after accounting for the necessary communications and knowledge consolidation among agents.

This is a really interesting idea. It's like the reverse of knowledge distillation (which I've been thinking about a lot[1]) where you have one giant model that knows a lot about a lot & you use that model to train smaller, faster models that know a lot about a little.

Instead, you if you could train a lot of models that know a lot about a little (which is a lot less computationally intensive because the problem space is so confined) and combine them into a generalized model, that'd be hugely beneficial.

Unfortunately, after a bit of digging into the paper & Github repo[2], this doesn't seem to be what's happening at all.

> The code will learn 102 small and separte heads(either a linear head or a linear head with a task bias) for each tasks respectively in order. This step can be parallized on multiple GPUS with one task per GPU. The heads will be saved in the weight folder. After that, the code will learn a task mapper(Either using GMMC or Mahalanobis) to distinguish image task-wisely. Then, all images will be evaluated in the same time without a task label.

So the knowledge isn't being combined (and the agents aren't learning from each other) into a generalized model. They're just training a bunch of independent models for specific tasks & adding a model-selection step that maps an image to the most relevant "expert". My guess is you could do the same thing using CLIP vectors as the routing method to supervised models trained on specific datasets (we found that datasets largely live in distinct regions of CLIP-space[3]).

[1] https://github.com/autodistill/autodistill

[2] https://github.com/gyhandy/Shared-Knowledge-Lifelong-Learnin...

[3] https://www.rf100.org

I'm Jacob, one of the authors of Roboflow 100, A Rich Multi-Domain Object Detection Benchmark, and I am excited to share our work with the community. In object detection, researchers are benchmarking their models on primarily COCO, and in many ways, it seems like a lot of these models are getting close to a saturation point. In practice, everyone is taking these models and finetuning them on their own custom dataset domains, which may vary from tagging swimming pools from Google Maps, to identifying defects in cell phones on an industrial line. We did some work to collect a representative benchmark of these custom domain problems by selecting from over 100,000 public projects on Roboflow Universe into 100 semantically diverse object detection datasets. Our benchmark comprises of 224,714 images, 11,170 labeling hourse, and 829 classes from the community for benchmarking on novel tasks. We also tried out the benchmark on a few popular models - comparing YOLOv5, YOLOv7, and the zero shot capabilities of GLIP. Use the benchmark here: https://github.com/roboflow-ai/roboflow-100-benchmark Paper link here: https://arxiv.org/pdf/2211.13523.pdf Or simply learn more here: https://www.rf100.org/ An immense thanks to the community, like this one, for making it possible to make this benchmark - we hope it moves the field forward! I'm around for any questions!

Or simply learn more: https://www.rf100.org/

github repository: https://github.com/roboflow-ai/roboflow-100-benchmark blogpost: https://blog.roboflow.com/roboflow-100/ arXiv paper: https://arxiv.org/abs/2211.13523

Github: https://github.com/roboflow-ai/roboflow-100-benchmark

At Roboflow, we've seen users fine-tune hundreds of thousands of computer vision models on custom datasets.

We observed that there's a huge disconnect between the types of tasks people are actually trying to perform in the wild and the types of datasets researchers are benchmarking their models on.

Datasets like MS COCO (with hundreds of thousands of images of common objects) are often used in research to compare models' performance, but then those models are used to find galaxies, look at microscope images, or detect manufacturing defects in the wild (often trained on small datasets containing only a few hundred examples). This leads to big discrepancies in models' stated and real-world performance.

We set out to tackle this problem by creating a new set of datasets that mirror many of the same types of challenges that models will face in the real world. We compiled 100 datasets from our community spanning a wide range of domains, subjects, and sizes.

We've benchmarked a couple of models (YOLOv5, YOLOv7, and GLIP) to start, but could use your help measuring the performance of others on this benchmark (check the GitHub for starter scripts showing how to pull the dataset, fine-tune models, and evaluate). We're very interested to learn which models do best in which real-world scenarios & to give researchers a new tool to make their models more useful for solving real-world problems.

An alternative to this is to leverage existing object detection, apply the model to patches or slices of fixed size in our image, and then stitch the results together. This is the idea behind Slicing-Aided Hyper Inference!

Hi All, I am trying to detect defects in the images using YOLOv8where some of the classes (defectType1, defectType2) have very small bounding boxes and some of them have large bounding boxes associated with the, (defectType3, defectType4). Also, real-time operation is desired (at least 5Hz on Jetson Xavier) What I have done till now: I am primarily trying to use the SAHI technique (Slicing Aided Hyper Inference)

I am using the default YOLOv5m6 model here with sahi/yolov5 library for my object detection project. I want to change just some of labels - for example when YOLO detects a human, I want it to label the human as "threat", not "person". Is there any way I can do it just changing some code, or I should train the model from scratch by just changing labels?

I need to execute this model https://github.com/obss/sahi upon an HTTP request. I will need between 32GB and 128GB of RAM (depending on the request). Also, I will only receive this request once or twice a week (they are not predefined dates). Each process may take a few hours.

https://github.com/obss/sahi should do the job

I think you have multiple options: why run inference on this large resolution? Why not run on 1024x512 or smaller. Use a smaller model which uses less memory, eg enet, erfnet, bisenet etc. Otherwise, patchbased inference is the way to go, there is a nice library, but also easy to implement yourself: https://github.com/obss/sahi

i have the EXACT thing ! the libs github!

Good idea. I haven’t looked too closely yet at the “hard” datasets.

We originally considered “fixing” the labels on these datasets by hand, but ultimately decided that label error is one of the challenges “real world” datasets have that models should work to become more robust against. There is some selection bias in that we did make sure that the datasets we chose passed the eye test (in other words, it looked like the user spent a considerable amount of time annotating & a sample of the images looked like they labeled some object of interest).

For aerial images in particular my guess would be that these models suffer from the “small object problem”[1] where the subjects are tiny compared to the size of the image. Trying a sliding window based approach like SAHI[2] on them would probably produce much better results (at the expense of much lower inference speed).

[1] https://blog.roboflow.com/detect-small-objects/

[2] https://github.com/obss/sahi

I am not very experienced, but do I understand that the problem is the size of the image? If so, have you heard of sahi

Try slicing and yolov4. https://github.com/obss/sahi