My6.0

[sunstricken]

🛠️ PR Summary

_{Made with ❤️ by Ultralytics Actions}

🌟 Summary

This PR updates default paths, modifies dependencies, and adjusts training parameters to better align with specific user setups and requirements.

📊 Key Changes

• Default Paths: Updated default paths for weights, datasets, and configurations to custom local directories.
• Dependencies: Changed dependency versions in requirements.txt to fixed versions for better reproducibility.
• Training Parameters: Adjusted default training epochs (300 → 150) and batch size (16 → 1).
• Device Default: Set the default CUDA device to 0 instead of leaving it blank.

🎯 Purpose & Impact

• Improved Customization: Tailors the code to specific user environments, making it easier for users with similar setups to get started.
• Reproducibility: Fixed dependency versions ensure consistent behavior across environments.
• Resource Optimization: Lowered batch size and epochs make the training process more accessible for users with limited hardware resources.
• Ease of Use: Setting a default CUDA device simplifies the setup for GPU-based training.

🚀 These changes enhance usability and reliability for users with custom setups or limited resources.

[github-actions]

Thank you for your submission, we really appreciate it. Like many open-source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution. You can sign the CLA by just posting a Pull Request Comment same as the below format.

---

I have read the CLA Document and I sign the CLA

---

1 out of 2 committers have signed the CLA.
✅ (UltralyticsAssistant)[https://github.com/UltralyticsAssistant]
❌ @sunstricken
_{You can retrigger this bot by commenting recheck in this Pull Request. Posted by the CLA Assistant Lite bot.}

[UltralyticsAssistant]

👋 Hello @sunstricken, thank you for submitting this ultralytics/yolov5 🚀 PR! We greatly appreciate your contribution. To help ensure a seamless review and integration process, please review the checklist below:

• ✅ Define a Purpose: Clearly explain the purpose of your changes in the PR description. The provided summary and key changes look great! 🎉 If applicable, link to any relevant issues for additional context.
• ✅ Synchronize with Source: Verify that your PR is up-to-date with the main branch of ultralytics/yolov5. If it's outdated, you can update it by clicking the 'Update branch' button or running git pull and git merge main locally.
• ✅ Ensure CI Checks Pass: Confirm that all Continuous Integration (CI) checks are successful. You can find more details about our CI process in the Ultralytics CI Guide. If any checks fail, please address them to avoid delays.
• ✅ Update Documentation: If your PR introduces or modifies features, ensure the relevant documentation is updated to reflect these changes.
• ✅ Add Tests: Include or update tests to cover your changes. Make sure all tests pass before final submission.
• ✅ Sign the CLA: If this is your first contribution, please sign our Contributor License Agreement (CLA) by commenting "I have read the CLA Document and I sign the CLA" in this PR thread.
• ✅ Minimize Changes: Keep your changes focused on the purpose of the PR. Limit modifications to the minimum necessary for the feature or fix. As Bruce Lee said: "It is not daily increase but daily decrease, hack away the unessential."

Additional Notes:

🔍 Regarding the .github template updates and other path adjustments in the PR, please ensure these changes align with the intended customization goals without affecting existing workflows.
📄 If this PR includes modifications to the README or CONTRIBUTING guides, double-check that all formatting and links render correctly.

For further guidance, please refer to our Contributing Guide. If you have any questions, feel free to drop a comment below, and an Ultralytics engineer will assist you shortly. Thank you for helping improve YOLOv5! 🚀✨