Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Update issue referenced in simulation_tips.md #1887

Merged
merged 2 commits into from
Jul 22, 2021
Merged

Update issue referenced in simulation_tips.md #1887

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
1562c82
Update simulation_tips.md
tomchor Jul 22, 2021
12248ce
Update docs/src/simulation_tips.md
tomchor Jul 22, 2021
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 2 additions & 3 deletions docs/src/simulation_tips.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -98,8 +98,8 @@ _variable_ `T₀` that must be declared `const`.

`ComputedField`s are the most convenient way to calculate diagnostics for your simulation. They will
always work on CPUs, but when their complexity is high (in terms of number of abstract operations)
the compiler can't translate them into GPU code and they fail for GPU runs. (This limitation is discussed
in [this Github issue](https://github.com/CliMA/Oceananigans.jl/issues/1241) and contributors are welcome.)
the compiler can't translate them into GPU code and they fail for GPU runs. (This limitation is summarized
in [this Github issue](https://github.com/CliMA/Oceananigans.jl/issues/1886) and contributions are welcome.)
For example, in the example below, calculating `u²` works in both CPUs and GPUs, but calculating
`ε` will not compile on GPUs when we call the command `compute!`:

Expand Down Expand Up @@ -313,4 +313,3 @@ to define initial conditions, boundary conditions or
forcing functions on a GPU. To learn more about working with `CuArray`s, see the
[array programming](https://juliagpu.github.io/CUDA.jl/dev/usage/array/) section
of the CUDA.jl documentation.