Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Documentation for model class properties #69

Open
sstainba opened this issue Jul 26, 2022 · 2 comments
Open

Documentation for model class properties #69

sstainba opened this issue Jul 26, 2022 · 2 comments

Comments

@sstainba
Copy link

For those of us who are newer to this, could you provide some more documentation on the YoloModel class and how the properties we need to override relate to our model? Perhaps show an example input/output tensor and then which values to use for which properties?

Specifically, the Dimensions, Strides, Anchors, Shapes and Confidence values.

@Red007Master
Copy link

Red007Master commented Aug 19, 2022

For those of us who are newer to this, could you provide some more documentation on the YoloModel class and how the properties we need to override relate to our model? Perhaps show an example input/output tensor and then which values to use for which properties?

Specifically, the Dimensions, Strides, Anchors, Shapes and Confidence values.

Well you need set dimension to {Lables.count}+5 to make it work. (all i can really help with) but most of values (Strides, Anchors, Shapes) related to training process (i believe so but sure about Anchors)
(I made fork with model save/load to/from json functionality if you need it: github.com/Red007Master/yolov5-net-SaveLoadModels)
If you have and questions i glad to help(if i can).

@sstainba
Copy link
Author

Yeah, I've learned that in the past week or so. The anchors come from the yolo config files but I'm still not sure about strides (which all seem to be base-2 with the same count as the anchors) or the shapes.

I do think this project needs a little love - specifically some abstraction into interfaces and maybe re-work to make it configurable at runtime instead of a generic needing a the inherited type. I might get around to that at some point.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants