Proposal
I propose allowing users to provide an (optional) custom ProgressReporter while using Ray integration for hyperparameter tuning.
Motivation
Right now, the Ray integration defaults to the standard CLIReporter, which often displays metrics that aren’t particularly relevant or at the desired frequency. Similar to how we allow users to specify a --cfg_class (e.g., CartpoleTheiaJobCfg), I suggest we let them optionally provide a custom ProgressReporter class (that goes to the RunConfig as an argument). If none is provided, we can fall back to the default.
Additional context
Discussed briefly in #2847. I will go ahead and open the PR.
Checklist
Acceptance Criteria
Add the criteria for which this task is considered done. If not known at issue creation time, you can add this once the issue is assigned.
Proposal
I propose allowing users to provide an (optional) custom
ProgressReporterwhile using Ray integration for hyperparameter tuning.Motivation
Right now, the Ray integration defaults to the standard
CLIReporter, which often displays metrics that aren’t particularly relevant or at the desired frequency. Similar to how we allow users to specify a --cfg_class (e.g.,CartpoleTheiaJobCfg), I suggest we let them optionally provide a customProgressReporterclass (that goes to theRunConfigas an argument). If none is provided, we can fall back to the default.Additional context
Discussed briefly in #2847. I will go ahead and open the PR.
Checklist
Acceptance Criteria
Add the criteria for which this task is considered done. If not known at issue creation time, you can add this once the issue is assigned.
ProgressReporteris added