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

Early end #1408

Closed
lccui opened this issue Jul 24, 2020 · 5 comments
Closed

Early end #1408

lccui opened this issue Jul 24, 2020 · 5 comments
Labels
question Further information is requested Stale Stale and schedule for closing soon

Comments

@lccui
Copy link

lccui commented Jul 24, 2020

❔Question

python train.py --data data/custom.data --weights pretrained/yolov4.conv.137 --batch-size 8 --cfg cfg/yolov4.cfg --img-size 256
Namespace(adam=False, batch_size=8, bucket='', cache_images=False, cfg='cfg/ship-yolov4.cfg', data='data/4wship.data', device='', epochs=300, evolve=False, freeze_layers=False, img_size=[256], multi_scale=False, name='', nosave=False, notest=False, rect=False, resume=False, single_cls=False, weights='pretrained/yolov4.conv.137')
批注 2020-07-24 192238

Additional context

run:python train.py --data data/custom.data --weights pretrained/yolov3-spp.pt --batch-size 8 --cfg cfg/yolov3-spp.cfg --img-size 256
is OK,normal

@lccui lccui added the question Further information is requested label Jul 24, 2020
@github-actions
Copy link

github-actions bot commented Jul 24, 2020

Hello @lccui, thank you for your interest in our work! Ultralytics has open-sourced YOLOv5 at https://github.com/ultralytics/yolov5, featuring faster, lighter and more accurate object detection. YOLOv5 is recommended for all new projects.

To continue with this repo, please visit our Custom Training Tutorial to get started, and see our Google Colab Notebook, Docker Image, and GCP Quickstart Guide for example environments.

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 model or data training question, please note that Ultralytics does not provide free personal support. As a leader in vision ML and AI, we do offer professional consulting, from simple expert advice up to delivery of fully customized, end-to-end production solutions for our clients, such as:

  • Cloud-based AI systems operating on hundreds of HD video streams in realtime.
  • Edge AI integrated into custom iOS and Android apps for realtime 30 FPS video inference.
  • Custom data training, hyperparameter evolution, and model exportation to any destination.

For more information please visit https://www.ultralytics.com.

@lccui
Copy link
Author

lccui commented Jul 24, 2020

I already use open-sourced YOLOv5,but I still want to know why

@glenn-jocher
Copy link
Member

@lccui strongly recommend moving from yolov3 to yolov5, as training instabilities have been fixed there. See ultralytics/yolov5#471 (comment)

@glenn-jocher
Copy link
Member

glenn-jocher commented Jul 24, 2020

I'll reference my YOLOv5 comments here for the benefit of all the local YOLOv3 watchers.

The original yolo/darknet box equations have a serious flaw. Width and Height are completely unbounded as they are simply out=exp(in), which is dangerous, as it can lead to runaway gradients, instabilities, NaN losses and ultimately a complete loss of training. yolov3 suffers from this problem as well as yolov4.

For yolov5 I made sure to patch this error by sigmoiding all model outputs, while also ensuring that the centerpoint remained unchanged 1=fcn(0), so nominal zero outputs from the model would cause the nominal anchor size to be used. The current eqn constrains anchor multiples from a minimum of 0 to a maximum of 4, and the anchor-target matching has also been updated to be width-height multiple based, with a nominal upper threshold hyperparameter of 4.0.

The original thread is #168
image

Originally posted by @glenn-jocher in ultralytics/yolov5#471 (comment)

@github-actions
Copy link

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@github-actions github-actions bot added the Stale Stale and schedule for closing soon label Aug 24, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested Stale Stale and schedule for closing soon
Projects
None yet
Development

No branches or pull requests

2 participants