SCEC Broadband Platform Capabilities and Plans Philip Maechling Information Technology Architect Southern California Earthquake Center (SCEC) 28 January 2008 SCEC: An NSF + USGS Research Center.
Download ReportTranscript SCEC Broadband Platform Capabilities and Plans Philip Maechling Information Technology Architect Southern California Earthquake Center (SCEC) 28 January 2008 SCEC: An NSF + USGS Research Center.
SCEC Broadband Platform Capabilities and Plans Philip Maechling Information Technology Architect Southern California Earthquake Center (SCEC) 28 January 2008 SCEC: An NSF + USGS Research Center Running a Simple BBP Example Purpose: – Calculate 10Hz seismograms (and spectral amplitudes) using a combinations of codes. Combine Results of Available Codes: – Rupture Generators – URS and UCSB – Low Frequency Codes – URS and UCSB • All codes use 1D velocity models for low frequency calculations. – High Freq Codes – URS and UCSB and SDSU/ETH Broadband Platform Workflow Greens Functions Rupture Generator Rupture Config Low Freq Sim Rupture Variation High Freq Sim Seismograms Spectral Amplitudes Seismograms Amps Running a Simple BBP Example • Select the collection of codes you would like to run and type in the number of that set of codes. Number Rupture Model Generator Low Frequency Seismogram High Frequency Seismograms 1 URS URS URS 2 URS UCSB UCSB 3 URS URS SDSU 4 UCSB UCSB UCSB 5 UCSB URS URS 6 UCSB URS SDSU Input a Rupture Description Input a Station Location File Input a Station 1D Velocity Model Running a Simple BBP Example • Login into the SCEC computer (intensity.usc.edu) – User account: bband – Pwd: TBD • Move to the configuration directory – Type “start” • This is an alias that will move you to the configuration directory • Review the three input files: – Eq.src – Earthquake Source Description – Stations.ll – Station Locations in Lat/lon (decimal degrees) – BB01-01.vld – velocity model • Run the platform by typing: – Type “run_bbp.py” • This is the name of the top level BB Platform script BB Platform Directory Structure • Every simulation is assigned a “simulation id” – This is basically a timestamp (epoch seconds) • Will wrap in about 3 months – Information about a simulation is keyed to this number • Input, tmp, and output directories are created for a simulation and the files related to the simulation are stored in these directories • The user should only need to look at the “data” directory, the output directory that contains the broadband seismograms and the metadata file. BB Platform Directory Structure • To help keep track of how seismograms were created, a “metadata.txt” file is created for each simulation. • This lists the programs and the parameters used to create the seismograms. BB Metadata File Structure Broadband Platform “Hanging Wall” Exercise Broadband Platform Seismograms Broadband Platform Station SA Amplitudes BB Platform Directory Structure Platform is designed by creating “components” that can be interchanged. A component is a python script that wraps all the executables and scripts needed to do that processing. Rupture Generator Rupture Config Low Freq Sim Rupture Variation High Freq Spectral Amplitudes Sim Seismograms Seismograms BB Platform Directory Structure Next Steps: • Distribute programs so that we can run on supercomputers. • Add new components by creating new components using new codes • Integrate capability to run 3D low frequency simulations • Integrate capability to just run HF part to add HF to low frequency seismograms. End