You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Follow-up PR after
huggingface#1093 and especially
this thread
huggingface#1093 (comment).
I agree with @NielsRogge's point that `ultralytics` _is_ the library
name. Yolov8 or Yolov10 are "just" model names.
---
_originally from @merveenoyan
(huggingface#1093 (comment)
> there's no way of knowing which yolo version would it be because
there's no config file.
The solution I suggest in this PR is to use the repo tags instead. I
have checked and all 258 [ultralytics
models](https://huggingface.co/models?other=ultralytics) have a "yolovX"
tag.
~In parallel I suggest to remove the `yolov10` library since code
snippet is now correctly generated for them as well. I have checked and
[29 out of 63 yolov10
models](https://huggingface.co/models?other=yolov10) don't have the
`ultranalytics` tag so they'll loose the code snippet. If we agree on
this solution I'll open PRs on these repos and everything should be
good.~ See below: in the end, I kept `yolov10` but unified the code
snippet generation.
@merveenoyan@NielsRogge@pcuenca let me know what you think. Will this
definitely close the yolo/ultranalytics tags matter ?
**Note:** some models have multiple yolo tags (e.g.
https://huggingface.co/Ultralytics/YOLOv8 has v10, v8, v3, v5, v9). In
that case I suggest to only take the first one (v10 in this case). But
to be honest, this looks more like something to fix in the model's
metadata
[here](https://huggingface.co/Ultralytics/YOLOv8/blob/main/README.md?code=true#L13).
0 commit comments