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
Copy file name to clipboardExpand all lines: CONTRIBUTING.md
+4Lines changed: 4 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,3 +7,7 @@ Generally we encourage people to become MLCommons members if they wish to contri
7
7
Regardless of whether you are a member, your organization (or you as an individual contributor) needs to sign the MLCommons Contributor License Agreement (CLA). Please submit your GitHub username to the [MLCommons Subscription form](https://mlcommons.org/community/subscribe/) to start that process.
8
8
9
9
MLCommons project work is tracked with issue trackers and pull requests. Modify the project in your own fork and issue a pull request once you want other developers to take a look at what you have done and discuss the proposed changes. Ensure that cla-bot and other checks pass for your pull requests.
10
+
11
+
## Scoring code
12
+
13
+
The leaderboard scoring code lives in [`scoring/`](./scoring/). See the [Scoring section of the README](./README.md#scoring) for how to install it and regenerate the leaderboard. Changes to `scoring/` are linted and unit-tested by the `Scoring Tests` GitHub Actions workflow.
Copy file name to clipboardExpand all lines: README.md
+61Lines changed: 61 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -58,6 +58,67 @@ To submit your algorithm for evaluation on the AlgoPerf leaderboard, please foll
58
58
2.**Create a Pull Request:** Fork this repository, create a new branch and add your submission code to a new folder within either `submissions/external_tuning/` or `submissions/self_tuning`. Open a pull request (PR) to the `evaluation` branch of this repository. Make sure to fill out the PR template asking for information such as submission name, authors, affiliations, etc.
59
59
3.**PR Review and Evaluation:** The AlgoPerf working group will review your PR. Based on our available resources and the perceived potential of the method, it will be selected for a free evaluation and merged into the `evaluation` branch. The working group will run your submission on all workloads and push the results, as well as the updated leaderboard, to the `main`branch.
60
60
61
+
## Scoring
62
+
63
+
The code that computes this leaderboard lives in [`scoring/`](./scoring/). Given a
64
+
directory of submission logs (such as those under [`previous_leaderboards/`](./previous_leaderboards/)),
65
+
it computes the performance profiles, time-to-target, AlgoPerf benchmark scores, and
66
+
speedups used in the tables above. This code was moved here from the
67
+
[`scoring/` directory of the algorithmic-efficiency repository](https://github.com/mlcommons/algorithmic-efficiency)
68
+
so that the repository that hosts the leaderboard also owns the code that produces it.
69
+
70
+
### Installation
71
+
72
+
The scoring code is self-contained: the per-workload target metrics, target
73
+
values, and step hints it needs are vendored in
74
+
[`scoring/workload_targets.json`](./scoring/workload_targets.json), so it
75
+
requires neither the `algoperf` package nor JAX/PyTorch/TensorFlow — just a
76
+
small numerical/plotting stack. As with the benchmark itself, set up a fresh
77
+
Python (>=3.11) environment, e.g. via `conda` or `virtualenv`:
0 commit comments