mlcommons / mlcommons/science

Call for new benchmarks

Open
#51 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Jupyter Notebook
Stars
15
Forks
3
PR merge metrics
No merged PRs in 30d

Description

Call for new benchmarks

The goal is to develop, test, deploy and evaluate Machine Learning benchmarks on a wide range of computing platforms. These benchmarks will be a starting point for exploring new ML methods, they can be used for ranking computers and help towards a better understanding of the interaction between ML applications and the underlying hardware. The main components of each benchmark are the scientific value, dataset, implementation and documentation. Details on how to contribute a benchmark can be found in the Policy and Submission Rules documents.

In the current suite there are four benchmarks which are drawn from various scientific domains such as material, life and earth sciences. The benchmarks are written in Python and they use libraries such as TensorFlow and PyTorch. The datasets are coming from various sources which include meteorological satellites, scanning tunnelling microscopes, seismographs and DNA sequencers. The size of these datasets covers a range from tens to hundreds of GigaBytes.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reading policy.adoc and submit.adoc, then inspect the existing entries in benchmarks. A contribution would need a scientific value, dataset, implementation, and documentation, but this issue does not identify a specific benchmark or entry point to change.

Written by the indexing model from the issue text.

Assessment

Tech stack
python, pytorch, tensorflow
Domain
data, machine-learning, performance
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.