Automatic Differentiation Construction Choice Recommendations

The choices for the auto-AD fill-ins with quick descriptions are:

  • AutoForwardDiff(): The fastest choice for small optimizations
  • AutoReverseDiff(compile=false): A fast choice for large scalar optimizations
  • AutoTracker(): Like ReverseDiff but GPU-compatible
  • AutoZygote(): The fastest choice for non-mutating array-based (BLAS) functions
  • AutoFiniteDiff(): Finite differencing, not optimal but always applicable
  • AutoSymbolics(): The fastest choice for large scalar optimizations
  • AutoEnzyme(): Highly performant AD choice for type stable and optimized code
  • AutoMooncake(): Like Zygote and ReverseDiff, but supports GPU and mutating code
  • AutoReactant(): Compiles the objective with Reactant.jl and differentiates the compiled program with Enzyme; runs on any XLA backend (CPU, GPU, TPU). Requires the OptimizationReactant sublibrary; first-order derivatives only.

Automatic Differentiation Choice API

The Auto-AD choices are defined and documented in ADTypes.jl. Optimization.jl accepts these choices when constructing optimization functions, but does not own their API.

ADTypes.AutoEnzyme — Type
AutoEnzyme <: AbstractADType

An AbstractADType choice for use in OptimizationFunction for automatically generating the unspecified derivative functions. Usage:

OptimizationFunction(f, AutoEnzyme(); kwargs...)

This uses the Enzyme.jl package. Enzyme performs automatic differentiation on the LLVM IR code generated from julia. It is highly-efficient and its ability perform AD on optimized code allows Enzyme to meet or exceed the performance of state-of-the-art AD tools.

  • Compatible with GPUs
  • Compatible with Hessian-based optimization
  • Compatible with Hv-based optimization
  • Compatible with constraints

Note that only the unspecified derivative functions are defined. For example, if a hess function is supplied to the OptimizationFunction, then the Hessian is not defined via Enzyme.

source
ADTypes.AutoFiniteDiff — Type
AutoFiniteDiff{T1,T2,T3} <: AbstractADType

An AbstractADType choice for use in OptimizationFunction for automatically generating the unspecified derivative functions. Usage:

OptimizationFunction(f, AutoFiniteDiff(); kwargs...)

This uses FiniteDiff.jl. While not necessarily the most efficient, this is the only choice that doesn't require the f function to be automatically differentiable, which means it applies to any choice. However, because it's using finite differencing, one needs to be careful as this procedure introduces numerical error into the derivative estimates.

  • Compatible with GPUs
  • Compatible with Hessian-based optimization
  • Compatible with Hv-based optimization
  • Compatible with constraint functions

Note that only the unspecified derivative functions are defined. For example, if a hess function is supplied to the OptimizationFunction, then the Hessian is not defined via FiniteDiff.

Constructor

AutoFiniteDiff(; fdtype = Val(:forward)fdjtype = fdtype, fdhtype = Val(:hcentral))
  • fdtype: the method used for defining the gradient
  • fdjtype: the method used for defining the Jacobian of constraints.
  • fdhtype: the method used for defining the Hessian

For more information on the derivative type specifiers, see the FiniteDiff.jl documentation.

source
ADTypes.AutoForwardDiff — Type
AutoForwardDiff{chunksize} <: AbstractADType

An AbstractADType choice for use in OptimizationFunction for automatically generating the unspecified derivative functions. Usage:

OptimizationFunction(f, AutoForwardDiff(); kwargs...)

This uses the ForwardDiff.jl package. It is the fastest choice for small systems, especially with heavy scalar interactions. It is easy to use and compatible with most Julia functions which have loose type restrictions. However, because it's forward-mode, it scales poorly in comparison to other AD choices. Hessian construction is suboptimal as it uses the forward-over-forward approach.

  • Compatible with GPUs
  • Compatible with Hessian-based optimization
  • Compatible with Hv-based optimization
  • Compatible with constraints

Note that only the unspecified derivative functions are defined. For example, if a hess function is supplied to the OptimizationFunction, then the Hessian is not defined via ForwardDiff.

source
ADTypes.AutoReactant — Type
AutoReactant <: AbstractADType

An AbstractADType choice for use in OptimizationFunction for automatically generating the unspecified derivative functions. Usage:

OptimizationFunction(f, AutoReactant(); kwargs...)

This uses the OptimizationReactant.jl sublibrary, which compiles the objective with Reactant.jl to StableHLO and differentiates it with Enzyme inside the compiled program. Because differentiation happens on the traced program rather than on Julia code, compiled objectives run on any XLA backend (CPU, GPU, TPU) selected through Reactant.XLA.set_default_backend, and they do not require Julia-side activity analysis of the objective.

  • Compatible with GPUs (via the Reactant XLA client)
  • Hessians, Hessian-vector products and constraint derivatives are not generated; pass them explicitly to OptimizationFunction or choose a different adtype
  • Not compatible with AutoSparse or SecondOrder

AutoReactant(; mode) accepts an AutoEnzyme selecting the Enzyme differentiation mode used inside the compiled program (default Reverse).

Note that only the unspecified derivative functions are defined. For example, if a grad function is supplied to the OptimizationFunction, then the gradient is not defined via Reactant.

source
ADTypes.AutoReverseDiff — Type
AutoReverseDiff <: AbstractADType

An AbstractADType choice for use in OptimizationFunction for automatically generating the unspecified derivative functions. Usage:

OptimizationFunction(f, AutoReverseDiff(); kwargs...)

This uses the ReverseDiff.jl package. AutoReverseDiff has a default argument, compile, which denotes whether the reverse pass should be compiled. compile should only be set to true if f contains no branches (if statements, while loops) otherwise it can produce incorrect derivatives!

AutoReverseDiff is generally applicable to many pure Julia codes, and with compile=true it is one of the fastest options on code with heavy scalar interactions. Hessian calculations are fast by mixing ForwardDiff with ReverseDiff for forward-over-reverse. However, its performance can falter when compile=false.

  • Not compatible with GPUs
  • Compatible with Hessian-based optimization by mixing with ForwardDiff
  • Compatible with Hv-based optimization by mixing with ForwardDiff
  • Not compatible with constraint functions

Note that only the unspecified derivative functions are defined. For example, if a hess function is supplied to the OptimizationFunction, then the Hessian is not defined via ReverseDiff.

Constructor

AutoReverseDiff(; compile = false)

Note: currently, compilation is not defined/used!

source
ADTypes.AutoTracker — Type
AutoTracker <: AbstractADType

An AbstractADType choice for use in OptimizationFunction for automatically generating the unspecified derivative functions. Usage:

OptimizationFunction(f, AutoTracker(); kwargs...)

This uses the Tracker.jl package. Generally slower than ReverseDiff, it is generally applicable to many pure Julia codes.

  • Compatible with GPUs
  • Not compatible with Hessian-based optimization
  • Not compatible with Hv-based optimization
  • Not compatible with constraint functions

Note that only the unspecified derivative functions are defined. For example, if a hess function is supplied to the OptimizationFunction, then the Hessian is not defined via Tracker.

source
ADTypes.AutoZygote — Type
AutoZygote <: AbstractADType

An AbstractADType choice for use in OptimizationFunction for automatically generating the unspecified derivative functions. Usage:

OptimizationFunction(f, AutoZygote(); kwargs...)

This uses the Zygote.jl package. This is the staple reverse-mode AD that handles a large portion of Julia with good efficiency. Hessian construction is fast via forward-over-reverse mixing ForwardDiff.jl with Zygote.jl

  • Compatible with GPUs
  • Compatible with Hessian-based optimization via ForwardDiff
  • Compatible with Hv-based optimization via ForwardDiff
  • Not compatible with constraint functions

Note that only the unspecified derivative functions are defined. For example, if a hess function is supplied to the OptimizationFunction, then the Hessian is not defined via Zygote.

source