Cargo Features
[dependencies]
burn-nn = { version = "0.20.1", default-features = false, features = ["std", "tracing", "doc", "test-cuda", "test-rocm", "test-tch", "test-wgpu", "test-vulkan", "test-metal", "test-memory-checks", "burn-remote", "burn-router"] }
- default = std
-
These default features are set whenever
burn-nnis added withoutsomewhere in the dependency tree.default-features = false Enables burn-core
** Please make sure all dependencies support no_std when std is disabled **
- std default doc?
-
Enables std of burn-core and num-traits
- tracing
-
Enables tracing of burn-core, optional burn-cuda, optional burn-fusion, optional burn-rocm, optional burn-tch, and optional burn-wgpu
burn-cuda:
FOR TESTING
- doc = std
- test-cuda
-
To use cuda during testing, default uses ndarray.
Enables burn-cuda
- test-rocm
-
To use hip during testing, default uses ndarray.
Enables burn-rocm
- test-tch
-
To use tch during testing, default uses ndarray.
Enables burn-tch
- test-wgpu test-metal? test-vulkan?
-
To use wgpu during testing, default uses ndarray.
Enables burn-wgpu
- test-vulkan = test-wgpu
-
To use wgpu-spirv during testing, default uses ndarray.
- test-metal = test-wgpu
-
To use wgpu-spirv during testing, default uses ndarray.
- test-memory-checks
-
Memory checks are disabled by default
Enables memory-checks of burn-fusion
Features from optional dependencies
In crates that don't use the dep: syntax, optional dependencies automatically become Cargo features. These features may have been created by mistake, and this functionality may be removed in the future.
- burn-cuda test-cuda?
- burn-rocm test-rocm?
- burn-remote implicit feature
-
Enables burn-remote
burn-remote:
Backend router decorator over the network
- burn-router implicit feature
-
Enables burn-router
burn-router:
Multi-backend router decorator for the Burn framework
- burn-tch test-tch?
- burn-wgpu test-metal? test-vulkan? test-wgpu?
- burn-fusion test-memory-checks?