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
Currently we use the word "benchmark" for both individual benchmarks of one model, and for the benchmark suite, or the app as a whole.
It would be easier to understand if we rename individual benchmarks to "tasks".
We already use this name in some places.
The text was updated successfully, but these errors were encountered:
We can either rename benchmark -> task or task -> benchmark since the 2 terms are used interchangeable here.
Actually, renaming task -> benchmark would be easier since it does not impact the backend code (all the backend settings currently use the term benchmark_setting and benchmark_id)
Currently we use the word "benchmark" for both individual benchmarks of one model, and for the benchmark suite, or the app as a whole.
It would be easier to understand if we rename individual benchmarks to "tasks".
We already use this name in some places.
The text was updated successfully, but these errors were encountered: