-
Notifications
You must be signed in to change notification settings - Fork 191
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.
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
Multiple warnings about "incremental compilation may be fatally broken for this module" #537
Comments
Try master Cassette.jl ;) |
That worked, thanks @vchuravy! PR incoming. |
After just recently installing Oceananigans I tried using the library and got this error. I gather things still work but wanted to point out tha tthere is still a Warning on my first use. See below for details.
|
Hi @francispoulin, thank you for reporting this! I believe the warning is due to #1141 which should be fixed with the next tagged release (v0.44.1), hopefully coming out a bit later today. PS: Hi from a uWaterloo grad! |
Thanks for the quick reply @ali-ramadhan . That is great that this is being fixed so soon. Would you like me to keep this open until after I test the new release? PS: Great to hear that UWaterloo grads are going off to do such cool things, like workong on this! |
Just re-opened the issue in case it still persists. Feel free to close this issue once you test the new release. I'll ping back here once v0.44.1 is out. |
Great and thanks again! |
@francispoulin v0.44.1 was just tagged so warning should be gone now! |
I agree the problem goes away. Thanks! A different issue, when I run this should I be seeing anything? I don't so have no way to observe whether it is doing anything reasonable or not. |
Awesome! I'll close the issue then. Hmmm, not sure what you're running but in general Oceananigans.jl doesn't give too much feedback (something we're hoping to improve, see #1013). If you're running things in the REPL it'll print/display what each expression returns (see below) but julia> using Oceananigans
julia> grid = RegularCartesianGrid(size=(100, 100, 50), extent=(2π, 2π, 1))
RegularCartesianGrid{Float64, Periodic, Periodic, Bounded}
domain: x ∈ [-5.496153587253255e-18, 6.283185307179586], y ∈ [-5.496153587253255e-18, 6.283185307179586], z ∈ [-1.0, 1.7080354225002348e-17]
topology: (Periodic, Periodic, Bounded)
resolution (Nx, Ny, Nz): (100, 100, 50)
halo size (Hx, Hy, Hz): (1, 1, 1)
grid spacing (Δx, Δy, Δz): (0.06283185307179587, 0.06283185307179587, 0.02)
julia> model = IncompressibleModel(grid=grid)
IncompressibleModel{CPU, Float64}(time = 0 seconds, iteration = 0)
├── grid: RegularCartesianGrid{Float64, Periodic, Periodic, Bounded}(Nx=100, Ny=100, Nz=50)
├── tracers: (:T, :S)
├── closure: IsotropicDiffusivity{Float64,NamedTuple{(:T, :S),Tuple{Float64,Float64}}}
├── buoyancy: SeawaterBuoyancy{Float64,LinearEquationOfState{Float64},Nothing,Nothing}
└── coriolis: Nothing
julia> simulation = Simulation(model, Δt=60, stop_time=3600)
Simulation{IncompressibleModel{CPU, Float64}}
├── Model clock: time = 0 seconds, iteration = 0
├── Next time step (Int64): 1 minute
├── Iteration interval: 1
├── Stop criteria: Any[Oceananigans.Simulations.iteration_limit_exceeded, Oceananigans.Simulations.stop_time_exceeded, Oceananigans.Simulations.wall_time_limit_exceeded]
├── Run time: 0 seconds, wall time limit: Inf
├── Stop time: 1 hour, stop iteration: Inf
├── Diagnostics: OrderedCollections.OrderedDict with no entries
└── Output writers: OrderedCollections.OrderedDict with no entries
julia> run!(simulation)
[ Info: Simulation is stopping. Model time 1 hour has hit or exceeded simulation stop time 1 hour. |
Thanks. I get the same output but no visuals and no data saved. I will learn how to do that. |
@francispoulin checkout the examples (like this one) for inspiration about how to save output and plot solutions and let us know if they are helpful! |
Thanks @glwagner , those examples look great! |
Non-fatal and easy to fix but should probably be done as these look bad to users.
The Casette warnings are non-trivial to fix according to @vchuravy so maybe supressing those warnings might work (see #366).
The text was updated successfully, but these errors were encountered: