ࡱ > b y jbjb % m m Kq L n n n n n n n ^ X X X 8 X , Y ^ Z
Z F PZ PZ PZ PZ " rZ ~Z , R ފ Z - E n Z PZ PZ Z Z - \q n n PZ PZ r \q \q \q Z
n PZ n PZ \q $ n n n n Z \q \q 7 n n Y h X f
ǃ \ 0 ۃ 8 \q 8 ( \q n ^ ^ DP X ^ ^ X NEODETERMINISTIC HAZARD COMPUTATIONS
To start the procedure with the default parameters you have to run the program
makehaz.out
and then execute the shell script hazard (prepared by makehaz.out) by typing:
sh hazard
LIST OF REQUIRED INPUT FILES
Before running the programs you must have in your folder the following files, listed below with the convention:
bold - file must be prepared by the user,
italic - file must be used "as is", independently on the run.
italic - file created by other package
italic - file modified by the user
Each run must be uniquely identified by a sequence of characters (root) in the filename. All the examples in this manual refer to a test run with root "xxx". Since rather long filenames are generated by the programs, it is strongly suggested that the root does not exceed 30 characters length.
makehaz.par the parameter file that creates the script that activates the sequence of programs, with default parameters
cells.par the parameter file for the first program of the sequence
xxx.fps the fault plane solutions available
yyy.dat the earthquake catalogue with historical seismicity
yyy.poc the polygons defining the area where xxx.dat has to be used
xxx.por the polygons associated with average regional structural models
xxx.pos the polygons that define the seismogenic zones
hazgmt.sh plotting job
eurocode.dat EC8 design spectra for computing Design Ground Acceleration (DGA)
gusev01.xy Spectral curves for scaling seismograms with magnitude
gusev02.xy "
gusev03.xy "
gusev04.xy "
gusev05.xy "
gusev06.xy "
gusev07.xy "
gusev08.xy "
gusev09.xy "
gusev10.xy "
xxx0001.spl spectral quantities associated with polygon 1 defined in .por (SH)
xxx0001.spr spectral quantities associated with polygon 1 defined in .por (P-SV)
xxx000n.spl spectral quantities associated with polygon n defined in .por (SH)
xxx000n.spr spectral quantities associated with polygon n defined in .por (P-SV)
These are examples of the files that the user should prepare in order to run the hazard script with default parameters. They are located in /XDST/HazExample. In this example it is assumed that the default run has the name xxx.
makehaz.par parameter file for the program that creates the hazard sequence
Parameters for program makehaz
----------------------------------------------------------------
RUN DEFINITION
----------------------------------------------------------------
xxx Name of the run (max 15 char.)
6 20 Min and max longitude (degrees)
36 48 Min and max latitude (degrees)
1 Use seismogenic zones (0=no, 1=yes)
0 Use nodes (0=no, 1=yes, 2= yes separately)
0 File with nodes coordinates (max 12 char.)(for nodes only)
0 Use alerted areas (0=no, 1=CN, 2=M8S)
0 Execution (0=full ,1=until sources,2=until paths,3=starting from obs+sut)
1 Clean level (0=no,1=yes)
----------------------------------------------------------------
SOURCE DEFINITION
----------------------------------------------------------------
5.0 Min magnitude associated with the run
-200 2009 First and last year in catalogue (years)
.2 Cell size (degrees)
3 Smoothing radius (cells)
0 Min. events for smooth (count)
0 50 Min and max depth (km)
999 Source depth (sdepth) (0=sut,999=auto,x=km)
----------------------------------------------------------------
PATH DEFINITION
----------------------------------------------------------------
1 0 Min. and max source-site distance km (0=auto)
0 Short paths (ishortpaths) (0=elim,1=use rmin,2=adjust)
0 File (.obs) with observation points (instead of default grid) (max 12 char.)
----------------------------------------------------------------
TIME SERIES
----------------------------------------------------------------
1. Peak frequency (peakfr) (1.0 or 10.0)
1 Interpolation (npint) (0-9)
1 Seismogram format (iform) (0=ASCII, 1=bin)
4096 Time series samples (npts) (4096)
0 Time series length (iall) (0=truncated,1=complete)
1 Type of motion (itype) (1=dis, 2=vel, 3=acc)
0 Vertical component (ivert) (1=yes,0=no)
1 90 Type of scaling (iscale,iaz) (1=classic,2=pulsyn)(angle)
eurocode.dat File with code response spectra for computing DGA (max 12 char.)
0 Plot seismograms (isis) (1=yes,0=no)
You must specify the name of the run xxx (maximum 15 characters).
To check if there are no problems in your input files, you can run the program makehaz.out changing the value of Execution first into 1 and then into 2. If everything is ok, you can run the program makehaz.out with the value 0.
cells.par parameter file for the first program of the package (seismicity gridding)
parameters for program ecells (filenames reading format: A40)
aaa.dat file with first earthquake catalogue
aaa.poc file with first polygons of validity
bbb.dat file with second earthquake catalogue
bbb.poc file with second polygons of validity
zzz.dat file with nth earthquake catalogue
zzz.poc file with nth polygons of validity
DETAILS
Each earthquake catalogue (.dat) has a polygon file (.poc) that defines its validity area. This is important mostly when dealing with neighboring countries, each one having its own earthquake catalogue available.
FAQS
Q:Do I have to prepare a .poc file if I dont have to take care of neighboring countries?
A:Yes, this is required by the software. You can just assume the rectangle including all the events listed in your catalogue. Neverheless, there is generally no need of considering events at distances larger than 200 km from the region for which youll compute the hazard.
WARNING
In general, when dealing with catalogues from neighboring countries, its recommended to analyze and merge the earthquake catalogues with care about possible duplicates reported at different coordinates in neighboring catalogues.
aaa.dat earthquake catalogue with observed seismicity
1005 1 1 0 0 0 4347 1188 0520520 05200
1005 1 1 0 0 0 4150 1375 0520520 05200
1991 531 949 0 4428 1005 5320 0 0 00
1991 53110 4 0 4346 1296 10220 0 0 00
FORTRAN statement to read one record:
read(1,1)iy,m,id,iho,mi,isc,la,lo,ih,m1,m2,
* m3,m4,idummy
1 format(i4,5i2,i5,i6,5i3,i1)
EXPLANATION OF DATA:
iy year
m month
id day
iho hour
mi minute
isc second
la latitude*100 (example: 1492 means 14.92 degrees North)
lo longitude*100 (example: -12372 means 123.72 degrees West)
ih depth (km)
m1 magnitude1 *100
m2 magnitude2 *100
m3 magnitude3 *100
m4 magnitude4 *100
idummy unused, set to 0
DETAILS
This file is the catalogue of known events that affected the studied area in the past. In parallel, file .poc contains the polygon that defines the area for which the catalogue can be assumed valid. When running for adjacent countries you have to carefully investigate the completeness of each national earthquake catalogue in the areas where they overlap. In this case files .poc should be set so that each catalogue is used where it is best compared with the others.
FAQS
Q:For historical events I do not have all the information. What can I do?
A:Just include what you know. You must include at least latitude, longitude and magnitude obtained from intensity. Put a 0 in all other fields.
Q:My catalogue is not complete. What can I do?
A:Opposite to what happens with probabilistic methods, in this deterministic approach we don't care much about catalogue completeness. Here seismicity will be discretized into cells (0.2 x 0.2), and only the biggest event that occurred in each cell will be considered. Furthermore, within seismogenic zones defined in file .pos, if magnitude observed in the catalogue is lower than 5 or no event is reported in the catalogue, magnitude 5 will be used by default.
Q:Can I include information on seismic potential of active faults known from geology, for which I have no information in the historical catalogue?
A:Yes, you can create a .dat file with seismic potential data rather than observations. But remember that the default run is meant to be made with observations! You can rerun programs with the catalogue of seismic potential, and consider it as a parametric test.
WARNING
If you know magnitude estimates in different scales (ie: Mb from body waves, MS from surface waves, Ml local magnitue, Mk macroseismic magnitude) you should usually store them separatly in m1, m2, m3 and m4. Anyway, program cells will read just m1. So you should put in m1 the maximum magnitude value available. Program edcatsun.out can help you in this.
xxx.fps file with list of available focal mechanisms
-------------------- FPGNDT.DAT Revi:sed- July 1, 1977 ------------------------
NUMBEA YEARMODY HRMISEC LA.TITN LON.GITE DEPT MLMDMSMBMA AGEN AREADESCRI
NUMBEF ST1 D1 RA1 ST2 D2 RA2 PDI PI TDI TI BDI BI Q REFE AREADESCRI
NUMBEM M00 SF REFE DURA F2 M0XX ER1 M0YY ER2 M0ZZ ER3 M0XY ER4 M0XZ ER5 M0YZ ER6
NUMBET HDR SF M0 TVAL TD TAZ NVAL ND NAZ PVAL PD PAZ AST AD ARA BST BD BRA REFER
NUMBEU SF SMRR ER1 SMTT ER2 SMFF ER3 SMRT ER4 SMRF ER5 SMTF ER6
--------------------------------------------------------------------------------
44A 19591223 929000 37.720N 14.610E 770 0 0 0 053 SICILY
00044F 077 43 004 344 87 132 041 29 289 34 161 43 0001 SICILY
54A 19671031 2108000 37.840N 14.600E 380 0 0 0 050 SICILY
00054F 009 61 189 274 80 333 228 27 324 13 077 60 0001 SICILY
57A 19680115 133000 37.890N 13.080E 200 0 0 0 051 SICILY
00057F 040 82 046 302 46 168 163 23 272 37 049 45 0001 SICILY
58A 19680115 201000 37.780N 13.030E 30 0 0 0 054 SICILY
00058F 204 70 015 108 75 159 157 04 065 25 255 65 0001 SICILY
58B 19680115 201085 37.750N 12.983E 100 0 0 054 0 SICILY
00058G 270 50 035 156 64 134 216 08 116 50 313 39 0002 SICILY
88A 19760917 123000 38.100N 13.300E 330 0 0 0 044 XXXX SICILY
00088F 322 69 240 200 36 323 194 56 074 19 334 28 0001 SICILY
00676A 19771225 1150 37.000N 15.200E 090 0 0 0 0 0 XXXX ETNA
00676F 036 76 093 206 15 079 124 30 310 59 216 03 0038 ETNA
601A 0000000000000 39.800N 19.000E 000 0 0 0 0 0 XXXX IONIAN SEA
601F 030 90 180 0000 IONIAN SEA
FORTRAN statements to read the event records: (numer before label A,... - only for user)
read(1,(a)) rec1 ! character*80 rec1
100 if(index(ABCDE,recl(6:6)).ne.0) read(rec1,2)
* labr,r1lat,lb,r1lon,lc,ide,ml,md,ms,mb,ma
do ilab=1,6
if(labr(ilab:ilab).eq.' ') labr(ilab:ilab)='0'
enddo
if(lb.eq.'S'.or.lb.eq.'s') r1lat=-r1lat
if(lc.eq.'W'.or.lc.eq.'w') r1lon=-r1lon
read(1,1) rec2 ! character*80 rec2
if(index(ABCDE,recl(6:6)).ne.0) then
rec1=rec2
go to 100
endif
if(index(FGHIL,recl(6:6)).ne.0)
* read(rec2,3) istr1,idip,irak1,istr2,idip2,irak2, iptre,ipplu,ittre,itplu
1 format(a80)
2 format(a6,17x,f7.3,a1,f8.3,a1,1x,i4,1x,5i2)
3 format(7x,2i3,1x,i3,2x,2i3,1x,i3,3x,2i3,2x,2i3)
EXPLANATION OF DATA
labr a 6-character label (5 digits and 1 lette r - A . . . M )
r 1 l a t l a t i t u d e i n d e g r e e s ( 0 d"r 1 l a t d"9 0 ; e x a m p l e 4 5 . 6 8 )
l b l a t i t u d e s p e c i f i c a t i o n ( N f o r N o r t h , S f o r S o u t h )
r 1 l o n l o n g i t u d e i n d e g r e e s ( 0 d"r 1 l o n d"1 8 0 ; e x a m p l e 1 2 0 . 8 8 )
l c l o n g i t u d e s p e c i f i c a t i o n ( E f o r E a s t , W f o r W e s t )
i d e d e p t h i n k m m u l t i p l i e d * 10
mL local magnitude multiplied * 10
md duration magnitude multiplied * 10
ms surface waves magnitude multiplied * 10
mb body waves magnitude multiplied * 10
ma other magnitude multiplied * 10
istr1 strike angle of plane A
idip1 dip angle of plane A
irak1 rake angle of plane A
istr2 strike angle of plane B
idip2 dip angle of plane B
irak2 rake angle of plane B
iptre p-axis trend
ipplu p-axis plunge
ittre t-axis trend
itplu t-axis plunge
DETAILS
This is the file with the list of focal mechanisms available for the region of interest. There are seven comment records to begin with (description of content for each type of record). After them, each fps has at least two records defined: record with label A (info for event) and F(fps). If you have different solutions proposed for the same event, you can enter them in the file with labels B and G (and then C and H, D and I and E and L) respectively. So at most 5 different solutions can be associated with the same event. All the solutions that you enter in the file will be used by the package, with no priorities. Records with label M (tensor components), T and U needn't to be defined.
You need to have at least one solution falling within each seismogenic zone defined in the file .pos. If you enter more than one mechanism per polygon program emecmed will compute a "representative" fps obtained as the average of the available moment tensors (each event and each solution together). This might not be a good choice in case the available solutions differ significatively one each other. It sounds more reasonable to include in the .FPS file just one representative focal mechanism per seismogenic zone.
FAQS
(none)
WARNING
The package will just read event index, coordinates, magnitude and strike, dip and rake of nodal plane A. For the sake of information completeness, you should better fill in all the other fields.
Event index (the numerical part of the label labr) must be different for different events. It must be equal only for different solutions associated with the same event.
Strike, dip and rake must be defined using the convention reported in Aki and Richards. Positive rake angles remain untouched. Negative rake angles should be transformed to positive performing the operation (360 + negative_rake). Here you have some examples:
Aki and Richards Operation Value for .fps file
90 none 90
-50 360-50 310
0 none 0
180 none 180
-160 360-160 200
xxx.poc validity area for the earthquake catalogue
Polygon associated with the catalogue of seismicity (file xxx.dat)
xxxaaa0001
6.0 36.0
20.0 36.0
20.0 48.0
6.0 48.0
FORTRAN statement to skip the first record:
read(1,*)
FORTRAN statements to read each polygon:
read(1,1) label,num ; polygon name
read(1,*) xlon,ylat ; vertex record
1 format(a6,i4)
EXPLANATION OF DATA:
label a six-character label
num a 4-digits number
xlon logitude in degrees
ylat latitude in degrees
DETAILS
This file defines the area where the earthquake catalogue (xxx.dat) has to be used. When running for a single nation the area shuold cover the whole territory plus about 100 km around the political borders. When running for adjacent nations one .poc file has to be defined for each catalogue, and the areas defined by each .poc file must not overlap. For each catalogue, only events falling within the relative .poc file will be considered.
FAQS
Q:Should I follow any specific order in the definition of the coordinates?
A:Yes, for each polygon corners should be listed following either clockwise or counterclockwise order, starting from any point.
Q:Should I close each polygon defining the same corner at the beginning and at the end of the coordinate list?
A:No.
WARNING
Please follow strictly the format of the example file. Do not use TABS, just SPACES (and count them well) when editing the files. With some editors tabs are inserted automatically to facilitate indentation. Be sure to avoid that option! Programs will complain quite a lot
Only one polygon has to be defined in file .poc, associated with the corresponding earthquake catalogue (.dat)
xxx.por areas associated with different structural models
Polygons associated with regional structural models (files *.spl and *.spr)
struct0001
11.750 44.250
11.900 44.600
11.300 44.650
11.200 44.380
struct0002
11.200 44.380
11.300 44.650
10.900 44.700
10.750 44.500
struct0003
10.750 44.500
10.600 44.300
11.500 44.000
11.750 44.250
11.200 44.380
FORTRAN statement to skip the first record:
read(1,*)
FORTRAN statements to read each polygon:
read(1,1) label,num ; polygon name
read(1,*) xlon,ylat ; vertex record
1 format(a6,i4)
EXPLANATION OF DATA:
label a six-character label
num a 4-digits number
xlon logitude in degrees
ylat latitude in degrees
DETAILS
This file defines the areas associated with different regional structural models, and therefore with files .spl and .spr. For minimization of CPU time, synthetic seismograms will be computed in a loop over structural models: there will be one .isg file for each polygon defined in the .por file.
The whole territory must be covered by the polygons, since synthetic seismograms will only be computed within them.
Polygons should not overlap, should not be defined off the coasts and should follow roughly the political borders in order to facilitate in the future the computation of joint maps with adjacent nations.
FAQS
Q:Should I follow any specific order in the definition of the coordinates?
A:Yes, for each polygon corners should be listed following either clockwise or counterclockwise order, starting from any point.
Q:Should I close each polygon defining the same corner at the beginning and at the end of the coordinate list?
A:No.
WARNING
It is strongly suggested that for .por files polygon sides defined exactly in the NS and EW directions are given coordinates ending with decimals .1, .3, .5, .7 or .9 when the cell size is (as always recommended) 0.2 degrees.
The label associated with each polygon must be made of 6 chars and 3 digits.
Please follow strictly the format of the example file. Do not use TABS, just SPACES (and count them well) when editing the files. With some editors tabs are inserted automatically to facilitate indentation. Be sure to avoid that option! Programs will complain quite a lot
It is not necessary to set numbers of polygons (num) sequentially, but the number must be unique. It is very convenient that uniqueness remain even when joining the results of different countries. So please ask about numbers that you could better use.
xxx.pos seismogenic zones
Seismogenic zones. In file xxx.fps at least one mechanism per polygon!
region0001 6.14
11.200 44.600
11.600 44.600
11.600 44.400
11.200 44.400
region0002 6.60
10.800 44.200
11.200 44.200
11.200 44.000
10.800 44.000
FORTRAN statement to skip the first record:
read(1,*)
FORTRAN statements to read each polygon:
read(1,1) label,num ; polygon name
read(1,*) xlon,ylat ; vertex record
1 format(a6,i4,f4.2)
EXPLANATION OF DATA:
label a six-character label
num a 4-digits number
lmmax maximum magnitude for seismogenic sources
x logitude in degrees
y latitude in degrees
DETAILS
This file defines the geometry of the seismogenic zones. In the computation of synthetic seismograms, sources will be considered only within these polygons.
Polygons should not overlap, and should account for all the active areas that could affect the region where seismograms will be computed, even off the coast and outside the political borders. Therefore they can (and should) be placed also outside the area covered by .por file.
Later programs eselmec and emecmed will assign one single focal mechanism to the sources belonging to the same seismogenic zone.
The magnitude for seismogenic zones is used only for accepting the zones. If the maximum magnitude is greater than the threshold alarm of CN and M8 region, the seismogenic zone is retained. If the lmmax value is blank the seismogenic zone is retained.
FAQS
Q:Should I follow any specific order in the definition of the coordinates?
A:Yes, for each polygon corners should be listed following either clockwise or counterclockwise order, starting from any point.
Q:Should I close each polygon, defining the same corner at the beginning and at the end of the coordinate list?
A:No.
WARNING
It is strongly suggested that for .pos files polygon sides defined exactly in the NS and EW directions are given coordinates ending with decimals .0, .2, .4, .6 or .8 when the cell size is (as always recommended) 0.2 degrees.
The label associated with each polygon must be made of 6 chars and 4 digits.
Please follow strictly the format of the example file. Do not use TABS, just SPACES (and count them well) when editing the files. With some editors tabs are inserted automatically to facilitate indentation. Be sure to avoid that option! Programs will complain quite a lot
It is not necessary to set numbers of polygons (num) sequentially, but the number must be unique. It is very convenient that uniqueness remain even when joining the results of different countries. So please ask about numbers that you could better use.
xxx0001.spl normal modes (SH, P-SV) associated with structural models
xxx0002.spl
xxx0003.spl
xxx0001.spr
xxx0002.spr
xxx0003.spr
DETAILS
These are large files generated by programs ray and lov, which are part of the standard modal summation package developed at the Department of Earth Sciences of the University of Trieste. Please refer to the manuals of that package to understand how to prepare them. In a default run, you have to chose maximum frequency xmaxfr = 1 Hz.
eurocode.dat Design Acceleration Response Spectra
0.0000E+00 0.1000E+01 0.1000E+01 0.9000E+00 0.1400E+01
0.5000E-01 0.1750E+01 0.1500E+01 0.1237E+01 0.2100E+01
0.1000E+00 0.2500E+01 0.2000E+01 0.1575E+01 0.2800E+01
0.1500E+00 0.2500E+01 0.2500E+01 0.1913E+01 0.3500E+01
0.2000E+00 0.2500E+01 0.2500E+01 0.2250E+01 0.3500E+01
0.2500E+00 0.2500E+01 0.2500E+01 0.2250E+01 0.3500E+01
0.3000E+00 0.2500E+01 0.2500E+01 0.2250E+01 0.3500E+01
0.3500E+00 0.2500E+01 0.2500E+01 0.2250E+01 0.3500E+01
0.4000E+00 0.2500E+01 0.2500E+01 0.2250E+01 0.3500E+01
0.4500E+00 0.2222E+01 0.2500E+01 0.2250E+01 0.3500E+01
0.5000E+00 0.2000E+01 0.2500E+01 0.2250E+01 0.3500E+01
0.5500E+00 0.1818E+01 0.2500E+01 0.2250E+01 0.3500E+01
0.6000E+00 0.1667E+01 0.2500E+01 0.2250E+01 0.3500E+01
0.3955E+02 0.1918E-02 0.2877E-02 0.3452E-02 0.4028E-02
0.3960E+02 0.1913E-02 0.2870E-02 0.3444E-02 0.4017E-02
0.3965E+02 0.1908E-02 0.2862E-02 0.3435E-02 0.4007E-02
0.3970E+02 0.1903E-02 0.2855E-02 0.3426E-02 0.3997E-02
0.3975E+02 0.1899E-02 0.2848E-02 0.3418E-02 0.3987E-02
0.3980E+02 0.1894E-02 0.2841E-02 0.3409E-02 0.3977E-02
0.3985E+02 0.1889E-02 0.2834E-02 0.3400E-02 0.3967E-02
0.3990E+02 0.1884E-02 0.2827E-02 0.3392E-02 0.3957E-02
0.3995E+02 0.1880E-02 0.2820E-02 0.3383E-02 0.3947E-02
0.4000E+02 0.1875E-02 0.2813E-02 0.3375E-02 0.3938E-02
DETAILS
This file is used by program efft to obtain Design Ground Acceleration (by definition at T = 0) out of a synthetic acceleration response spectrum calculated for T > 0 (by default in the package for T > 1 s).
The Design Response Spectrum used are the one defined in EC8 or in the Italian seismic code for a stiff soil of type A.
FAQS
Q:Can I use different Design Response Spectra?
A:Yes.
WARNING
Program efft will use always the first two columns of data, that is period and design spectrum for soil A. Roughly speaking, soils are classified A when Vs > 900 m/s. If the upper layer velocity is slower than that, you should consider other design spectra. This is still under testing.
gusev01.xy curves for scaling of synthetic seismograms
(similarly for other curves up to gusev30.xy)
gusev21
-3.658 21
-3.465 21
-3.162 21
-2.826 21
-2.445 21
-2.138 20.992
-1.672 20.984
-1.209 20.97
-0.824 20.977
-0.407 20.967
-0.163 20.936
0.071 20.851
0.213 20.761
1.936 16.929
2.011 16.732
2.109 16.498
2.202 16.259
2.287 16.032
2.365 15.832
DETAILS
These files define the frequency scaling laws used by program efft to scale the synthetic seismograms with magnitude. Programs nsgl, nsgr, nsgv generate the seismograms in the point source approximation with M0 = 1E+20 dyn cm. The true scalar seismic moment is obtained with the rule
log(M0) = 1.5 M + 16.05
where M is the magnitude. For the scaling, each seismogram is Fourier-transformed and its amplitude spectrum is multiplied by the curve having the right M0, obtained by bilinear interpolation from the basic curves reported by Aki and based on the original paper by Gusev. With another Fourier transform the signals are again defined in the time domain.
FAQS
Q:Can I use different scaling laws?
A:Yes, efft program is alre a d y s e t f o r u s i n g w2 l a w s . Y o u c a n a l s o d e f i n e d i f f e r e n t c u r v e s i n t h e g u s e v ? ? . x y f i l e s , b u t a t t h i s m o m e n t y o u c a n n o t u s e d i f f e r e n t f i l e n a m e s .
W A R N I N G
" P l e a s e n o t e t h a t w i t h t h i s k i n d o f s c a l i n g s o u r c e d i m e n s i o n i s t a k e n i n t o a c c o u n t , b u t n o t t h e d e t a ils of the rupturing process. Therefore the shape of the unscaled signal will be affected by thew scaling, but not its duration. To account for duration, complex sources should be used, built as a superposition of point sources properly weighted and distributed in space and time. This is beyound the scope of this package. Please refer to the work by Angela Sara et al.
The Gusev scaling laws are appropriate and tested against observations for shallow events (roughly speaking h < 20 km). For deep events different laws should be used, and thoroughly tested.
If you prepare new digitized curves, you have to define them for the log(M0) values of 21,22,30 as in the original gusev??.xy files, mantaining the same filenames. No more than 99 samples should be defined. Sampling interval doesn't need to be regular.
hazgmt.sh
Job for plotting maps
PLOTTING
The command to plot maps is:
hazgmt.sh [-options]
The options must be chosen according to the extentions of the .
The command generates two output files (one in pfd format and one in ps format). The content is the same.
The options are listed in the table below:
optionsExtensions of input filestype of output dataExtensions of output files.amx, .dga, .uni, .ung, .unm, .uns,.poc, .por, .pos,.gmtdisplacements, velocities, DGA, magnitudes, intensities, polygons.pdf4.amxT of maximum (4th column).t.pdfball extensionsmaps in gray scale (Black and white).bw.pdfcall extensions no title (Clear).pdft1
t2
t5all extensionsmaps with Topography with different level of detail (t1 for regional scale (1km) t2 for intermediate scale (etopo2)- t5 for global scale (etopo5)) .pdf
Description of the maps:
xxx.gmt.pdf focal mechanisms (within seismogenic zones)
xxx.poc.pdf polygon associated with earthquake catalogue
xxx.por.pdf regional polygons associated with structural models
xxx.pos.pdf polygons associated with seismogenic zones
xxx.ung.pdf gridded magnitudes (within earthquake catalogue polygons)
xxx.uni.pdf smoothed magnitudes (within seismogenic zones)
xxx.unm.pdf smoothed magnitudes (within earthquake catalogue polygons)
xxx.uns.pdf smoothed final magnitudes (within seismogenic zones)
xxxf0res.amx.pdf displacement peak values (inside regional polygons)
xxxf0res.amx.t.pdf period of the displacement peak for max component between NS and EW (inside regional polygons)
xxxf1res.amx.pdf velocity peak values (inside regional polygons)
xxxf1res.amx.t.pdf period of the velocity peak for max component between NS and EW (inside regional polygons)
xxxf2max.dga.pdf DGA (Design Ground Acceleration) values (inside regional polygons)
xxxf2res.amx.pdf acceleration peak values (inside regional polygons)
xxxf2res.amx.t.pdf period of the acceleration peak for max component between NS and EW (inside regional polygons)
PAGE
FILENAME classic run_3.doc PAGE 4 of NUMPAGES18
% & v m n r M X
4
;
p
w
3 < J V O Z
7
B
q
|
6 A | = h >* h >*h 6>* h 6 h 5
h CJ h OJ QJ
h PJ h L % & u v m n % & L M
" $
n a$ $
,^,a$ $a$
! Ky y
4
p
3 J P 8
r
6 ) * +
$
a$ $
n a$ + ! " # $ % & ' ( ) * + $a$ + , - . / 0 1 2 3 4 5 6 7 8 9 : ; < = ; 3 7$ 8$ H$ $a$ = y $ % B T U I! ! ! ," S" Y" " " " # % +&