[CIG-SEISMO] cubit2specfem3d export

[s.khan-1 at utwente.nl]

Dear Emanuele,

Please find the scripts and the volume in attachment. I use block_mesh.py after making some modification to it. I am using Cubit 13.0.

Thanks
Best regards,
Saad Khan

From: cig-seismo-bounces at geodynamics.org [mailto:cig-seismo-bounces at geodynamics.org] On Behalf Of emanuele casarotti
Sent: Monday, January 13, 2014 8:51 PM
To: cig-seismo at geodynamics.org
Subject: Re: [CIG-SEISMO] cubit2specfem3d export

Hi
Can you share the scripta and the volumes?
And the version of cubit...


Emanuele

Il giorno 13/gen/2014, alle ore 19:47, "s.khan-1 at utwente.nl<mailto:s.khan-1 at utwente.nl>" <s.khan-1 at utwente.nl<mailto:s.khan-1 at utwente.nl>> ha scritto:
Dear All,

The boundary_definition.py script does not catch my topographic surface. I have to define it manually after running the script (boundary_definition.py). Then I export the mesh with run_cubit2specfem3d.py, which says
:
Writing MESH/free_surface_file.....
  block name: face_topo id: 2
  number of faces =  0
:
:
# all files needed by SCOTCH are now in directory MESH

Rest of the process goes smoothly and I also get result in the OUTPUT. The question is, what does "number of face=0" mean any does it affect the results?

Another thing, when I use very fine mesh (e.g. mesh interval 3000) the result (in seismograms) produces a lot of NaNs and at some places Infinities. Why is it so?

Note: The topo surface has been modified while the rest of geo model is the same as given in homogeneous_halfspace example. The topo surface is made of several surfaces which are combined to one using simplify option in cubit. I am using SPECFEM3D_Cartesian 2.1.

Thanks in advance.

Best regards,
Saad Khan
_______________________________________________
CIG-SEISMO mailing list
CIG-SEISMO at geodynamics.org<mailto:CIG-SEISMO at geodynamics.org>
http://geodynamics.org/cgi-bin/mailman/listinfo/cig-seismo
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://geodynamics.org/pipermail/cig-seismo/attachments/20140114/2847aa85/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: block_mesh.py
Type: application/octet-stream
Size: 1971 bytes
Desc: block_mesh.py
URL: <http://geodynamics.org/pipermail/cig-seismo/attachments/20140114/2847aa85/attachment-0006.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: boundary_definition.py
Type: application/octet-stream
Size: 15375 bytes
Desc: boundary_definition.py
URL: <http://geodynamics.org/pipermail/cig-seismo/attachments/20140114/2847aa85/attachment-0007.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: cubit2specfem3d.py
Type: application/octet-stream
Size: 34731 bytes
Desc: cubit2specfem3d.py
URL: <http://geodynamics.org/pipermail/cig-seismo/attachments/20140114/2847aa85/attachment-0008.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: run_boundary_definition.py
Type: application/octet-stream
Size: 382 bytes
Desc: run_boundary_definition.py
URL: <http://geodynamics.org/pipermail/cig-seismo/attachments/20140114/2847aa85/attachment-0009.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: run_cubit2specfem3d.py
Type: application/octet-stream
Size: 599 bytes
Desc: run_cubit2specfem3d.py
URL: <http://geodynamics.org/pipermail/cig-seismo/attachments/20140114/2847aa85/attachment-0010.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: cone_1.cub
Type: application/octet-stream
Size: 5527714 bytes
Desc: cone_1.cub
URL: <http://geodynamics.org/pipermail/cig-seismo/attachments/20140114/2847aa85/attachment-0011.obj>