Hardcoding of `Float64` in loss

Open
#156 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Refactor
Clarity
Mostly clear
Activity status
Stale
Tech stack
julia

Research direction

Start at src/loss-penalty/generic.jl line 21 and trace how the Float64 scaling is used by the loss penalties. Determine whether the definition can support Float16, Float32, and Float64 regression outputs without breaking existing behavior. Done means the motivation is established and the genericity question is resolved in the implementation or issue discussion.

Written by the indexing model from the issue text.

Description

Is there a motivation for hardcoding the scaling in the loss penalties as Float64? If not, would a more generic definition allow for multiple types of regression outputs (Float64, 32, 16)?

Dominant language
Julia
Stars
86
Forks
16
PR merge metrics
No merged PRs in 30d

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 JuliaAI/MLJLinearModels.jl

All issues in JuliaAI/MLJLinearModels.jl

Similar issues

More Julia issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.