[CIG-SEISMO] SPECFEM3D-problems
abolfazl komeazi
komeaz at gmail.com
Sun Jul 2 04:57:28 PDT 2017
Dear Dr. Komatitsch,
I'm working with specfem3d version *2.0.1.* I've created my Mesh file using
cubit. the problem is when I run the program it seems my stations aren't in
a correct location. I've get this error:
need at least one receiver
Error detected, aborting MPI... proc 0
--------------------------------------------------------------------------
MPI_ABORT was invoked on rank 0 in communicator MPI_COMM_WORLD
with errorcode 30.
My target region is in latitude(25,34) and longitude(52,61) [which is part
of IRAN] and the corresponding UTM part is 40. attached you can find my
STATION file. looking at "output_solver.txt" file, I found that the program
didn't recognize my target region since it says:
check that stations in file ./DATA/STATIONS are within
longitude min/max: 52.511256102833592 61.535490745169042
latitude min/max : 0.0000000000000000 9.0094311157611440
UTM x min/max: 0.0000000000000000 999000.00000000000
UTM y min/max : 0.0000000000000000 999000.00000000000
Any help would be appreciated.
Sincerely Yours,
Abolfazl Komeazi
--
Ph.D Student of Geophysics - Seismology,
Seismological Research Center,
International Institute of Earthquake Engineering and Seismology (IIEES),
Seismology Department
P.O. Box 19395-3913,
Tehran, Iran,
komeaz at gmail.com
a.komeazi at iiees.ac.ir
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.geodynamics.org/pipermail/cig-seismo/attachments/20170702/5a94b0e9/attachment-0001.html>
-------------- next part --------------
**********************************************
**** Specfem 3-D Solver - MPI version f90 ****
**********************************************
Version: v2.0.2-2178-g6b93bc9
Fixing slow underflow trapping problem using small initial field
There are 1 MPI processes
Processes are numbered from 0 to 0
There is a total of 1 slices
NDIM = 3
NGLLX = 5
NGLLY = 5
NGLLZ = 5
using single precision for the calculations
smallest and largest possible floating-point numbers are: 1.17549435E-38 3.40282347E+38
velocity model: default
total acoustic elements : 0
total elastic elements : 142560
total poroelastic elements : 0
********
minimum and maximum number of elements
and points in the CUBIT + SCOTCH mesh:
NSPEC_global_min = 142560
NSPEC_global_max = 142560
NSPEC_global_max / NSPEC_global_min imbalance = 1.00000000 = 0.00000000 %
NSPEC_global_sum = 142560
NGLOB_global_min = 9367159
NGLOB_global_max = 9367159
NGLOB_global_max / NGLOB_global_min imbalance = 1.00000000 = 0.00000000 %
NGLOB_global_sum = 9367159
If you have elements of a single type (all acoustic, all elastic, all poroelastic, and without CPML)
in the whole mesh, then there should be no significant imbalance in the above numbers.
Otherwise, it is normal to have imbalance in elements and points because the domain decomposer
compensates for the different cost of different elements by partitioning them unevenly among processes.
********
********
Model: P velocity min,max = 5000.00000 8230.00000
Model: S velocity min,max = 2800.00000 4560.00000
Model: Poisson's ratio min,max = 0.239989176 0.301242232
********
*********************************************
*** Verification of simulation parameters ***
*********************************************
*** Xmin and Xmax of the model = 0.00000000 999000.000
*** Ymin and Ymax of the model = 0.00000000 999000.000
*** Zmin and Zmax of the model = -100000.000 2590.92261
*** Max GLL point distance = 4862.95752
*** Min GLL point distance = 27.3437538
*** Max/min ratio = 177.845276
*** Max element size = 14916.4326
*** Min element size = 35.9687500
*** Max/min ratio = 414.705353
*** Minimum period resolved = 5.73660755
*** Maximum suggested time step = 1.69836986E-03
*** for DT : 1.2000000000000000E-002
*** Max stability for wave velocities = 3.53279948
Elapsed time for checking mesh resolution in seconds = 0.15254497528076172
saving VTK files for Courant number and minimum period
******************************************
There is a total of 1 slices
******************************************
sources:
UTM projection:
UTM zone: 40
*************************************
locating source 1
*************************************
source located in slice 0
in element 1
in elastic domain
using moment tensor source:
xi coordinate of source in that element: -1.0000000000000000
eta coordinate of source in that element: 1.0000000000000000
gamma coordinate of source in that element: 1.0000000000000000
source time function:
using Gaussian source time function
Source time function is a Heaviside, convolve later
half duration: 5.9999999999999998E-002 seconds
time shift: 0.0000000000000000 seconds
magnitude of the source:
scalar moment M0 = 1.3781354517608221E+025 dyne-cm
moment magnitude Mw = 6.0595281272975043
original (requested) position of the source:
latitude: 28.123999999999999
longitude: 56.887999999999998
UTM x: 489000.50498456747
UTM y: 3110928.1325351126
depth: 8.0000000000000000 km
topo elevation: 2386.0551757812500
position of the source that will be used:
UTM x: 989750.00000000000
UTM y: 8534.0234375000000
depth: 33.364680175781253 km
z: -30978.625000000000
error in location of the source: 3142649.00 m
*****************************************************
*****************************************************
***** WARNING: source location estimate is poor *****
*****************************************************
*****************************************************
maximum error in location of the sources: 3142649.00 m
Elapsed time for detection of sources in seconds = 5.9499740600585938E-003
End of source detection - done
printing the source-time function
receivers:
there are 5 stations in file ./DATA/STATIONS
saving 0 stations inside the model in file ./DATA/STATIONS_FILTERED
excluding 5 stations located outside the model
error filtered stations:
simulation needs at least 1 station but got 0
check that stations in file ./DATA/STATIONS are within
longitude min/max: 52.511256102833592 61.535490745169042
latitude min/max : 0.0000000000000000 9.0094311157611440
UTM x min/max: 0.0000000000000000 999000.00000000000
UTM y min/max : 0.0000000000000000 999000.00000000000
-------------- next part --------------
A non-text attachment was scrubbed...
Name: STATIONS
Type: application/octet-stream
Size: 155 bytes
Desc: not available
URL: <http://lists.geodynamics.org/pipermail/cig-seismo/attachments/20170702/5a94b0e9/attachment-0002.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Par_file
Type: application/octet-stream
Size: 14478 bytes
Desc: not available
URL: <http://lists.geodynamics.org/pipermail/cig-seismo/attachments/20170702/5a94b0e9/attachment-0003.obj>
-------------- next part --------------
******************************************
*** Specfem3D MPI Mesher - f90 version ***
******************************************
Version: v2.0.2-2178-g6b93bc9
This is process 0
There are 1 MPI processes
Processes are numbered from 0 to 0
There is a total of 1 slices
NGLLX = 5
NGLLY = 5
NGLLZ = 5
Shape functions defined by NGNOD = 8 control nodes
Surface shape functions defined by NGNOD2D = 4 control nodes
Beware! Curvature (i.e. HEX27 elements) is not handled by our internal mesher
velocity model: default
using UTM projection in region 40
no attenuation
no anisotropy
no oceans
incorporating Stacey absorbing conditions
using a CMTSOLUTION source
using a Gaussian source time function
**************************
creating mesh in the model
**************************
external mesh points : 158103
defined materials : 486
undefined materials : 0
total number of spectral elements: 142560
absorbing boundaries:
xmin,xmax : 1320 1320
ymin,ymax : 1296 1296
bottom,top: 11880 300
total number of C-PML elements in the global mesh: 0
number of MPI partition interfaces: 0
minimum memory used so far : 485.252899 MB per process
minimum total memory requested : 2277.1708908081055 MB per process
create regions:
...allocating arrays
File DATA/Par_file_faults not found: assume no faults
...setting up jacobian
...indexing global points
...preparing MPI interfaces
total MPI interface points: 0
total assembled MPI interface points: 0
...setting up absorbing boundaries
absorbing boundary:
total number of free faces = 300
total number of faces = 17112
...determining velocity model
10 % time remaining: 7.9413225403842909E-009 s
20 % time remaining: 7.0450781984627176E-009 s
30 % time remaining: 6.1550471839816207E-009 s
40 % time remaining: 5.3170136669342226E-009 s
50 % time remaining: 4.4344464865790577E-009 s
60 % time remaining: 3.5407512532723424E-009 s
70 % time remaining: 2.6508547788530566E-009 s
80 % time remaining: 1.7630248397408886E-009 s
90 % time remaining: 8.8131681736461364E-010 s
100 % time remaining: 0.0000000000000000 s
...detecting acoustic-elastic-poroelastic surfaces
total acoustic elements : 0
total elastic elements : 142560
total poroelastic elements: 0
...element inner/outer separation
for overlapping of communications with calculations:
percentage of edge elements 0.00000000 %
percentage of volume elements 100.000000 %
...element mesh coloring
use coloring = F
...external binary models
no external binary model used
...creating mass matrix
...saving databases
saving mesh files for AVS, OpenDX, Paraview
saving additonal mesh files with surface/coupling points
...checking mesh resolution
********
minimum and maximum number of elements
and points in the CUBIT + SCOTCH mesh:
NSPEC_global_min = 142560
NSPEC_global_max = 142560
NSPEC_global_max / NSPEC_global_min imbalance = 1.00000000 = 0.00000000 %
NSPEC_global_sum = 142560
NGLOB_global_min = 9367159
NGLOB_global_max = 9367159
NGLOB_global_max / NGLOB_global_min imbalance = 1.00000000 = 0.00000000 %
NGLOB_global_sum = 9367159
If you have elements of a single type (all acoustic, all elastic, all poroelastic, and without CPML)
in the whole mesh, then there should be no significant imbalance in the above numbers.
Otherwise, it is normal to have imbalance in elements and points because the domain decomposer
compensates for the different cost of different elements by partitioning them unevenly among processes.
********
********
Model: P velocity min,max = 5000.00000 8230.00000
Model: S velocity min,max = 2800.00000 4560.00000
Model: Poisson's ratio min,max = 0.239989176 0.301242232
********
*********************************************
*** Verification of simulation parameters ***
*********************************************
*** Xmin and Xmax of the model = 0.00000000 999000.000
*** Ymin and Ymax of the model = 0.00000000 999000.000
*** Zmin and Zmax of the model = -100000.000 2590.92261
*** Max GLL point distance = 4862.95752
*** Min GLL point distance = 27.3437538
*** Max/min ratio = 177.845276
*** Max element size = 14916.4326
*** Min element size = 35.9687500
*** Max/min ratio = 414.705353
*** Minimum period resolved = 5.73660755
*** Maximum suggested time step = 1.69836986E-03
Elapsed time for checking mesh resolution in seconds = 0.15224289894104004
saving VTK files for Courant number and minimum period
min and max of topography included in mesh in m is 1240.0000000000000 2590.9226859999999
Repartition of elements:
-----------------------
total number of elements in mesh slice 0: 142560
total number of points in mesh slice 0: 9367159
total number of elements in entire mesh: 142560
approximate total number of points in entire mesh (with duplicates on MPI edges): 9367159.0000000000
approximate total number of DOFs in entire mesh (with duplicates on MPI edges): 28101477.000000000
total number of time steps in the solver will be: 40000
using single precision for the calculations
smallest and largest possible floating-point numbers are: 1.17549435E-38 3.40282347E+38
Elapsed time for mesh generation and buffer creation in seconds = 166.58818387985229
End of mesh generation
done
More information about the CIG-SEISMO
mailing list