UCVM Review
From SCECpedia
Jump to navigationJump to searchThese links are information about the current UCVM software.
Contents
- 1 Example PBS scripts
- 2 Test UCVMC Install on Blue Waters and Titan
- 3 confirm en-jui projection issue fixed
- 4 basin_query z2500 first occurence or second occurence test
- 5 basin_query serial and mpi tests
- 6 mpi ucvm2mesh tests
- 7 Basin region Specs
- 8 notes on basin data
- 9 Introductory Presentations
- 10 Related Entries
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
notes on basin data
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).
