`log1pmx`and `logmxp1` are probably not optimized for `Float32` and `Float16`

Open
  • Is something wrong?
#46 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
28/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
julia
Domain
performance

Research direction

Start by locating the implementations of log1pmx and logmxp1 in LogExpFunctions.jl and examine how they behave for Float32 and Float16. Check numerical accuracy and problematic inputs for both types, then determine whether type-specific optimizations are needed and add coverage showing the expected behavior.

Written by the indexing model from the issue text.

Description

We need to check whether there are numerical accuracy issues or problematic inputs for Float32 and Float16, and if there are, write optimizations for these types.

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

  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 JuliaStats/LogExpFunctions.jl

All issues in JuliaStats/LogExpFunctions.jl

Similar issues

More Julia issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.