Difference between revisions of "BBP CyberShake 2015"
(Redirected page to CyberShake Study 15.12) |
|||
| (11 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
| + | #redirect[[CyberShake Study 15.12]] | ||
| + | == Compuational Goal == | ||
| + | |||
| + | We are working on doing a series of broadband CyberShake runs, extending the 1 Hz deterministic results we generated in the spring with stochastic results from high-frequency implementation on the BBP. | ||
| + | |||
| + | Before we setup the calculation, we evaluate questions about the 1D velocity model needed for the high frequency results. It seems like there are three ways we could handle this in the context of CyberShake: | ||
| + | |||
| + | #Use the same model (LA Basin?) for all CyberShake sites and all ruptures. | ||
| + | #Select the model based on the CyberShake site, and use the same model for all ruptures on that site. | ||
| + | #Select the model based on the rupture, and use the same model for all sites which include that rupture. | ||
| + | |||
| + | == Development Approach == | ||
| + | Begin work on a software prototype in which we combine CyberShake 15.4 1Hz CyberShake seismograms with GP BBP High Frequencies, to produce Broadband CyberShake Seismograms. For each site, we expect to take each CyberShake rupture variation, retrieve the SRF used, and the 1Hz seismograms produced, and then run the most recent BBP GP high frequency codes, and merge the HF with the 1Hz CyberShake LF, and produced BBP CyberShake seismograms. We will try to show, using a limited number of sites, we get usable BBP seismograms results. Eventually, we may add the BBP HF processing to the CyberShake platform, and routine produce both 1Hz and BBP seismograms and amplitude data sets. | ||
| + | |||
| + | == Technical Approach == | ||
| + | |||
| + | There are specific details here and it has to do with the way site-response is handled for the high frequencies. | ||
| + | |||
| + | The current BBP is set-up for computing ground motions at a "hard-rock" site, typically Vs30=865 m/s. | ||
| + | (The reason behind this seemingly random value is that the site-response module in GP2010 used the | ||
| + | Campbell-Bozorgnia amplification factors, which are linear functions for Vs30 >= 865 m/s.) | ||
| + | |||
| + | To compute the high-frequency motions for sites with Vs30 < 865 m/s, it is not as straightforward as simply replacing the prescribed 1D velocity structure with something that has lower velocities in the near surface. The problem is that the HF simulation codes on the BBP do not model non-linear behavior. GP2010 addressed this by using a post-processing step that applied empirically-based, frequency-dependent, non-linear amplification factors to adjust the computed rock-site motions to a (presumably lower) site-specific Vs30 value. The codes to do this are in the BBP source code distribution("wcc_siteamp"). However, they were not used for any of the validation exercises since those were all hard-rock based, and the BBP scripts probably have had any references to these codes deleted or commented out. | ||
| + | |||
| + | Our Proposed method on how to proceed for CyberShake is as follows: | ||
| + | |||
| + | #Use a single 1D velocity profile for all LA area sites that is "hard-rock". The Northridge 1D model | ||
| + | (with Vs30=865 m/s) that is already on the BBP is the current preferred choice. | ||
| + | #For "rock" sites, the HF and LF results could be combined and used as is. | ||
| + | # For sites with Vs30 lower than about 600-700 m/s, the HF results should be modified to account for site-specific ground motion response. This should be done to the HF motions prior to combining with the LF response. At this point, we will not make any type of modification to the LF motions, for soft soil sites, although we can reconsider that decision in the future. | ||
| + | |||
== Computational Details == | == Computational Details == | ||
| − | Program Name: wcc_siteamp14.c | + | A copy of BBP v15.4 is installed on Blue Waters; /u/sciteam/scottcal/scratch/bbp/15.3.0/bbp/src/gp/WccFormat/Progs |
| + | In the recent BBP install, find it under <version#>/bbp/src/gp/WccFormat/Pros | ||
| + | |||
| + | We confirmed the version of CVM-S4.26 used for CyberShake Study 15.4 does include the GTL, with a 500 m/s minimum cutoff. It sounds like it would be better to extract Vs30 values from it rather than Wills. Should we apply the 500 m/s cutoff to the Vs30 values we pass to site response like we did with CyberShake, or use them as-is? | ||
| + | |||
| + | Site response module: wcc_siteamp. The current version of the code uses site amplification factors based on the 2014 NGA GMPEs. Check to see if that is on the BBP. This version is not formally validated this version (e.g. by redoing the GP2010 validations).Need to make sure to run some compatibility checks just to make sure the results looked OK. | ||
| + | |||
| + | Should we only do it if the Vs30 for the site is below 600-700 m/s. | ||
| + | |||
| + | Apply the modification to all sites without worrying about the specific Vs30. For sites that have Vs30 greater than about 600-700 the modification will be very minor. But the extra overhead in running the code for all sites is probably insignificant relative to the (equally trivial) overhead in checking the sites for an arbitrary Vs30 threshold and having different processing streams based on this. | ||
| + | |||
| + | Related question - in 2011 we pulled the Vs30 values from Wills. Is that still correct, or should we use Vs30 from the velocity model we used for the CyberShake deterministic (CVM-S4.26)? | ||
| + | |||
| + | There are some concerns about the near-surface velocity values in the CVM used for the previous calcualtions, in particular, very high Vs for rock sites, and that is why we used Wills In CVM-S4.26, does it include the "geotechnical layer"? If so, then its probably best to use these values, so that the LF and HF portions are consistent. | ||
| + | |||
| + | Program Name: wcc_siteamp14.c | ||
The input and output are the same as previous versions with the possible exception being the parameter "model". | The input and output are the same as previous versions with the possible exception being the parameter "model". | ||
| Line 8: | Line 54: | ||
Check to see if this parameter was set previously. (i.e., as model=<something> either in a parfile or on the command line) | Check to see if this parameter was set previously. (i.e., as model=<something> either in a parfile or on the command line) | ||
| − | Regarding the question of whether we should we apply the 500 m/s cutoff to the Vs30 values we pass to site response like we did with CyberShake, or use them as-is? | + | Regarding the question of whether we should we apply the 500 m/s cutoff to the Vs30 values we pass to site response like we did with CyberShake, or use them as-is? Current decision is to use them as is. There will be an apparent disconnect with the 500 m/s cutoff at some sites, although the the 500 m/s value with a 100 meter grid spacing is an adequate approximation for the LF calculation. |
| − | Current decision is to use them as is. There will be an apparent disconnect with the 500 m/s cutoff at some sites, although the the 500 m/s value with a 100 meter grid spacing is an adequate approximation for the LF calculation. | ||
== Priority CyberShake Sites of Interest == | == Priority CyberShake Sites of Interest == | ||
| Line 21: | Line 66: | ||
*LADP - another rock site, near fault | *LADP - another rock site, near fault | ||
| + | == BBP CyberShake Schematic 2009 == | ||
*[http://scec.usc.edu/scecwiki/images/4/4a/HF_Schematic.png Schematic] | *[http://scec.usc.edu/scecwiki/images/4/4a/HF_Schematic.png Schematic] | ||
| − | |||
== Related Entries == | == Related Entries == | ||
Latest revision as of 00:48, 8 February 2016
Redirect to:
Contents
Compuational Goal
We are working on doing a series of broadband CyberShake runs, extending the 1 Hz deterministic results we generated in the spring with stochastic results from high-frequency implementation on the BBP.
Before we setup the calculation, we evaluate questions about the 1D velocity model needed for the high frequency results. It seems like there are three ways we could handle this in the context of CyberShake:
- Use the same model (LA Basin?) for all CyberShake sites and all ruptures.
- Select the model based on the CyberShake site, and use the same model for all ruptures on that site.
- Select the model based on the rupture, and use the same model for all sites which include that rupture.
Development Approach
Begin work on a software prototype in which we combine CyberShake 15.4 1Hz CyberShake seismograms with GP BBP High Frequencies, to produce Broadband CyberShake Seismograms. For each site, we expect to take each CyberShake rupture variation, retrieve the SRF used, and the 1Hz seismograms produced, and then run the most recent BBP GP high frequency codes, and merge the HF with the 1Hz CyberShake LF, and produced BBP CyberShake seismograms. We will try to show, using a limited number of sites, we get usable BBP seismograms results. Eventually, we may add the BBP HF processing to the CyberShake platform, and routine produce both 1Hz and BBP seismograms and amplitude data sets.
Technical Approach
There are specific details here and it has to do with the way site-response is handled for the high frequencies.
The current BBP is set-up for computing ground motions at a "hard-rock" site, typically Vs30=865 m/s. (The reason behind this seemingly random value is that the site-response module in GP2010 used the Campbell-Bozorgnia amplification factors, which are linear functions for Vs30 >= 865 m/s.)
To compute the high-frequency motions for sites with Vs30 < 865 m/s, it is not as straightforward as simply replacing the prescribed 1D velocity structure with something that has lower velocities in the near surface. The problem is that the HF simulation codes on the BBP do not model non-linear behavior. GP2010 addressed this by using a post-processing step that applied empirically-based, frequency-dependent, non-linear amplification factors to adjust the computed rock-site motions to a (presumably lower) site-specific Vs30 value. The codes to do this are in the BBP source code distribution("wcc_siteamp"). However, they were not used for any of the validation exercises since those were all hard-rock based, and the BBP scripts probably have had any references to these codes deleted or commented out.
Our Proposed method on how to proceed for CyberShake is as follows:
- Use a single 1D velocity profile for all LA area sites that is "hard-rock". The Northridge 1D model
(with Vs30=865 m/s) that is already on the BBP is the current preferred choice.
- For "rock" sites, the HF and LF results could be combined and used as is.
- For sites with Vs30 lower than about 600-700 m/s, the HF results should be modified to account for site-specific ground motion response. This should be done to the HF motions prior to combining with the LF response. At this point, we will not make any type of modification to the LF motions, for soft soil sites, although we can reconsider that decision in the future.
Computational Details
A copy of BBP v15.4 is installed on Blue Waters; /u/sciteam/scottcal/scratch/bbp/15.3.0/bbp/src/gp/WccFormat/Progs In the recent BBP install, find it under <version#>/bbp/src/gp/WccFormat/Pros
We confirmed the version of CVM-S4.26 used for CyberShake Study 15.4 does include the GTL, with a 500 m/s minimum cutoff. It sounds like it would be better to extract Vs30 values from it rather than Wills. Should we apply the 500 m/s cutoff to the Vs30 values we pass to site response like we did with CyberShake, or use them as-is?
Site response module: wcc_siteamp. The current version of the code uses site amplification factors based on the 2014 NGA GMPEs. Check to see if that is on the BBP. This version is not formally validated this version (e.g. by redoing the GP2010 validations).Need to make sure to run some compatibility checks just to make sure the results looked OK.
Should we only do it if the Vs30 for the site is below 600-700 m/s.
Apply the modification to all sites without worrying about the specific Vs30. For sites that have Vs30 greater than about 600-700 the modification will be very minor. But the extra overhead in running the code for all sites is probably insignificant relative to the (equally trivial) overhead in checking the sites for an arbitrary Vs30 threshold and having different processing streams based on this.
Related question - in 2011 we pulled the Vs30 values from Wills. Is that still correct, or should we use Vs30 from the velocity model we used for the CyberShake deterministic (CVM-S4.26)?
There are some concerns about the near-surface velocity values in the CVM used for the previous calcualtions, in particular, very high Vs for rock sites, and that is why we used Wills In CVM-S4.26, does it include the "geotechnical layer"? If so, then its probably best to use these values, so that the LF and HF portions are consistent.
Program Name: wcc_siteamp14.c
The input and output are the same as previous versions with the possible exception being the parameter "model". If "model" is not specified, then the default settings are used, which is fine.
Check to see if this parameter was set previously. (i.e., as model=<something> either in a parfile or on the command line)
Regarding the question of whether we should we apply the 500 m/s cutoff to the Vs30 values we pass to site response like we did with CyberShake, or use them as-is? Current decision is to use them as is. There will be an apparent disconnect with the 500 m/s cutoff at some sites, although the the 500 m/s value with a 100 meter grid spacing is an adequate approximation for the LF calculation.
Priority CyberShake Sites of Interest
Broadband-Cybershake motions for a few sites combining the stochastic and Cybershake signals:
- STNI - basin site
- LADT - basin site
- PAS - rock site
- WNGC - between basins, with expected high ground motions
- LADP - another rock site, near fault
