Mismatch between Maximum Runtime in the DOCS and `max_allowed_runtime_sec` in the code

[Niccolo-Ajroldi]

Description

The "maximum runtime" of this table differ from max_allowed_runtime_sec in the code.

Few examples below:

Criteo:

algorithmic-efficiency/algorithmic_efficiency/workloads/criteo1tb/workload.py

Line 96 in a1bff14

return 7703 # ~2 hours.

Deepspeech:

algorithmic-efficiency/algorithmic_efficiency/workloads/librispeech_deepspeech/librispeech_pytorch/workload.py

Line 84 in a1bff14

return 55_506 # ~15.4 hours

ViT:

algorithmic-efficiency/algorithmic_efficiency/workloads/imagenet_vit/workload.py

Line 84 in a1bff14

return 77_520 # ~22 hours

[priyakasimbeg]

Thanks for bringing this to our attention. The docs seem to be out of date. Will update them.
In the meantime please refer to the code as the source of truth.