Difference between revisions of "UCVM Review"

From SCECpedia
Jump to navigationJump to search
 
(73 intermediate revisions by 4 users not shown)
Line 1: Line 1:
−
These links are information about the current UCVM software.
+
== Basin Depth plots at -118.76, 34.0 ==
 +
*[[Depth plot Review]]
  
−
== basin_query z1000 first occurence or second occurence test ==
+
== Projection Correction issues ==
−
* goal of this test is to evaluate the difference between results for the z1000 test using difference rules for which z1000 depth to return, the first occurence of the specified Vs, or the second occurence, or something else. We need to document the algorithms available in ucvmc, and show example return values for each.
+
*[[Final Projection Review Result]]
 +
*[[CCA06 Projection Review]]
  
−
== basin_query serial and mpi tests ==
+
== Result of latest Basin Query ==
−
* goal of this test is to evaluate the results from basin_query and basin_query_mpi to demonstrate the produce the same results.
+
*[[Final CCA06 Crossings Result]] Generated using updated UCVM v17.1 with CCA06 with updated projection fix
 +
*[[Basin Query Depth Profile and Cross Section Result]]
 +
*[[Basin Query Result]] - Generated using UCVM v17.1 updated with original CCA06
  
−
== mpi ucvm2mesh tests ==
+
== CCA Model Plots and Notes ==
−
* 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
+
*[[Basin Query Notes]]
−
* ucvmc Installation instructions need to be updated to describe how to create mpi version if running on usc hpc.
+
*[[CCA06 Basin Depth]]
 +
*[http://hypocenter.usc.edu/research/ucvmc/CCA0to2k.pptx CCA Plots 0k to 2k]
 +
*[http://hypocenter.usc.edu/research/ucvmc/CCA0to2k_gtl.pptx CCA Plots 0k to 2k w/ GTL]
 +
*[http://hypocenter.usc.edu/research/ucvmc/CCA0to70k.pptx CCA Plots 0k to 70k]
  
−
== notes on basin data =
+
== Basin Depth Algorithm Description ==
−
<pre>
+
*[http://hypocenter.usc.edu/research/ucvm/17.3.0/docs/availablemodels.html#operators Basin Depth Algorithm]
 +
*[https://scec.usc.edu/scecpedia/Study_17.3_Data_Products#Velocity_Maps Basin Depth Maps - OpenSHA]
 +
*[http://scec.usc.edu/scecpedia/CCA06_Basin_Depth CCA Basin Depth]
 +
*[http://scec.usc.edu/scecpedia/CVM4.26_Basin_Depth CVM426 Basin Depth]
 +
*[https://scec.usc.edu/scecpedia/File:Summary_of_z_values.pptx Summary of Z values (GMPEs) and related verification and science tasks]
  
−
When I receive values from Scott I will check them by plotting and comparing with previous versions. I need separate files for Z1.0 and Z2.5 in meters.
+
== Basin_Query Previous Results ==
 +
Binary Z files used in OpenSHA, along with some metadata, are posted here:
  
−
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:
+
*4.26-M01: https://github.com/opensha/opensha-commons/tree/master/src/resources/data/site/CVM4i26
 +
*CCA06: https://github.com/opensha/opensha-commons/tree/master/src/resources/data/site/CCAi6
  
−
lon = xIndex * gridSpacing + minLon
+
We plan to implements a way to read these files and plot them in python which can be included with UCVM. Plotting would be similar to existing horizontal slide plotting scripts (which are likely included in both versions of UCVM, though I have not used them), and will be a useful feature going forward. Once that tool exists, comparisons will become easier. If in the meantime help is needed extracting individual values from these files, there is an OpenSHA tool which can access them (via Java).
−
lat = yIndex * gridSpacing + minLat
 
  
−
and for calculating the file position for a given xIndex/yIndex:
+
== Velocity mesh plotting scripts from CyberShake codebase ==
 +
As part of the CyberShake work, we've developed a few Python scripts for plotting horizontal cross-sections (plot_horiz_slice.py), vertical cross-sections (plot_vertical_slice.py), and profile plots (plot_profile.py).  The scripts are available in the CyberShake SVN repository, at http://source.usc.edu/svn/cybershake/import/trunk/UCVM/smoothing/ .  As input, they expect a mesh in AWP format, and also a [[CyberShake_Code_Base#Coord|model coords]] file, which contains a listing of the lat/lon values for each surface point in the mesh (this is used for decimation purposes). Sample plots produced using these scripts can be seen [[Study_16.9_Velocity_Plots|here]].
  
−
filePos = 4 * (nx * yIndex + xIndex)
+
== Review of Vp/Vs Ratio Checks in UCVM ==
−
 
+
*[[UCVM Vp/Vs Ratio]]
−
The first data point is bottom left (at minX, minY).
 
−
 
 
−
Kevin
 
−
 
 
−
On 7/11/2017 5:44 PM, Philip J. Maechling wrote:
 
−
> Kevin,
 
−
>  How are you checking the results you get form Scott? Maybe this cross check with UCVMC is not needed.
 
−
>  Also, what parameters are you extracting?
 
−
>  Also what is binary regular mesh format? binary 32bit floats? What order? fast x, y? or other?
 
−
> Thanks,
 
−
> Phil M.
 
−
> On 7/11/17 7:26 PM, Kevin Milner wrote:
 
−
>> Phil,
 
−
>>
 
−
>> Scott is working on generating these files for me with the python version of UCVM. I need binary regular meshes, which David generated for me from both codebases. If you want to proceed in parallel and you find the regular mesh generation utility in UCVMC, here are the parameters that specify the regions:
 
−
>>
 
−
>> CCA:
 
−
>>    minLat = 33.35
 
−
>>    minLon = -123
 
−
>>    nx = 1551
 
−
>>    ny = 1201
 
−
>>    gridSpacing = 0.005
 
−
>>
 
−
>> 4.26:
 
−
>>    minLat = 31;
 
−
>>    minLon = -121;
 
−
>>    nx = 1701;
 
−
>>    ny = 1101;
 
−
>>    gridSpacing = 0.005;
 
−
>>
 
−
>> Thanks,
 
−
>> Kevin
 
−
>>
 
−
>> On 07/11/2017 05:12 PM, Philip J. Maechling wrote:
 
−
>>> Scott and/or Kevin,
 
−
>>>
 
−
>>>  Christine reminded me that we want to re-extract CVM parameters. Can you send me the points of interest? And the parameter of interest for each point?
 
−
>>>
 
−
>>>  Although the last released version of UCVMC does not include CCA06, there may be some overlapping points I can try to query using UCVMC. I think the UCVMC software provides specialized queries that the UCVM does not have, queries that provide first occurrence, or last occurrence of the Vs value, as an option.
 
−
>>>
 
−
>>>  Also, we want to make sure that the changes to UCVM to support the depth of last occurance, are preserved in version control. Can either of your determine where those changes are saved in our source code?
 
−
>>>
 
−
>>>  Scott's version of UCVMC must support CCA06, since it was used to create the CyberShake 17.3 meshes, so presumably we could back engineer the addition of that model, if needed.
 
−
>>>
 
−
>>> Phil M.
 
−
 
 
−
 
 
−
</pre>
 
−
 
 
−
== Introductory Presentations ==
 
−
*[http://hypocenter.usc.edu/research/UCVM/UCVM_Intro.zip UCVM PPT Files]
 
  
 
== Related Entries ==
 
== Related Entries ==
 +
*[[UCVM Introduction]]
 +
*[[Planned UCVM Test Cases]]
 
*[[UCVM]]
 
*[[UCVM]]
 +
*[[USR]]
 +
*[[CVM-S]]
 +
*[[CVM-H]]

Latest revision as of 23:32, 29 January 2019

Basin Depth plots at -118.76, 34.0

Projection Correction issues

Result of latest Basin Query

CCA Model Plots and Notes

Basin Depth Algorithm Description

Basin_Query Previous Results

Binary Z files used in OpenSHA, along with some metadata, are posted here:

We plan to implements a way to read these files and plot them in python which can be included with UCVM. Plotting would be similar to existing horizontal slide plotting scripts (which are likely included in both versions of UCVM, though I have not used them), and will be a useful feature going forward. Once that tool exists, comparisons will become easier. If in the meantime help is needed extracting individual values from these files, there is an OpenSHA tool which can access them (via Java).

Velocity mesh plotting scripts from CyberShake codebase

As part of the CyberShake work, we've developed a few Python scripts for plotting horizontal cross-sections (plot_horiz_slice.py), vertical cross-sections (plot_vertical_slice.py), and profile plots (plot_profile.py). The scripts are available in the CyberShake SVN repository, at http://source.usc.edu/svn/cybershake/import/trunk/UCVM/smoothing/ . As input, they expect a mesh in AWP format, and also a model coords file, which contains a listing of the lat/lon values for each surface point in the mesh (this is used for decimation purposes). Sample plots produced using these scripts can be seen here.

Review of Vp/Vs Ratio Checks in UCVM

Related Entries

Retrieved from "https://strike.scec.org/scecwiki/index.php?title=UCVM_Review&oldid=22204"