document approach to accuracy
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 62/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- julia
- Domain
- documentation
Research direction
Read the recent discussion in issue #45 and compare it with the proposed accuracy guidance in issue #134. Find the package documentation entry point and add a concise description covering the listed accuracy goals, generic fallbacks, method docstrings, and how to request greater accuracy; done when this guidance is documented consistently with the discussion.
Written by the indexing model from the issue text.
Description
Following up on the recent discussion at #45, we should perhaps consider documenting the package's approach to accuracy.
I would say roughly this:
- We aim for accurate implementations of at least
Float64inputs. "Accurate" is determined as a practical trade-off. - Most methods have
::Float32and::Float16implementations, with similar aims. - All methods have a generic fallback, which may not be as accurate but should not produce wildly incorrect results.
- Docstrings should document more specific claims for each method.
- If more accuracy is needed, please open an issue.
- Dominant language
- Julia
- Stars
- 86
- Forks
- 25
- Avg merge
- 4d 7h
- Merged PRs (30d)
- 3
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from JuliaStats/LogExpFunctions.jl
-
Precision loss for BigFloat in logexpm1, logcosh and log1pmxPossibly taken @devmotion claimed this today. Open
Difficulty 4/5 3-5 days Newbie friendliness 30/100
JuliaStats/LogExpFunctions.jl#135 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
JuliaStats/LogExpFunctions.jl#102 · 4 comments ·
-
exp-weighted meanOpen
Difficulty 5/5 Over a week Newbie friendliness 25/100
-
log-cumsum-exp ?Open
Difficulty 4/5 3-5 days Newbie friendliness 25/100
-
Add logmeanexpMay be free again A pull request for this issue was closed without being merged. Open
Difficulty 3/5 1-2 days Newbie friendliness 35/100
JuliaStats/LogExpFunctions.jl#81 · 2 comments ·
All issues in JuliaStats/LogExpFunctions.jl
Similar issues
-
code bug PowerSystems 6.0
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Sienna-Platform/PowerSystems.jl#1849 ·
Maintainers usually reply within 7 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 1-3 hours Newbie friendliness 86/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
FluxML/Metalhead.jl#407 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100