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

[dkomati1 at geodynamics.org]

Author: dkomati1
Date: 2013-09-20 12:15:14 -0700 (Fri, 20 Sep 2013)
New Revision: 22819

Removed:
   seismo/3D/SPECFEM3D/trunk/CUBIT_GEOCUBIT/run_boundary_definition.py
Modified:
   seismo/3D/SPECFEM3D/trunk/doc/USER_MANUAL/manual_SPECFEM3D_Cartesian.pdf
   seismo/3D/SPECFEM3D/trunk/doc/USER_MANUAL/manual_SPECFEM3D_Cartesian.tex
Log:
deleted CUBIT_GEOCUBIT/run_boundary_definition.py, since the same thing is done better by run_cubit2specfem3d.py


Deleted: seismo/3D/SPECFEM3D/trunk/CUBIT_GEOCUBIT/run_boundary_definition.py
===================================================================
--- seismo/3D/SPECFEM3D/trunk/CUBIT_GEOCUBIT/run_boundary_definition.py	2013-09-20 18:57:45 UTC (rev 22818)
+++ seismo/3D/SPECFEM3D/trunk/CUBIT_GEOCUBIT/run_boundary_definition.py	2013-09-20 19:15:14 UTC (rev 22819)
@@ -1,30 +0,0 @@
-#!/usr/bin/env python
-
-import boundary_definition
-#import cubit2specfem3d 
-import os
-import sys
-
-# put the path to your installation of the "bin" directory of the CUBIT package here
-sys.path.append("/home/komatits/bin/cubit/bin")
-import cubit
-
-# let us also add the local GEOCUBIT library
-sys.path.append("./geocubitlib")
-
-# define the name of the CUBIT file to convert to SPECFEM format in the line below
-#cubit.cmd('open "large_test_cpml.cub"')
-cubit.cmd('open "test_cmpl_2layers.cub"')
-
-
-###### This is boundary_definition.py of GEOCUBIT
-#..... which extracts the bounding faces and defines them into blocks
-#reload(boundary_definition)
-
-# for CUBIT version 14 and higher (now called TRELIS) you may have to change 'face' to 'Face' in the line below
-boundary_definition.entities=['face']
-
-# this command can run in parallel or not
-#boundary_definition.define_bc(boundary_definition.entities,parallel=True)
-boundary_definition.define_bc(boundary_definition.entities,parallel=False)
-

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:57:45 UTC (rev 22818)
+++ seismo/3D/SPECFEM3D/trunk/doc/USER_MANUAL/manual_SPECFEM3D_Cartesian.tex	2013-09-20 19:15:14 UTC (rev 22819)
@@ -724,7 +724,7 @@
 from the command line ("claro" is the command to run CUBIT from the command line).
 
 
-\subsection{Exporting the Mesh with \texttt{cubit2specfem3d.py} }
+\subsection{Exporting the Mesh with \texttt{run\_cubit2specfem3d.py} }
 
 \label{subsec:Exporting-the-Mesh}
 
@@ -732,7 +732,7 @@
 the model for exportation with the definition of material blocks and
 boundary surfaces. Thus, prior to exporting the mesh, you need to
 define blocks specifying the materials and absorbing boundaries in
-CUBIT. This process could be done automatically using the script \texttt{boundary\_definition.py}
+CUBIT. This process could be done automatically using the script \texttt{run\_cubit2specfem3d.py}
 if the mesh meets some conditions or manually, following the block
 convention:
 \begin{description}
@@ -979,8 +979,8 @@
 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".
+In directory "CUBIT\_GEOCUBIT" we provide a script that can help doing the above tasks of exporting a CUBIT mesh
+to SPECFEM3D format automatically for you: "run\_cubit2specfem3d.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