Skip to content

Commit

Permalink
Formalize rule regarding benchmark lifecycle
Browse files Browse the repository at this point in the history
Address comment mlcommons#171 (comment)
  • Loading branch information
ShriyaPalsamudram committed Jul 18, 2024
1 parent d52a9c8 commit 76d67fa
Showing 1 changed file with 3 additions and 0 deletions.
3 changes: 3 additions & 0 deletions submission_rules.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -779,8 +779,11 @@ Otherwise, the committee will designate an investigator with no conflict of inte
2. The result-in-question is moved to open for noncompliance with the rules.
3. The result-in-question is removed due to intentional cheating.

## 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 relevant working group, followed by a formal vote to determine the benchmark's status.

## Appendices

Expand Down

0 comments on commit 76d67fa

Please sign in to comment.