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

how to include our own model in the model list #2270

Closed
Ironman1508 opened this issue Oct 7, 2020 · 2 comments · Fixed by #3124
Closed

how to include our own model in the model list #2270

Ironman1508 opened this issue Oct 7, 2020 · 2 comments · Fixed by #3124
Assignees
Labels
documentation Documentation should be updated duplicate This issue or pull request already exists

Comments

@Ironman1508
Copy link

Hello, Can someone share the process/steps to include our own like yolov3, yolov5, or faster rcnn model into the Model list for automatic/ semi automatic annotation. I wanna add my own model which i have trained on my own dataset.

@nmanovic nmanovic self-assigned this Oct 8, 2020
@nmanovic nmanovic added this to the 1.2.0-release milestone Oct 8, 2020
@nmanovic nmanovic added documentation Documentation should be updated duplicate This issue or pull request already exists labels Oct 8, 2020
@nmanovic
Copy link
Contributor

nmanovic commented Oct 8, 2020

@Ironman1508 , we are working on the tutorial. For now you have to look at examples inside the repository: https://github.com/openvinotoolkit/cvat/tree/develop/serverless

@nmanovic nmanovic modified the milestones: 1.2.0-release, 1.3.0-alpha Jan 8, 2021
@nmanovic nmanovic removed this from the 1.3.0-alpha milestone Mar 8, 2021
@valavanisleonidas
Copy link

Is it added in the tutorial ? I haven't found it anywhere

@nmanovic nmanovic added this to the Backlog milestone Mar 9, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Documentation should be updated duplicate This issue or pull request already exists
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants