You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Following #4034 I was able to reliably reproduce the error. When using a 16³ LatitudeLongitudeGrid with Float32 on an NVIDIA RTX 4090 with --check-bounds=yes (needed!) the MWE below produces the error below.
There is no error with a smaller 8³ grid. There is no error with Float64. And there is no error on a RectilinearGrid.
I was not able to reproduce on a V100. But I've seen this error show up when running simulations on an immersed LatitudeLongitudeGrid with Float64 on a V100 and H100 without --check-bounds=yes.
I will try to reproduce using just CUDA.jl. It's interesting that the error suggests that the RTX 4090 has a "Maximum number of threads per block" of 512 when CUDA deviceQuery says it's 1024.
MWE:
using Oceananigans
using Oceananigans.Advection: cell_advection_timescaleᶜᶜᶜ
grid =LatitudeLongitudeGrid(GPU(), Float32;
topology = (Bounded, Bounded, Bounded),
size = (16, 16, 16),
longitude = (-10, 10),
latitude = (-10, 10),
z = (-100, 0)
)
model =HydrostaticFreeSurfaceModel(; grid)
u, v, w = model.velocities
τ =KernelFunctionOperation{Center, Center, Center}(cell_advection_timescaleᶜᶜᶜ, grid, u, v, w)
τ_min =minimum(τ)
But to upgrade to CUDA.jl v5.6.1 I had to change the GPUArrays.jl [compat] entry in Project.toml, and manually disable scalar operations. Maybe this doesn't allow the error to show up.
It could be that solving the scalar operations issue and upgrading to the latest CUDA.jl (#4036) solves this issue too.
Following #4034 I was able to reliably reproduce the error. When using a 16³
LatitudeLongitudeGrid
withFloat32
on an NVIDIA RTX 4090 with--check-bounds=yes
(needed!) the MWE below produces the error below.There is no error with a smaller 8³ grid. There is no error with
Float64
. And there is no error on aRectilinearGrid
.I was not able to reproduce on a V100. But I've seen this error show up when running simulations on an immersed
LatitudeLongitudeGrid
withFloat64
on a V100 and H100 without--check-bounds=yes
.I will try to reproduce using just CUDA.jl. It's interesting that the error suggests that the RTX 4090 has a "Maximum number of threads per block" of 512 when CUDA deviceQuery says it's 1024.
MWE:
Error:
Environment: Oceananigans.jl
main
branch.The text was updated successfully, but these errors were encountered: