using warning

[liasiegelman]

Hi, do you know how to fix the following ? Thanks

[ali-ramadhan]

Oh this is kinda weird. I don't think Oceananigans uses StaticArrays anymore.

What version of Oceananigans.jl and Julia are you using? You should be able to get this info from executing versioninfo() and using Pkg; Pkg.status() at the REPL.

[liasiegelman]

[ali-ramadhan]

Ah Julia installed Oceananigans v0.5.1 (an extremely ancient version), probably due to conflicts between dependency versions. The latest release is Oceananigans v0.57.1.

To grab the latest version you can try to explicitly update by typing ] add Oceananigans@0.57.1 in the REPL.

There may be conflicts with some other packages like CUDA v3.1.0. Oceananigans is still depending on CUDA v2 so you might have to ] rm CUDA to be able to ] add Oceananigans@0.57.1.

This might also explain the weird error you reported in #1635.

PS: You might encounter issues when using Oceananigans.jl with Julia 1.6 right now. It still requires Julia 1.5 for now.

[liasiegelman]

ah thanks but the all point is that I would like to test the GPU ...

[liasiegelman]

I ll try with CUDA there and see what I get.

[liasiegelman]

it works but gives me this warning

[ali-ramadhan]

When you ] add Oceananigans it will also add/install a compatible version of CUDA.jl so you can still use the GPU.

You only need to ] add CUDA if you want to use CUDA.jl directly.

[ali-ramadhan]

Ah I wouldn't worry about the MPI warning for now.

[liasiegelman]

ok cool thanks a lot !
So when trying running https://clima.github.io/OceananigansDocumentation/stable/generated/ocean_wind_mixing_and_convection/
I get this warning, seems ok no?

[ali-ramadhan]

That looks good! It's a mostly harmless warning about halo regions that the original grid is now different from model.grid.

Hopefully if you run the entire example you'll end up with a movie that looks like the one from the example.

[liasiegelman]

Yay, thanks a lot Ali !

[francispoulin]

@ali-ramadhan and I created that warning message. Maybe it's too agressive and we should rethink it as people clearly become concerned by it? Will have to think about that a bit more but glad it's working!

[glwagner]

I think the warning is a good idea. Probably a solution to alleviating user stress is to make halo=(3, 3, 3) the default, so that the warning is rarely invoked. #1245

[navidcy]

Is this resolved or should it stay open?

[francispoulin]

I'm okay with the warning message that we have and closing this.