Difference between revisions of "Broadband Validation Events"
From SCECpedia
Jump to navigationJump to search| Line 1: | Line 1: | ||
| + | == Broadband Platform Validation Processing == | ||
| + | The Broadband Platform can calculate 0-10Hz seismograms (velocity and acceleration) for user-defined earthquakes. These broadband seismograms are intended to be accurate representations of ground motions caused by the earthquakes. | ||
| + | |||
| + | To validate the platform, the platform is designed to calculate seismograms for three historical California earthquakes. | ||
| + | |||
| + | |||
== Overview == | == Overview == | ||
| Line 6: | Line 12: | ||
* UCSB | * UCSB | ||
* UDSU | * UDSU | ||
| − | |||
Three validation events are provided in the Broadband Platform: | Three validation events are provided in the Broadband Platform: | ||
| Line 13: | Line 18: | ||
* Landers | * Landers | ||
* Loma Prieta | * Loma Prieta | ||
| − | |||
Each of these events will be tested for each codebase. Although the platform allows codebases to be mixed and matched for low-frequency seismogram synthesis, high-frequency seismogram synthesis, and site response, validation events will be simulated with only a single codebase for now. Thus, there are nine unique simulation possibilities: | Each of these events will be tested for each codebase. Although the platform allows codebases to be mixed and matched for low-frequency seismogram synthesis, high-frequency seismogram synthesis, and site response, validation events will be simulated with only a single codebase for now. Thus, there are nine unique simulation possibilities: | ||
Revision as of 21:00, 30 April 2012
Contents
Broadband Platform Validation Processing
The Broadband Platform can calculate 0-10Hz seismograms (velocity and acceleration) for user-defined earthquakes. These broadband seismograms are intended to be accurate representations of ground motions caused by the earthquakes.
To validate the platform, the platform is designed to calculate seismograms for three historical California earthquakes.
Overview
The Broadband Platform 11.2.2 provides three primary codebases for seismogram synthesis:
- URS
- UCSB
- UDSU
Three validation events are provided in the Broadband Platform:
- Northridge
- Landers
- Loma Prieta
Each of these events will be tested for each codebase. Although the platform allows codebases to be mixed and matched for low-frequency seismogram synthesis, high-frequency seismogram synthesis, and site response, validation events will be simulated with only a single codebase for now. Thus, there are nine unique simulation possibilities:
- Northridge with URS
- Northridge with UCSB
- Northridge with SDSU
- Landers with URS
- Landers with UCSB
- Landers with SDSU
- Loma Prieta with URS
- Loma Prieta with UCSB
- Loma Prieta with SDSU
These nine simulations will be run on both broadband.usc.edu and USC HPCC, and the results will be compared for accuracy.
Run Commands
The validation simulations were run using the standard run_bbp_2G.py start script. The following lists the run commands used with each codebase:
URS Simulations:
/home/broadband-01/patrices/11.2.2/bbp_2g/comps/run_bbp_2G.py -o /home/broadband-01/patrices/study/validation/nr_options_urs.txt -l /home/broadband-01/patrices/11.2.2/bbp_2g/logs/nr_urs_validation.log /home/broadband-01/patrices/11.2.2/bbp_2g/comps/run_bbp_2G.py -o /home/broadband-01/patrices/study/validation/lp_options_urs.txt -l /home/broadband-01/patrices/11.2.2/bbp_2g/logs/lp_urs_validation.log /home/broadband-01/patrices/11.2.2/bbp_2g/comps/run_bbp_2G.py -o /home/broadband-01/patrices/study/validation/la_options_urs.txt -l /home/broadband-01/patrices/11.2.2/bbp_2g/logs/la_urs_validation.log
UCSB Simulations:
/home/broadband-01/patrices/11.2.2/bbp_2g/comps/run_bbp_2G.py -o /home/broadband-01/patrices/study/validation/nr_options_ucsb.txt -l /home/broadband-01/patrices/11.2.2/bbp_2g/logs/nr_ucsb_validation.log /home/broadband-01/patrices/11.2.2/bbp_2g/comps/run_bbp_2G.py -o /home/broadband-01/patrices/study/validation/lp_options_ucsb.txt -l /home/broadband-01/patrices/11.2.2/bbp_2g/logs/lp_ucsb_validation.log /home/broadband-01/patrices/11.2.2/bbp_2g/comps/run_bbp_2G.py -o /home/broadband-01/patrices/study/validation/la_options_ucsb.txt -l /home/broadband-01/patrices/11.2.2/bbp_2g/logs/la_ucsb_validation.log
SDSU Simulations:
/home/broadband-01/patrices/11.2.2/bbp_2g/comps/run_bbp_2G.py -o /home/broadband-01/patrices/study/validation/nr_options_sdsu.txt -l /home/broadband-01/patrices/11.2.2/bbp_2g/logs/nr_sdsu_validation.log /home/broadband-01/patrices/11.2.2/bbp_2g/comps/run_bbp_2G.py -o /home/broadband-01/patrices/study/validation/lp_options_sdsu.txt -l /home/broadband-01/patrices/11.2.2/bbp_2g/logs/lp_sdsu_validation.log /home/broadband-01/patrices/11.2.2/bbp_2g/comps/run_bbp_2G.py -o /home/broadband-01/patrices/study/validation/la_options_sdsu.txt -l /home/broadband-01/patrices/11.2.2/bbp_2g/logs/la_sdsu_validation.log
Where the option .txt files are provided here: http://earth.usc.edu/~patrices/downloads/bbp_validation_option_files.tar
broadband.usc.edu versus HPCC cluster
Broadband.usc.edu:
| Codebase | Northridge | Landers | Loma Prieta |
|---|---|---|---|
| URS | Complete | Complete | Complete |
| UCSB | Complete | Complete Fixed (Python Exception 1) |
Complete Fixed (Python Exception 2) |
| SDSU | Complete Fixed (Python Exception 5) |
Complete Fixed (Python Exception 3) |
Complete Fixed (Python Exception 4) |
USC HPCC:
| Codebase | Northridge | Landers | Loma Prieta |
|---|---|---|---|
| URS | Complete | Complete | Complete |
| UCSB | Complete | Complete Fixed (Python Exception 1) |
Complete Fixed (Python Exception 2) |
| SDSU | Complete Fixed (Python Exception 5) |
Complete Fixed (Python Exception 3) |
Complete Fixed (Python Exception 4) |
Match Broadband vs HPCC:
| Codebase | Northridge | Landers | Lome Prieta |
|---|---|---|---|
| URS | Identical | Identical | Identical |
| UCSB | Differ (http://earth.usc.edu/~patrices/downloads/bbp_validation_ucsb_nr.tar.gz) | Differ (http://earth.usc.edu/~patrices/downloads/bbp_validation_ucsb_la.tar.gz) | Differ (http://earth.usc.edu/~patrices/downloads/bbp_validation_ucsb_lp.tar.gz) |
| SDSU | Differ (http://earth.usc.edu/~patrices/downloads/bbp_validation_sdsu_nr.tar.gz) | Differ (http://earth.usc.edu/~patrices/downloads/bbp_validation_sdsu_la.tar.gz) | Differ (http://earth.usc.edu/~patrices/downloads/bbp_validation_sdsu_lp.tar.gz) |
Errors and Fixes
The tables above reference several python errors. The following table describes each error and the fix:
- [1] IOError: [Errno 2] No such file or directory: '/export/broadband-01/patrices/11.2.2/bbp_2g/tmpdata/4255795/luc.3comp'. Solution is to rename UCSB LA/LP Green's functions to correct names expected by the platform. For the UCSB Lander's Green's functions, create the symlink shown below and update the filename in Green_Bank.inf and GreenFar.in:
[patrices@broadband Landers]$ pwd /home/broadband-01/patrices/11.2.2/bbp_2g_gf/ucsb/GreenBank/Landers [patrices@broadband Landers]$ ls -l total 2259816 -rw-r--r-- 1 patrices bband 2311766784 Oct 25 2011 Green1D.Landers lrwxrwxrwx 1 patrices cme 15 Apr 26 11:00 Green_1d.soil -> Green1D.Landers -rw-r--r-- 1 patrices bband 1325 Apr 26 11:05 Green_Bank.inf -rw-r--r-- 1 patrices cme 1327 Apr 26 11:05 Green_Bank.inf.original -rwxr-xr-x 1 patrices bband 455 Apr 26 11:06 GreenFar.in -rwxr-xr-x 1 patrices cme 457 Apr 26 11:06 GreenFar.in.original
- [2] IOError: [Errno 2] No such file or directory: '/export/broadband-01/patrices/11.2.2/bbp_2g/tmpdata/4255790/lgpc.3comp'. Same solution as #1.
- [3] IOError: [Errno 2] No such file or directory: '/export/broadband-01/patrices/11.2.2/bbp_2g/indata/4255183/stations.dat'. Same solution as #5.
- [4] IOError: [Errno 2] No such file or directory: '/export/broadband-01/patrices/11.2.2/bbp_2g/indata/4255178/stations.dat' Same solution as #5.
- [5] IOError: [Errno 2] No such file or directory: '/export/broadband-01/patrices/11.2.2/bbp_2g/indata/4252651/stations_kappa.dat'. Solution is to add $BBP_INSTALL_GF/sdsu/Northridge/stations_kappa.dat to the stage-in file list for the HF module in run_bbp_2G.py. Specifically, add the following at run_bbp_2G.py:L279:
elif codebase=="SDSU":
hf_module.addStageFile(val_obj.getInput("SDSU", "stations"))
