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

No best.pt after training #1893

Closed
mark375chen opened this issue Feb 3, 2022 · 4 comments
Closed

No best.pt after training #1893

mark375chen opened this issue Feb 3, 2022 · 4 comments

Comments

@mark375chen
Copy link

mark375chen commented Feb 3, 2022

@mark375chen detection can be run on any trained model, i.e. python detect.py path/to/best.pt

Originally posted by @glenn-jocher in #1570 (comment)

Training custom data:
After python train.py --img 320 --batch 32 --epochs 5 --data my_thingy.yaml --weights yolov3.pt, I get
image

ls -l in /weights gives me nothing. ie. There is no best.pt file.

I'm not sure why this happens.

@github-actions
Copy link

github-actions bot commented Feb 3, 2022

👋 Hello @mark375chen, thank you for your interest in YOLOv3 🚀! Please visit our ⭐️ Tutorials to get started, where you can find quickstart guides for simple tasks like Custom Data Training all the way to advanced concepts like Hyperparameter Evolution.

If this is a 🐛 Bug Report, please provide screenshots and minimum viable code to reproduce your issue, otherwise we can not help you.

If this is a custom training ❓ Question, please provide as much information as possible, including dataset images, training logs, screenshots, and a public link to online W&B logging if available.

For business inquiries or professional support requests please visit https://ultralytics.com or email Glenn Jocher at glenn.jocher@ultralytics.com.

Requirements

Python>=3.6.0 with all requirements.txt installed including PyTorch>=1.7. To get started:

$ git clone https://github.com/ultralytics/yolov3
$ cd yolov3
$ pip install -r requirements.txt

Environments

YOLOv3 may be run in any of the following up-to-date verified environments (with all dependencies including CUDA/CUDNN, Python and PyTorch preinstalled):

Status

CI CPU testing

If this badge is green, all YOLOv3 GitHub Actions Continuous Integration (CI) tests are currently passing. CI tests verify correct operation of YOLOv3 training (train.py), validation (val.py), inference (detect.py) and export (export.py) on MacOS, Windows, and Ubuntu every 24 hours and on every commit.

@glenn-jocher
Copy link
Member

glenn-jocher commented Feb 3, 2022

@mark375chen detection can be run on any arbitrary model: python detect.py --weights path/to/any_model.pt

@mark375chen
Copy link
Author

@glenn-jocher
Edited initial comment, sorry for the confusion.

I have ran python train.py --img 640 --batch 32 --epochs 2 --data my_thing.yaml --weights yolov3.pt

$ find . -type f -name "*.pt" gives:
./yolov3/yolov3.pt

I want to detect on the training with respect to /exp3 as an example. However, I don't have any .pt in any /exp.

@glenn-jocher
Copy link
Member

glenn-jocher commented Feb 3, 2022

@mark375chen 👋 hi, thanks for letting us know about this possible problem with YOLOv5 🚀. YOLOv3 trains correctly and saves weights as expected:

Screenshot 2022-02-03 at 19 20 07

We've created a few short guidelines below to help users provide what we need in order to get started investigating a possible problem.

How to create a Minimal, Reproducible Example

When asking a question, people will be better able to provide help if you provide code that they can easily understand and use to reproduce the problem. This is referred to by community members as creating a minimum reproducible example. Your code that reproduces the problem should be:

  • Minimal – Use as little code as possible to produce the problem
  • Complete – Provide all parts someone else needs to reproduce the problem
  • Reproducible – Test the code you're about to provide to make sure it reproduces the problem

For Ultralytics to provide assistance your code should also be:

  • Current – Verify that your code is up-to-date with GitHub master, and if necessary git pull or git clone a new copy to ensure your problem has not already been solved in master.
  • Unmodified – Your problem must be reproducible using official YOLOv5 code without changes. Ultralytics does not provide support for custom code ⚠️.

If you believe your problem meets all the above criteria, please close this issue and raise a new one using the 🐛 Bug Report template with a minimum reproducible example to help us better understand and diagnose your problem.

Thank you! 😃

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