-
Notifications
You must be signed in to change notification settings - Fork 8
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
issue about the precision #14
Comments
Hello! How can I use the train.py code? I am now receiving the following error: What are the input parameters of train.py? |
obviously you need to check your dataset
…---Original---
From: "zihaozhang9"<notifications@github.com>
Date: Wed, Oct 23, 2019 22:14 PM
To: "erikguo/yolov3"<yolov3@noreply.github.com>;
Cc: "Asong"<1113461781@qq.com>;"Author"<author@noreply.github.com>;
Subject: Re: [erikguo/yolov3] issue about the precision (#14)
Hello! How can I use the train.py code? I am now receiving the following error:
AssertionError: No labels found. Recommend correcting image and label paths.
What are the input parameters of train.py?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
Finally I solved this problem by using "--evolve " in the training process to find out the best heper-parameters. |
Have you resolved your problem? |
I am training in yolov3.weights model with my own single class data. F1 score increased to 0.88 in the first 50 epochs but now it is constant for all the next epochs with e-5 learning rate. |
Hi, erikguo,Thanks for your excellent job!
I trained the yolov3-spp model on coco dataset, but got really bad performance, whose precision is really low but the recall is very high. One sample of test result is shown below.
I referenced some issue such as #2 , #295 , #188 and #71, and I modify the hypermeter "iou_t" but the mAP drop a lot, so did you trained the model in public dataset such as coco? How can you balance betweem the precision and recall? Thank you!
The text was updated successfully, but these errors were encountered: