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

Are --image-weights and DDP training still incompatible? #11037

Closed
1 task done
shenck0 opened this issue Feb 22, 2023 · 4 comments
Closed
1 task done

Are --image-weights and DDP training still incompatible? #11037

shenck0 opened this issue Feb 22, 2023 · 4 comments
Labels
question Further information is requested Stale

Comments

@shenck0
Copy link

shenck0 commented Feb 22, 2023

Search before asking

Question

In train.py, I found that the assert is made here:

    if LOCAL_RANK != -1:
        msg = 'is not compatible with YOLOv5 Multi-GPU DDP training'
        assert not opt.image_weights, f'--image-weights {msg}'      # <----- this assert
        assert not opt.evolve, f'--evolve {msg}'

This assert was added by #3275 , and according to #4579, --image-weights can be use with DDP training.
I comment out this assert line and found dataset.indices modified at every epoch beginning can be broadcast to other processes correctly.
Are --image-weights and DDP training still incompatible now?

Additional

No response

@shenck0 shenck0 added the question Further information is requested label Feb 22, 2023
@github-actions
Copy link
Contributor

github-actions bot commented Feb 22, 2023

👋 Hello @shenck0, thank you for your interest in YOLOv5 🚀! 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 a minimum reproducible example to help us debug it.

If this is a custom training ❓ Question, please provide as much information as possible, including dataset image examples and training logs, and verify you are following our Tips for Best Training Results.

Requirements

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

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

Environments

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

Status

YOLOv5 CI

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

Introducing YOLOv8 🚀

We're excited to announce the launch of our latest state-of-the-art (SOTA) object detection model for 2023 - YOLOv8 🚀!

Designed to be fast, accurate, and easy to use, YOLOv8 is an ideal choice for a wide range of object detection, image segmentation and image classification tasks. With YOLOv8, you'll be able to quickly and accurately detect objects in real-time, streamline your workflows, and achieve new levels of accuracy in your projects.

Check out our YOLOv8 Docs for details and get started with:

pip install ultralytics

@github-actions
Copy link
Contributor

github-actions bot commented Mar 25, 2023

👋 Hello, this issue has been automatically marked as stale because it has not had recent activity. Please note it will be closed if no further activity occurs.

Access additional YOLOv5 🚀 resources:

Access additional Ultralytics ⚡ resources:

Feel free to inform us of any other issues you discover or feature requests that come to mind in the future. Pull Requests (PRs) are also always welcomed!

Thank you for your contributions to YOLOv5 🚀 and Vision AI ⭐!

@github-actions github-actions bot added the Stale label Mar 25, 2023
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Apr 4, 2023
@ztyree42
Copy link

ztyree42 commented Apr 6, 2023

Bumping because the question was not answered. It appears that DDP and --image-weights run fine together but is there still some sort of foot-gun present in their interaction and if so what is it?

@glenn-jocher
Copy link
Member

@shenck0, I apologize for the confusion. You are correct, based on this PR as and as of the current implementation, there are no known issues or incompatibilities with using DDP and --image-weights together. Previously, the assert checked that --image-weights were not present when using DDP in older implementation, but it has since been updated.

Thank you for bringing this to our attention and please let me know if you have any further questions or concerns.

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
Projects
None yet
Development

No branches or pull requests

3 participants