[cig-commits] r22816 - in seismo/3D/SPECFEM3D/trunk: CUBIT_GEOCUBIT/geocubitlib doc/USER_MANUAL

[dkomati1 at geodynamics.org]

Author: dkomati1
Date: 2013-09-20 11:48:08 -0700 (Fri, 20 Sep 2013)
New Revision: 22816

Modified:
   seismo/3D/SPECFEM3D/trunk/CUBIT_GEOCUBIT/geocubitlib/cubit2specfem3d.py
   seismo/3D/SPECFEM3D/trunk/doc/USER_MANUAL/manual_SPECFEM3D_Cartesian.pdf
   seismo/3D/SPECFEM3D/trunk/doc/USER_MANUAL/manual_SPECFEM3D_Cartesian.tex
Log:
updated the manual regarding how to use "claro" and also "run_cubit2specfem3d.py";
also fixed a typo in a GEOCUBIT script


Modified: seismo/3D/SPECFEM3D/trunk/CUBIT_GEOCUBIT/geocubitlib/cubit2specfem3d.py
===================================================================
--- seismo/3D/SPECFEM3D/trunk/CUBIT_GEOCUBIT/geocubitlib/cubit2specfem3d.py	2013-09-20 18:34:57 UTC (rev 22815)
+++ seismo/3D/SPECFEM3D/trunk/CUBIT_GEOCUBIT/geocubitlib/cubit2specfem3d.py	2013-09-20 18:48:08 UTC (rev 22816)
@@ -531,7 +531,7 @@
                 helpstring="#material_domain_id #material_id #rho #vp #vs #Q_mu #anisotropy"
                 txt='%1i %3i %s \n' % (properties[0],properties[1],helpstring)
             else:
-                helpstring=" -->       sintax: #material_domain_id #material_id #rho #vp #vs #Q_mu #anisotropy"
+                helpstring=" -->       syntax: #material_domain_id #material_id #rho #vp #vs #Q_mu #anisotropy"
                 txt='%1i %3i %s %s\n' % (properties[0],properties[1],properties[2],helpstring)
         elif flag < 0:
             if properties[2] == 'tomography':
@@ -539,7 +539,7 @@
             elif properties[2] == 'interface':
                 txt='%1i %3i %s %s %1i %1i\n' % (properties[0],properties[1],properties[2],properties[3],properties[4],properties[5])
             else:
-                helpstring=" -->       sintax: #material_domain_id 'tomography' #file_name "
+                helpstring=" -->       syntax: #material_domain_id 'tomography' #file_name "
                 txt='%1i %3i %s %s \n' % (properties[0],properties[1],properties[2],helpstring)
                 #
         return txt

Modified: seismo/3D/SPECFEM3D/trunk/doc/USER_MANUAL/manual_SPECFEM3D_Cartesian.pdf
===================================================================
(Binary files differ)

Modified: seismo/3D/SPECFEM3D/trunk/doc/USER_MANUAL/manual_SPECFEM3D_Cartesian.tex
===================================================================
--- seismo/3D/SPECFEM3D/trunk/doc/USER_MANUAL/manual_SPECFEM3D_Cartesian.tex	2013-09-20 18:34:57 UTC (rev 22815)
+++ seismo/3D/SPECFEM3D/trunk/doc/USER_MANUAL/manual_SPECFEM3D_Cartesian.tex	2013-09-20 18:48:08 UTC (rev 22816)
@@ -720,7 +720,10 @@
 Please feel free to contribute your own example to this package by
 contacting the CIG Computational Seismology Mailing List \urlwithparentheses{cig-seismo at geodynamics.org}.
 
+In most cases, to re-create the meshes for the examples given, just type "claro ./block\_mesh.py" or similar 
+from the command line ("claro" is the command to run CUBIT from the command line).
 
+
 \subsection{Exporting the Mesh with \texttt{cubit2specfem3d.py} }
 
 \label{subsec:Exporting-the-Mesh}
@@ -976,7 +979,23 @@
 to load-balance the mesh. Please see the next section for further
 details.
 
+In directory "CUBIT\_GEOCUBIT" we provide two scripts that can help doing the above tasks of exporting a CUBIT mesh
+to SPECFEM3D format automatically for you: "run\_cubit2specfem3d.py" and "run\_boundary\_definition.py".
+Just edit them to indicate the path to your local installation of CUBIT and also the name of the *.cub existing CUBIT mesh file
+that you want to export to SPECFEM3D format. These scripts will do the conversion for you automatically except assigning material properties
+to the different mesh layers. To do so, you will then need to edit the file 
+called "nummaterial\_velocity\_file" that will have just been created and change it from the prototype created:
 
+    0 1 vol1 --> syntax: \#material\_domain\_id \#material\_id \#rho \#vp \#vs \#Q\_kappa \#Q\_mu \#anisotropy
+    0 2 vol2 --> syntax: \#material\_domain\_id \#material\_id \#rho \#vp \#vs \#Q\_kappa \#Q\_mu \#anisotropy
+
+(where "vol1" and "vol2" here represent the volume labels that you have set while creating the mesh in CUBIT)
+to for instance
+
+    2 1 1500 2300 1800 9999.0 9999.0 0
+    2 2 1600 2500 20000 9999.0 9999.0 0
+
+
 \subsubsection*{Checking the mesh quality}
 
 The quality of the mesh may be inspected more precisely based upon