[cig-commits] [commit] devel,master: added socal1D sub-example to illustrate how to extend the identical model downward in depth; because layers are ordered from bottom up, this requires several minor changes to ensure that the meshes are identical in the overlapping region. (d026ee8)
cig_noreply at geodynamics.org
cig_noreply at geodynamics.org
Wed Jun 18 16:48:52 PDT 2014
Repository : https://github.com/geodynamics/specfem3d
On branches: devel,master
Link : https://github.com/geodynamics/specfem3d/compare/6026e367984905ab133865f62fa6293b343759b9...47f703851338234f96397e7da9fbff63d8178b8a
>---------------------------------------------------------------
commit d026ee890360efdb976030e2487b7835b68a59ad
Author: Carl Tape <carltape at gi.alaska.edu>
Date: Sun Apr 10 18:22:52 2011 +0000
added socal1D sub-example to illustrate how to extend the identical model downward in depth; because layers are ordered from bottom up, this requires several minor changes to ensure that the meshes are identical in the overlapping region.
>---------------------------------------------------------------
d026ee890360efdb976030e2487b7835b68a59ad
.../Mesh_Par_file_deep} | 15 +++++------
.../Mesh_Par_file_deep_honor60km} | 18 ++++++-------
meshfem3D_examples/socal1D/example_deep/README | 29 +++++++++++++++++++++
.../socal1D/example_deep/honor60km_or_not.png | Bin 0 -> 23030 bytes
.../socal1D/example_deep/interface0.dat | 4 +++
.../interfaces_deep.dat} | 6 ++---
.../interfaces_deep_honor60km.dat} | 9 +++++--
.../{utm_example => example_utm}/CMTSOLUTION_utm | 0
.../Mesh_Par_file_utm} | 0
.../{utm_example => example_utm}/Par_file_utm | 0
.../socal1D/{utm_example => example_utm}/README | 6 ++---
.../{utm_example => example_utm}/STATIONS_utm | 0
.../interfaces_utm.dat | 0
13 files changed, 62 insertions(+), 25 deletions(-)
diff --git a/meshfem3D_examples/socal1D/Mesh_Par_file_001 b/meshfem3D_examples/socal1D/example_deep/Mesh_Par_file_deep
similarity index 84%
copy from meshfem3D_examples/socal1D/Mesh_Par_file_001
copy to meshfem3D_examples/socal1D/example_deep/Mesh_Par_file_deep
index acb120f..2f458d5 100644
--- a/meshfem3D_examples/socal1D/Mesh_Par_file_001
+++ b/meshfem3D_examples/socal1D/example_deep/Mesh_Par_file_deep
@@ -4,7 +4,7 @@ LATITUDE_MIN = 33.790d0
LATITUDE_MAX = 34.157d0
LONGITUDE_MIN = -118.728d0
LONGITUDE_MAX = -118.237d0
-DEPTH_BLOCK_KM = 60.d0
+DEPTH_BLOCK_KM = 200.d0
UTM_PROJECTION_ZONE = 11
SUPPRESS_UTM_PROJECTION = .false.
@@ -26,8 +26,8 @@ USE_REGULAR_MESH = .false.
# Only for irregular meshes, number of doubling layers (1 or 2) and their position
NDOUBLINGS = 2
# NZ_DOUGLING_1 is the parameter to set up if there is only one doubling layer
-NZ_DOUGLING_1 = 6
-NZ_DOUGLING_2 = 9
+NZ_DOUGLING_1 = 20
+NZ_DOUGLING_2 = 23
# create mesh files for visualisation or further checking
CREATE_ABAQUS_FILES = .true.
@@ -51,8 +51,7 @@ NMATERIALS = 4
NREGIONS = 4
# define the different regions of the model as :
#NEX_XI_BEGIN #NEX_XI_END #NEX_ETA_BEGIN #NEX_ETA_END #NZ_BEGIN #NZ_END #material_id
-1 24 1 24 1 3 1
-1 24 1 24 4 6 2
-1 24 1 24 7 9 3
-1 24 1 24 10 12 4
-
+1 24 1 24 1 17 1
+1 24 1 24 18 20 2
+1 24 1 24 21 23 3
+1 24 1 24 24 26 4
\ No newline at end of file
diff --git a/meshfem3D_examples/socal1D/Mesh_Par_file_001 b/meshfem3D_examples/socal1D/example_deep/Mesh_Par_file_deep_honor60km
similarity index 80%
copy from meshfem3D_examples/socal1D/Mesh_Par_file_001
copy to meshfem3D_examples/socal1D/example_deep/Mesh_Par_file_deep_honor60km
index acb120f..608ce8a 100644
--- a/meshfem3D_examples/socal1D/Mesh_Par_file_001
+++ b/meshfem3D_examples/socal1D/example_deep/Mesh_Par_file_deep_honor60km
@@ -4,7 +4,7 @@ LATITUDE_MIN = 33.790d0
LATITUDE_MAX = 34.157d0
LONGITUDE_MIN = -118.728d0
LONGITUDE_MAX = -118.237d0
-DEPTH_BLOCK_KM = 60.d0
+DEPTH_BLOCK_KM = 200.d0
UTM_PROJECTION_ZONE = 11
SUPPRESS_UTM_PROJECTION = .false.
@@ -26,8 +26,8 @@ USE_REGULAR_MESH = .false.
# Only for irregular meshes, number of doubling layers (1 or 2) and their position
NDOUBLINGS = 2
# NZ_DOUGLING_1 is the parameter to set up if there is only one doubling layer
-NZ_DOUGLING_1 = 6
-NZ_DOUGLING_2 = 9
+NZ_DOUGLING_1 = 20
+NZ_DOUGLING_2 = 23
# create mesh files for visualisation or further checking
CREATE_ABAQUS_FILES = .true.
@@ -48,11 +48,11 @@ NMATERIALS = 4
3 2670 6300 3640 0.0 0 2
4 2400 5500 3180 0.0 0 2
# number of regions
-NREGIONS = 4
+NREGIONS = 5
# define the different regions of the model as :
#NEX_XI_BEGIN #NEX_XI_END #NEX_ETA_BEGIN #NEX_ETA_END #NZ_BEGIN #NZ_END #material_id
-1 24 1 24 1 3 1
-1 24 1 24 4 6 2
-1 24 1 24 7 9 3
-1 24 1 24 10 12 4
-
+1 24 1 24 1 14 1
+1 24 1 24 15 17 1
+1 24 1 24 18 20 2
+1 24 1 24 21 23 3
+1 24 1 24 24 26 4
\ No newline at end of file
diff --git a/meshfem3D_examples/socal1D/example_deep/README b/meshfem3D_examples/socal1D/example_deep/README
new file mode 100644
index 0000000..c7d58d5
--- /dev/null
+++ b/meshfem3D_examples/socal1D/example_deep/README
@@ -0,0 +1,29 @@
+README
+(SPECFEM3D/examples/meshfem3D_examples/socal1D/example_deep/README)
+
+This example illustrates two options for extending the bottom layer of the socal1D model. In some scenarios, it is helpful to extend the boundaries to eliminate spurious reflections from boundaries.
+
+First run the default socal1D example with 1 core.
+Then try examples A and B.
+
+EXAMPLE A: Change bottom interface from -60 km to -200 km; use uniform element
+ spacing in bottom layer.
+
+ > cp Mesh_Par_file_deep ../Mesh_Par_file
+ > cd interfaces_deep.dat ../interfaces.dat
+ > cd ..
+ > ./process.sh
+
+EXAMPLE B: Change bottom interface from -60 km to -200 km; add -60 km as a
+ new interface, such that the mesh above -60 km remains identical to
+ the default model that extends to 60 km depth only.
+
+ > cp Mesh_Par_file_deep_honor60km ../Mesh_Par_file
+ > cp interfaces_deep_honor60km.dat ../interfaces.dat
+ > cp interface0.dat ..
+ > cd ..
+ > ./process.sh
+
+The models for A and B are identical, but the meshes are subtley different: as shown in honor60km_or_not.png, mesh A does not honor the 60 km interface, whereas mesh B does. Since there is no material contrast at 60 km depth, the synthetics are expected to be nearly identical.
+
+=======================
\ No newline at end of file
diff --git a/meshfem3D_examples/socal1D/example_deep/honor60km_or_not.png b/meshfem3D_examples/socal1D/example_deep/honor60km_or_not.png
new file mode 100644
index 0000000..7aa512d
Binary files /dev/null and b/meshfem3D_examples/socal1D/example_deep/honor60km_or_not.png differ
diff --git a/meshfem3D_examples/socal1D/example_deep/interface0.dat b/meshfem3D_examples/socal1D/example_deep/interface0.dat
new file mode 100644
index 0000000..adacb1c
--- /dev/null
+++ b/meshfem3D_examples/socal1D/example_deep/interface0.dat
@@ -0,0 +1,4 @@
+-60000
+-60000
+-60000
+-60000
diff --git a/meshfem3D_examples/socal1D/interfaces.dat b/meshfem3D_examples/socal1D/example_deep/interfaces_deep.dat
similarity index 93%
copy from meshfem3D_examples/socal1D/interfaces.dat
copy to meshfem3D_examples/socal1D/example_deep/interfaces_deep.dat
index 6395dba..29521e2 100644
--- a/meshfem3D_examples/socal1D/interfaces.dat
+++ b/meshfem3D_examples/socal1D/example_deep/interfaces_deep.dat
@@ -21,10 +21,10 @@
#
# for each layer, we give the number of spectral elements in the vertical direction
# layer number 1 (bottom layer)
- 3
+ 17
# layer number 2
3
-# layer number 4
+# layer number 3
3
-# layer number 5 (top layer)
+# layer number 4 (top layer)
3
\ No newline at end of file
diff --git a/meshfem3D_examples/socal1D/interfaces.dat b/meshfem3D_examples/socal1D/example_deep/interfaces_deep_honor60km.dat
similarity index 85%
copy from meshfem3D_examples/socal1D/interfaces.dat
copy to meshfem3D_examples/socal1D/example_deep/interfaces_deep_honor60km.dat
index 6395dba..7e5c166 100644
--- a/meshfem3D_examples/socal1D/interfaces.dat
+++ b/meshfem3D_examples/socal1D/example_deep/interfaces_deep_honor60km.dat
@@ -1,11 +1,14 @@
# number of interfaces
- 4
+ 5
#
# We describe each interface below, structured as a 2D-grid, with several parameters :
# number of points along XI and ETA, minimal XI ETA coordinates
# and spacing between points which must be constant.
# Then the records contain the Z coordinates of the NXI x NETA points.
#
+# interface number 0
+ .false. 2 2 -121.d0 32.d0 6.0d0 6.0d0
+ interface0.dat
# interface number 1 (moho)
.false. 2 2 -121.d0 32.d0 6.0d0 6.0d0
interface1.dat
@@ -20,7 +23,9 @@
interface4.dat
#
# for each layer, we give the number of spectral elements in the vertical direction
-# layer number 1 (bottom layer)
+# layer number 0 (bottom layer)
+ 14
+# layer number 1
3
# layer number 2
3
diff --git a/meshfem3D_examples/socal1D/utm_example/CMTSOLUTION_utm b/meshfem3D_examples/socal1D/example_utm/CMTSOLUTION_utm
similarity index 100%
rename from meshfem3D_examples/socal1D/utm_example/CMTSOLUTION_utm
rename to meshfem3D_examples/socal1D/example_utm/CMTSOLUTION_utm
diff --git a/meshfem3D_examples/socal1D/utm_example/Mesh_Par_file_001_utm b/meshfem3D_examples/socal1D/example_utm/Mesh_Par_file_utm
similarity index 100%
rename from meshfem3D_examples/socal1D/utm_example/Mesh_Par_file_001_utm
rename to meshfem3D_examples/socal1D/example_utm/Mesh_Par_file_utm
diff --git a/meshfem3D_examples/socal1D/utm_example/Par_file_utm b/meshfem3D_examples/socal1D/example_utm/Par_file_utm
similarity index 100%
rename from meshfem3D_examples/socal1D/utm_example/Par_file_utm
rename to meshfem3D_examples/socal1D/example_utm/Par_file_utm
diff --git a/meshfem3D_examples/socal1D/utm_example/README b/meshfem3D_examples/socal1D/example_utm/README
similarity index 79%
rename from meshfem3D_examples/socal1D/utm_example/README
rename to meshfem3D_examples/socal1D/example_utm/README
index 3e865a7..2259496 100644
--- a/meshfem3D_examples/socal1D/utm_example/README
+++ b/meshfem3D_examples/socal1D/example_utm/README
@@ -1,5 +1,5 @@
README
-(SPECFEM3D/examples/meshfem3D_examples/socal1D/utm/README)
+(SPECFEM3D/examples/meshfem3D_examples/socal1D/example_utm/README)
This example is mainly to show the ease of using either UTM or lon-lat coordinates.
The utm example is better suited for direct comparison with external meshes for
@@ -10,7 +10,7 @@ First, run the default socal1D example with 1 core.
EXAMPLE A: Input geographic bounds in UTM, everything else in lon-lat.
- > cp Mesh_Par_file_001_utm ../Mesh_Par_file
+ > cp Mesh_Par_file_utm ../Mesh_Par_file
> cd ..
> ./process.sh
@@ -19,7 +19,7 @@ EXAMPLE B: All input values in UTM.
> cp CMTSOLUTION_utm ../CMTSOLUTION
> cp STATIONS_utm ../STATIONS
> cp interfaces_utm.dat ../interfaces.dat
- > cp Mesh_Par_file_001_utm ../Mesh_Par_file
+ > cp Mesh_Par_file_utm ../Mesh_Par_file
> cp Par_file_utm ../Par_file
> cd ..
> ./process.sh
diff --git a/meshfem3D_examples/socal1D/utm_example/STATIONS_utm b/meshfem3D_examples/socal1D/example_utm/STATIONS_utm
similarity index 100%
rename from meshfem3D_examples/socal1D/utm_example/STATIONS_utm
rename to meshfem3D_examples/socal1D/example_utm/STATIONS_utm
diff --git a/meshfem3D_examples/socal1D/utm_example/interfaces_utm.dat b/meshfem3D_examples/socal1D/example_utm/interfaces_utm.dat
similarity index 100%
rename from meshfem3D_examples/socal1D/utm_example/interfaces_utm.dat
rename to meshfem3D_examples/socal1D/example_utm/interfaces_utm.dat
More information about the CIG-COMMITS
mailing list