-
Notifications
You must be signed in to change notification settings - Fork 3
GTL Testing
There are multiple GTL settings within ucvm, and the behavior of various combinations is not obvious. The following plots show the impact of various plotting configurations.
[ucvm@ac3e0e643150 target]$ ucvm_query -f /app/ucvm/conf/ucvm.conf -m cvmh < querypts.txt Using Geo Depth coordinates as default mode. -118.4810 34.3120 100.000 386.051 397.973 cvmh 1946.508 505.610 1880.905 none 0.000 0.000 0.000 crust 1946.508 505.610 1880.905 -118.5000 34.5000 100.000 573.044 527.718 cvmh 3994.835 2271.410 2392.620 none 0.000 0.000 0.000 crust 3994.835 2271.410 2392.620 -117.5000 33.5500 100.000 381.905 518.900 cvmh 5087.308 2795.410 2548.363 none 0.000 0.000 0.000 crust 5087.308 2795.410 2548.363 -117.5000 35.5000 100.000 721.905 394.017 cvmh 4855.963 2866.868 2513.006 none 0.000 0.000 0.000 crust 4855.963 2866.868 2513.006 -116.5000 34.4000 100.000 791.036 293.500 cvmh 4730.289 2751.258 2494.663 none 0.000 0.000 0.000 crust 4730.289 2751.258 2494.663
[ucvm@ac3e0e643150 target]$ ucvm_query -f /app/ucvm/conf/ucvm.conf -m cvmh,elygtl:ely -z 0,350 < querypts.txt Using Geo Depth coordinates as default mode. -118.4810 34.3120 100.000 386.051 397.973 cvmh 2139.914 672.340 1965.082 elygtl 0.000 397.973 0.000 ely 2226.984 600.934 1999.243 -118.5000 34.5000 100.000 573.044 527.718 cvmh 4398.315 2524.129 2448.169 elygtl 0.000 527.718 0.000 ely 3334.547 1485.425 2289.937 -117.5000 33.5500 100.000 381.905 518.900 cvmh 5074.826 2788.256 2546.395 elygtl 0.000 518.900 0.000 ely 3609.738 1589.793 2335.911 -117.5000 35.5000 100.000 721.905 394.017 cvmh 4860.199 2866.500 2513.634 elygtl 0.000 394.017 0.000 ely 3369.378 1523.207 2296.108 -116.5000 34.4000 100.000 791.036 293.500 cvmh 4713.636 2738.400 2492.270 elygtl 0.000 293.500 0.000 ely 3177.536 1389.021 2260.583
[ucvm@ac3e0e643150 target]$ ucvm_query -f /app/ucvm/conf/ucvm.conf -m cvmh,elygtl:linear -z 0,350 < querypts.txt Using Geo Depth coordinates as default mode. -118.4810 34.3120 100.000 386.051 397.973 cvmh 2139.914 672.340 1965.082 elygtl 0.000 397.973 0.000 linear 0.000 0.000 0.000 -118.5000 34.5000 100.000 573.044 527.718 cvmh 4398.315 2524.129 2448.169 elygtl 0.000 527.718 0.000 linear 0.000 0.000 0.000 -117.5000 33.5500 100.000 381.905 518.900 cvmh 5074.826 2788.256 2546.395 elygtl 0.000 518.900 0.000 linear 0.000 0.000 0.000 -117.5000 35.5000 100.000 721.905 394.017 cvmh 4860.199 2866.500 2513.634 elygtl 0.000 394.017 0.000 linear 0.000 0.000 0.000 -116.5000 34.4000 100.000 791.036 293.500 cvmh 4713.636 2738.400 2492.270 elygtl 0.000 293.500 0.000 linear 0.000 0.000 0.000
[ucvm@ac3e0e643150 target]$ ucvm_query -f /app/ucvm/conf/ucvm.conf -m cvmh < querypts.txt Using Geo Depth coordinates as default mode. -118.4810 34.3120 100.000 386.051 397.973 cvmh 2164.931 561.880 1975.122 none 0.000 0.000 0.000 crust 2164.931 561.880 1975.122 -118.5000 34.5000 100.000 573.044 527.718 cvmh 3571.999 1661.088 2329.946 none 0.000 0.000 0.000 crust 3571.999 1661.088 2329.946 -117.5000 33.5500 100.000 381.905 518.900 cvmh 3633.909 1606.619 2339.684 none 0.000 0.000 0.000 crust 3633.909 1606.619 2339.684 -117.5000 35.5000 100.000 721.905 394.017 cvmh 3221.180 1432.285 2269.012 none 0.000 0.000 0.000 crust 3221.180 1432.285 2269.012 -116.5000 34.4000 100.000 791.036 293.500 cvmh 3256.877 1437.267 2275.747 none 0.000 0.000 0.000 crust 3256.877 1437.267 2275.747
[ucvm@ac3e0e643150 target]$ ucvm_query -f /app/ucvm/conf/ucvm.conf -m cvmh,elygtl:ely -z 0,350 < querypts.txt Using Geo Depth coordinates as default mode. -118.4810 34.3120 100.000 386.051 397.973 cvmh 2139.914 672.340 1965.082 elygtl 0.000 397.973 0.000 ely 2226.984 600.934 1999.243 -118.5000 34.5000 100.000 573.044 527.718 cvmh 4398.315 2524.129 2448.169 elygtl 0.000 527.718 0.000 ely 3334.547 1485.425 2289.937 -117.5000 33.5500 100.000 381.905 518.900 cvmh 5074.826 2788.256 2546.395 elygtl 0.000 518.900 0.000 ely 3609.738 1589.793 2335.911 -117.5000 35.5000 100.000 721.905 394.017 cvmh 4860.199 2866.500 2513.634 elygtl 0.000 394.017 0.000 ely 3369.378 1523.207 2296.108 -116.5000 34.4000 100.000 791.036 293.500 cvmh 4713.636 2738.400 2492.270 elygtl 0.000 293.500 0.000 ely 3177.536 1389.021 2260.583
[ucvm@ac3e0e643150 target]$ ucvm_query -f /app/ucvm/conf/ucvm.conf -m cvmh,elygtl:linear -z 0,350 < querypts.txt Using Geo Depth coordinates as default mode. -118.4810 34.3120 100.000 386.051 397.973 cvmh 2139.914 672.340 1965.082 elygtl 0.000 397.973 0.000 linear 0.000 0.000 0.000 -118.5000 34.5000 100.000 573.044 527.718 cvmh 4398.315 2524.129 2448.169 elygtl 0.000 527.718 0.000 linear 0.000 0.000 0.000 -117.5000 33.5500 100.000 381.905 518.900 cvmh 5074.826 2788.256 2546.395 elygtl 0.000 518.900 0.000 linear 0.000 0.000 0.000 -117.5000 35.5000 100.000 721.905 394.017 cvmh 4860.199 2866.500 2513.634 elygtl 0.000 394.017 0.000 linear 0.000 0.000 0.000 -116.5000 34.4000 100.000 791.036 293.500 cvmh 4713.636 2738.400 2492.270 elygtl 0.000 293.500 0.000 linear 0.000 0.000 0.000
[ucvm@28d7188735e6 target]$ vs30_query -f /app/ucvm/conf/ucvm.conf -m cvms5 < vs30pts.txt -118.4810 34.3120 479.035 -118.5000 34.5000 542.880 -117.5000 33.5500 1488.633 -117.5000 35.5000 1301.073 -116.5000 34.4000 1297.697 [ucvm@28d7188735e6 target]$ vs30_query -f /app/ucvm/conf/ucvm.conf -m cvms5,elygtl:ely -z 0,350 < vs30pts.txt -118.4810 34.3120 209.404 -118.5000 34.5000 276.783 -117.5000 33.5500 313.116 -117.5000 35.5000 246.636 -116.5000 34.4000 200.306 [ucvm@28d7188735e6 target]$ vs30_query -f /app/ucvm/conf/ucvm.conf -m cvms5,elygtl:linear -z 0,350 < vs30pts.txt -118.4810 34.3120 0.000 -118.5000 34.5000 0.000 -117.5000 33.5500 0.000 -117.5000 35.5000 0.000 -116.5000 34.4000 0.000
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. We expect that Vs values in the top 300m will be lower for sites when the USE_GTL flag is set to 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_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:
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.
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: