Fling Study

Overview

The Fling study is a set of broadband platform simulations defined by NGA researchers and run by the SCEC Broadband platform group.

Terminology

To help the engineers, seismologists, and computer scientists talk about this computational study, we have defined the following terms for use in broadband calculations:

1. Study - A well-defined set of calculations to be performed. To qualify as a "study", the problem must defined to the level of detail that a knowledgeable user could calculate the total number and type of output files that will be calculated. We are currently conducting the Fling study.
2. Scenario - A scenario refers to a general description of an earthquake as observed by a particular set of stations and for a specified velocity model. The earthquake scenario is defined by magnitude, fault dimensions (length, width, depth, segmentation) and fault geometry (strike, dip, average rake). A scenario does not define the details of the rupture history (slip distribution, slip time function, rupture speed), and does not define hypocenter location. The Fling study has 42 scenarios, numbered 101 to 142.
3. Source Realization - Earthquake source definitions, given as a part of a scenario, are elaborated into distinct source realizations. Source realizations may differ by initial stress distribution, slip distribution, slip time function, hypocenter location, and rupture velocity. In the Fling study, each Scenario has 30 source realizations. A broadband source realization is equivalent to a "rupture variation", a term used in SCEC CyberShake work.
4. Simulations - A Broadband platform simulation is defined by an invocation of the main program, called run_bbp_2G.py. A simulation is defined by a source realization, a station list, and a set of Green's functions to use. In the Fling study, we run a simulation for each source realization.
5. Seismograms - The smallest unit of computational work in a broadband simulation is a seismogram. In broadband, a seismogram refers to a 3 component seismogram associated with a site. At a minimum, the relation between the source location and the site is known. In many cases, the geographical location of the site is known. In the Fling study, the number of seismograms is determined by the number of stations in the station list each simulation. For Fling scenarios with smaller magnitude earthquakes, the station lists may have 96 stations. Scenarios with larger magnitude earthquakes may have up to 279 stations. More stations are typical for larger earthquakes because strong ground motions are expected over a larger region. We will calculate the total number of seismograms and use that as a computation metric for the Fling study. Below is a table showing the number of seismograms for each scenario.

Number of stations and seismograms per scenario

Scenario	Number of Realizations	Number of Stations	Number of 3 Component Seismograms
Scenario101	30	96	2880
Scenario102	30	96	2880
Scenario103	30	138	4140
Scenario104	30	158	4740
Scenario105	30	178	5340
Scenario106	30	198	5940
Scenario107	30	107	3210
Scenario108	30	107	3210
Scenario109	30	165	4950
Scenario110	30	203	6090
Scenario111	30	241	7230
Scenario112	30	279	8370
Scenario113	30	107	3210
Scenario114	30	107	3210
Scenario115	30	127	3810
Scenario116	30	165	4950
Scenario117	30	203	6090
Scenario118	30	241	7230
Scenario119	30	96	2880
Scenario120	30	96	2880
Scenario121	30	118	3540
Scenario122	30	138	4140
Scenario123	30	158	4740
Scenario124	30	178	5340
Scenario125	30	113	3390
Scenario126	30	113	3390
Scenario127	30	113	3390
Scenario128	30	113	3390
Scenario129	30	215	6450
Scenario130	30	215	6450
Scenario131	30	257	7710
Scenario132	30	110	3300
Scenario133	30	110	3300
Scenario134	30	110	3300
Scenario135	30	110	3300
Scenario136	30	210	6300
Scenario137	30	210	6300
Scenario138	30	250	7500
Scenario139	30	275	8250
Scenario140	30	149	4470
Scenario141	30	149	4470
Scenario142	30	275	8250
Totals	1260		203910

Fling Study Scenario List

scenario_id	magnitude	dip	rake	Ztor	fault_length	fault_width		Priority
								
101	6	90	180	0	14	8		1
102	6.5	90	180	0	24	13		
103	7	90	180	0	68	15		
104	7.5	90	180	0	210	15		
105	7.8	90	180	0	420	15		
106	8.2	90	180	0	470	15		
								
107	6	70	180	0	14	8		2
108	6.5	70	180	0	24	13		
109	7	70	180	0	68	15		
110	7.5	70	180	0	210	15		
111	7.8	70	180	0	420	15		
112	8.2	70	180	0	470	15		
								
113	6	70	180	0	14	8		3
114	6.5	70	180	0	24	13		
115	7	70	180	0	40	25		
116	7.5	70	180	0	100	32		
117	7.8	70	180	0	160	40		
118	8.2	70	180	0	400	40		
								
119	6	90	180	0	14	8		4
120	6.5	90	180	0	24	13		
121	7	90	180	0	40	25		
122	7.5	90	180	0	100	32		
123	7.8	90	180	0	160	40		
124	8.2	90	180	0	400	40		
								
125	6	45	90	0	10	10		5
126	6	45	90	5	10	10		
127	6.5	45	90	0	18	18		
128	6.5	45	90	5	18	18		
129	7	45	90	0	44	23		
130	7.5	45	90	0	126	25		
131	7.8	45	90	0	180	25		
								
132	6	60	90	0	10	10		
133	6	60	90	5	10	10		
134	6.5	60	90	0	18	18		
135	6.5	60	90	5	18	18		
136	7	60	90	0	50	20		
137	7.5	60	90	0	150	20		
138	7.8	60	90	0	200	20

139	7.0	45	90	0	18	18
140	6.5	45	90	0	18	18
141	6.5	45	90	5	18	18
142	7.0	45	90	0	44	23
		

Completed Scenarios

1. Scenario101:
   1. Codebase: URS/URS/URS/URS
   2. Operator: PJM
   3. Results Staged:/home/broadband-01/maechlin/flingstudy/Scenario101
   4. Total Files: 22Gb
   5. outdata: 2.0Gb
   6. Starttime: May 19 10:34:30 PDT 2012
   7. Endtime: May 19 12:09:21 PDT 2012
   8. Cores: 16

1. Scenario102:
   1. Codebase: URS/URS/URS/URS
   2. Operator: PJM
   3. Results Staged:/home/broadband-01/maechlin/flingstudy/Scenario102
   4. Total Files: 22Gb
   5. outdata: 2.0Gb
   6. Starttime: May 19 20:30:40 PDT 2012
   7. Endtime: May 20 00:16:31 PDT 2012
   8. Cores: 16

1. Scenario140:
   1. Codebase: URS/URS/URS/URS
   2. Operator: PJM
   3. Results Staged:/home/broadband-01/maechlin/flingstudy/Scenario140
   4. Total Files: 28Gb
   5. outdata: 2.5Gb
   6. Starttime: May 15 14:54:44 PDT 2012
   7. Endtime: May 16 04:37:16 PDT 2012
   8. Cores: 16

1. Scenario141:
   1. Codebase: URS/URS/URS/URS
   2. Operator: PJM
   3. Results Staged:/home/broadband-01/maechlin/flingstudy/Scenario141
   4. Total Files: 28Mb
   5. outdata: 2.5Gb
   6. Starttime: Mon May 14 22:05:02 PDT 2012
   7. Endtime: May 15 11:20:47 PDT 2012
   8. Cores: 16

1. Scenario142:
   1. Codebase: URS/URS/URS/URS
   2. Operator: PJM
   3. Results Staged:/home/broadband-01/maechlin/flingstudy/Scenario142
   4. Total Files: 64Mb
   5. outdata: 4.7Gb
   6. Starttime: May 16 10:48:00 PDT 2012
   7. Endtime: May 18 10:17:28 PDT 2012
   8. Cores: 16

Related Entries

• Broadband Platform
• CyberShake
• Broadband Terminology