Difference between revisions of "UCVM Review"
Line 1: | Line 1: | ||
These links are information about the current UCVM software. | These links are information about the current UCVM software. | ||
+ | |||
+ | == UCVM-Python Tutorials == | ||
+ | Training Day 1: | ||
+ | *[http://hypocenter.usc.edu/research/Goulet/ucvmTrainingVideos/ Session 1] | ||
+ | |||
+ | Additional training found on hypocenter (4 videos in the root here): | ||
+ | *[http://hypocenter.usc.edu/research/ucvm/17.3.0/ Sessions 2-5] | ||
== Example PBS scripts == | == Example PBS scripts == |
Revision as of 21:15, 1 November 2017
These links are information about the current UCVM software.
Contents
- 1 UCVM-Python Tutorials
- 2 Example PBS scripts
- 3 Test UCVMC Install on Blue Waters and Titan
- 4 confirm en-jui projection issue fixed
- 5 basin_query z2500 first occurence or second occurence test
- 6 basin_query serial and mpi tests
- 7 mpi ucvm2mesh tests
- 8 Basin region Specs
- 9 Velocity mesh plotting scripts from CyberShake codebase
- 10 Introductory Presentations
- 11 Related Entries
UCVM-Python Tutorials
Training Day 1:
Additional training found on hypocenter (4 videos in the root here):
Example PBS scripts
Test UCVMC Install on Blue Waters and Titan
- Install UCVMC 17.1 on Blue Water and Titans.
- Regenerate ucvm2mesh_mpi meshes and confirm them match ones from USC
confirm en-jui projection issue fixed
DG made a change to fix projection issue in CCA06. Confirm this is in latest UCVMC
basin_query z2500 first occurence or second occurence test
- goal of this test is to evaluate the difference between results for the z2500 test. We will test the impact of different methods for selecting the z2500 values from a velocity model. Some algorithms return the first occurence of the specified Vs, or the second occurence, or the last occurence found. We need to document the algorithms available in ucvmc, and show example return values for each.
basin_query serial and mpi tests
- The goal of this test is to evaluate the results from basin_query and basin_query_mpi to demonstrate the produce the same results.
- We determined that the serial code returns
mpi ucvm2mesh tests
- goal of this test is to construct AWP test meshes using both ucvm2mesh and ucvm2mesh_mpi.
- Then we want to compare the resulting meshes and make sure they are identical
- ucvmc Installation instructions need to be updated to describe how to create mpi version if running on usc hpc.
Basin region Specs
CCA:
- minLat = 33.35
- minLon = -123
- nx = 1551
- ny = 1201
- gridSpacing = 0.005 m
CVM-S4.26:
- minLat = 31;
- minLon = -121;
- nx = 1701;
- ny = 1101;
- gridSpacing = 0.005 degrees
- define depth
When we extract these basin data sets as binary regular mesh format, we will check them by plotting and comparing with previous versions. We need separate files for Z1.0 and Z2.5 in meters.
The binary files are 4 byte float, little endian, fast XY, no rotation. Here are the formulas for lat/lon at a given x/y index:
lon = xIndex * gridSpacing + minLon lat = yIndex * gridSpacing + minLat
and for calculating the file position for a given xIndex/yIndex:
filePos = 4 * (nx * yIndex + xIndex)
The first data point is bottom left (at minX, minY).
Velocity mesh plotting scripts from CyberShake codebase
As part of the CyberShake work, we've developed a few Python scripts for plotting horizontal cross-sections (plot_horiz_slice.py), vertical cross-sections (plot_vertical_slice.py), and profile plots (plot_profile.py). The scripts are available in the CyberShake SVN repository, at http://source.usc.edu/svn/cybershake/import/trunk/UCVM/smoothing/ . As input, they expect a mesh in AWP format, and also a model coords file, which contains a listing of the lat/lon values for each surface point in the mesh (this is used for decimation purposes).
Sample plots produced using these scripts can be seen here.