Closed khandriod closed 1 week ago
👋 Hello @khandriod, thank you for your interest in Ultralytics 🚀! We recommend visiting the Docs for guidance, where you can find many Python and CLI usage examples, along with answers to many common questions.
If this is a 🐛 Bug Report or environment setup issue, please provide a minimum reproducible example detailing your exact setup and steps to replicate. This will help ensure we can debug effectively.
It seems like your issue revolves around environment isolation and the way ultralytics
is resolving paths. To troubleshoot:
ultralytics
installation.PYTHONPATH
configuration to ensure paths are correctly aligned with your current directory.python -c "import ultralytics; print(ultralytics.__version__, ultralytics.__file__)"
For real-time discussions and additional troubleshooting, we encourage you to join the Ultralytics community:
Ensure you're working with the latest ultralytics
version to minimize potential issues. Upgrade in your respective environments using:
pip install -U ultralytics
YOLO is highly versatile and can be used in the following verified setups (with dependencies like CUDA/CUDNN, Python, and PyTorch preinstalled):
If this badge is green, all Ultralytics CI tests are passing. CI tests cover all YOLO Modes and Tasks daily across various platforms.
This is an automated response to your issue, but rest assured, an Ultralytics engineer will assist you further as soon as possible. Thank you for your patience and understanding! 😊
Hello, I have solved the issue. The path to dataset in data.yaml should be relative not absolute. Thanks
It can be both absolute and relative. If it's relative, it will consider it relative to the datasets_dir in the settings, not your current working directory.
Thanks for reporting this issue and for your patience! A potential fix has now been merged via PR #18953. This PR improves clarity in dataset configuration by explicitly documenting how relative paths behave. Specifically:
path
field are resolved based on the default datasets_dir
.Huge thanks to the efforts of the PR author @Y-T-G and contributions from @glenn-jocher for addressing this!
To test if this update resolves your issue, you can:
pip install git+https://github.com/ultralytics/ultralytics.git@main
Your feedback would be incredibly valuable! Please let us know if this resolves the issue for you or if you're still experiencing any challenges. Thank you again for reporting this, and feel free to share any further feedback or suggestions. 🙏
Search before asking
Question
I have multiple Conda environments (e.g., yolov8, yolov11) with separate YOLO installations. However, when I activate an environment, it continues to reference code and settings from a previous default directory instead of the current project directory.
Example:
Environment yolov8 should reference /projects/yolov8/code Environment yolov11 should reference /projects/yolov11/code But both currently point to an older directory (e.g., /projects/yolov8/code).
What I’ve Tried/Expected:
Installed YOLO in each environment separately. Expected each environment to use its own local code/settings when activated.
Question: How do I configure each Conda environment to prioritize the current working directory for code and settings?
OS: Ubuntu 22.04 (WSL2)
I just found this setting.json file
I have fixed the runs folder but should I have to set dataset and weights here ?
I have this setting.json file
Error form CLI