You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
trial_name_creator and trial_dirname_creator are removed from ray tune in 2.0. It would be great if we can have them back.
Use case
Our use case wrap ray tune underneath and we will write artifacts along with ray tune artifacts in the trainable. We would like to write both ray tune and our own artifacts at the same location. With trial_name_creator and trial_dirname_creator, it's easier to do so
The text was updated successfully, but these errors were encountered:
We're looking to add these utilities to the TuneConfig, but I wanted to ask if there were any additional functionality/improvements you would want from this API? Is it possible to share some more details about your use case?
In particular, is it useful to have the flexibility of constructing the name/dirname from the entire Trial object, or would it be clearer to only expose certain Trial attributes such as trainable_name, trial_id, and config? For example: trial_name_creator=lambda trainable_name, trial_id, config: f"{trainable_name}_{trial_id}"?
For my use case, the ability to control trial name and trial dirname is enough. Hoewver, as a developer, I would always want more api exposed. Guess it's your choice on what's easier to maintain
Description
trial_name_creator
andtrial_dirname_creator
are removed from ray tune in 2.0. It would be great if we can have them back.Use case
Our use case wrap ray tune underneath and we will write artifacts along with ray tune artifacts in the trainable. We would like to write both ray tune and our own artifacts at the same location. With
trial_name_creator
andtrial_dirname_creator
, it's easier to do soThe text was updated successfully, but these errors were encountered: