LinasKo

Hi @illian01, @Griffin-Sullivan, Having had a few conversations and looking around, we've decided to keep the current method. Prepending the 0 and 1 for precision and recall seems to be...

Hey @onuralpszr :wave: That looks really good. I'm very fond of having validators, especially if they're nice and encapsulated like that. Plus, the structure is pretty much like `Detections` -...

In this case, I only mean the new `Keypoints` module. `Detections` would remain as it currently is. And yes, no rush! :)

As you can see, in these tests it only helped the Ultralytics case. Known insufficiencies: * ~~Inference 1 model is fit for vehicle detection but is tested on an image...

Ready for review. Tests in aforementioned Colab: https://colab.research.google.com/drive/1j85QErM74VCSLADoGliM296q4GFUdnGM?usp=sharing It's safe to do 'Run All', though it will ask for Roboflow auth midway and HF token at the end. The main...

Ah, force-pushing a revert to `develop` closes the PR. Makes sense, and is fine. New changes: https://github.com/roboflow/supervision/pull/1239

You can find examples of the new and old function calls in [this Colab](https://colab.research.google.com/drive/1mYNfB__p6CjmJw2wDv0ruG7smiGAvMbY?usp=sharing)

Hi @shaddu 👋 That's an analysis we vitally needed. Thank you very much! `from_tensors` was a typo and I've now fixed it. I very much appreciate you clarifying it before...

I've assigned the ticket to you. Let us know how it goes! The assumption is true, however there's some flexibility - `Detections.data` allows you to include additional data from the...

Hi @onuralpszr, @jeslinpjames, Apologies for the delay on our part. Despite it being merged, I wanted to look at the code now.