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

Allow YOLOv5 execution from arbitrary cwd #4954

Merged
merged 2 commits into from
Sep 28, 2021

Conversation

glenn-jocher
Copy link
Member

@glenn-jocher glenn-jocher commented Sep 28, 2021

πŸ› οΈ PR Summary

Made with ❀️ by Ultralytics Actions

🌟 Summary

Enhancements to file path handling for improved relative path support in YOLOv5 scripts.

πŸ“Š Key Changes

  • Default paths for weights, data, and project directories in detect.py, export.py, train.py, and val.py are now relative to the current working directory.
  • Conversion of source to string format for compatibility in detect.py.
  • Additional calls to check_yaml and check_file functions to validate YAML and file paths in train.py and val.py.

🎯 Purpose & Impact

  • These changes aim to reduce path errors when scripts are executed from different directories, increasing the robustness and user-friendliness of the codebase.
  • The updates standardize the way paths are handled across different scripts, making it easier to understand and maintain the code.
  • Users should experience fewer issues with file not found errors, especially when running the code in various environments or directory structures. πŸ› οΈπŸ“

@glenn-jocher glenn-jocher merged commit 4e04cb0 into master Sep 28, 2021
@glenn-jocher glenn-jocher deleted the update/runnable_elsewhere branch September 28, 2021 00:40
CesarBazanAV pushed a commit to CesarBazanAV/yolov5 that referenced this pull request Sep 29, 2021
* Allow YOLOv5 execution from arbitrary `cwd`

* Fix str bugs
BjarneKuehl pushed a commit to fhkiel-mlaip/yolov5 that referenced this pull request Aug 26, 2022
* Allow YOLOv5 execution from arbitrary `cwd`

* Fix str bugs
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

Successfully merging this pull request may close these issues.

None yet

1 participant