From 285f4e17bb5e76d09a9b54d4711c288cd18309fa Mon Sep 17 00:00:00 2001 From: Shriya Palsamudram Date: Fri, 15 Nov 2024 08:54:11 -0800 Subject: [PATCH] Formalize rule regarding benchmark lifecycle Signed-off-by: Shriya Palsamudram --- training_rules.adoc | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/training_rules.adoc b/training_rules.adoc index f95b586..b9011a8 100644 --- a/training_rules.adoc +++ b/training_rules.adoc @@ -93,6 +93,14 @@ The benchmark suite consists of the benchmarks shown in the following table. |=== +### Benchmark Lifecycle + +Developing high-quality benchmarks requires significant effort, computational resources, and commitment. Therefore, each benchmark is expected to remain part of the benchmark suite for a minimum of two years or four submission rounds, whichever comes first. + +A benchmark may be considered for early retirement due to reasons such as, but not limited to, low industry adoption. Early retirement requests will be reviewed by the Training working group, followed by a formal vote to determine the benchmark's status. + +### Benchmark reference implementation + MLCommons provides a reference implementation of each benchmark, which includes the following elements: Code that implements the model in a framework.