Difference between revisions of "Cascadia Simulations"
From SCECpedia
Jump to navigationJump to search (Created page with "Daniel Roten, Kim Olsen have used AWP-ODC-GPU software to run simulations of large magnitude earthquakes in the Cascadia region. == Cascadia M9.2 == *Daniel Roten recently r...") |
|||
| Line 5: | Line 5: | ||
* These data are on the Alpine file system in | * These data are on the Alpine file system in | ||
| − | /gpfs/alpine/proj-shared/geo112/rotend/Cascadia.alpine/scen_13_a_S_66m_dm_summit_flt | + | /gpfs/alpine/proj-shared/geo112/rotend/Cascadia.alpine/scen_13_a_S_66m_dm_summit_flt |
| + | A previous version of the data is on Rhea/Titan in the directory: | ||
| + | |||
| + | /lustre/atlas/proj-shared/geo112/rotend/Cascadia/scen_8_a_N_66m_dm/output_sfc | ||
| + | |||
| + | == Metadatda == | ||
| + | |||
| + | Daniel Roten put together a list of metadata for NVIDIA to work with the Cascadia simulation output. | ||
| + | |||
| + | <pre> | ||
| + | Points in X: 9,720 | ||
| + | Points in Y: 16,065 | ||
| + | Resolution along X and Y: 66.666 m | ||
| + | The projection is UTM for zone 10. There is no rotation, with the X | ||
| + | axis pointing from west to east and the Y axis from south to north. | ||
| + | The UTM coordinates for the X and Y axis are given in the two attached | ||
| + | ASCII files. | ||
| + | The sampling interval in the output is 40 ms (250 samples per second). | ||
| + | The total simulation duration is 450 seconds. | ||
| + | |||
| + | The time step used in the finite difference simulation was 4 ms, and | ||
| + | 102,000 time steps were computed. | ||
| + | |||
| + | The output files are binary, and contain ground velocities (m/s) as | ||
| + | 32-bit floating point numbers. There is no file header. | ||
| + | Each component is saved in separate files, and the data are aggregated | ||
| + | in files containing 100 time steps. The naming convention is | ||
| + | S%c_0_%07d, where the character stands for the component (X, Y or Z), | ||
| + | the 7-digit number for the last time step in the file (e.g., 1000 for | ||
| + | the first file, and 102,000 for the last one). | ||
| + | Inside each binary file, X increases fastest, followed by Y, and time t increasing slowest. | ||
| + | |||
| + | </pre> | ||
| + | |||
| + | == Animations: == | ||
| + | Daniel Roten created a sample visualization done from a similar simulation (same resolution, but different scenario), which you might want to share along with the data: | ||
| + | |||
| + | *[https://drive.google.com/file/d/12HQb5J8dS-ICg4K-SYVUqqyUFH0RyPrx/view Google Drive Movie] | ||
== Related Entries == | == Related Entries == | ||
*[[AWP-ODC]] | *[[AWP-ODC]] | ||
*[[CME Project]] | *[[CME Project]] | ||
Revision as of 23:06, 19 September 2019
Daniel Roten, Kim Olsen have used AWP-ODC-GPU software to run simulations of large magnitude earthquakes in the Cascadia region.
Cascadia M9.2
- Daniel Roten recently ran a simulation of a M9.2 Cascadia earthquake on Summit, to compare ground motions against the previous Titan simulations, using 375 V100 GPUs for 3:30 hrs.
- These data are on the Alpine file system in
/gpfs/alpine/proj-shared/geo112/rotend/Cascadia.alpine/scen_13_a_S_66m_dm_summit_flt
A previous version of the data is on Rhea/Titan in the directory:
/lustre/atlas/proj-shared/geo112/rotend/Cascadia/scen_8_a_N_66m_dm/output_sfc
Metadatda
Daniel Roten put together a list of metadata for NVIDIA to work with the Cascadia simulation output.
Points in X: 9,720 Points in Y: 16,065 Resolution along X and Y: 66.666 m The projection is UTM for zone 10. There is no rotation, with the X axis pointing from west to east and the Y axis from south to north. The UTM coordinates for the X and Y axis are given in the two attached ASCII files. The sampling interval in the output is 40 ms (250 samples per second). The total simulation duration is 450 seconds. The time step used in the finite difference simulation was 4 ms, and 102,000 time steps were computed. The output files are binary, and contain ground velocities (m/s) as 32-bit floating point numbers. There is no file header. Each component is saved in separate files, and the data are aggregated in files containing 100 time steps. The naming convention is S%c_0_%07d, where the character stands for the component (X, Y or Z), the 7-digit number for the last time step in the file (e.g., 1000 for the first file, and 102,000 for the last one). Inside each binary file, X increases fastest, followed by Y, and time t increasing slowest.
Animations:
Daniel Roten created a sample visualization done from a similar simulation (same resolution, but different scenario), which you might want to share along with the data:
