Open wmheigl opened 3 years ago
Thanks for your comment, @wmheigl. You can provide a topography file with negative elevation to remove that part of the computational domain. However, a free surface boundary condition will still be imposed on the top boundary, which probably is not what you want?
That is correct, Anders. For my needs I would need absorbing boundaries all around the model.
It’s great to see that you follow up the communities suggestions.
On Jan 13, 2022, at 11:10 AM, Anders Petersson @.***> wrote:
Thanks for your comment, @wmheigl https://github.com/wmheigl. You can provide a topography file with negative elevation to remove that part of the computational domain. However, a free surface boundary condition will still be imposed on the top boundary, which probably is not what you want?
— Reply to this email directly, view it on GitHub https://github.com/geodynamics/sw4/issues/100#issuecomment-1012336153, or unsubscribe https://github.com/notifications/unsubscribe-auth/AHXVTXLNMWMRCCFGSRLA2ZDUV4BQHANCNFSM5CEFWMOA. Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub. You are receiving this because you were mentioned.
In borehole seismic applications, one often has velocity information over certain depth interval only and one is generally not interested in surface phenomena. It would be advantageous to have a datum parameter that allows to have the top of the computational grid not at z=0 but at some chosen depth, thus reducing the size of the computational grid and the computing time.