MagnificentSeaurchin79 you can delay it with:task.set_resource_monitor_iteration_timeout(seconds_from_start=1800)
It reverts back, but it cannot "delete" the last reported iteration value.
Make sense ?
not according to the logs:
info ClearML Monitor: Reporting detected, reverting back to iteration based reporting
Yes, but I "think" it does not update back the "last iteration"
very possible yes..but doesn't it fallback to iteration =epoch then after?
I understand that it uses time in seconds when there is no report being logged..but, it has already logged three times..
Hmm could it be the reporting started 3 min after the Task started ?
I understand that it uses time in seconds when there is no report being logged..but, it has already logged three times..