Difference between revisions of "Registering CS173 into UCVM"

From SCECpedia
Jump to navigationJump to search
Line 1: Line 1:
 
This page details the steps involved in delivering a velocity mesh to John Shaw and Andreas Plesch, so that the Harvard group's Central California basins can be integrated into a velocity model, which can be fed back into UCVM and used for CyberShake.
 
This page details the steps involved in delivering a velocity mesh to John Shaw and Andreas Plesch, so that the Harvard group's Central California basins can be integrated into a velocity model, which can be fed back into UCVM and used for CyberShake.
  
== Velocity Mesh region ==
+
== Velocity mesh region ==
  
The region we will extract is 560 km x 1218 km x 50.4 km, with 55 degree rotation counter-clockwise.  The corner points are approximately  
+
The region we will extract is 560 km x 1218 km x 50.4 km, with 55 degree rotation counter-clockwise.  The mesh will have 175m grid point spacing.  The corner points are approximately  
  
 
  W: (37.30489, -127.62831)
 
  W: (37.30489, -127.62831)
Line 11: Line 11:
  
 
[[File:Velocity_Mesh_with_models.png|thumb|left|600px|The mesh is depicted in white; the region covered by CCA-06 is in blue, by CVM-S4.26 in red, and by USGS Bay Area in green.]]
 
[[File:Velocity_Mesh_with_models.png|thumb|left|600px|The mesh is depicted in white; the region covered by CCA-06 is in blue, by CVM-S4.26 in red, and by USGS Bay Area in green.]]
 +
 +
== Mesh extraction process ==
 +
 +
To deliver the mesh, Scott will follow the following procedure:
 +
 +
#CyberShake processing tools will be used to construct a mesh, with the location of each point defined as km offsets from the center of the mesh at the surface.
 +
#The location of each mesh point will be redefined as a UTM easting and northing, by translating the center of the mesh from lat/lon to UTM coordinates in Zone 11 and then applying the offsets.
 +
#The Proj4 package will be used to convert the UTM coordinates at each point into a latitude and longitude value, to 5 decimal places.
 +
#This list of points will be used to query UCVM and create a velocity mesh.  Additionally, we will query the USGS topo model in UCVM to obtain the surface elevation at each point.
 +
#Smoothing will be applied to the velocity mesh for all points within 10 km of an interface, by averaging the neighbors for 10km in the N, S, E, and W directions.
 +
#Scott will deliver three meshes (one each with Vp, Vs, and rho) in fast y, x, z binary format with 4-byte floats, a list of the elevation of each surface point, a list of the coordinates of each surface point in lat/lon and UTM zone 11, and MD5 sums for all products.

Revision as of 17:35, 26 October 2017

This page details the steps involved in delivering a velocity mesh to John Shaw and Andreas Plesch, so that the Harvard group's Central California basins can be integrated into a velocity model, which can be fed back into UCVM and used for CyberShake.

Velocity mesh region

The region we will extract is 560 km x 1218 km x 50.4 km, with 55 degree rotation counter-clockwise. The mesh will have 175m grid point spacing. The corner points are approximately

W: (37.30489, -127.62831)
N: (41.59023, -124.28641)
E: (35.17113, -112.97233)
S: (31.19740, -116.67400)
The mesh is depicted in white; the region covered by CCA-06 is in blue, by CVM-S4.26 in red, and by USGS Bay Area in green.

Mesh extraction process

To deliver the mesh, Scott will follow the following procedure:

  1. CyberShake processing tools will be used to construct a mesh, with the location of each point defined as km offsets from the center of the mesh at the surface.
  2. The location of each mesh point will be redefined as a UTM easting and northing, by translating the center of the mesh from lat/lon to UTM coordinates in Zone 11 and then applying the offsets.
  3. The Proj4 package will be used to convert the UTM coordinates at each point into a latitude and longitude value, to 5 decimal places.
  4. This list of points will be used to query UCVM and create a velocity mesh. Additionally, we will query the USGS topo model in UCVM to obtain the surface elevation at each point.
  5. Smoothing will be applied to the velocity mesh for all points within 10 km of an interface, by averaging the neighbors for 10km in the N, S, E, and W directions.
  6. Scott will deliver three meshes (one each with Vp, Vs, and rho) in fast y, x, z binary format with 4-byte floats, a list of the elevation of each surface point, a list of the coordinates of each surface point in lat/lon and UTM zone 11, and MD5 sums for all products.