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
I'd like to run GEOCLAW (CLAWPACK 5.4.1) in 1D with Cartesian grid. As ndim=1 doesn't work, I set it as suggested here: https://www.clawpack.org/sphinx-versioning/amrclaw1d.html. However in this case it doesn't see the topography.
I get an error: *** Error, grid cell does not overlap any topo grid xim = 0.00000000000000E+00 xip = 0.10000000000000E+04 yjm = 0.00000000000000E+00 yjp = 0.00000000000000E+00
But it doesn't give error about not overlapping area. I also tried to fully comment second dimension, but in that case it gives error about domain overlapping.
Also, I found a problem setting any other than topotype=2 topography and qinit dtopo (as in example for "bowl-radial" simulation) in Cartesian grid simulation. GEOCLAW doesn't provide any error, but doesn't see dtopo in other formats.
The text was updated successfully, but these errors were encountered:
I'd like to run GEOCLAW (CLAWPACK 5.4.1) in 1D with Cartesian grid. As ndim=1 doesn't work, I set it as suggested here: https://www.clawpack.org/sphinx-versioning/amrclaw1d.html. However in this case it doesn't see the topography.
My setrun.py:
My topography file:
I get an error:
*** Error, grid cell does not overlap any topo grid xim = 0.00000000000000E+00 xip = 0.10000000000000E+04 yjm = 0.00000000000000E+00 yjp = 0.00000000000000E+00
But it doesn't give error about not overlapping area. I also tried to fully comment second dimension, but in that case it gives error about domain overlapping.
I found 1D version here: https://github.com/clawpack/geoclaw_1d, but not sure if it is ready to use.
Also, I found a problem setting any other than topotype=2 topography and qinit dtopo (as in example for "bowl-radial" simulation) in Cartesian grid simulation. GEOCLAW doesn't provide any error, but doesn't see dtopo in other formats.
The text was updated successfully, but these errors were encountered: