An optional faster Model M mode (design discussion first)

Open
#34 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
30/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
cpp
Domain
performance

Research direction

Start by examining how Model M currently ensures output matches its reference exactly. Before proposing code, discuss how to define and measure a published quality limit, how players would choose and identify the optional faster mode, and how it should be tested. Done for this issue means reaching agreement on that design while keeping exact output as the default.

Written by the indexing model from the issue text.

Description

area: runtime enhancement performance

Today Model M aims for output that matches its reference exactly. An optional, clearly labelled faster mode could allow
small output differences within a published quality limit, chosen by the player. Before any code: discuss here how the
quality limit is defined and measured, how the mode is chosen and shown, and how it is tested. The default stays exact.

Dominant language
C++
Stars
12
Forks
2
Avg merge
3h 10m
Merged PRs (30d)
171

Getting set up

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.

More from phantoslayer21/wronggpu

All issues in phantoslayer21/wronggpu

Similar issues

More C++ issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.