Broadband Platform

From SCECpedia
Revision as of 19:23, 30 September 2013 by Fsilva (talk | contribs)
Jump to navigationJump to search
Fig 1: Broadband Platform.

The SCEC Broadband Platform is a software system which generates 0-100 Hz seismograms for historical and scenario earthquakes in California and Japan.

Overview

The goal of the SCEC Broadband Simulation Platform is to generate broadband (0-100 Hz) ground motions for earthquakes. The SCEC Broadband Platform is a collaborative software development project involving SCEC researchers, research engineers, graduate students, and the SCEC/CME software development group. SCEC scientific groups have contributed modules to the Broadband Platform including rupture generation, low- and high-frequency seismogram synthesis, non-linear site effects, and visualization. These complex scientific codes have been integrated into a system that supports easy on-demand computation of broadband seismograms. The SCEC Broadband Platform is designed to be used by both scientific and engineering researchers with some experience interpreting ground motion simulations.

Users may calculate broadband seismograms for both historical earthquakes (validation events including Northridge and Loma Prieta) and user-defined earthquakes. The platform produces a variety of data products, including broadband seismograms, rupture visualizations, and several goodness-of-fit plots. Users can install the platform on their own machine, verify that it is installed correctly, and run their own simulations on demand without requiring knowledge of any of the code involved. Users may run a validation event, supply their own simple source description, or provide a rupture description in SRF format. Users may specify their own list of stations or use a provided list. Currently the platform supports stations and events in Southern California, the Bay Area, the Mojave Desert, Central and Western Japan. Users may select among various method that include rupture generation, low-frequency synthesis, high-frequency synthesis, and incorporation of site effects, with the option of running a goodness-of-fit comparison against observed or simulated seismograms. These codes have been validated against recorded ground motions from real events.

The Broadband Platform was implemented using software development best practices, including version control, user documentation, acceptance tests, and formal releases, with the aim of ease of installation and use.

Current Release

The current official release of Broadband Platform is v13.9.0. This distribution was posted online on Thursday, 26 September 2013. This is a new version of the platform that includes a large number of new capabilities. It is the first major release of the Broadband Platform since version 11.2.3, released in May 2012. Details of the new features along with several bugs fixes are provided in the release notes and the "changes" section below. New, and old Broadband platform users should work with this version of the software, and we recommend current Broadband platform users migrate to this new version whenever possible.

Dependencies

Broadband has the following dependencies:

A non-commercial copy of Intel C and FORTRAN compilers can be obtained by registering for a non-commercial account with Intel and downloading the compilers from the Intel website.

Documentation

User Guide Wiki (includes installation instructions):

Downloads

To install and use the Broadband platform, you need the source code, one or more Green's Functions packages, and optionally one or more Validation packages. The Broadband Platform contains cumulative improvements to the geoscientific codes and software infrastructure. We recommend use of the most recent version of the Broadband Platform, unless you are trying to reproduce results generated with an earlier version of the platform.

Users that are upgrading from previous version of the Broadband Platform will need to retrieve new versions of all the Broadband Platform packages as there have been significant changes in all the packages since the previous 11.2.3 release.

There are detailed installation instructions in the Broadband User Guide v13.9.0.

Detailed instructions to setup the Broadband Platform as a local installation on a Linux Machine are provided in the Broadband User Guide v13.9.0. Briefly, they can be summarized in the following steps:

  1. The software can be installed in an account on a Linux computer with at least 10GB of disk storage and C, Fortran, and Python software installed.
  2. From this Linux computer, start a web browser and point to this download page. Alternatively, you can download the files to a different machine and use FTP or SFTP to copy them over.
  3. Download each file into a directory and run the md5sum program to confirm you have an undamaged version of the distribution files by comparing the md5sum provided below against the one calculated at the local Linux computer.
  4. Uncompress the distribution (tar.gz) files into the proper directory structure as described in the Broadband User Guide v13.9.0.
  5. Build the executables by running the top level makefile.
  6. Configure your environment by adding a few Broadband Platform variables to your shell's environment.
  7. Confirm the code is built correctly by running UnitTests.
  8. Confirm the code runs correctly on your system by running AcceptanceTests.
  9. Use the platform for research purposes.

Current Broadband Platform Release

The current SCEC Broadband platform release is v13.9.0. Links to the source distribution and Green's Functions and Validation packages are listed in the table below:

Version Release Date Files User Guide
Source Code Green's Functions Packages Validations Packages
13.9.0 09/26/2013 BBP 13.9.0,

BBP 13.9.0.md5

Central Japan, Central Japan.md5

LA Basin, LA Basin.md5

LOMAP (NoCal), LOMAP.md5

Mojave, Mojave.md5

Western Japan, Western Japan.md5

Loma Prieta, Loma Prieta.md5

Northridge, Northridge.md5

Broadband User Guide v13.9.0

Broadband v13.9.0 Release Notes

Optional Broadband Platform Patches

There are currently no optional patches available for 13.9.0.

Previous Broadband Platform Release

Earlier version of the broadband platform software and data distributions are provided to support existing Broadband platform users. However, we recommend all users upgrade to the most recent version at first opportunity.

Version Release Date Files User Guide
Source Code Data Patches
11.2.3 5/09/2012 bbp_dist_v11.2.3.tgz

bbp_dist_v11.2.3.tgz.md5

bbp_data_v11.2.3.tgz

bbp_data_v11.2.3.tgz.md5

Broadband User Guide v11.2.3

Broadband v11.2.3 Release Notes

11.2.2 10/21/2011 bbp_dist_v11.2.2.tgz

bbp_dist_v11.2.2.tgz.md5

bbp_data_v11.2.2.tgz

bbp_data_v11.2.2.tgz.md5

bbp_patch_v11.2.2.1.tgz

bbp_patch_v11.2.2.2.tgz

Broadband User Guide v11.2.2

Broadband v11.2.2 Release Notes

11.2.1 09/29/2011 bbp_dist_v11.2.1.tgz

bbp_dist_v11.2.1.tgz.md5

bbp_data_v11.2.1.tgz

bbp_data_v11.2.1.tgz.md5

Broadband User Guide v11.2.1

Broadband v11.2.1 Release Notes

11.2.0 02/18/2011 bbp_dist_v11.2.0.tgz

bbp_dist_v11.2.0.tgz.md5

bbp_data_v11.2.0.tgz

bbp_data_v11.2.0.tgz.md5

Broadband User Guide v11.2

Supporting Materials

Development version

If you're interested in working with the latest development version of the platform, you can check it out from 

svn co https://source.usc.edu/svn/broadband/trunk

Details about working with the development version are provided in the User Guide.

The next version of Broadband is expected to be released in Q4 of 2013.

Help

For assistance with the Broadband Platform, you may

  • Email software @ scec.org with specific questions
  • Browse and submit new trouble tickets, or feature requests, at Broadband Trac site. SCEC user login is required to submit trouble tickets this way.

License

SCEC Broadband Platform software distributions are released under an Apache 2.0 open-source license as described here Broadband License.

Changes in Broadband Platform

Broadband Platform 13.9.0

Broadband Platform v13.9.0, released in September 2013 is considered a major released of the Broadband Platform. It contains most of the capabilities of the v11.2.3 version with the following modifications:

  • Trac # 38 - Running validation events with SDSU and incorrect station names causes a crash
  • Trac # 57 - Setting fmax=20.0 Hz in bbtoolbox_cfg.py generates NaNs in output bbp
  • Trac # 80 - Add NGA attenuenation relationship
  • Trac # 82 - Separate validation files from GF
  • Trac # 83 - Separate GF into individual events
  • Trac # 84 - User selectable GF
  • Trac # 87 - Integrate Atkinson module into broadband
  • Trac # 88 - Integrate Irikura Module into BBP
  • Trac # 89 - Provide no site correction option
  • Trac # 94 - Add number cutoff distance and number of stations to bias plots
  • Trac # 96 - Add link to bias plot results into validation table
  • Trac # 98 - Rename main run script to run_bbp.py
  • Trac # 100 - Rename urs modules to gp modules
  • Trac # 101 - add test to check for mixed spaces and tabs
  • Trac # 102 - Move plot files out of Greens Functions
  • Trac # 103 - Make site response optional in the platform
  • Trac # 104 - Use environment variables to find Greens Functions and Validation directories
  • Trac # 106 - Review BBP bbtoobox unit tests on broadband.usc.edu
  • Trac # 112 - Collect additional metadata using CSEP environment script and generate full manifest for software distribution
  • Trac # 120 - Link velocity model and code to specific gf
  • Trac # 121 - full validation runs with src file or user selected srf file
  • Trac # 122 - Allow users to provide an alternative directory for input/output data files
  • Trac # 123 - reliable system for self reporting software version for broadband
  • Trac # 124 - Plot of station map with SDSU code base
  • Trac # 125 - Migrate pbs script and parallel scripts into svn trunk
  • Trac # 126 - move plots into bbp home directory
  • Trac # 130 - Amp Fac Unit test fails due to long filenames
  • Trac # 131 - Make parallel scripts configurable to run a number of concurrent instances
  • Trac # 136 - Move y2r2b.cpt file from URS_DATA/plot to BBP distribution plot/data directory
  • Trac # 137 - Rupture model png not copied to outdata directory
  • Trac # 140 - Add Arias Duration plots for bbp full validation sims
  • Trac # 142 - Add rotd50 routine to BBP
  • Trac # 143 - URS validation fails due to long file paths
  • Trac # 144 - Automatically adjust time series plot window to capture entire event
  • Trac # 147 - Convert peer obs files to bbp format obs
  • Trac # 148 - lowfreq corner of -99 in station list
  • Trac # 149 - Check in uwo EXSIM code into trunk with tests
  • Trac # 150 - Include the rupture generator in the validation workflow
  • Trac # 152 - Rupture plot appears distorted
  • Trac # 153 - Generate html option copies extra files to output directory
  • Trac # 154 - check rotd50 code
  • Trac # 155 - Fix units label on full validation seismogram plots
  • Trac # 156 - Enable rotD50 module to handle bbp and peer inputs files
  • Trac # 157 - Validate Broadband using ifort version 12.0 on HPCC
  • Trac # 159 - Make FMAX user-configurable in BBToolbox
  • Trac # 160 - Use RotD50 data in Bias plot instead of average horizontals
  • Trac # 161 - Bias plot should only include data within band-pass filter
  • Trac # 162 - Show band-pass bars on per-station plots
  • Trac # 163 - Create new bias plot showing fit over station distance
  • Trac # 164 - Move md5sums into validation and gf packages
  • Trac # 165 - Derive UCSB station list from Broadband station list
  • Trac # 166 - Derive BBToolbox inputs from Broadband inputs for validation runs
  • Trac # 167 - The 2 horizontal components in the PSa5/RotD50 bias plot are inverted
  • Trac # 168 - Create a KML file with stations and fault line
  • Trac # 169 - Extend RotD50 GOF plot range 0.1Hz - 100Hz
  • Trac # 171 - The geobb_srf script fails to find fault corners in certain scenarios
  • Trac # 172 - Check station names' length and abort if above max limit
  • Trac # 173 - Package GMPE code into the Broadband Platform
  • Trac # 174 - Introduce version numbers for validation and GFs packages
  • Trac # 175 - Integrate scripts to produce GMPE boxplots into the Platform
  • Trac # 176 - Randomize hypocenter location when running multiple validation realizations
  • Trac # 177 - Use same UCSB rupture generator binary for vertical and dipping faults
  • Trac # 178 - Plot station map with fault using SRC file
  • Trac # 179 - Create single component GOF plot
  • Trac # 180 - Generate SRF file in XYZ format for the SDSU method
  • Trac # 181 - Add Qp and Qs to the SDSU velocity model file
  • Trac # 182 - Make switch for randomizing hypocenter required on cluster script
  • Trac # 183 - Make SDSU seismograms module take regular station list
  • Trac # 185 - Implement resume workflow feature on the Broadband Platform
  • Trac # 184 - Check if SRF file exists if user wants to skip rupture generator
  • Trac # 186 - Make BBToolbox use magnitude from SRC file
  • Trac # 187 - Calculate HYPO_DEPTH automatically for the UCSB method
  • Trac # 188 - Add option for users to run the Broadband Platform on the background
  • Trac # 189 - Optimize arias_duration script
  • Trac # 190 - Remove duplicate tests in UnitTest.py
  • Trac # 191 - Add simulation timestamp to index.html file
  • Trac # 192 - Integrate UNR Composite Source Model into the Platform
  • Trac # 194 - Enable cluster to run user-defined simulations
  • Trac # 196 - Create a map GOF plot with color
  • Trac # 197 - Create combined GOF for all realizations and stations
  • Trac # 198 - Whenever running binary files, print an error message if it is not found
  • Trac # 199 - Print error when velocity model doesn't exist for selected method/event
  • Trac # 201 - Update the BBToolbox version in the Platform to 1.5
  • Trac # 202 - PlotMap.py doesn't work for Matplotlib v1.2.0
  • Trac # 203 - Integrate updated version of UCSB rupture generator
  • Trac # 204 - Support multiple colorsets on GOF plots
  • Trac # 206 - Regenerate acceptance tests for trunk
  • Trac # 208 - Add check to make sure number of stations is under UCSB's syn1D limit
  • Trac # 209 - Fix race condition for matplotlib cache file when running on the cluster
  • Trac # 210 - Increase array size is respect in order to handle larger seismograms
  • Trac # 211 - Increase CSM's station limit and check if station list is under new limit

Broadband Platform 11.2.3

Broadband Platform v11.2.3, released in May 2012 is considered a 'bug-fix' release of Broadband Platform. Broadband Platform v11.2.3 contains the same functional capabilities as v11.2.2 with the following modifications.

  • Trac # 30 Change tolerance depending on acceptance test combo
  • Trac # 69 UCSB high and low frequency modules don't work for Loma Prieta validation
  • Trac # 70 UCSB src/ucsb/Converter/utlFault.h srf name buffer length too short
  • Trac # 71 Allow tolerance checks to be disabled in unit/acceptance tests
  • Trac # 72 run_bbp_2G.py option file parsing exception when selecting a file among two or more choices
  • Trac # 74 Minor bug in a routine that is used for geographic conversions in the URS simulations on the BB platform
  • Trac # 75 Update Green's function data file with fixes and new datasets
  • Trac # 76 Change DEFAULT_KAPPA from 0.02 to 0.01 in ./comps/stas2files.py
  • Trac # 77 Remove station "olem" vs30 value from from UCSB Loma Prieta stations.vs30 in 11.7.0/trunk data sets
  • Trac # 78 Updated geobb_srf.py to use URS ll2xy coordinate conversion routines on trunk

Broadband Platform 11.2.2

Broadband Platform v11.2.2, released in October 2011 is considered a 'bug-fix' release of Broadband Platform. Broadband Platform v11.2.2 contains the same functional capabilities as v11.2.1 with the following modifications.

  • Trac # 56 Convert BBP Matlab scripts to Python
  • Trac # 67 Rename the cleanup.py so that people do not run it accidentally
  • Trac # 68 Build Broadband with latest (2011) Intel and GNU compilers

Broadband Platform 11.2.1

11.2.1 - September 2011 - Bug-fix release.

List of Trac items fixed in this release:

  • Trac # 41 - Add License file (EULA) to Broadband distribution.
  • Trac # 42 - Add a file manifest to the distribution archives.
  • Trac # 46 - Remove Hardcoded Green_Bank.inf entries.
  • Trac # 47 - Syn1d Module fails with IO error due to missing file.
  • Trac # 54 - plot_SRF.csh fails with "Newline in variable name".
  • Trac # 61 - Provide an option to remove temporary folders at end of Broadband simulation run.
  • Trac # 62 - Add a warning and user prompt to comps/cleanup.py script.
  • Trac # 63 - Acceptance resume.txt should not be created in ref_data/accept_inputs.
  • Trac # 64 - Simulations with URS HF module fail with IOError and segmentation faults.
  • Trac # 65 - Add the XML file generated during a Broadband simulation to the output directory as metadata.

Broadband Platform 11.2.0

11.2.0 - February 2011 - Initial release.

Collaborators

Frequently Asked Questions (FAQ)

We post BBP user questions and our response to a Broadband Platform Frequently Asked Questions (FAQ) page:

See Also

References

  1. Graves, R. W. and A. Pitarka (2010). “Broadband Ground-Motion Simulation Using a Hybrid Approach.” Bull. Seis. Soc. Am., 100(5A), pp. 2095-2123, doi: 10.1785/0120100057. link
  2. Mai, P.M., W. Imperatori, and K.B. Olsen (2010). “Hybrid broadband ground motion simulations: combining long-period deterministic synthetics with high frequency multiple S-to-S back-scattering.” Bull. Seis. Soc. Am., 100(5A), pp. 2124-2142, doi: 10.1785/0120080194. link
  3. Schmedes, J., R. J. Archuleta, and D. Lavallée (2010). “Correlation of earthquake source parameters inferred from dynamic rupture simulations.” J. Geophys. Res., 115, B03304, doi:10.1029/2009JB006689. link
Retrieved from "https://strike.scec.org/scecwiki/index.php?title=Broadband_Platform&oldid=8459"