M8 Data Products - Revision history

Maechlin at 23:04, 9 April 2011

2011-04-09T23:04:38Z

Eqadmin at 17:41, 7 October 2010

2010-10-07T17:41:33Z

Eqadmin at 17:26, 7 October 2010

2010-10-07T17:26:05Z

Sandarsh: /* M8 Data Products */

2010-10-07T00:13:23Z

M8 Data Products

Sandarsh: /* M8 Data Products */

2010-10-07T00:12:07Z

M8 Data Products

Maechlin at 20:43, 6 October 2010

2010-10-06T20:43:00Z

Maechlin at 20:17, 1 October 2010

2010-10-01T20:17:52Z

Maechlin at 20:16, 1 October 2010

2010-10-01T20:16:10Z

Maechlin at 20:15, 1 October 2010

2010-10-01T20:15:41Z

Maechlin at 18:25, 29 September 2010

2010-09-29T18:25:36Z

@@ Line 9: / Line 9: @@
 **[http://scecdata.usc.edu/maechling/M8_SAF_Surface_Trace_detailed.kml M8 San Andreas Fault Trace 80m Resolution (KML Format)]
 **[[media:M8-source-gm.pdf]]
-**[http://scecdata.usc.edu/maechling/M8_Region_SAF_Epicenter.kml M8 Simulation Region, San Andreas Fault Trace, and M8 Epicenter in Lat,Lon (KML Format)]
+**[http://hypocenter.usc.edu/research/scecdata/M8_Region_SAF_Epicenter.kml M8 Simulation Region, San Andreas Fault Trace, and M8 Epicenter in Lat,Lon (KML Format)]
 *'''M8 Simulation Outputs Data Sets'''

@@ Line 17: / Line 17: @@
 **[http://visservices.sdsc.edu/projects/scec/m8/1.0/ SDSC M8 Visualizations]
 **[http://visservices.sdsc.edu/projects/scec/ SDSC Visualization Services SCEC Home Page]
-**[[VShaker]] Building Response Simulations
+**[[VShaker#M8 Building Response Study]] Simulations
 **[http://scec.usc.edu/websims/repo/m8/ws-index.html Websims M8 Data Page]
 <qt>file=M8-1.0-Vmag-1Mx_720_test.mp4|width=720|height=420|autoplay=false|controller=true</qt>

@@ Line 17: / Line 17: @@
 **[http://visservices.sdsc.edu/projects/scec/m8/1.0/ SDSC M8 Visualizations]
 **[http://visservices.sdsc.edu/projects/scec/ SDSC Visualization Services SCEC Home Page]
-**[[Virtual Shaker]] Building Response Simulations
+**[[VShaker]] Building Response Simulations
 **[http://scec.usc.edu/websims/repo/m8/ws-index.html Websims M8 Data Page]
 <qt>file=M8-1.0-Vmag-1Mx_720_test.mp4|width=720|height=420|autoplay=false|controller=true</qt>

@@ Line 19: / Line 19: @@
 **[[Virtual Shaker]] Building Response Simulations
 **[http://scec.usc.edu/websims/repo/m8/ws-index.html Websims M8 Data Page]
-<qt>file=M8-1.0-Vmag-1Mx_720_test.mp4|width=720|height=404|autoplay=false|controller=true</qt>
+<qt>file=M8-1.0-Vmag-1Mx_720_test.mp4|width=720|height=420|autoplay=false|controller=true</qt>
 [[File:M8Rupture.png|256px|thumb|right|Fig 1: M8 Rupture extended for 545km along the Southern San Andreas Fault]]

@@ Line 19: / Line 19: @@
 **[[Virtual Shaker]] Building Response Simulations
 **[http://scec.usc.edu/websims/repo/m8/ws-index.html Websims M8 Data Page]
 [[File:M8Rupture.png|256px|thumb|right|Fig 1: M8 Rupture extended for 545km along the Southern San Andreas Fault]]

← Older revision		Revision as of 20:43, 6 October 2010
Line 1:		Line 1:
−	~~== M8 Mesh Specifications ==~~
−
−	~~a proposal for volume output box. With these specifications, the box to be less than 14 GB in memory requirement to fit into a single node. By skipping second grid,~~
−
−	~~10125 NX = x model dimension in nodes~~
−	~~5000 NY = y model dimension in nodes~~
−	~~1060 NZ = z model dimension in nodes~~
−
−	~~75 NPX = number of procs in the x direction~~
−	~~40 NPY = number of procs in the Y direction~~
−	~~10 NPZ = number of procs in the Z direction~~
−
−
−	~~Volume output range should be this way:~~
−
−	~~1001 NBGX2 = first x node to contain receivers~~
−	~~9000 NEDX2 = last x node to contain receivers~~
−	~~2 NSKPX2 = skip of nodes containing x receivers~~
−	~~501 NBGY2 = first y node to contain receivers~~
−	~~4500 NEDY2 = last y node to contain receivers~~
−	~~2 NSKPY2 = skip of nodes containing y receivers~~
−	~~1 NBGZ2 = first z node to contain receivers~~
−	~~900 NEDZ2 = last z node to contain receivers~~
−	~~2 NSKPZ2 = skip of nodes containing z receivers~~
−
−	~~80 NTISKP2 = time skip of seismograms (every nth step)~~
−
−	~~This would generate 4000x2000x450x4bytes --> 13.4GB each component and step, that is 39 TB size outputs in total.~~
−
	== M8 Data Products ==		== M8 Data Products ==

@@ Line 1: / Line 1: @@
 == M8 Mesh Specifications ==
-a proposal for volume output box, please let me know you have any
+a proposal for volume output box. With these specifications, the box to be less than 14 GB in memory requirement to fit into a single node. By skipping second grid,
-> suggestions. I came up with this size because Amit wants the box to be less
-> than 14 GB in memory requirement to fit into a single node. By skipping
+NX            = x model dimension in nodes
-> second grid,
+NY            = y model dimension in nodes
+NZ            = z model dimension in nodes
->     10125 NX            = x model dimension in nodes
->      5000 NY            = y model dimension in nodes
+  NPX           = number of procs in the x direction
->      1060 NZ            = z model dimension in nodes
+  NPY           = number of procs in the Y direction
+  NPZ           = number of procs in the Z direction
->       75  NPX           = number of procs in the x direction
 Volume output range should be this way:
-−
 NBGX2         = first x node to contain receivers
 NEDX2         = last x node to contain receivers
@@ Line 42: / Line 25: @@
 NTISKP2       = time skip of seismograms (every nth step)
 == M8 Data Products ==

← Older revision		Revision as of 20:16, 1 October 2010
Line 1:		Line 1:
	== M8 Mesh Specifications ==		== M8 Mesh Specifications ==

		+	a proposal for volume output box, please let me know you have any
		+	> suggestions. I came up with this size because Amit wants the box to be less
		+	> than 14 GB in memory requirement to fit into a single node. By skipping
		+	> second grid,
		+	>
		+	> 10125 NX = x model dimension in nodes
		+	> 5000 NY = y model dimension in nodes
		+	> 1060 NZ = z model dimension in nodes
		+	>
		+	> 75 NPX = number of procs in the x direction
		+	> 40 NPY = number of procs in the Y direction
		+	> 10 NPZ = number of procs in the Z direction
		+	>
		+	> 1001 NBGX2 = first x node to contain receivers
		+	> 9000 NEDX2 = last x node to contain receivers
		+	> 501 NSKPX2 = skip of nodes containing x receivers
		+	> 4500 NBGY2 = first y node to contain receivers
		+	> 5000 NEDY2 = last y node to contain receivers
		+	> 2 NSKPY2 = skip of nodes containing y receivers
		+	> 1 NBGZ2 = first z node to contain receivers
		+	> 900 NEDZ2 = last z node to contain receivers
		+	> 2 NSKPZ2 = skip of nodes containing z receivers
		+	>
		+	> 80 NTISKP2 = time skip of seismograms (every nth step)
		+	>
		+	> This would generate 4000x2000x450x4bytes --> 13.4GB each component and step,
		+	> that is 39 TB size outputs in total.

	Volume output range should be this way:		Volume output range should be this way:

← Older revision		Revision as of 20:15, 1 October 2010
Line 1:		Line 1:
−	~~'''~~M8 Data Products~~'''~~	+	== M8 Mesh Specifications ==
		+
		+
		+	Volume output range should be this way:
		+
		+	1001 NBGX2 = first x node to contain receivers
		+	9000 NEDX2 = last x node to contain receivers
		+	2 NSKPX2 = skip of nodes containing x receivers
		+	501 NBGY2 = first y node to contain receivers
		+	4500 NEDY2 = last y node to contain receivers
		+	2 NSKPY2 = skip of nodes containing y receivers
		+	1 NBGZ2 = first z node to contain receivers
		+	900 NEDZ2 = last z node to contain receivers
		+	2 NSKPZ2 = skip of nodes containing z receivers
		+
		+	80 NTISKP2 = time skip of seismograms (every nth step)
		+
		+	== M8 Data Products ==
		+
	The following data products are inputs or outputs from the SCEC [[M8]] Project.		The following data products are inputs or outputs from the SCEC [[M8]] Project.

@@ Line 2: / Line 2: @@
 The following data products are inputs or outputs from the SCEC [[M8]] Project.
-'''*M8 Simulation Input Data Sets'''
+*'''M8 Simulation Input Data Sets'''
 **[http://scec.usc.edu/websims/repo/m8/data/trace.kml M8 rupture trace lon/lat (KML format)]
 **[http://scecdata.usc.edu/maechling/m8_trace_80m1.txt M8 rupture trace lat,long, UTM, x,y(ASCII)]
@@ Line 10: / Line 10: @@
 **[http://scecdata.usc.edu/maechling/M8_Region_SAF_Epicenter.kml M8 Simulation Region, San Andreas Fault Trace, and M8 Epicenter in Lat,Lon (KML Format)]
-'''*M8 Simulation Outputs Data Sets'''
+*'''M8 Simulation Outputs Data Sets'''
 **[http://scec.usc.edu/websims/repo/m8/ws-index.html M8 Data on SCEC Websims]
 **[[SCEC Visualization Projects]]