policies

policies copied to clipboard

Experimental Tag for benchmarks

5

Agile tag is a way for MLPerf to stay agile & make early bets on upcoming hot benchmarks. It allows adopting viral benchmarks while also providing a way to update,...

nv-rborkar

Update withdrawal rules

1

Objective: Penalize submitters who participate in the private review period but do not contribute any result to the public table. Edit New objective: based on discussion in WG, spell out...

nv-rborkar

Update MLPerf_Compatibility_Table.adoc tiny

1

Update the compatibility table for tiny

peladodigital

Update MLPerf_Results_Messaging_Guidelines.adoc

1

Update trademark to registred trademark for MLPerf

peladodigital

Replace reference to "submitter working group" to Inference & Training.

1

The Submission Rules refers to the "submitters" working group which is now a non-existant working group (back when we had Submitters and Special Topics) prior to the refactor to Training...

bitfort

Update MLPerf_Compatibility_Table.adoc - Inference

1

Update MLPerf_Compatibility_Table.adoc - Inference

peladodigital

Remove host_processor_vcpu_count

1

Proposed fix for https://github.com/mlcommons/inference/issues/1631

szutenberg

Review chairs election update

1

Review chairs election update to follow directors election MLC rules

peladodigital

Address issue #122 according to Inf WG discussion

23

This also adds a definition of a Reproducible software component so that RDI does not become a venue for submissions that are not reproducible and can never be reproducible.

DilipSequeira

Clarify rules on Preview system

2

Note that this does not change the rule. This PR only clarifies the Preview HW rules by rewording since we found the current wording as confusing. If folks would like...

nv-ananjappa