-
Notifications
You must be signed in to change notification settings - Fork 34
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
Discussion during calculating the rays in 3D model #71
Comments
Did you visualize your velocity model to make sure it is OK? What cell size are you using? 2D or 3D? rectilinear or unstructured? Which method (SPM, DSPM, FSM)? |
What method are you using. You must have a very strong velocity contrast. Are you defining slowness at nodes or cells? You get this kind of result with the SPM? |
yes, i use he SPM to calculate travel time considering diffraction in tunnel voids after defining slowness at nodes |
With the SPM, raypaths go throught the nodes of the mesh. If you have a low density of nodes, you likely end up with the kind of trajectory we see in your results. The solution would be to increase the number of secondary nodes and/or decrease the size of the tetrahedra at the rock/tunnel boundary. |
Also, can you confirm that you have defined velocity for cells, not at nodes? For models like yours, I would definitively use a model with velocity assigned to cells, not nodes. |
You are not using a tetrahedral mesh, Grid3D is a rectilinear mesh. Please read carefully the documentation on readthedocs. |
@bernard-giroux
Dear Professor Bernard Giroux , I would like to understand the reasons for the difference in calculation time for a pair of symmetric sensors, as well as the reasons for the sawtooth phenomenon in the path.
The text was updated successfully, but these errors were encountered: