Enable NaN-safe mode by default
@devmotion ya está trabajando en esto.
Desde el 12/10/2026.
Evaluación
- Dificultad
- 5/5
- Tiempo estimado
- Más de una semana
- Aptitud para principiantes
- 25/100
- Tipo de issue
- Nueva funcionalidad
- Claridad
- Bastante claro
- Estado de actividad
- Activo
- Área
- backend
Línea de trabajo
Read the discussion in #719 and the behavior changes in #777 and #856, then trace nansafe_mode and the Dual^Real branch. Decide whether NaN-safe mode should become the default, accounting for correctness and the reported performance cost; done means the default behavior and opt-out preference are settled and documented.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
I'd like to propose enabling NaN-safe mode by default, and making the current behaviour opt-in via the nansafe_mode preference.
This was discussed in #719 (starting at https://github.com/JuliaDiff/ForwardDiff.jl/issues/719#issuecomment-2471545577), but since switching the default is not breaking, the question was not resolved there and #719 was closed with the 1.0 release. So I open a separate issue for it, as suggested in https://github.com/JuliaDiff/ForwardDiff.jl/issues/719#issuecomment-2474602850.
IMO NaN-safe mode is not primarily about NaNs but about the definition of dual numbers: a dual number with a zero partial is unperturbed in that direction, so it must not contribute to the derivative in that direction, regardless of the derivative of the primal function at that point. The default mode violates this whenever the derivative is not finite (0 * Inf and 0 * NaN are NaN). Our documentation even says so ("oops, this NaN should be 0.0").
As a consequence, the default mode returns incorrect derivatives:
julia> f(v) = sqrt(v[1]) + v[2];
julia> ForwardDiff.gradient(f, [0.0, 1.0]) # ∂f/∂v[2] = 1
2-element Vector{Float64}:
Inf
NaN
Moreover, results depend on implementation details that should be irrelevant:
- whether an unperturbed argument is a
Realor aDualwith zero partials (see #856), - the chunk size: with the existing all-or-nothing check in the
Dual^Realbranch of^,v[1]^0.5 + v[2]returns[Inf, 1.0]withChunk{1}and[Inf, NaN]withChunk{2}.
In NaN-safe mode, all of these examples return [Inf, 1.0] for any chunk size (since #777 the check is applied to each partial separately).
IMO NaN-safe mode should be the default regardless of its performance impact. Correctness should be the default, and faster but incorrect results should be opt-in (as with, e.g., @fastmath) - one can always be fast by returning nonsense. The documentation states a performance impact of ~5-10%, but that's outdated: in the Rosenbrock benchmark in #777 the gradient took 853 μs with NaN-safe mode vs 597 μs without (median), i.e., about 40% more. That's worth documenting for users who want to opt out, but it shouldn't decide the default. Also note that since #777 NaN-safe mode does not turn the partials multiplication into branchy code anymore (one of the concerns in https://github.com/JuliaDiff/ForwardDiff.jl/issues/719#issuecomment-2484955066): _mul_partials compiles to SIMD instructions with an additional comparison and mask per partial (see the native code in #777).
- Lenguaje dominante
- Julia
- Estrellas
- 1k
- Forks
- 162
- Métricas de merge de PR
- Sin PR fusionados en 30 d
Preparar el entorno
Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de JuliaDiff/ForwardDiff.jl
-
missing floatmin, floatmax, and issubnormal for DualPosiblemente ocupada @devmotion la tomó hace 13 días. Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
JuliaDiff/ForwardDiff.jl#852 · 6 comentarios ·
-
Dificultad 4/5 3-5 días Aptitud para principiantes 52/100
JuliaDiff/ForwardDiff.jl#854 · 1 comentario ·
-
Dificultad 3/5 1-2 días Aptitud para principiantes 75/100
JuliaDiff/ForwardDiff.jl#849 ·
-
`gradient!` leaves part of the result unwritten when `f` does not depend on its argumentPosiblemente ocupada @devmotion la tomó hace 42 días. Abierto
Dificultad 3/5 1-2 días Aptitud para principiantes 78/100
JuliaDiff/ForwardDiff.jl#847 ·
-
hessian!(::ImmutableDiffResult, f, ::StaticArray) errors when f does not depend on its argumentPosiblemente ocupada @devmotion la tomó hace 43 días. Abierto
Dificultad 3/5 1-2 días Aptitud para principiantes 76/100
JuliaDiff/ForwardDiff.jl#846 · 1 comentario ·
Todos los issues de JuliaDiff/ForwardDiff.jl
Issues similares
-
tagbot-manual
Dificultad 1/5 Menos de una hora Aptitud para principiantes 75/100
tshort/StaticCompiler.jl#191 ·
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
SciML/SciMLSensitivity.jl#1703 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
JuliaGPU/GPUCompiler.jl#1008 ·
Los mantenedores suelen responder en 1 día
-
`biggs6` disagrees with CUTEst and is unbounded belowPosiblemente ocupada @timholy la tomó hace 1 día. Abiertobug
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
-
Cannot set point coordinates with `Range`s (or arbitrary arrays) using `Makie.Resampler` in `heatmap`Posiblemente ocupada @ffreyer la tomó hoy. Abiertobug
Dificultad 2/5 1-3 horas Aptitud para principiantes 74/100
Los mantenedores suelen responder en 1 día