-
Notifications
You must be signed in to change notification settings - Fork 229
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
absorbing boundary problem in Mount_stHelens #1688
Comments
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
to do so, copy an example from
|
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?
The text was updated successfully, but these errors were encountered: