Difference between revisions of "M8 Simulation Specifications"
From SCECpedia
Jump to navigationJump to search| (One intermediate revision by the same user not shown) | |||
| Line 1: | Line 1: | ||
'''M8 Simulation Specifications''' | '''M8 Simulation Specifications''' | ||
| + | A fairly complete set of simulation specifications is given in this spec sheet. | ||
| + | |||
| + | *Summary of M8 Simulation Parameters:[[File:M8_Fact_Sheet_v4.pdf]] | ||
'''Region Definition''' | '''Region Definition''' | ||
| Line 35: | Line 38: | ||
This would generate 4000x2000x450x4bytes --> 13.4GB each component and step, that is 39 TB size outputs in total. | This would generate 4000x2000x450x4bytes --> 13.4GB each component and step, that is 39 TB size outputs in total. | ||
| + | |||
| + | == Related Entries == | ||
| + | *[[M8]] | ||
| + | *[[UCVM]] | ||
| + | |||
| + | == See Also == | ||
| + | *[[Main Page]] | ||
Latest revision as of 04:35, 9 April 2011
M8 Simulation Specifications A fairly complete set of simulation specifications is given in this spec sheet.
Region Definition
Timesteps
Min Vs
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.