waylonflinn/weblas

Unit Test Float Encode Exhaustively

Open

#11 opened on Dec 16, 2015

View on GitHub
 (2 comments) (0 reactions) (0 assignees)JavaScript (56 forks)batch import
correctnesshelp wanted

Repository metrics

Stars
 (701 stars)
PR merge metrics
 (No merged PRs in 30d)

Description

The floating point encode step is a tricky bit to get right. Issue #10 shows that numerical stability issues can make a big difference in some edge cases.

Encoding each unique floating point value as an element of a 4098 square matrix should require only a few hundred of these matrices. This should be doable in a reasonable amount of time.

References

Contributor guide

Research direction
Implement an exhaustive unit test that encodes each unique floating point value as a 4096 element square matrix. Use provided references to handle edge cases and numerical stability.
Tech stack
javascript
Domain
backend
Issue type
Test
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
JavaScript
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
65