Skip to main content
edited body
Source Link

Shallow Water Gravity Waves Equations are presented below: enter image description hereenter image description here Here are my code cuttings:

Shallow Water Gravity Waves Equations are presented below: enter image description here Here are my code cuttings:

Shallow Water Gravity Waves Equations are presented below: enter image description here Here are my code cuttings:

added 1 character in body
Source Link

Furthermore, I’ve also googled some other different options for NDSolveValue function from here and here, but none of them helped me to stabilize calculation process near the boundary of the simulation region. At the small simulation times I can clearly see my tsunami propagating correctly. In contrast, at the large times numerical interpolation solution explodes with enormous water surface height values without any reason.

Furthermore I’ve also googled some other different options for NDSolveValue function from here and here, but none of them helped me to stabilize calculation process near the boundary of the simulation region. At the small simulation times I can clearly see my tsunami propagating correctly. In contrast, at the large times numerical interpolation solution explodes with enormous water surface height values without any reason.

Furthermore, I’ve also googled some other different options for NDSolveValue function from here and here, but none of them helped me to stabilize calculation process near the boundary of the simulation region. At the small simulation times I can clearly see my tsunami propagating correctly. In contrast, at the large times numerical interpolation solution explodes with enormous water surface height values without any reason.

added 5 characters in body
Source Link

Being frustrated about FEM's accuracy by the discussion, I've tried to play with "SpatialDiscretization" -> {"TensorProductGrid", "DifferenceOrder" -> "Pseudospectral"} as it was recommended in the post. This attempt corresponds to initialconditions2 & method2 & region2 parameters for RunNDSolveValue function. Boundary conditions here are still periodic here, but futurefurther complexification of the spatial domain is unavailable. Unfortunately, this hopeful scheme also crashes with the same error "At t == ~1200, step size is effectively zero; singularity or stiff system suspected." and new warning "An insufficient number of boundary conditions have been specified for the direction of independent variable [Theta]. Artificial boundary effects may be present in the solution."

Being frustrated about FEM's accuracy by the discussion, I've tried to play with "SpatialDiscretization" -> {"TensorProductGrid", "DifferenceOrder" -> "Pseudospectral"} as it was recommended in the post. This attempt corresponds to initialconditions2 & method2 & region2 parameters for RunNDSolveValue function. Boundary conditions here are still periodic, but future complexification of spatial domain is unavailable. Unfortunately, this hopeful scheme also crashes with the same error "At t == ~1200, step size is effectively zero; singularity or stiff system suspected." and new warning "An insufficient number of boundary conditions have been specified for the direction of independent variable [Theta]. Artificial boundary effects may be present in the solution."

Being frustrated about FEM's accuracy by the discussion, I've tried to play with "SpatialDiscretization" -> {"TensorProductGrid", "DifferenceOrder" -> "Pseudospectral"} as it was recommended in the post. This attempt corresponds to initialconditions2 & method2 & region2 parameters for RunNDSolveValue function. Boundary conditions are still periodic here, but further complexification of the spatial domain is unavailable. Unfortunately, this hopeful scheme also crashes with the same error "At t == ~1200, step size is effectively zero; singularity or stiff system suspected." and new warning "An insufficient number of boundary conditions have been specified for the direction of independent variable [Theta]. Artificial boundary effects may be present in the solution."

added 236 characters in body
Source Link
Loading
added 278 characters in body
Source Link
Loading
added 209 characters in body
Source Link
Loading
added 163 characters in body
Source Link
Loading
added 163 characters in body
Source Link
Loading
added 163 characters in body
Source Link
Loading
added 163 characters in body
Source Link
Loading
added 661 characters in body
Source Link
Loading
edited body
Source Link
Loading
edited body
Source Link
Loading
edited title
Link
user64494
  • 29.1k
  • 4
  • 29
  • 56
Loading
edited tags
Link
user21
  • 40.7k
  • 8
  • 114
  • 170
Loading
added 166 characters in body
Source Link
Loading
Source Link
Loading