model.tune does not respect the project directory when using ray[tune]

[ShaharJamshy]

Hi, I don't know if this is the right location to post this, but I would like to report a bug in model tuning. If this is not the correct way to report bugs please let me know what the best way would be, thank you!

When setting up a tuning run

model.tune(
       model.tune(
        use_ray=True,
        project='/path/to/project',
        ...

The tune data is saved under the root directory because the tuner code uses DEFAULT_CFG to determine the save directory instead of the arguments from the function call:

ultralytics/ultralytics/utils/tuner.py

Line 137 in ed25222

tune_dir = get_save_dir(DEFAULT_CFG, name="tune").resolve() # must be absolute dir

[UltralyticsAssistant]

👋 Hello @ShaharJamshy, thank you for bringing this to our attention 🚀! It seems like you might have encountered an issue with model tuning when using Ray. We suggest checking out the Docs for additional guidance and to see if similar issues have been addressed.

If this is a 🐛 Bug Report, could you please provide a minimum reproducible example to help us investigate further? This would greatly assist us in debugging the issue.

In the meantime, ensure that you've upgraded to the latest ultralytics package, as issues are sometimes resolved in newer releases. You can do so with:

pip install -U ultralytics

If this is a feature request ❓ or requires deeper technical engagement, feel free to supply more context or details. You can also join our dynamic community discussions over at Discord 🎧, Discourse, or Subreddit to interact with other users and experts.

Our development team is continuously ensuring all systems are operational, as shown in the status badge below. You can trust that an Ultralytics engineer will look into this shortly!

Status

This is an automated response, but an Ultralytics engineer will assist soon to help resolve your issue. Thank you for your patience and collaboration!

[glenn-jocher]

@ShaharJamshy thank you for reporting this issue. The best way to report bugs is through the GitHub Issues page for the repository. This allows us to track and address the problem effectively. Please feel free to open an issue there with the details you've provided.

[ShaharJamshy]

Thanks for the quick reply @glenn-jocher issue reported:
#17473

[glenn-jocher]

@ShaharJamshy thank you for reporting the issue. We'll review it and address it as soon as possible.