ClearML's set_report_period's time is defined in minutes not seconds. (#9186)

* ClearML's set_report_period's time is defined in minutes not seconds. https://clear.ml/docs/latest/docs/references/sdk/hpo_optimization_hyperparameteroptimizer/#set_report_period set_report_period function takes in time in terms of minutes, not seconds. Signed-off-by: HighMans <42877729+HighMans@users.noreply.github.com> * [pre-commit.ci] auto fixes from pre-commit.com hooks for more information, see https://pre-commit.ciSigned-off-by: HighMans <42877729+HighMans@users.noreply.github.com> Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com> Co-authored-by: Glenn Jocher <glenn.jocher@ultralytics.com>

ClearML's set_report_period's time is defined in minutes not seconds. (#9186)
cf5d9cbc · HighMans · GitHub · e57275a2 · cf5d9cbc
--- a/utils/loggers/clearml/hpo.py
+++ b/utils/loggers/clearml/hpo.py
@@ -69,7 +69,7 @@ optimizer = HyperParameterOptimizer(
 )

 # report every 10 seconds, this is way too often, but we are testing here
-optimizer.set_report_period(10)
+optimizer.set_report_period(10 / 60)
 # You can also use the line below instead to run all the optimizer tasks locally, without using queues or agent
 # an_optimizer.start_locally(job_complete_callback=job_complete_callback)
 # set the time limit for the optimization process (2 hours)