Bounding box annotations and object orientation

This page summarizes the projects mentioned and recommended in the original post on /r/computervision

Our great sponsors
  • InfluxDB - Power Real-Time Data Analytics at Scale
  • WorkOS - The modern identity platform for B2B SaaS
  • SaaSHub - Software Alternatives and Reviews
  • darknet

    YOLOv4 / Scaled-YOLOv4 / YOLO - Neural Networks for Object Detection (Windows and Linux version of Darknet ) (by AlexeyAB)

    One thing I'd like to point out: YOLOv5 may not be what you think it is. Note that a company took the the YOLO name, released something called YOLOv5 just days (weeks?) after YOLOv4 was announced by AlexeyAB. In the end, YOLOv4 is both faster and more precise than YOLOv5. You can find some of the details on the YOLOv5 shenanigans here: https://github.com/AlexeyAB/darknet/issues/5920

  • Yet-Another-EfficientDet-Pytorch

    The pytorch re-implement of the official efficientdet with SOTA performance in real time and pretrained weights.

    However, there are papers on oriented object detectors (see https://arxiv.org/pdf/1911.07732.pdf) for example. In that paper, they do achieve better results using oriented bounding boxes. If you want to go down that route, I would suggest using the EfficientDet model, because the PyTorch code that you'll find for it is quite easy to understand and modify. For example, I've taken https://github.com/zylo117/Yet-Another-EfficientDet-Pytorch, and modified it to include a "thing-ness" logit, and this was pretty easy to do. Classic EfficientDet models only include logits (aka output neurons that get softmax-ed) for each class, and if any one of these class neurons is greater than 0.5, then it is considered "a thing". Anyway - that's digression, but my point is that I've thought about adding oriented box support to an EfficientDet model, and it didn't seem to be too hard, although I haven't actually done it. If I was to start now, I would probably go with https://github.com/rwightman/efficientdet-pytorch, since Ross Wightman's models are becoming a de-facto standard in the PyTorch world for all things image-related.

  • InfluxDB

    Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.

  • efficientdet-pytorch

    A PyTorch impl of EfficientDet faithful to the original Google impl w/ ported weights

    However, there are papers on oriented object detectors (see https://arxiv.org/pdf/1911.07732.pdf) for example. In that paper, they do achieve better results using oriented bounding boxes. If you want to go down that route, I would suggest using the EfficientDet model, because the PyTorch code that you'll find for it is quite easy to understand and modify. For example, I've taken https://github.com/zylo117/Yet-Another-EfficientDet-Pytorch, and modified it to include a "thing-ness" logit, and this was pretty easy to do. Classic EfficientDet models only include logits (aka output neurons that get softmax-ed) for each class, and if any one of these class neurons is greater than 0.5, then it is considered "a thing". Anyway - that's digression, but my point is that I've thought about adding oriented box support to an EfficientDet model, and it didn't seem to be too hard, although I haven't actually done it. If I was to start now, I would probably go with https://github.com/rwightman/efficientdet-pytorch, since Ross Wightman's models are becoming a de-facto standard in the PyTorch world for all things image-related.

NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a more popular project.

Suggest a related project

Related posts