ClimaComms.jl Release Notes

v0.6.3

Bugfix: cuda_sync was missing in the extension and, as a result, ClimaComms.@cuda_sync was not actually synchronizing. We've also removed the abstract fallback, so that we instead method-error if we pass a cuda device when the cuda extension does not exist.

v0.6.2

We added a device-agnostic allowscalar(f, ::AbstractDevice, args...; kwargs...) to further assist in making CUDA an extension.

v0.6.1

Macros have been refactored to hopefully fix some code loading issues.

v0.6.0

ClimaComms does no longer try to guess the correct compute device: the default is now CPU. To control which device to use, use the CLIMACOMMS_DEVICE environment variable.
CUDA and MPI are now extensions in ClimaComms. To use CUDA/MPI, CUDA.jl/MPI.jl have to be loaded. A convenience macro ClimaComms.@import_required_backends checks what device/context could be used and conditionally loads CUDA.jl/MPI.jl. It is recommended to change
```
import ClimaComms
```
to
```
import ClimaComms
ClimaComms.@import_required_backends
```
This has to be done before calling ClimaComms.context().