Test Cases CVMH Flags

CVM-H GTL and 1D flags in ucvm.conf

The user can specify whether a geotechnical layer, based on Ely Vs30 technique is added to the top 300M of the cvm-h model, by editing a flag in the ucvm.conf file. The user can also include a 1D background model to extend CVM-H beyond its model boundary by editing a flag in the ucvm.conf file.

# The entries below are manually updated by the user, as needed.
#
# CVM-H model flags. The model defaults are:
# No 1D background model
# No GTL added
#
cvmh_param=USE_1D_BKG,False
cvmh_param=USE_GTL,False
#

We expect that Vs values in the top 300m will be lower for sites when the USE_GTL flag is set to true.

Plot the depth profile of 5 locations with the last one outside of the CVM-H boundary,

./plot_depth_profile.py -s 34,-118 -b 0  -e 10000 -d vs -v 10 -c cvmh -o cvmh_gtl_depth_pt1.png
./plot_depth_profile.py -s 33.2589,-115.4502 -b 0  -e 10000 -d vs -v 10 -c cvmh -o cvmh_gtl_dep
th_pt2.png
./plot_depth_profile.py -s 36.3121,-119.7785 -b 0  -e 10000 -d vs -v 10 -c cvmh -o cvmh_gtl_dep
th_pt3.png
./plot_depth_profile.py -s 33.8115,-116.6794 -b 0  -e 10000 -d vs -v 10 -c cvmh -o cvmh_gtl_dep
th_pt4.png
./plot_depth_profile.py -s 33.4494,-112.0749 -b 0  -e 10000 -d vs -v 10 -c cvmh -o cvmh_gtl_dep
th_pt5.png

Without GTL,

With GTL,

A cross plot through Southern part of CVM-H,

./plot_cross_section.py -b 33.25,-119 -u 36,-112 -h 1000 -v 10 -d vs -c cvmh -a d -s 0.0 -e 100
00 -o cvmh_gtl.png

Without GTL,

With GTL,

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

We ran this query without USE_GTL by setting conf/ucvm.conf file flag this way:

cvmh_param=USE_1D_BKG,False
cvmh_param=USE_GTL,False

We ran this query with USE_GTL by setting conf/ucvm.conf file flag this way:

cvmh_param=USE_1D_BKG,False
cvmh_param=USE_GTL,True

We posted the results on a SCEC Website at:

• USE_GTL_FALSE
• USE_GTL_True

This shows the the USE_GTL flag return different material properties in the top 500m. However, the columns showing combined results (from model and GTL) are identical. This suggests that the combined properties columns change only when an external GTL is returned from the UCVM. CVM-H internal GTL does not appear as a "combined" material properties, but rather as native model properties.

Show that the CVM-H USE_1D background model flag in ucvm.conf has effect

The user can specify a CVM-H configuration flag that enables or disables use of a 1D background model. We run ucvm_query twice, for a point outside the cvm-h region, and show that the flag takes effect. The default CVM-H flag is not to use a 1D background model. We expect ucvm to return material properties for regions outside of the CVM-H region when the 1D background model is true.

We called ucvm_query this way:

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

We ran this query without 1D bkg by setting conf/ucvm.conf file flag this way:

cvmh_param=USE_1D_BKG,False
cvmh_param=USE_GTL,False

We ran this query with 1D bkg by setting conf/ucvm.conf file flag this way:

cvmh_param=USE_1D_BKG,True
cvmh_param=USE_GTL,False

We posted the results on a SCEC Website at:

• 1D_BKG_True
• 1D_BKG_False