Open HakunanMatatat opened 6 months ago
no worries - Hakuna Matata :) let's just eat some bugs. and thanks for pointing this one out, i like a crunchy bite.
when importing GEOCUBIT boundary_definition routines, they use some internal tolerance values to detect the absorbing surfaces. these tolerance values have been set to some smaller values in the past, having non-destructive testing examples in mind. as you found out, this won't work anymore with the Mount St.Helens example. let me update the corresponding scripts a bit and submit a fix soon - many thanks.
hi Daniel, Have you started fixing it yet? I tried to change some parameters in boundary_definition.py but failed.
this has been addressed by PR #1696 - please try again with the newest devel version and let me know if there are still issues with the script.
please note that using CUBIT to mesh a region with topography is possible, but for most cases the in-house mesher xmeshfem3D
is probably easier to use. a utility script in the package can help importing the topography for any specified region:
utils/scripts/run_get_simulation_topography.py
to do so, copy an example from EXAMPLES/applications/meshfem3D_examples/
, e.g., the socal1D/
example, and then run the script within your example folder and specify your desired target region. for example, to get Taiwan:
./run_get_simulation_topography.py 120.5 22.5 123.0 25.5 --SRTM=topo3
hi In the Mount_stHelens example, in the generated mesh, only face_topo and face-abs_bottom have data, while the other four faces have no data. What's going on?