Floating-point rounding issues in test parameters
- Dominant language
- Python
- Stars
- 2
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
Test parameters (and probably observation values) have awkward representation issues (see e.g. Amplitude below):
That is from the test "RheobaseTestToRemove" on the staging server. Desired behavior would be to represent 1e10 as 1e10, not as 1.0000000000002e10. This could mean using higher precision floats or explicit representations of decimals.
Contributor guide
No contributing guide indexed for this repository
Research direction
Reproduce the representation shown for the Amplitude value in the staging server, using the test "RheobaseTestToRemove" as the starting case. Trace how test parameters and observation values are represented and displayed; done means values such as 1e10 appear as 1e10 rather than 1.0000000000002e10, with related cases checked.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100