[cig-commits] r16352 - seismo/3D/SPECFEM3D_GLOBE/trunk/USER_MANUAL
bozdag at geodynamics.org
bozdag at geodynamics.org
Sat Feb 27 10:17:49 PST 2010
Author: bozdag
Date: 2010-02-27 10:17:48 -0800 (Sat, 27 Feb 2010)
New Revision: 16352
Modified:
seismo/3D/SPECFEM3D_GLOBE/trunk/USER_MANUAL/bibliography.bib
seismo/3D/SPECFEM3D_GLOBE/trunk/USER_MANUAL/manual_SPECFEM3D_GLOBE.pdf
seismo/3D/SPECFEM3D_GLOBE/trunk/USER_MANUAL/manual_SPECFEM3D_GLOBE.tex
Log:
Updated the manual
Modified: seismo/3D/SPECFEM3D_GLOBE/trunk/USER_MANUAL/bibliography.bib
===================================================================
--- seismo/3D/SPECFEM3D_GLOBE/trunk/USER_MANUAL/bibliography.bib 2010-02-26 21:56:57 UTC (rev 16351)
+++ seismo/3D/SPECFEM3D_GLOBE/trunk/USER_MANUAL/bibliography.bib 2010-02-27 18:17:48 UTC (rev 16352)
@@ -3826,7 +3826,7 @@
@ARTICLE{EUCrust07,
author = {M. Tesauro and M. K. Kaban and S. A. P. L. Cloetingh},
- title = {EuCrust-07: A new reference model for the European crust},
+ title = {EuCrust-07: A new reference model for the {European} crust},
journal = grl,
year = {2008},
volume = {35},
Modified: seismo/3D/SPECFEM3D_GLOBE/trunk/USER_MANUAL/manual_SPECFEM3D_GLOBE.pdf
===================================================================
(Binary files differ)
Modified: seismo/3D/SPECFEM3D_GLOBE/trunk/USER_MANUAL/manual_SPECFEM3D_GLOBE.tex
===================================================================
--- seismo/3D/SPECFEM3D_GLOBE/trunk/USER_MANUAL/manual_SPECFEM3D_GLOBE.tex 2010-02-26 21:56:57 UTC (rev 16351)
+++ seismo/3D/SPECFEM3D_GLOBE/trunk/USER_MANUAL/manual_SPECFEM3D_GLOBE.tex 2010-02-27 18:17:48 UTC (rev 16352)
@@ -453,8 +453,8 @@
for a discussion on how to specify your own 3D attenuation model.
\end{description}
\item [{\textmd{NOTE:}}]~\\
-When a 3D mantle model is chosen in \texttt{Par\_file}, the simulations are performed together with 3D crustal model Crust2.0. Alternatively, Crust2.0 can be combined with a higher resolution European crustal model EUCrust07 \citep{EUCrust07}. This can be done by setting the crustal type to \texttt{ICRUST\_CRUSTMAPS} in the \texttt{constant.h} file.
-It is also possible to run simulations using a 3D mantle model with a 1D crustal model on top. This can be done by setting the model in \texttt{Par\_file} to \texttt{<3D mantle>\_1Dcrust}, e.g., \texttt{s20rts\_1Dcrust, s362ani\_1Dcrust}, etc. In this case, 1D crustal model will be the one that is used in the 3D mantle model as a reference model (e.g., transversely isotropic PREM for s20rts, REF for s362ani, etc.).
+When a 3D mantle model is chosen in \texttt{Par\_file}, the simulations are performed together with the 3D crustal model Crust2.0. Alternatively, Crust2.0 can be combined with a higher resolution European crustal model EUCrust07 \citep{EUCrust07}. This can be done by setting the crustal type to \texttt{ICRUST\_CRUSTMAPS} in the \texttt{constant.h} file.
+It is also possible to run simulations using a 3D mantle model with a 1D crustal model on top. This can be done by setting the model in \texttt{Par\_file} to \texttt{<3D mantle>\_1Dcrust}, e.g., \texttt{s20rts\_1Dcrust, s362ani\_1Dcrust}, etc. In this case, the 1D crustal model will be the one that is used in the 3D mantle model as a reference model (e.g., transversely isotropic PREM for s20rts, REF for s362ani, etc.).
\item [{\texttt{OCEANS}}] Set to \texttt{.true.} if the effect of the oceans
on seismic wave propagation should be incorporated based upon the
@@ -2570,19 +2570,19 @@
\chapter{Post-Processing Scripts}
Several post-processing scripts/programs are provided in the \texttt{UTILS/seis\_process}
-directory, and most of them need to be adjusted when used on different
+directory, most of which need to be adjusted for different
systems, for example, the path of the executable programs. Here we
only list the available scripts and provide a brief description, and
you can either refer to the related sections for detailed usage or,
-in a lot of cases, type the script/program name without arguments
-for its usage.
+in many cases, type the script/program name without arguments
+to see its usage.
\section{Clean Local Database}
After all the simulations are done, you may need to clean the local
-scratch disk for the next simulation. This is especially important
-in the case of 1- or 2-chunk kernel simulation, where very large files
+scratch disks for the next simulation. This is especially important
+in the case of 1- or 2-chunk kernel simulations, where very large files
are generated for the absorbing boundaries to help with the reconstruction
of the regular forward wavefield. A sample script is provided in \texttt{UTILS/Cluster/lsf}:
@@ -2592,13 +2592,25 @@
\section{Process Data and Synthetics\label{sec:Process-data-and-syn}}
-In many cases, the SEM synthetics are calculated and compared to data
+In many cases, the SEM synthetics are calculated and compared to observed
seismograms recorded at seismic stations. Since the SEM synthetics
are accurate for a certain frequency range, both the original data
and the synthetics need to be processed before a comparison can be
-made. We generally use the following scripts:
+made. For such comparisons, the following steps are recommended:
+\begin{enumerate}
+\item Make sure that both synthetic and observed seismograms have the correct station/event and timing information.
+\item Convolve synthetic seismograms with a source time function with the half duration specified in the \texttt{CMTSOLUTION} file, provided, as recommended, you used a zero half duration in the SEM simulations.
+\item Resample both observed and synthetic seismograms to a common sampling rate.
+\item Cut the records using the same window.
+\item Remove the trend and mean from the records and taper them.
+\item Remove the instrument response from the observed seismograms (recommended) or convolve the synthetic seismograms with the instrument response.
+\item Make sure that you apply the same filters to both observed and synthetic seismograms. Preferably, avoid filtering your records more than once.
+\item Now, you are ready to compare your synthetic and observed seismograms.
+\end{enumerate}
+We generally use the following scripts for processing:
+
\subsection{\texttt{process\_data.pl}}
This script cuts a given portion of the original data, filters it,
@@ -2607,16 +2619,15 @@
without any argument. An example of the usage of the script:
\begin{lyxcode}
-{\small process\_data.pl~-m~CMTSOLUTION~-l~0/4000~-t~40/500~-i~-p~-x~bp~1999.330{*}.LH?.SAC}{\small \par}
+{\footnotesize process\_data.pl~-m~CMTSOLUTION~-s~1.0~-l~0/4000~-t~40/500~-f~-i~-p~-x~bp~1999.330{*}.LH?.SAC}{\small \par}
\end{lyxcode}
-which has cut all the sac files between 0 and 4000 seconds, filtered
-them between 40 and 500 seconds, transfered them into displacement
-records, picked the first P and S arrivals, and add suffix `\texttt{bp}'
-to the file names.
-Note that all of the scripts in this section actually use the SAC,
+\noindent which has resampled the SAC files to a sampling rate of 1 seconds, cut them between 0 and 4000 seconds, transfered them into displacement
+records and filtered them between 40 and 500 seconds, picked the first P and S arrivals, and added suffix `\texttt{bp}' to the file names.
+
+Note that all of the scripts in this section actually use SAC,
saclst and/or IASP91 to do the core operations; therefore make sure
-that SAC, saclst and IASP91 packages are installed properly on your
+that the SAC, saclst and IASP91 packages are installed on your
system, and that all the environment variables are set properly before
running these scripts.
@@ -2628,26 +2639,25 @@
An example of the usage of the script:
\begin{lyxcode}
-{\footnotesize process\_syn.pl~-m~CMTSOLUTION~-h~-a~STATIONS~-l~0/4000~-t~40/500~-p~-x~bp~syn/{*}.LH?.semd}{\footnotesize \par}
+{\footnotesize process\_syn.pl~-m~CMTSOLUTION~-h~-a~STATIONS~-s~1.0~-l~0/4000~-t~40/500~-f~-p~-x~bp~syn/{*}.LH?.semd}{\footnotesize \par}
\end{lyxcode}
which will convolve the synthetics with a triangular source-time function
from the \texttt{CMTSOLUTION} file, convert the synthetics into SAC
-format, add event and station information into the SAC headers, cut
-the SAC files between 0 and 4000 seconds, filter them between 40 and
-500 seconds, pick the first P and S arrivals, and add the suffix `\texttt{bp}'
+format, add event and station information into the SAC headers, resample the SAC files with a sampling rate of 1 seconds, cut them between 0 and 4000 seconds, filter them between 40 and
+500 seconds with the same filter used for the observed data, pick the first P and S arrivals, and add the suffix `\texttt{bp}'
to the file names.
-More options are available for this script, such as adding time shift
+More options are available for this script, such as adding a time shift
to the origin time of the synthetics, convolving the synthetics with
a triangular source time function with a given half duration, etc.
-Type \texttt{process\_syn.pl} without any argument for a detailed
+Type \texttt{process\_syn.pl} without any argument for detailed
usage.
\subsection{\texttt{rotate.pl}}
To rotate the horizontal components of both the data and the synthetics
-(LHN and LHE) to the transverse and radial direction (LHT and LHR),\texttt{\small{}
+(LHN and LHE) to the transverse and radial directions (LHT and LHR),\texttt{\small{}
}use{\small{} }\texttt{\small rotate.pl}:
\begin{lyxcode}
@@ -2667,12 +2677,12 @@
Note: You need to have the \texttt{sismoutil-0.9b} package installed
on your computer if you want to run this script on binary SAC files.
-The software is available at the ORFEUS web site \url{www.orfeus-eu.org}.
+The software is available via the ORFEUS web site \url{www.orfeus-eu.org}.
In case the simulation crashes during run-time without computing and
writing all time steps, the SAC files (if flags \texttt{OUTPUT\_SEISMOS\_SAC\_ALPHANUM}
or \texttt{OUTPUT\_SEISMOS\_SAC\_BINARY} have been set to \texttt{.true.})
-are corrupt and cannot be used properly in SAC. If the simulation
+are corrupted and cannot be used in SAC. If the simulation
ran long enough so that the synthetic data may still be of use, you
can run the script called \texttt{clean\_sac\_headers\_after\_crash.sh}
(located in the \texttt{UTILS} directory) on the SAC files to correct
More information about the CIG-COMMITS
mailing list