Test Cases ucvm_query

Query by elevation, Query by depth

CVM-H provides a native query by elevation interface. We have constructed a set of test points in two forms, lat,lon,depth and an equivalnet lat,lon, elevation. Compare results when you call ucvm_query.py, give it query by depth file, and set query by depth, and you call ucvm_query.py, give it query by elevation file, and set query by elevation.

We called CVM-H through ucvm_query by elevation this way:

./bin/ucvm_query -f ./conf/ucvm.conf -m cvmh -c ge < ./tests/inputs/test_latlons_socal_pts_elev.txt > ucvm_cvmh_elev_results.txt

We called CVM-H through ucvm_query by depth this way:

./bin/ucvm_query -f ./conf/ucvm.conf -m cvmh -c gd < ./tests/inputs/test_latlons_socal_pts.txt > ucvm_cvmh_depth_results.txt

• Input Points for socal locations by depth

• Input Points for socal locations by elevation

The resulting material properties file:

• UCVM Queries CVM-H, Queryby elevation w/ elevation input file
• UCVM Queries CVM-H, Query by depth w/ depth input file

Show that each UCVM model returns values within its defined geographical region.

Show that topography and vs30 values are defined in California area, and are not defined outside that region.