scec cvms and the unified community velocity model ......-regular grid in utm space cybershake study...

SCEC CVMs and the Unified Community Velocity Model (UCVM) Software

Philip Maechling ([email protected])SCEC Community Velocity Model Technical Activity Group Workshop

7 Sept 2019Palm Springs, California

Southern California Earthquake Center

Outline of Talk

Southern California Earthquake Center 2

Role in SCEC CVM DevelopmentSCEC CVMs used in ground motion modelingGeneral Types of SCEC CVMsUCVM SoftwareUpdates in Latest Version of UCVMFuture SCEC Community Model Development

Role in SCEC CVM Model Activities (2002-2019)


• As the software lead on the SCEC Community Modeling Environment project, I began working with and maintaining the SCEC Community Velocity Models (then CVM-S2) in 2002.

• I now lead the SCEC software group that maintains the software and data files for the SCEC CVMs and to develop software to distribute and use CVMs.

• In my experience, the primary user of SCEC CVMs are scientists and engineering performing ground motion modeling research.

• I’m currently involved in developing software and web pages in support of other SCEC Community Models including UCVM software, CFM Web viewer, and Geological Framework Model (GFM) Web viewer.

Agenda



SCEC’s Community Velocity Models are implemented using data files and computer programs that provide access to seismic velocity models that define location-specific seismic properties including Vp, Vs, and density (rho).

Other crustal properties used in ground motion modeling, such as Qp, Qs, are typically not provided by the CVMs and are calculated externally often scaled on CVM model parameters such as Vs.

SCEC researchers have developed several alternative California velocity models using different data sources, and alternative data integration methods. Ground motion modelers want to run simulations using different California velocity models and compare results.

Standard Parameters returned by CVMs


Coverage regions for CVMs registered into UCVM v19.4

1. UCVM Digital Elevation model and Vs30 maps: yellow 2. CVM-S4: red, CVM-S4 geotechnical regions: red

polygons 3. CVM-H high resolution: small light blue square 4. CVM-H low resolution: larger light blue square 5. USGS High Resolution Bay Area: small white rectangle 6. USGS Low Resolution Bay Area: large white rectangle 7. CVM-S4.26 : green rectangle8. CVM-S4.26M01: green rectangle9. CCA 06: small yellow rectangle 10. CS17.3: large orange rectangle11. CS17.3-H: Harvard San Joaquin Basin Model: small

orange rectangle 12. CS17.3-H: Havard Santa Maria Basin Model: orange

square 13. CS18.8 CyberShake Study's Tiled Velocity Model: blue

rectangle


UCVM v19.4

http://hypocenter.usc.edu/research/ucvm/UCVM_v19_4_Coverage_Regions_v1.kml

SCEC CVM’s accessible through UCVM


Model Name Description UCVM Abbreviation Size

1 CVM-H v15.1 Southern California Velocity Model developed by Harvard Structural Geology Group with optional geotechnical layer cvmh 1.6G

2 CVM-S4 Southern California Velocity Model developed by SCEC, Caltech, USGS Group with geotechnical layer cvms 326M

3 CVM-S4.26 Tomography improved version of CVM-S4 with optional geotechnical layer(Ely-Jordan GTL, default is off) cvms5 1.2G

4 CVM-S4.26.M01 CVM-S4.26 with added geotechnical layer cvmsi 1.6G

5 CCA06 Central California Velocity Model with optional geotechnical layer (Ely-Jordan GTL, default is off) cca 9.2G

6 CS17.3 Cypershake study 17.3 Central California Velocity Model and optional geotechincal layer (Ely-Jordan GTL, default is off) cs173 72G

7 CS17.3-HCypershake study 17.3 Central California Velocity Model with San Joaquin and Santa Maria Basins data from Havard's group and optional geoptechnical layer (Ely-Jordan GTL, default is off)

cs173h 72G

8 CS18.8 CyperShake study 18.8 Northern and Central California Velocity Model and optional geotechincal layer (Ely-Jordan GTL, default is off) cs188 72G

9 USGS Bay Area Velocity Model 0.8.3 USGS developed San Francisco and Central California velocity model cencal 17M

10 Southern California 1D Modified Hadley Kanamori 1D model based on Hadley-Kanamori model 1d 8k

11 Northridge Region 1D Los Angeles Region 1D model used in SCEC Broadband Platform bbp1d -

Agenda



General Types of SCEC CVM Types


1. 1D ModelsHadley Kanamori, Northridge Region

2. Original 3D SCEC ModelCVM-S

3. Unified Structure Representation ModelCVM-H

4. Tomography Improved Models CVM-S4.26, CVM-S4.26-M01, CCA06

5. Simulation-Specific Tiled ModelsCS-17.3, CS-18.8

6. Embedded Basin ModelsCS-17.3-H

7. Geotechnical Layer ModificationsUse CVM-S4 GTL, Ely-Jordan Method, SVM Method

Modified Hadley-KanamoriSouthern California 1D Model

Modified Hadley-Kanamori 1D

BBP 1D Northridge Region Model

CVM-S4 (native gtl,bkg)

SCEC Unified Structural Representation (USR)

• An object-oriented, 3D description of crust and upper mantle velocity and fault structure in southern California • The USR development workflow seeks to use the best available data and techniques to constrain velocity structurre, and to ensures internal consistency of model components

CVM-HCFM

CVM-H 15.1 (native gtl, no bkg)






4. Full 3d Tomography Improved Models CVM-S4.26, CVM-S4.26-M01, CCA06




CVM-S4.26 (no gtl,no bkg)

CVM-S4.26 (no gtl, no bkg)









7. Geotechnical Layer ModificationsUser CVM-S4 GTL, Ely-Jordan Method, SVM Method

Example of Tiling Models (Bay Area,CCA06,CVM-S4.25M01,1D)

(0 depth (left), 1k depth (right))

24

UCVM queries each model in order, and return properties from first model that defines properties for the point

• SCEC simulation specific CVMs (CS-173, CS-18.8) combine multiple regional models to perform specific simulations. The modelers define a CVM model query order, output model resolution based on max simulation frequency and min Vs, the smoothing distances used at model interfaces, the type of geotechnical layer used for each model, and other simulation specific settings.

• Current storage of simulation specific models is impractical for most applications, except re-running the simulations they were created to run.


Figure: Vs at 1km depth showing CyberShake Study 18.8 velocity model tiling which defined model order as Bay Area, CCA06 with Ely GTL, and CVM-S4.25M01 which includes a 1D background model.






4. Tomography Improved Models CVM-H, CVM-S4.26, CVM-S4.26-M01, CCA06




- 6960 x 3200 x 288 cells(6.4 billion cells)

- 175m x 175m x 175m resolution

- origin at S corner at548969, 3459243, 0(UTM Z11, WGS84)

- Regular grid in UTM space

CyberShake Study CS17.3 mesh (cca06, bay area, cvm-s4.26.m01)

- 424 x 148 x 131 cells- 1000m x 1000m x 100m

resolution- Regular grid in UTM space- Registered relative to sea level

Embedding challenges:

- Translation (‘squashing’) of z coordinates to CCA registration (ground level near the surface)

- Grid orientations- Resolution refinement

San Joaquin basin

(Above) SCEC has developed a new Central California Velocity Model (coverage region indicated by larger white rectangle), called CS173-H, that includes detailed representations of the San Joaquin Basin (smaller white rectangle - center) and the Santa Maria Basin (small white square).

(Right) Vs at 1K depth and horizontal cross section of the CS173 velocity model show the original CS173 velocity model (Top Row) and the updated CS173-H velocity model (Bottom Row) which includes the San Joaquin and Santa Maria Basins.

Comparison of CVM CS173 and CS173-H

CVM CS173 without (left) and with (right) Basins

(Above) SCEC has developed a new Central California Velocity Model (coverage region indicated by larger white rectangle), called CS173-H, that includes detailed representations of the San Joaquin Basin (smaller white rectangle - center) and the Santa Maria Basin (small white square).

(Right) Vs at 1K depth and horizontal cross section of the CS173 velocity model show the original CS173 velocity model (Top Row) and the updated CS173-H velocity model (Bottom Row) which includes the San Joaquin and Santa Maria Basins.






4. Tomography Improved Models CVM-H, CVM-S4.26, CVM-S4.26-M01, CCA06




CVM-S4 ModelLocation 34.0, -118.0 (Whittier)

CVM-S4.26 Model with min Vs ~900m/s

CVM-S4.26 (no gtl,no bkg)

CVM-S4.26-M01 (native gtl, bkg)

CVM-S4.26.M01 (cvmsi) has tomography improvements and CVM-S4 (cvms) gtl properties restored to 0-300m. Used in CyberShake Study 15.4 because it provided Vs values down to min Vs of 500m/s used in study..

CVM-S4.26 (cvms5) is a tomographically improved version of CVM-S4 (cvms) which used a min Vs=900m/s during calculation. Defined on a 500m grid, with UCVM providing trilinear interpolation for queries to give smooth change in properties with depth. Min Vs values returned by this model is about 900m/s.

In order to provide low Vs values removed during the tomography process, UCVM and update Vp,Vs, rho values in the top 350 using the Ely-Jordan GTL method, which is based on using known Vs30 values to estimate velocities in the top 350m. The cvms5 model configuration file GTL_ON=True parameter must be set to add this GTL.

Impact of Ely GTL on Z2.5 Values

Agenda



1. Ground motion modelers want to compare ground motion simulations using alternative velocity models.

2. Goal was to create software tools for generating equivalent meshes from different velocity models (e.g. develop a standard way to query by depth for models that are query by elevation)

3. Needed to convert models from one projection to another.

4. Needed to combine CVMs and add background models.

5. Needed tools to query models provided on regular grids, including standard interpolation methods

Motivations for UCVM Development


Existing California Seismic velocity models: • are delivered in a variety of formats (on regular grids, rule-based software, custom

software interfaces) • may use different projections:• may provide their own query interface.

Examples include:• CVM-S4 – provides btest-in (Fortran) software interface• CVM-H - provides vx and vx-lite (C-language) software interface)• CCA06 - provides properties defined on 500m regular mesh• CenCal (USGS Bay Area Model) – provides properties defined in high and low

resolution etree structures.

Seismic Velocity Models Software


ucvm_query manual page:NAME

ucvm_query

SYNOPSISucvm_query [-h] [-f config] [-m model] [-c coordtype] [-v] [-z zmin,zmax]

DESCRIPTIONThe command ucvm_query queries an installed velocity model to retreive its material properties at a particular latitude and longitude.Any set of crustal and GTL velocity models may be selected and queried in order of preference. Points may be queried by (lon,lat,dep) or (lon,lat,elev) and the coordinate conversions for a particular model are handled transparently.

Common Parameters-h Displays the help message.-f Location of the configuration file, config, that tells the program which velocity models are installed.-m A comma-separated list of models to query.

Less Used Parameters-c Z-coordinate mode. Geo-depth (default) is "gd",

but queries can also be done by elevation as specified by "ge".-v Display model version information only.-z Specifies depth range for gtl/crust interpolation.

EXAMPLEucvm_query -f ../conf/ucvm.conf -m cvmsInput format is:

lon lat ZOutput format is:

lon lat Z surf vs30 crustal cr_vp cr_vs cr_rho gtl gtl_vp gtl_vs gtl_rho cmb_algo cmb_vp cmb_vs cmb_rho


$cd /home/ucvm/ucvm194/utilities$./plot_depth_profile.py -s 34,-118 -b 0 -e 20000 -d vp,vs,density -v 5 -c cvmh -o whittier_cvms_profile.png

After processing, the output file is found in/home/ucvm/ucvm194/utilities/whittier_cvmh_profile.png

CVM-H Results:


$cd /home/ucvm/ucvm194/utilities$./plot_depth_profile.py -s 34.0,-118.0 -b 0 -e 20000 -d vp,vs,density -v 5 -c cvms -o whittier_cvms_profile.png

After processing, the output file is found in/home/ucvm/ucvm194/utilities/whittier_cvms_profile.png

Comparison to CVM-S Profile


$ ./plot_cross_section.pyPlots a cross-section given two latitude, longitude points, a depth, the CVM to plot, and other settings.

Valid arguments:-s, --starting: starting depth for cross-section (meters)-e, --ending: ending depth for cross-section (meters)-h, --horizontal: horizontal spacing for cross-section (meters)-v, --vertical: vertical spacing for cross-section (meters)-d, --datatype: either 'vs', 'vp', 'rho', or 'poisson', without quotation marks-c, --cvm: one of the installed CVMs-a, --scale: color scale, either 's' for smooth, 'd' for discretized or 'b' for bi-color scale, without quotes-g, --gate: optional gate value for bi-color scale gate-b, --origin: origin latitude, longitude from which to start plot (e.g. 34,-118)-u, --destination: destination latitude, longitude to end plot (e.g. 35,-117)-f, --datafile: optional input filename-o, --outfile: optional png output filename

plot_cross_section.py Syntax


$cd /home/ucvm/ucvm194/utilities$./plot_cross_section.py -b 34.0,-118.75 -u 34.0,-117.5 -h 100 -v 100 -d vs -c cvmh -s 0.0 -e 10000.0 –a d –o cvmh_cross_section.png

After processing, the output file is found in/home/ucvm/ucvm194/utilities/cvmh_cross_section.png

CVM-H Results:


$cd /home/ucvm/ucvm194/utilities$./plot_cross_section.py -b 34.0,-118.75 -u 34.0,-117.5 -h 100 -v 100 -d vs -c cvms -s 0.0 -a d -e 10000.0 –o cvms_cross_section.png

After processing, the output file is found in/home/ucvm/ucvm194/utilities/cvmh_cross_section.png

Comparison to CVM-S


$ ./plot_horizontal_slice.pyPlots a horizontal slice given two bounding latitude and longitude co-ordinates,the CVM to plot, and a couple of other settings.

Valid arguments:-b, --bottomleft: bottom-left latitude, longitude (e.g. 34,-118)-u, --upperright: upper-right latitude, longitude (e.g. 35,-117)-s, --spacing: grid spacing in degrees (typically 0.01)-e, --depth: depth for horizontal slice in meters (e.g. 1000)-d, --datatype: either 'vs', 'vp', 'density', or 'poisson', without quotation marks-c, --cvm: one of the installed velocity models-a, --scale: color scale, either 's' for smooth or 'd' for discretized, without quotes-f, --datafile: optional binary input data filename-o, --outfile: optional png output filename

plot_horizontal_slice.py syntax


$ cd /home/ucvm/ucvm194/utilities$ ./plot_horizontal_slice.py -b 33.6,-118.5 -u 34.2,-117.9 -s 0.001 -e 1000.0 -d vs -a d -c cvmh -o cvmh_vs_map.png

Using parameters:

datafile = Nonelat1 = 33.6data_type = vslat2 = 34.2color = doutfile = cvmh_vs_map.pngspacing = 0.001cvm_selected = cvmhdepth = 1000.0lon1 = -118.5lon2 = -117.9

After processing, the output file is found in/home/ucvm/ucvm194/utilities/cvmh_vs_map.png

CVM-H Results


$ cd /home/ucvm/ucvm194/utilities$ ./plot_horizontal_slice.py -b 33.6,-118.5 -u 34.2,-117.9 -s 0.001 -e 1000.0 -d vs -a d -c cvms -o cvms_vs_map.png

Using parameters:

datafile = Nonelat1 = 33.6data_type = vslat2 = 34.2color = doutfile = cvms_vs_map.pngspacing = 0.001cvm_selected = cvmsdepth = 1000.0lon1 = -118.5lon2 = -117.9

After processing, the output file is found in/home/ucvm/ucvm194/utilities/cvmh_vs_map.png

Showing Alternative Velocity Model - CVMS


Vs at 1km depth for CVM-H v15.1 (left), for CVM-S4 (left center)

Comparison of CVM-S and CVM-H LA Basin Z1.0 and Z2.5 depths

49

Z2.5 depth for CVM-H (right center), and CVM-S4 (right)

Summary of UCVM Software Features1. UCVM provides a uniform query interface to several California velocity models. Models may be queried by

(lon,lat,depth) or (lon,lat,elev).

• ucvm_query: Linux command-line query tool

• API: C interface to UCVM

2. UCVM easily combine two or more regional velocity models together into one meta-model. Models are tiled in specified order.

3. Codes to modify top 350 meters as geotechnical layer using Ely-Jordan, and other methods.

4. Allows users to add 1D background models for regions outside CVM coverage

5. Create and populate meshes from any registered CVM in various formats including AWP (Cartesian meshes) and CMU/SCEC-formatted Etrees

6. Support parallel mesh building and population for very large meshes

7. Plotting and visualization scripts


Significant Usage of UCVM

• UCVM used to construct very large meshes for SCEC ground motion simulations (e.g. M8, CyberShake)

• UCVM used to construct Hercules Etrees comparing impact of CVMs on ground motion goodness-of-fit studies (e.g. Chino Hills event)

• UCVM used for to construct meshes for several SCEC CyberShake studies (e.g. 15.4, 17.3, 18.8)

• Used to support SCEC High Frequency (High-F) ground motion modeling group building high resolution (e.g. 20m resolution) meshes


Agenda


Role in SCEC CVM DevelopmentSCEC CVMs used in ground motion modelingGeneral Types of SCEC CVMsUCVM SoftwareUpdates in Latest Version of UCVM v19.4Future SCEC Community Model Development

SCEC UCVM v19.4 Improvements Include:


A new version of UCVM v19.4 was release earlier this year. Improvements include:

* Upgraded projection software from Proj4 to Proj-5.0.0* Updated Wills map used for Vs30 model from Wills 2006 to Wills 2015* Registered CCA06 a tomography-improved Central California Velocity Model* Registered CS17.3 a composite Central California VM used in CyberShake Study 17.3* Registered CS17.3-H a VM that adds San Joaquin and Santa Maria Basins to the CS17.3 model* Fixed the proper tiling of models to create a state-wide VM used in CyberShake Study 18.8 * Fixed the implementation of plugin schema for the dynamic loading of newer models* Added new cross-section plotting capability showing both elevation and depth * Expanded plotting scripts to preserve intermediate data product and metadata* Expanded processing results from basin_query_mpi to basin_query_mpi_complete* Expanded scalability of ucvm2mesh_mpi_layer

UCVM Vs30 values updated from Wills 2006 to Wills 2015

SCEC Open-Source UCVM Software

The current version of UCVM v19.4 is open-source software that can be downloaded, compiled using open-source Linux software development environment, and run on the users own computers. The source codes and data files are available for download from: https://github.com/SCECcode/UCVMC

A version of the UCVM software the runs in a Virtual Box containers is available for download from: http://scec.usc.edu/scecpedia/SSA_Velocity_Model_Workshop_2019

If you use the UCVM software in your research, please include a reference to this software. The preferred reference for the UCVM software is:

• Small, P., Gill, D., Maechling, P. J., Taborda, R., Callaghan, S., Jordan, T. H., Ely, G. P., Olsen, K. B., & Goulet, C. A. (2017). The SCEC Unified Community Velocity Model Software Framework. Seismological Research Letters, 88(5). https://doi.org/doi:10.1785/0220170082


https://github.com/SCECcode/UCVMC

http://scec.usc.edu/scecpedia/SSA_Velocity_Model_Workshop_2019

https://doi.org/doi:10.1785/0220170082

Agenda



Community Fault Model (CFM)Web Viewer - Beta


https://stress.scec.org/research/cfm-viewer/

https://stress.scec.org/research/cfm-viewer/

Prototype Geological Framework Model (GFM)Web Viewer


http://asperity.scec.org/GFM_web/web/viewer.php

http://asperity.scec.org/GFM_web/web/viewer.php

IRIS ParaView-based Tools for 3D model Visualizations


With SCEC CVM-S4.26.M01 formatted in NetCDF format, it can be visualized using IRIS Earth Model Collaboration ParaView software:http://ds.iris.edu/ds/products/emc/

http://ds.iris.edu/ds/products/emc/

Example proposal: ISO/IEC-19775-1 (X3D) for explicit geometry (CFM)

ISO/IEC-19775 is free and open

- Used in computer graphics- Focussed on mesh and grid geometry- Geospatial capability- Extensive Meta-data capability for labeling- Multiple encodings (XML, json, python ..)

<?xml version="1.0" encoding="utf-8"?><!DOCTYPE X3D PUBLIC "ISO//Web3D//DTD X3D 3.0//EN"

"http://www.web3d.org/specifications/x3d-3.0.dtd">

<X3D version='3.0' profile='Interchange'><head>

<meta name='filename' content='GeometricProperties.x3d'/></head><Scene>

<Shape><IndexedFaceSet coordIndex='0, 1, 3, -1, 0, 2, 3, -1'>

<Coordinate point='0 0 0, 1 0 0, 1 0 -1, 0.5 1 0'/><Color color='0.2 0.7 0.8, 0.5 0 0, 0.1 0.8 0.1, 0 0 0.7'/><Normal vector='0 0 1, 0 0 1, 0 0 1, 0 0 1'/><TextureCoordinate point='0 0, 1 0, 1 0.4, 1 1'/>

</IndexedFaceSet><Appearance>

<Material transparency='0.5'/><PixelTexture image='2 2 1 0xFF 0x80 0x80 0xFF'/>

</Appearance></Shape>

</Scene></X3D>

Forecasting Future CXM Model Developments


1. SCEC will develop more web-based tools for viewing, working with Community Models.2. SCEC will develop UCVM-like query software will return properties from multiple SCEC community models

including Geological Framework Model (GFM), Rheology Model, Thermal Model, and others.3. SCEC will increasingly adopt data management practices like use of Digital Object Identifiers (DOIs) and

registration of data sets for discovery by other researchers.4. SCEC will increase use of standardized formats (e.g. netcdf) to take advantage of existing meshing and model

building tools.5. Multiple groups will work to develop improved representation of top the 500m in velocity models, important in high

frequency ground motion simulations.6. Ground motion modelers will make greater use of topography in simulations.7. Ground motion modelers will need better tools to build multi-resolution meshes.8. SCEC will improved tools for viewing and reviewing models.9. Modelers will increase use of alternative, simulation centered projections, to reduce distortion of large regional

simulation volumes10.SCEC researchers will develop automated methods for near-optimal smoothing between different resolution

models, to enable embedding geotechnical models, in basin models, in regional crustal models, in global models.11.SCEC will develop CVM validation test suite. Users re-run ground motion simulations in the test suite to validate

CVM use in ground motion models.

End


Comments/Questions

[email protected]

Southern California Earthquake Center

scec cvms and the unified community velocity model ......-regular grid in utm space cybershake study...

Documents