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've been playing around with SPECFEM2D and have mostly been working with Gmsh and Cubit for mesh generation. However, I haven't yet stumbled onto a working solution for creating readable CPML layers for either of these meshers:
Cubit: the conversion script "cubit2specfem2d.py" in /utils/cubit2specfem2d doesn't seem to be working (at least for me) for any of my own meshes or any of the provided examples in /EXAMPLES or /utils/cubit2specfem2d - the generated "nodes_coords_file", "mesh_file" & "materials_file" come out blank.
Gmsh: "LibGmsh2Specfem_convert_Gmsh_to_Specfem2D_official.py" in /utils/Gmsh runs fine for the Stacey BC option, but doesn't look to be configured yet for CPML. Modifying the executables in /utils/CPML for the Gmsh mesh files is successful, but only for 'ngnod' =4 in "Par_file" and generates spurious reflections within the simulation.
Is the only option thus far for CPML conditions is to use the internal mesher? No problem if so for my relatively simple models, but was just curious if I missed something or if that functionality hasn't been implemented yet.
Cheers,
Ian
The text was updated successfully, but these errors were encountered:
Hello Ian, I am working on a similar issue; I have been using the JensenMesh.py example from EXAMPLES/ paper_axisymmetry_example which purports to do this externally using the geocubit library.
Hi there,
I've been playing around with SPECFEM2D and have mostly been working with Gmsh and Cubit for mesh generation. However, I haven't yet stumbled onto a working solution for creating readable CPML layers for either of these meshers:
Is the only option thus far for CPML conditions is to use the internal mesher? No problem if so for my relatively simple models, but was just curious if I missed something or if that functionality hasn't been implemented yet.
Cheers,
Ian
The text was updated successfully, but these errors were encountered: