https://strike.scec.org/scecwiki/api.php?action=feedcontributions&feedformat=atom&user=Patrices SCECpedia - User contributions [en] 2026-04-23T10:43:22Z User contributions MediaWiki 1.34.2 https://strike.scec.org/scecwiki/index.php?title=Chino_Hills_1D_and_3D&diff=10561 Chino Hills 1D and 3D 2014-07-16T19:22:43Z <p>Patrices: </p> <hr /> <div>SCEC researchers are comparing the differences between Chino Hills simulations using 1D methods, based on the Broadband Platform, and 3D methods, based on SCEC 3D codes including Hercules-GPU and AWP-GPU.<br /> <br /> == BBP Chino Hills Evaluation Methods ==<br /> <br /> SCEC BBP researchers use the Chino Hills earthquake as a validation event. They have defined a 1D velocity model for the region, selected a consensus fault geometry and earthquake magnitude, and selected a set of ground motion observations for use in comparisons to synthetics.<br /> <br /> == BBP Velocity Model for Chino Hills ==<br /> In the following file, the first line indicates how many layers compose the velocity model. The following lines, one for each layer, describes the layer in details. The first column is the thickness of the layer (in kilometers). The second and third columns are Vp and Vs, respectively, both in km/s. The forth column contains the rho value (in g/cm3), while the last two columns contain the Qp and Qs parameters respectively.<br /> <br /> 18<br /> 0.0020 1.7000 0.4500 2.0000 45.00 22.50<br /> 0.0040 1.8000 0.6500 2.1000 65.00 32.50<br /> 0.0060 1.8000 0.8500 2.1000 85.00 42.50<br /> 0.0080 1.9000 0.9500 2.1000 95.00 47.50<br /> 0.0100 2.0000 1.1500 2.2000 115.00 57.50<br /> 0.0700 2.4000 1.2000 2.2000 120.00 60.00<br /> 0.2000 2.8000 1.4000 2.3000 140.00 70.00<br /> 0.2000 3.1000 1.6000 2.4000 160.00 80.00<br /> 0.2000 3.4000 1.8000 2.4500 180.00 90.00<br /> 0.3000 3.7000 2.1000 2.5000 210.00 105.00<br /> 2.0000 4.4000 2.4000 2.6000 240.00 120.00<br /> 2.0000 5.1000 2.8000 2.7000 280.00 140.00<br /> 1.0000 5.6000 3.1500 2.7500 315.00 157.50<br /> 5.0000 6.1500 3.6000 2.8250 360.00 180.00<br /> 5.0000 6.3200 3.6500 2.8500 365.00 182.50<br /> 5.0000 6.5500 3.7000 2.9000 370.00 185.00<br /> 10.0000 6.8000 3.8000 2.9500 380.00 190.00<br /> 999.0000 7.8000 4.5000 3.2000 450.00 225.00<br /> <br /> == Chino Hills Source Description in SRC Format ==<br /> <br /> MAGNITUDE = 5.39<br /> LAT_TOP_CENTER = 33.939<br /> LON_TOP_CENTER = -117.771<br /> STRIKE = 296<br /> DIP = 66<br /> RAKE = 146<br /> FAULT_LENGTH = 6.30<br /> FAULT_WIDTH = 4.60<br /> DEPTH_TO_TOP = 12.79 <br /> HYPO_ALONG_STK = 0.0<br /> HYPO_DOWN_DIP = 2.30<br /> DLEN = 0.1<br /> DWID = 0.1<br /> SEED = 4745706<br /> <br /> == Chino Hills Source Description in SRF Format ==<br /> <br /> * [http://hypocenter.usc.edu/research/ChinoHills/chinohills-gp-0011.srf Chino Hills SRF File]<br /> <br /> == Chino Hills Station List ==<br /> <br /> (Please only use first 3 columns as lat, long, station_id).<br /> <br /> #BBP Station List for EQID=25 (Chino Hills)<br /> #SLong SLat RSN Rrup(km) Vs30(m/s) LoPass_Freq(Hz) HiPass_Freq(Hz) Obs_File<br /> -117.803 33.927 25029 12.6 378 0.0500 111.1111 CHINOH/25029_N.acc<br /> -117.820 33.912 25040 13.2 374 0.1375 111.1111 CHINOH/25040_N.acc<br /> -117.896 33.933 25028 15.6 396 0.1000 111.1111 CHINOH/25028_N.acc<br /> -117.817 33.854 25027 16.0 359 0.1000 111.1111 CHINOH/25027_N.acc<br /> -117.789 33.829 25022 16.9 440 0.4750 111.1111 CHINOH/25022_N.acc<br /> -117.951 34.010 25024 20.2 342 0.3375 111.1111 CHINOH/25024_N.acc<br /> -117.807 34.092 25017 20.4 462 0.3250 111.1111 CHINOH/25017_N.acc<br /> -117.844 33.788 25013 21.7 318 0.2625 111.1111 CHINOH/25013_N.acc<br /> -117.562 34.005 25010 22.6 335 0.3625 111.1111 CHINOH/25010_N.acc<br /> -117.609 33.795 25015 22.7 699 0.4250 111.1111 CHINOH/25015_N.acc<br /> -117.911 34.132 25031 26.4 363 0.1000 111.1111 CHINOH/25031_N.acc<br /> -117.638 34.121 25014 26.8 388 0.3250 111.1111 CHINOH/25014_N.acc<br /> -117.439 34.100 25005 36.2 335 0.4000 111.1111 CHINOH/25005_N.acc<br /> -118.102 34.150 25006 38.3 383 0.2500 111.1111 CHINOH/25006_N.acc<br /> -118.178 34.037 25001 38.8 349 0.2750 111.1111 CHINOH/25001_N.acc<br /> -117.879 33.597 25007 40.6 389 0.2750 111.1111 CHINOH/25007_N.acc<br /> -117.321 33.920 25035 40.9 557 0.1750 111.1111 CHINOH/25035_N.acc<br /> -118.058 34.224 25012 41.2 760 0.3000 111.1111 CHINOH/25012_N.acc<br /> -118.230 34.096 25032 45.2 370 0.1250 111.1111 CHINOH/25032_N.acc<br /> -117.365 34.205 25036 47.9 495 0.1875 111.1111 CHINOH/25036_N.acc<br /> -118.315 33.909 25030 49.8 354 0.0625 111.1111 CHINOH/25030_N.acc<br /> -118.294 33.713 25004 54.4 393 0.2875 111.1111 CHINOH/25004_N.acc<br /> -118.377 33.896 25034 55.5 332 0.1000 111.1111 CHINOH/25034_N.acc<br /> -117.235 34.232 25019 58.6 393 0.4750 111.1111 CHINOH/25019_N.acc<br /> -117.367 34.366 25008 60.4 365 0.2875 111.1111 CHINOH/25008_N.acc<br /> -118.404 33.743 25018 62.0 530 0.3000 111.1111 CHINOH/25018_N.acc<br /> -116.959 33.787 25025 75.0 306 0.1125 111.1111 CHINOH/25025_N.acc<br /> -116.931 33.744 25026 78.6 351 0.1375 111.1111 CHINOH/25026_N.acc<br /> -118.560 34.277 25037 80.5 450 0.1125 111.1111 CHINOH/25037_N.acc<br /> -118.646 34.059 25021 80.5 750 0.2375 111.1111 CHINOH/25021_N.acc<br /> -118.299 34.687 25002 95.0 347 0.2500 111.1111 CHINOH/25002_N.acc<br /> -116.717 33.708 25033 98.6 845 0.1375 111.1111 CHINOH/25033_N.acc<br /> -118.905 34.281 25011 109.6 355 0.1375 111.1111 CHINOH/25011_N.acc<br /> -116.390 33.917 25038 125.2 388 0.2000 111.1111 CHINOH/25038_N.acc<br /> -117.230 32.875 25039 126.8 388 0.3125 111.1111 CHINOH/25039_N.acc<br /> -116.378 33.648 25016 130.5 786 0.2625 111.1111 CHINOH/25016_N.acc<br /> -119.138 34.437 25020 135.7 351 0.2125 111.1111 CHINOH/25020_N.acc<br /> -116.846 32.891 25003 142.6 805 0.2500 111.1111 CHINOH/25003_N.acc<br /> -116.226 33.575 25023 146.1 1100 0.2500 111.1111 CHINOH/25023_N.acc<br /> -116.041 34.227 25009 160.1 1188 0.2875 111.1111 CHINOH/25009_N.acc<br /> <br /> == Chino Hills Broadband Platform Output ==<br /> <br /> * [http://bbpvault.usc.edu/bbp/tests/chino_hills/10000011/index-10000011.html Output for best realization]<br /> <br /> == BBP La Habra Seismograms ==<br /> <br /> [http://hypocenter.usc.edu/research/ucvm/bbp.tar.gz BBP La Habra Simulation 6 Seismograms]<br /> <br /> == Sample LF Seismogram file in BBP Format ==<br /> <br /> # LP Sim NGAH, stat=FRD<br /> # time(sec) N-S(cm/s) E-W(cm/s) U-D(cm/s)<br /> 0.000000e+00 2.825620e-08 5.209200e-10 -5.558530e-08<br /> 2.500000e-02 -1.010070e-07 5.667850e-07 1.468970e-07<br /> 5.000000e-02 -1.182370e-07 -3.640960e-07 -1.177720e-07<br /> 7.500000e-02 9.593570e-08 5.037590e-07 4.191010e-08<br /> 1.000000e-01 -7.050750e-08 -4.319790e-07 -7.905130e-08<br /> 1.250000e-01 9.230950e-08 4.570090e-07 8.472100e-08<br /> 1.500000e-01 -8.961420e-08 -4.516160e-07 -8.670470e-08<br /> 1.750000e-01 7.846830e-08 4.504290e-07 6.739040e-08<br /> 2.000000e-01 -9.872560e-08 -4.366750e-07 -7.091230e-08<br /> ...<br /> <br /> == Hercules Simulation Volume and Rotation ==<br /> <br /> == Attenuation Model Used ==<br /> Check the 3D simulations so that Qp Qs used are equivalent to what was used in BBP simulations.<br /> <br /> == Runs ==<br /> <br /> <br /> === Hercules Runs ===<br /> <br /> {| class=&quot;wikitable&quot; border=&quot;1&quot;<br /> |-<br /> ! Run Number<br /> ! Etree<br /> ! Source<br /> ! Stations<br /> ! Notes<br /> |-<br /> | 1<br /> | ch-cvms426-223-4hz-200ms.e<br /> | extended-ricardo-run1<br /> | [http://earth.usc.edu/~patrices/hercules/chino_bbp/CH_stations.txt CH_stations.txt]<br /> |<br /> |-<br /> | 2<br /> | ch-bbp1d-4hz-200ms.e<br /> | extended-ricardo-run2<br /> | [http://earth.usc.edu/~patrices/hercules/chino_bbp/CH_stations.txt CH_stations.txt]<br /> |<br /> |}<br /> <br /> == Related Entries ==<br /> *[[La_Habra_Simulations_on_Titan]]<br /> *[[Hercules]]<br /> *[[Broadband Platform]]</div> Patrices https://strike.scec.org/scecwiki/index.php?title=Chino_Hills_1D_and_3D&diff=10560 Chino Hills 1D and 3D 2014-07-16T18:51:13Z <p>Patrices: </p> <hr /> <div>SCEC researchers are comparing the differences between Chino Hills simulations using 1D methods, based on the Broadband Platform, and 3D methods, based on SCEC 3D codes including Hercules-GPU and AWP-GPU.<br /> <br /> == BBP Chino Hills Evaluation Methods ==<br /> <br /> SCEC BBP researchers use the Chino Hills earthquake as a validation event. They have defined a 1D velocity model for the region, selected a consensus fault geometry and earthquake magnitude, and selected a set of ground motion observations for use in comparisons to synthetics.<br /> <br /> == BBP Velocity Model for Chino Hills ==<br /> In the following file, the first line indicates how many layers compose the velocity model. The following lines, one for each layer, describes the layer in details. The first column is the thickness of the layer (in kilometers). The second and third columns are Vp and Vs, respectively, both in km/s. The forth column contains the rho value (in g/cm3), while the last two columns contain the Qp and Qs parameters respectively.<br /> <br /> 18<br /> 0.0020 1.7000 0.4500 2.0000 45.00 22.50<br /> 0.0040 1.8000 0.6500 2.1000 65.00 32.50<br /> 0.0060 1.8000 0.8500 2.1000 85.00 42.50<br /> 0.0080 1.9000 0.9500 2.1000 95.00 47.50<br /> 0.0100 2.0000 1.1500 2.2000 115.00 57.50<br /> 0.0700 2.4000 1.2000 2.2000 120.00 60.00<br /> 0.2000 2.8000 1.4000 2.3000 140.00 70.00<br /> 0.2000 3.1000 1.6000 2.4000 160.00 80.00<br /> 0.2000 3.4000 1.8000 2.4500 180.00 90.00<br /> 0.3000 3.7000 2.1000 2.5000 210.00 105.00<br /> 2.0000 4.4000 2.4000 2.6000 240.00 120.00<br /> 2.0000 5.1000 2.8000 2.7000 280.00 140.00<br /> 1.0000 5.6000 3.1500 2.7500 315.00 157.50<br /> 5.0000 6.1500 3.6000 2.8250 360.00 180.00<br /> 5.0000 6.3200 3.6500 2.8500 365.00 182.50<br /> 5.0000 6.5500 3.7000 2.9000 370.00 185.00<br /> 10.0000 6.8000 3.8000 2.9500 380.00 190.00<br /> 999.0000 7.8000 4.5000 3.2000 450.00 225.00<br /> <br /> == Chino Hills Source Description in SRC Format ==<br /> <br /> MAGNITUDE = 5.39<br /> LAT_TOP_CENTER = 33.939<br /> LON_TOP_CENTER = -117.771<br /> STRIKE = 296<br /> DIP = 66<br /> RAKE = 146<br /> FAULT_LENGTH = 6.30<br /> FAULT_WIDTH = 4.60<br /> DEPTH_TO_TOP = 12.79 <br /> HYPO_ALONG_STK = 0.0<br /> HYPO_DOWN_DIP = 2.30<br /> DLEN = 0.1<br /> DWID = 0.1<br /> SEED = 4745706<br /> <br /> == Chino Hills Source Description in SRF Format ==<br /> <br /> * [http://hypocenter.usc.edu/research/ChinoHills/chinohills-gp-0011.srf Chino Hills SRF File]<br /> <br /> == Chino Hills Station List ==<br /> <br /> (Please only use first 3 columns as lat, long, station_id).<br /> <br /> #BBP Station List for EQID=25 (Chino Hills)<br /> #SLong SLat RSN Rrup(km) Vs30(m/s) LoPass_Freq(Hz) HiPass_Freq(Hz) Obs_File<br /> -117.803 33.927 25029 12.6 378 0.0500 111.1111 CHINOH/25029_N.acc<br /> -117.820 33.912 25040 13.2 374 0.1375 111.1111 CHINOH/25040_N.acc<br /> -117.896 33.933 25028 15.6 396 0.1000 111.1111 CHINOH/25028_N.acc<br /> -117.817 33.854 25027 16.0 359 0.1000 111.1111 CHINOH/25027_N.acc<br /> -117.789 33.829 25022 16.9 440 0.4750 111.1111 CHINOH/25022_N.acc<br /> -117.951 34.010 25024 20.2 342 0.3375 111.1111 CHINOH/25024_N.acc<br /> -117.807 34.092 25017 20.4 462 0.3250 111.1111 CHINOH/25017_N.acc<br /> -117.844 33.788 25013 21.7 318 0.2625 111.1111 CHINOH/25013_N.acc<br /> -117.562 34.005 25010 22.6 335 0.3625 111.1111 CHINOH/25010_N.acc<br /> -117.609 33.795 25015 22.7 699 0.4250 111.1111 CHINOH/25015_N.acc<br /> -117.911 34.132 25031 26.4 363 0.1000 111.1111 CHINOH/25031_N.acc<br /> -117.638 34.121 25014 26.8 388 0.3250 111.1111 CHINOH/25014_N.acc<br /> -117.439 34.100 25005 36.2 335 0.4000 111.1111 CHINOH/25005_N.acc<br /> -118.102 34.150 25006 38.3 383 0.2500 111.1111 CHINOH/25006_N.acc<br /> -118.178 34.037 25001 38.8 349 0.2750 111.1111 CHINOH/25001_N.acc<br /> -117.879 33.597 25007 40.6 389 0.2750 111.1111 CHINOH/25007_N.acc<br /> -117.321 33.920 25035 40.9 557 0.1750 111.1111 CHINOH/25035_N.acc<br /> -118.058 34.224 25012 41.2 760 0.3000 111.1111 CHINOH/25012_N.acc<br /> -118.230 34.096 25032 45.2 370 0.1250 111.1111 CHINOH/25032_N.acc<br /> -117.365 34.205 25036 47.9 495 0.1875 111.1111 CHINOH/25036_N.acc<br /> -118.315 33.909 25030 49.8 354 0.0625 111.1111 CHINOH/25030_N.acc<br /> -118.294 33.713 25004 54.4 393 0.2875 111.1111 CHINOH/25004_N.acc<br /> -118.377 33.896 25034 55.5 332 0.1000 111.1111 CHINOH/25034_N.acc<br /> -117.235 34.232 25019 58.6 393 0.4750 111.1111 CHINOH/25019_N.acc<br /> -117.367 34.366 25008 60.4 365 0.2875 111.1111 CHINOH/25008_N.acc<br /> -118.404 33.743 25018 62.0 530 0.3000 111.1111 CHINOH/25018_N.acc<br /> -116.959 33.787 25025 75.0 306 0.1125 111.1111 CHINOH/25025_N.acc<br /> -116.931 33.744 25026 78.6 351 0.1375 111.1111 CHINOH/25026_N.acc<br /> -118.560 34.277 25037 80.5 450 0.1125 111.1111 CHINOH/25037_N.acc<br /> -118.646 34.059 25021 80.5 750 0.2375 111.1111 CHINOH/25021_N.acc<br /> -118.299 34.687 25002 95.0 347 0.2500 111.1111 CHINOH/25002_N.acc<br /> -116.717 33.708 25033 98.6 845 0.1375 111.1111 CHINOH/25033_N.acc<br /> -118.905 34.281 25011 109.6 355 0.1375 111.1111 CHINOH/25011_N.acc<br /> -116.390 33.917 25038 125.2 388 0.2000 111.1111 CHINOH/25038_N.acc<br /> -117.230 32.875 25039 126.8 388 0.3125 111.1111 CHINOH/25039_N.acc<br /> -116.378 33.648 25016 130.5 786 0.2625 111.1111 CHINOH/25016_N.acc<br /> -119.138 34.437 25020 135.7 351 0.2125 111.1111 CHINOH/25020_N.acc<br /> -116.846 32.891 25003 142.6 805 0.2500 111.1111 CHINOH/25003_N.acc<br /> -116.226 33.575 25023 146.1 1100 0.2500 111.1111 CHINOH/25023_N.acc<br /> -116.041 34.227 25009 160.1 1188 0.2875 111.1111 CHINOH/25009_N.acc<br /> <br /> == Chino Hills Broadband Platform Output ==<br /> <br /> * [http://bbpvault.usc.edu/bbp/tests/chino_hills/10000011/index-10000011.html Output for best realization]<br /> <br /> == BBP La Habra Seismograms ==<br /> <br /> [http://hypocenter.usc.edu/research/ucvm/bbp.tar.gz BBP La Habra Simulation 6 Seismograms]<br /> <br /> == Sample LF Seismogram file in BBP Format ==<br /> <br /> # LP Sim NGAH, stat=FRD<br /> # time(sec) N-S(cm/s) E-W(cm/s) U-D(cm/s)<br /> 0.000000e+00 2.825620e-08 5.209200e-10 -5.558530e-08<br /> 2.500000e-02 -1.010070e-07 5.667850e-07 1.468970e-07<br /> 5.000000e-02 -1.182370e-07 -3.640960e-07 -1.177720e-07<br /> 7.500000e-02 9.593570e-08 5.037590e-07 4.191010e-08<br /> 1.000000e-01 -7.050750e-08 -4.319790e-07 -7.905130e-08<br /> 1.250000e-01 9.230950e-08 4.570090e-07 8.472100e-08<br /> 1.500000e-01 -8.961420e-08 -4.516160e-07 -8.670470e-08<br /> 1.750000e-01 7.846830e-08 4.504290e-07 6.739040e-08<br /> 2.000000e-01 -9.872560e-08 -4.366750e-07 -7.091230e-08<br /> ...<br /> <br /> == Hercules Simulation Volume and Rotation ==<br /> <br /> == Attenuation Model Used ==<br /> Check the 3D simulations so that Qp Qs used are equivalent to what was used in BBP simulations.<br /> <br /> == Runs ==<br /> <br /> <br /> === Hercules Runs ===<br /> <br /> {| class=&quot;wikitable&quot; border=&quot;1&quot;<br /> |-<br /> ! Run Number<br /> ! Etree<br /> ! Source<br /> ! Stations<br /> ! Notes<br /> |-<br /> | 1<br /> | ch-cvms426-223-4hz-200ms.e<br /> | extended-ricardo-run1<br /> | [http://earth.usc.edu/~patrices/hercules/chino_bbp/CH_stations.txt CH_stations.ext]<br /> |<br /> |-<br /> | 2<br /> | ch-bbp1d-4hz-200ms.e<br /> | extended-ricardo-run2<br /> | [http://earth.usc.edu/~patrices/hercules/chino_bbp/CH_stations.txt CH_stations.ext]<br /> |<br /> |}<br /> <br /> == Related Entries ==<br /> *[[La_Habra_Simulations_on_Titan]]<br /> *[[Hercules]]<br /> *[[Broadband Platform]]</div> Patrices https://strike.scec.org/scecwiki/index.php?title=Chino_Hills_1D_and_3D&diff=10559 Chino Hills 1D and 3D 2014-07-16T18:49:10Z <p>Patrices: </p> <hr /> <div>SCEC researchers are comparing the differences between Chino Hills simulations using 1D methods, based on the Broadband Platform, and 3D methods, based on SCEC 3D codes including Hercules-GPU and AWP-GPU.<br /> <br /> == BBP Chino Hills Evaluation Methods ==<br /> <br /> SCEC BBP researchers use the Chino Hills earthquake as a validation event. They have defined a 1D velocity model for the region, selected a consensus fault geometry and earthquake magnitude, and selected a set of ground motion observations for use in comparisons to synthetics.<br /> <br /> == BBP Velocity Model for Chino Hills ==<br /> In the following file, the first line indicates how many layers compose the velocity model. The following lines, one for each layer, describes the layer in details. The first column is the thickness of the layer (in kilometers). The second and third columns are Vp and Vs, respectively, both in km/s. The forth column contains the rho value (in g/cm3), while the last two columns contain the Qp and Qs parameters respectively.<br /> <br /> 18<br /> 0.0020 1.7000 0.4500 2.0000 45.00 22.50<br /> 0.0040 1.8000 0.6500 2.1000 65.00 32.50<br /> 0.0060 1.8000 0.8500 2.1000 85.00 42.50<br /> 0.0080 1.9000 0.9500 2.1000 95.00 47.50<br /> 0.0100 2.0000 1.1500 2.2000 115.00 57.50<br /> 0.0700 2.4000 1.2000 2.2000 120.00 60.00<br /> 0.2000 2.8000 1.4000 2.3000 140.00 70.00<br /> 0.2000 3.1000 1.6000 2.4000 160.00 80.00<br /> 0.2000 3.4000 1.8000 2.4500 180.00 90.00<br /> 0.3000 3.7000 2.1000 2.5000 210.00 105.00<br /> 2.0000 4.4000 2.4000 2.6000 240.00 120.00<br /> 2.0000 5.1000 2.8000 2.7000 280.00 140.00<br /> 1.0000 5.6000 3.1500 2.7500 315.00 157.50<br /> 5.0000 6.1500 3.6000 2.8250 360.00 180.00<br /> 5.0000 6.3200 3.6500 2.8500 365.00 182.50<br /> 5.0000 6.5500 3.7000 2.9000 370.00 185.00<br /> 10.0000 6.8000 3.8000 2.9500 380.00 190.00<br /> 999.0000 7.8000 4.5000 3.2000 450.00 225.00<br /> <br /> == Chino Hills Source Description in SRC Format ==<br /> <br /> MAGNITUDE = 5.39<br /> LAT_TOP_CENTER = 33.939<br /> LON_TOP_CENTER = -117.771<br /> STRIKE = 296<br /> DIP = 66<br /> RAKE = 146<br /> FAULT_LENGTH = 6.30<br /> FAULT_WIDTH = 4.60<br /> DEPTH_TO_TOP = 12.79 <br /> HYPO_ALONG_STK = 0.0<br /> HYPO_DOWN_DIP = 2.30<br /> DLEN = 0.1<br /> DWID = 0.1<br /> SEED = 4745706<br /> <br /> == Chino Hills Source Description in SRF Format ==<br /> <br /> * [http://hypocenter.usc.edu/research/ChinoHills/chinohills-gp-0011.srf Chino Hills SRF File]<br /> <br /> == Chino Hills Station List ==<br /> <br /> (Please only use first 3 columns as lat, long, station_id).<br /> <br /> #BBP Station List for EQID=25 (Chino Hills)<br /> #SLong SLat RSN Rrup(km) Vs30(m/s) LoPass_Freq(Hz) HiPass_Freq(Hz) Obs_File<br /> -117.803 33.927 25029 12.6 378 0.0500 111.1111 CHINOH/25029_N.acc<br /> -117.820 33.912 25040 13.2 374 0.1375 111.1111 CHINOH/25040_N.acc<br /> -117.896 33.933 25028 15.6 396 0.1000 111.1111 CHINOH/25028_N.acc<br /> -117.817 33.854 25027 16.0 359 0.1000 111.1111 CHINOH/25027_N.acc<br /> -117.789 33.829 25022 16.9 440 0.4750 111.1111 CHINOH/25022_N.acc<br /> -117.951 34.010 25024 20.2 342 0.3375 111.1111 CHINOH/25024_N.acc<br /> -117.807 34.092 25017 20.4 462 0.3250 111.1111 CHINOH/25017_N.acc<br /> -117.844 33.788 25013 21.7 318 0.2625 111.1111 CHINOH/25013_N.acc<br /> -117.562 34.005 25010 22.6 335 0.3625 111.1111 CHINOH/25010_N.acc<br /> -117.609 33.795 25015 22.7 699 0.4250 111.1111 CHINOH/25015_N.acc<br /> -117.911 34.132 25031 26.4 363 0.1000 111.1111 CHINOH/25031_N.acc<br /> -117.638 34.121 25014 26.8 388 0.3250 111.1111 CHINOH/25014_N.acc<br /> -117.439 34.100 25005 36.2 335 0.4000 111.1111 CHINOH/25005_N.acc<br /> -118.102 34.150 25006 38.3 383 0.2500 111.1111 CHINOH/25006_N.acc<br /> -118.178 34.037 25001 38.8 349 0.2750 111.1111 CHINOH/25001_N.acc<br /> -117.879 33.597 25007 40.6 389 0.2750 111.1111 CHINOH/25007_N.acc<br /> -117.321 33.920 25035 40.9 557 0.1750 111.1111 CHINOH/25035_N.acc<br /> -118.058 34.224 25012 41.2 760 0.3000 111.1111 CHINOH/25012_N.acc<br /> -118.230 34.096 25032 45.2 370 0.1250 111.1111 CHINOH/25032_N.acc<br /> -117.365 34.205 25036 47.9 495 0.1875 111.1111 CHINOH/25036_N.acc<br /> -118.315 33.909 25030 49.8 354 0.0625 111.1111 CHINOH/25030_N.acc<br /> -118.294 33.713 25004 54.4 393 0.2875 111.1111 CHINOH/25004_N.acc<br /> -118.377 33.896 25034 55.5 332 0.1000 111.1111 CHINOH/25034_N.acc<br /> -117.235 34.232 25019 58.6 393 0.4750 111.1111 CHINOH/25019_N.acc<br /> -117.367 34.366 25008 60.4 365 0.2875 111.1111 CHINOH/25008_N.acc<br /> -118.404 33.743 25018 62.0 530 0.3000 111.1111 CHINOH/25018_N.acc<br /> -116.959 33.787 25025 75.0 306 0.1125 111.1111 CHINOH/25025_N.acc<br /> -116.931 33.744 25026 78.6 351 0.1375 111.1111 CHINOH/25026_N.acc<br /> -118.560 34.277 25037 80.5 450 0.1125 111.1111 CHINOH/25037_N.acc<br /> -118.646 34.059 25021 80.5 750 0.2375 111.1111 CHINOH/25021_N.acc<br /> -118.299 34.687 25002 95.0 347 0.2500 111.1111 CHINOH/25002_N.acc<br /> -116.717 33.708 25033 98.6 845 0.1375 111.1111 CHINOH/25033_N.acc<br /> -118.905 34.281 25011 109.6 355 0.1375 111.1111 CHINOH/25011_N.acc<br /> -116.390 33.917 25038 125.2 388 0.2000 111.1111 CHINOH/25038_N.acc<br /> -117.230 32.875 25039 126.8 388 0.3125 111.1111 CHINOH/25039_N.acc<br /> -116.378 33.648 25016 130.5 786 0.2625 111.1111 CHINOH/25016_N.acc<br /> -119.138 34.437 25020 135.7 351 0.2125 111.1111 CHINOH/25020_N.acc<br /> -116.846 32.891 25003 142.6 805 0.2500 111.1111 CHINOH/25003_N.acc<br /> -116.226 33.575 25023 146.1 1100 0.2500 111.1111 CHINOH/25023_N.acc<br /> -116.041 34.227 25009 160.1 1188 0.2875 111.1111 CHINOH/25009_N.acc<br /> <br /> == Chino Hills Broadband Platform Output ==<br /> <br /> * [http://bbpvault.usc.edu/bbp/tests/chino_hills/10000011/index-10000011.html Output for best realization]<br /> <br /> == BBP La Habra Seismograms ==<br /> <br /> [http://hypocenter.usc.edu/research/ucvm/bbp.tar.gz BBP La Habra Simulation 6 Seismograms]<br /> <br /> == Sample LF Seismogram file in BBP Format ==<br /> <br /> # LP Sim NGAH, stat=FRD<br /> # time(sec) N-S(cm/s) E-W(cm/s) U-D(cm/s)<br /> 0.000000e+00 2.825620e-08 5.209200e-10 -5.558530e-08<br /> 2.500000e-02 -1.010070e-07 5.667850e-07 1.468970e-07<br /> 5.000000e-02 -1.182370e-07 -3.640960e-07 -1.177720e-07<br /> 7.500000e-02 9.593570e-08 5.037590e-07 4.191010e-08<br /> 1.000000e-01 -7.050750e-08 -4.319790e-07 -7.905130e-08<br /> 1.250000e-01 9.230950e-08 4.570090e-07 8.472100e-08<br /> 1.500000e-01 -8.961420e-08 -4.516160e-07 -8.670470e-08<br /> 1.750000e-01 7.846830e-08 4.504290e-07 6.739040e-08<br /> 2.000000e-01 -9.872560e-08 -4.366750e-07 -7.091230e-08<br /> ...<br /> <br /> == Hercules Simulation Volume and Rotation ==<br /> <br /> == Attenuation Model Used ==<br /> Check the 3D simulations so that Qp Qs used are equivalent to what was used in BBP simulations.<br /> <br /> == Runs ==<br /> <br /> <br /> === Hercules Runs ===<br /> <br /> {| class=&quot;wikitable&quot; border=&quot;1&quot;<br /> |-<br /> ! Run Number<br /> ! Etree<br /> ! Source<br /> ! Stations<br /> ! Notes<br /> |-<br /> | 1<br /> | ch-cvms426-223-4hz-200ms.e<br /> | extended-ricardo-run1<br /> |<br /> |<br /> |-<br /> | 2<br /> | ch-bbp1d-4hz-200ms.e<br /> | extended-ricardo-run2<br /> |<br /> |<br /> |}<br /> <br /> == Related Entries ==<br /> *[[La_Habra_Simulations_on_Titan]]<br /> *[[Hercules]]<br /> *[[Broadband Platform]]</div> Patrices https://strike.scec.org/scecwiki/index.php?title=La_Habra_Simulations_on_Titan&diff=10558 La Habra Simulations on Titan 2014-07-16T18:45:23Z <p>Patrices: </p> <hr /> <div>== Overview ==<br /> <br /> A series of simulations modelling the La Habra 5.1 event will be performed on ORNL Titan with in order to address these scientific and computational goals:<br /> <br /> * Demonstrate that Hercules-GPU software is in production status and evaluate its performance versus the CPU version<br /> * Evaluate goodness of fit for synthetic waveforms versus observed at 1.0 Hz, using Po Chen's updated CVM-S4 velocity model as the material properties source for the simulation.<br /> * [Optionally] Validate the simulation results generated by Hercules-GPU and AWP-GPU<br /> <br /> <br /> == Solver Parameters ==<br /> <br /> <br /> {| class=&quot;wikitable&quot; border=&quot;1&quot;<br /> |-<br /> ! Parameter<br /> ! Value<br /> ! Notes<br /> |-<br /> | Frequency<br /> | 1.0 Hz<br /> | <br /> |-<br /> | Simulation Length<br /> | 100 s<br /> | <br /> |-<br /> | Delta T<br /> | 0.005<br /> | <br /> |-<br /> | Plane Output Resolution<br /> | 250m<br /> | <br /> |-<br /> | I/O Print Rate<br /> | every 10 steps<br /> | <br /> |-<br /> | Station List<br /> | [http://earth.usc.edu/~patrices/hercules/lahabra/LH_stations.txt LH_stations.txt]<br /> | Merged from En-Jui's 0.2Hz station list and Ricardo's CH master list<br /> |-<br /> | Software Version<br /> | Hercules-GPU commit c95f1ab017e5f93613a0e3e2c6b5a849eb4117ad<br /> | GPU codes, no frequency dependent Q<br /> |}<br /> <br /> <br /> <br /> == Simulation Box / Velocity Model ==<br /> <br /> {| class=&quot;wikitable&quot; border=&quot;1&quot;<br /> |-<br /> ! Parameter<br /> ! Value<br /> ! Notes<br /> |-<br /> | Dimensions (km)<br /> | 180 x 135 x 61.875<br /> | <br /> |-<br /> | Bounding Box (LL)<br /> | -119.288842 34.120549, -118.354016 35.061096, -116.846030 34.025873, -117.780976 33.096503<br /> | <br /> |-<br /> | UCVM Version<br /> | 13.9.0<br /> | No heterogeneities<br /> |-<br /> | Velocity Model Versions<br /> | CVM-S4, CVM-S4 v26<br /> | CVM-S5?<br /> |- <br /> |Miniumum Vs<br /> | 200 m/s<br /> | <br /> |-<br /> | Samples per wavelength<br /> | 8<br /> |<br /> |-<br /> | Hercules Etree<br /> | ch-cvms400-100-4hz-200ms.e, ch-cvms426-223-4hz-200ms.e<br /> | CVM-S5 etree?<br /> |}<br /> <br /> <br /> == Sources ==<br /> <br /> The simulation will be repeated for two point sources and one extended source.<br /> <br /> === Point Source Parameters ===<br /> <br /> {| class=&quot;wikitable&quot; border=&quot;1&quot;<br /> |-<br /> ! Parameter<br /> ! Value<br /> ! Notes<br /> |-<br /> | Event Name<br /> | La Habra<br /> | <br /> |-<br /> | Origin Time<br /> | 2014/03/29 04:09:42.97<br /> | Source: En-Jui<br /> |-<br /> | Origin Location<br /> | -117.930; 33.922; 5.0km<br /> | Source: En-Jui<br /> |-<br /> | Strike/Dip/Rake 1<br /> | 134/55/155<br /> | Source: En-Jui, initial<br /> |-<br /> | Strike/Dip/Rake 2<br /> | 239/70/38<br /> | Source: En-Jui, based on review of aftershock sequence<br /> |-<br /> | Rise Time<br /> | 0.75 s<br /> | <br /> |-<br /> | Origin X/Y<br /> | [http://earth.usc.edu/~patrices/hercules/lahabra/EQ_lahabra_xy.list EQ_lahabra_xy.list]<br /> | <br /> |}<br /> <br /> <br /> === SRC Format La Habra Source ===<br /> *MAGNITUDE = 5.12<br /> *FAULT_LENGTH = 5.0<br /> *FAULT_WIDTH = 2.25<br /> *DEPTH_TO_TOP = 4.7125<br /> *STRIKE = 239<br /> *RAKE = 38<br /> *DIP = 70<br /> *LAT_TOP_CENTER = 33.9119<br /> *LON_TOP_CENTER = -117.940<br /> *HYPO_ALONG_STK = 0.0<br /> *HYPO_DOWN_DIP = 1.125<br /> *DLEN = 0.1<br /> *DWID = 0.1<br /> <br /> == Volume ==<br /> <br /> The four corners are:<br /> * -119.288842 34.120549<br /> * -118.354016 35.061096<br /> * -116.846030 34.025873<br /> * -117.780976 33.096503<br /> <br /> And the box has size<br /> *180,000 m x 135,000 m x 61,875 m<br /> <br /> == Runs ==<br /> <br /> <br /> === Hercules Runs ===<br /> <br /> {| class=&quot;wikitable&quot; border=&quot;1&quot;<br /> |-<br /> ! Run Number<br /> ! Etree<br /> ! Source<br /> ! Notes<br /> |-<br /> | 1<br /> | ch-cvms400-100-4hz-200ms.e<br /> | point-ricardo-134-55-155<br /> |<br /> |-<br /> | 2<br /> | ch-cvms426-223-4hz-200ms.e<br /> | point-ricardo-134-55-155<br /> |<br /> |-<br /> | 3<br /> | ch-cvms400-100-4hz-200ms.e<br /> | point-ricardo-239-70-38<br /> |<br /> |-<br /> | 4<br /> | ch-cvms426-223-4hz-200ms.e<br /> | point-ricardo-239-70-38<br /> |<br /> |-<br /> | 5<br /> | ch-cvms400-100-4hz-200ms.e<br /> | extended-ricardo<br /> |<br /> |-<br /> | 6<br /> | ch-cvms426-223-4hz-200ms.e<br /> | extended-ricardo<br /> |<br /> |}<br /> <br /> <br /> === BBP Run ===<br /> *[http://bbpvault.usc.edu/bbp/tests/la_habra/run1/la_habra_2014_06_19.src SRC for this event]<br /> <br /> *[http://bbpvault.usc.edu/bbp/tests/la_habra/run1/la_habra_2014_06_19.png SRF Image]<br /> *[http://bbpvault.usc.edu/bbp/tests/la_habra/run1/la_habra_2014_06_19.srf SRF for this SRC]<br /> <br /> <br /> == La Habra Earthquake Observations ==<br /> *[http://strongmotioncenter.org/vdc/scripts/event.plx?evt=1295 Center for Strong Motion Engineering Data Center]<br /> <br /> == La Habra References ==<br /> *[http://www.scsn.org/2014lahabra.html SCSN La Habra Event Summary]<br /> *[http://www.data.scec.org/MomentTensor/solutions/web_15481673/ci15481673_MT.html SCSN La Habra Moment Tensor Solution]<br /> <br /> <br /> == References ==<br /> # Bielak, J., H. Karaoglu, and R. Taborda, 2011. Memory-efficient displacement-based internal friction for wave propagation simulation, Geophysics, 76(6):T131-T145.<br /> # Taborda, R., Lopez, J., Karaoglu, H., Urbanic, J., and Bielak, J. (2010). Speeding up finite element wave propagation for large-scale earthquake simulations. Technical Report CMU-PDL-10-109, Carnegie Mellon University, Parallel Data Lab. <br /> # Tu, T., Yu, H., Ramírez-Guzmán, L., Bielak, J., Ghattas, O., Ma, K.-L., &amp; O’Hallaron, D.R., 2006. From mesh generation to scientific visualization: an end-to-end approach to parallel supercomputing, in Proceedings of the 2006 ACM/IEEE International Conference for High Performance Computing, Networking, Storage and Analysis, p. 15, IEEE Computer Society, Tampa, Florida.</div> Patrices https://strike.scec.org/scecwiki/index.php?title=La_Habra_Simulations_on_Titan&diff=10398 La Habra Simulations on Titan 2014-06-27T17:21:06Z <p>Patrices: </p> <hr /> <div>== Overview ==<br /> <br /> A series of simulations modelling the La Habra 5.1 event will be performed on ORNL Titan with in order to address these scientific and computational goals:<br /> <br /> * Demonstrate that Hercules-GPU software is in production status and evaluate its performance versus the CPU version<br /> * Evaluate goodness of fit for synthetic waveforms versus observed at 1.0 Hz, using Po Chen's updated CVM-S4 velocity model as the material properties source for the simulation.<br /> * [Optionally] Validate the simulation results generated by Hercules-GPU and AWP-GPU<br /> <br /> <br /> == Solver Parameters ==<br /> <br /> <br /> {| class=&quot;wikitable&quot; border=&quot;1&quot;<br /> |-<br /> ! Parameter<br /> ! Value<br /> ! Notes<br /> |-<br /> | Frequency<br /> | 1.0 Hz<br /> | <br /> |-<br /> | Simulation Length<br /> | 100 s<br /> | <br /> |-<br /> | Delta T<br /> | 0.005<br /> | <br /> |-<br /> | Plane Output Resolution<br /> | 250m<br /> | <br /> |-<br /> | I/O Print Rate<br /> | every 10 steps<br /> | <br /> |-<br /> | Station List<br /> | [http://earth.usc.edu/~patrices/hercules/lahabra/LH_stations.txt LH_stations.txt]<br /> | Merged from En-Jui's 0.2Hz station list and Ricardo's CH master list<br /> |-<br /> | Software Version<br /> | Hercules-GPU commit c95f1ab017e5f93613a0e3e2c6b5a849eb4117ad<br /> | GPU codes, no frequency dependent Q<br /> |}<br /> <br /> <br /> <br /> == Simulation Box / Velocity Model ==<br /> <br /> {| class=&quot;wikitable&quot; border=&quot;1&quot;<br /> |-<br /> ! Parameter<br /> ! Value<br /> ! Notes<br /> |-<br /> | Dimensions (km)<br /> | 180 x 135 x 61.875<br /> | <br /> |-<br /> | Bounding Box (LL)<br /> | -119.288842 34.120549, -118.354016 35.061096, -116.846030 34.025873, -117.780976 33.096503<br /> | <br /> |-<br /> | UCVM Version<br /> | 13.9.0<br /> | No heterogeneities<br /> |-<br /> | Velocity Model Versions<br /> | CVM-S4, CVM-S4 v26<br /> | CVM-S5?<br /> |- <br /> |Miniumum Vs<br /> | 200 m/s<br /> | <br /> |-<br /> | Samples per wavelength<br /> | 8<br /> |<br /> |-<br /> | Hercules Etree<br /> | ch-cvms400-100-4hz-200ms.e, ch-cvms426-223-4hz-200ms.e<br /> | CVM-S5 etree?<br /> |}<br /> <br /> <br /> == Sources ==<br /> <br /> The simulation will be repeated for two point sources and one extended source.<br /> <br /> <br /> === Point Source Parameters ===<br /> <br /> {| class=&quot;wikitable&quot; border=&quot;1&quot;<br /> |-<br /> ! Parameter<br /> ! Value<br /> ! Notes<br /> |-<br /> | Event Name<br /> | La Habra<br /> | <br /> |-<br /> | Origin Time<br /> | 2014/03/29 04:09:42.97<br /> | Source: En-Jui<br /> |-<br /> | Origin Location<br /> | -117.930; 33.922; 5.0km<br /> | Source: En-Jui<br /> |-<br /> | Strike/Dip/Rake 1<br /> | 134/55/155<br /> | Source: En-Jui, initial<br /> |-<br /> | Strike/Dip/Rake 2<br /> | 239/70/38<br /> | Source: En-Jui, based on review of aftershock sequence<br /> |-<br /> | Rise Time<br /> | 0.75 s<br /> | <br /> |}<br /> <br /> <br /> === SRC Format La Habra Source ===<br /> *MAGNITUDE = 5.12<br /> *FAULT_LENGTH = 5.0<br /> *FAULT_WIDTH = 2.25<br /> *DEPTH_TO_TOP = 4.7125<br /> *STRIKE = 239<br /> *RAKE = 38<br /> *DIP = 79 (typo? should be 70?)<br /> *LAT_TOP_CENTER = 33.9119<br /> *LON_TOP_CENTER = -117.940<br /> *HYPO_ALONG_STK = 0.0<br /> *HYPO_DOWN_DIP = 1.125<br /> *DLEN = 0.1<br /> *DWID = 0.1<br /> <br /> <br /> == Runs ==<br /> <br /> <br /> === Hercules Runs ===<br /> <br /> {| class=&quot;wikitable&quot; border=&quot;1&quot;<br /> |-<br /> ! Run Number<br /> ! Etree<br /> ! Source<br /> ! Notes<br /> |-<br /> | 1<br /> | ch-cvms400-100-4hz-200ms.e<br /> | point-ricardo-134-55-155<br /> |<br /> |-<br /> | 2<br /> | ch-cvms426-223-4hz-200ms.e<br /> | point-ricardo-134-55-155<br /> |<br /> |-<br /> | 3<br /> | ch-cvms400-100-4hz-200ms.e<br /> | point-ricardo-239-70-38<br /> |<br /> |-<br /> | 4<br /> | ch-cvms426-223-4hz-200ms.e<br /> | point-ricardo-239-70-38<br /> |<br /> |-<br /> | 5<br /> | ch-cvms400-100-4hz-200ms.e<br /> | extended-ricardo<br /> |<br /> |-<br /> | 6<br /> | ch-cvms426-223-4hz-200ms.e<br /> | extended-ricardo<br /> |<br /> |}<br /> <br /> <br /> === BBP Run ===<br /> *[http://bbpvault.usc.edu/bbp/tests/la_habra/run1/la_habra_2014_06_19.src SRC for this event]<br /> <br /> *[http://bbpvault.usc.edu/bbp/tests/la_habra/run1/la_habra_2014_06_19.png SRF Image]<br /> *[http://bbpvault.usc.edu/bbp/tests/la_habra/run1/la_habra_2014_06_19.srf SRF for this SRC]<br /> <br /> <br /> == La Habra Earthquake Observations ==<br /> *[http://strongmotioncenter.org/vdc/scripts/event.plx?evt=1295 PEER Data Center]<br /> <br /> <br /> == La Habra References ==<br /> *[http://www.scsn.org/2014lahabra.html SCSN La Habra Event Summary]<br /> *[http://www.data.scec.org/MomentTensor/solutions/web_15481673/ci15481673_MT.html SCSN La Habra Moment Tensor Solution]<br /> <br /> <br /> == References ==<br /> # Bielak, J., H. Karaoglu, and R. Taborda, 2011. Memory-efficient displacement-based internal friction for wave propagation simulation, Geophysics, 76(6):T131-T145.<br /> # Taborda, R., Lopez, J., Karaoglu, H., Urbanic, J., and Bielak, J. (2010). Speeding up finite element wave propagation for large-scale earthquake simulations. Technical Report CMU-PDL-10-109, Carnegie Mellon University, Parallel Data Lab. <br /> # Tu, T., Yu, H., Ramírez-Guzmán, L., Bielak, J., Ghattas, O., Ma, K.-L., &amp; O’Hallaron, D.R., 2006. From mesh generation to scientific visualization: an end-to-end approach to parallel supercomputing, in Proceedings of the 2006 ACM/IEEE International Conference for High Performance Computing, Networking, Storage and Analysis, p. 15, IEEE Computer Society, Tampa, Florida.</div> Patrices https://strike.scec.org/scecwiki/index.php?title=La_Habra_Simulations_on_Titan&diff=10392 La Habra Simulations on Titan 2014-06-26T22:38:56Z <p>Patrices: </p> <hr /> <div>== Overview ==<br /> <br /> A series of simulations modelling the La Habra 5.1 event will be performed on ORNL Titan with in order to address these scientific and computational goals:<br /> <br /> * Demonstrate that Hercules-GPU software is in production status and evaluate its performance versus the CPU version<br /> * Evaluate goodness of fit for synthetic waveforms versus observed at 1.0 Hz, using Po Chen's updated CVM-S4 velocity model as the material properties source for the simulation.<br /> * [Optionally] Validate the simulation results generated by Hercules-GPU and AWP-GPU<br /> <br /> <br /> == Solver Parameters ==<br /> <br /> <br /> {| class=&quot;wikitable&quot; border=&quot;1&quot;<br /> |-<br /> ! Parameter<br /> ! Value<br /> ! Notes<br /> |-<br /> | Frequency<br /> | 1.0 Hz<br /> | <br /> |-<br /> | Simulation Length<br /> | 100 s<br /> | <br /> |-<br /> | Delta T<br /> | 0.005<br /> | <br /> |-<br /> | Plane Output Resolution<br /> | 250m<br /> | <br /> |-<br /> | I/O Print Rate<br /> | every 10 steps<br /> | <br /> |-<br /> | Station List<br /> | [http://earth.usc.edu/~patrices/hercules/lahabra/LH_stations.txt LH_stations.txt]<br /> | Merged from En-Jui's 0.2Hz station list and Ricardo's CH master list<br /> |-<br /> | Software Version<br /> | Hercules-GPU i3<br /> | GPU codes, no frequency dependent Q<br /> |}<br /> <br /> <br /> <br /> == Simulation Box / Velocity Model ==<br /> <br /> {| class=&quot;wikitable&quot; border=&quot;1&quot;<br /> |-<br /> ! Parameter<br /> ! Value<br /> ! Notes<br /> |-<br /> | Dimensions (km)<br /> | 180 x 135 x 61.875<br /> | <br /> |-<br /> | Bounding Box (LL)<br /> | -119.288842 34.120549, -118.354016 35.061096, -116.846030 34.025873, -117.780976 33.096503<br /> | <br /> |-<br /> | UCVM Version<br /> | 13.9.0<br /> | No heterogeneities<br /> |-<br /> | Velocity Model Versions<br /> | CVM-S4, CVM-S4 v26<br /> | CVM-S5?<br /> |- <br /> |Miniumum Vs<br /> | 200 m/s<br /> | <br /> |-<br /> | Samples per wavelength<br /> | 8<br /> |<br /> |-<br /> | Hercules Etree<br /> | ch-cvms400-100-4hz-200ms.e, ch-cvms426-223-4hz-200ms.e<br /> | CVM-S5 etree?<br /> |}<br /> <br /> <br /> == Sources ==<br /> <br /> The simulation will be repeated for two point sources and one extended source.<br /> <br /> <br /> === Point Source Parameters ===<br /> <br /> {| class=&quot;wikitable&quot; border=&quot;1&quot;<br /> |-<br /> ! Parameter<br /> ! Value<br /> ! Notes<br /> |-<br /> | Event Name<br /> | La Habra<br /> | <br /> |-<br /> | Origin Time<br /> | 2014/03/29 04:09:42.97<br /> | Source: En-Jui<br /> |-<br /> | Origin Location<br /> | -117.930; 33.922; 5.0km<br /> | Source: En-Jui<br /> |-<br /> | Strike/Dip/Rake 1<br /> | 134/55/155<br /> | Source: En-Jui, initial<br /> |-<br /> | Strike/Dip/Rake 2<br /> | 239/70/38<br /> | Source: En-Jui, based on review of aftershock sequence<br /> |-<br /> | Rise Time<br /> | 0.75 s<br /> | <br /> |}<br /> <br /> <br /> === SRC Format La Habra Source ===<br /> *MAGNITUDE = 5.12<br /> *FAULT_LENGTH = 5.0<br /> *FAULT_WIDTH = 2.25<br /> *DEPTH_TO_TOP = 4.7125<br /> *STRIKE = 239<br /> *RAKE = 38<br /> *DIP = 79 (typo? should be 70?)<br /> *LAT_TOP_CENTER = 33.9119<br /> *LON_TOP_CENTER = -117.940<br /> *HYPO_ALONG_STK = 0.0<br /> *HYPO_DOWN_DIP = 1.125<br /> *DLEN = 0.1<br /> *DWID = 0.1<br /> <br /> <br /> == Runs ==<br /> <br /> <br /> === Hercules Runs ===<br /> <br /> {| class=&quot;wikitable&quot; border=&quot;1&quot;<br /> |-<br /> ! Run Number<br /> ! Etree<br /> ! Source<br /> ! Notes<br /> |-<br /> | 1<br /> | ch-cvms400-100-4hz-200ms.e<br /> | point-ricardo-134-55-155<br /> |<br /> |-<br /> | 2<br /> | ch-cvms426-223-4hz-200ms.e<br /> | point-ricardo-134-55-155<br /> |<br /> |-<br /> | 3<br /> | ch-cvms400-100-4hz-200ms.e<br /> | point-ricardo-239-70-38<br /> |<br /> |-<br /> | 4<br /> | ch-cvms426-223-4hz-200ms.e<br /> | point-ricardo-239-70-38<br /> |<br /> |-<br /> | 5<br /> | ch-cvms400-100-4hz-200ms.e<br /> | extended-ricardo<br /> |<br /> |-<br /> | 6<br /> | ch-cvms426-223-4hz-200ms.e<br /> | extended-ricardo<br /> |<br /> |}<br /> <br /> <br /> === BBP Run ===<br /> *[http://bbpvault.usc.edu/bbp/tests/la_habra/run1/la_habra_2014_06_19.src SRC for this event]<br /> <br /> *[http://bbpvault.usc.edu/bbp/tests/la_habra/run1/la_habra_2014_06_19.png SRF Image]<br /> *[http://bbpvault.usc.edu/bbp/tests/la_habra/run1/la_habra_2014_06_19.srf SRF for this SRC]<br /> <br /> <br /> == La Habra Earthquake Observations ==<br /> *[http://strongmotioncenter.org/vdc/scripts/event.plx?evt=1295 PEER Data Center]<br /> <br /> <br /> == La Habra References ==<br /> *[http://www.scsn.org/2014lahabra.html SCSN La Habra Event Summary]<br /> *[http://www.data.scec.org/MomentTensor/solutions/web_15481673/ci15481673_MT.html SCSN La Habra Moment Tensor Solution]<br /> <br /> <br /> == References ==<br /> # Bielak, J., H. Karaoglu, and R. Taborda, 2011. Memory-efficient displacement-based internal friction for wave propagation simulation, Geophysics, 76(6):T131-T145.<br /> # Taborda, R., Lopez, J., Karaoglu, H., Urbanic, J., and Bielak, J. (2010). Speeding up finite element wave propagation for large-scale earthquake simulations. Technical Report CMU-PDL-10-109, Carnegie Mellon University, Parallel Data Lab. <br /> # Tu, T., Yu, H., Ramírez-Guzmán, L., Bielak, J., Ghattas, O., Ma, K.-L., &amp; O’Hallaron, D.R., 2006. From mesh generation to scientific visualization: an end-to-end approach to parallel supercomputing, in Proceedings of the 2006 ACM/IEEE International Conference for High Performance Computing, Networking, Storage and Analysis, p. 15, IEEE Computer Society, Tampa, Florida.</div> Patrices https://strike.scec.org/scecwiki/index.php?title=La_Habra_Simulations_on_Titan&diff=10390 La Habra Simulations on Titan 2014-06-23T20:55:24Z <p>Patrices: </p> <hr /> <div>== Overview ==<br /> <br /> A series of simulations modelling the La Habra 5.1 event will be performed on ORNL Titan with in order to address these scientific and computational goals:<br /> <br /> * Demonstrate that Hercules-GPU software is in production status and evaluate its performance versus the CPU version<br /> * Evaluate goodness of fit for synthetic waveforms versus observed at 1.0 Hz, using Po Chen's updated CVM-S4 velocity model as the material properties source for the simulation.<br /> * [Optionally] Validate the simulation results generated by Hercules-GPU and AWP-GPU<br /> <br /> <br /> == Solver Parameters ==<br /> <br /> <br /> {| class=&quot;wikitable&quot; border=&quot;1&quot;<br /> |-<br /> ! Parameter<br /> ! Value<br /> ! Notes<br /> |-<br /> | Frequency<br /> | 1.0 Hz<br /> | <br /> |-<br /> | Simulation Length<br /> | 100 s<br /> | <br /> |-<br /> | Delta T<br /> | 0.005<br /> | <br /> |-<br /> | Plane Output Resolution<br /> | 250m<br /> | <br /> |-<br /> | I/O Print Rate<br /> | every 10 steps<br /> | <br /> |-<br /> | Station List<br /> | [http://earth.usc.edu/~patrices/hercules/lahabra/LH_stations.txt LH_stations.txt]<br /> | Merged from En-Jui's 0.2Hz station list and Ricardo's CH master list<br /> |-<br /> | Software Version<br /> | Hercules-GPU i3<br /> | GPU codes, no frequency dependent Q<br /> |}<br /> <br /> <br /> <br /> == Simulation Box / Velocity Model ==<br /> <br /> {| class=&quot;wikitable&quot; border=&quot;1&quot;<br /> |-<br /> ! Parameter<br /> ! Value<br /> ! Notes<br /> |-<br /> | Dimensions (km)<br /> | 180 x 135 x 61.875<br /> | <br /> |-<br /> | Bounding Box (LL)<br /> | -119.288842 34.120549, -118.354016 35.061096, -116.846030 34.025873, -117.780976 33.096503<br /> | <br /> |-<br /> | UCVM Version<br /> | 13.9.0<br /> | No heterogeneities<br /> |-<br /> | Velocity Model Versions<br /> | CVM-S4, CVM-S4 v26, CVM-S5<br /> | <br /> |- <br /> |Miniumum Vs<br /> | 200 m/s<br /> | <br /> |-<br /> | Samples per wavelength<br /> | 8<br /> |<br /> |-<br /> | Hercules Etree<br /> | ch-cvms400-100-4hz-200ms.e, ch-cvms426-223-4hz-200ms.e<br /> | CVM-S5 etree?<br /> |}<br /> <br /> <br /> == Sources ==<br /> <br /> The simulation will be repeated for two point sources and one extended source.<br /> <br /> <br /> === Point Source Parameters ===<br /> <br /> {| class=&quot;wikitable&quot; border=&quot;1&quot;<br /> |-<br /> ! Parameter<br /> ! Value<br /> ! Notes<br /> |-<br /> | Event Name<br /> | La Habra<br /> | <br /> |-<br /> | Origin Time<br /> | 2014/03/29 04:09:42.97<br /> | Source: En-Jui<br /> |-<br /> | Origin Location<br /> | -117.930; 33.922; 5.0km<br /> | Source: En-Jui<br /> |-<br /> | Strike/Dip/Rake 1<br /> | 134/55/155<br /> | Source: En-Jui, initial<br /> |-<br /> | Strike/Dip/Rake 2<br /> | 239/70/38<br /> | Source: En-Jui, based on review of aftershock sequence<br /> |-<br /> | Rise Time<br /> | 0.75 s<br /> | <br /> |}<br /> <br /> <br /> === SRC Format La Habra Source ===<br /> *MAGNITUDE = 5.12<br /> *FAULT_LENGTH = 5.0<br /> *FAULT_WIDTH = 2.25<br /> *DEPTH_TO_TOP = 4.7125<br /> *STRIKE = 239<br /> *RAKE = 38<br /> *DIP = 79<br /> *LAT_TOP_CENTER = 33.9119<br /> *LON_TOP_CENTER = -117.940<br /> *HYPO_ALONG_STK = 0.0<br /> *HYPO_DOWN_DIP = 1.125<br /> *DLEN = 0.1<br /> *DWID = 0.1<br /> <br /> == BBP Run for La Habra ==<br /> *[http://bbpvault.usc.edu/bbp/tests/la_habra/run1/la_habra_2014_06_19.src SRC for this event]<br /> <br /> *[http://bbpvault.usc.edu/bbp/tests/la_habra/run1/la_habra_2014_06_19.png SRF Image]<br /> *[http://bbpvault.usc.edu/bbp/tests/la_habra/run1/la_habra_2014_06_19.srf SRF for this SRC]<br /> <br /> == La Habra Earthquake Observations ==<br /> *[http://strongmotioncenter.org/vdc/scripts/event.plx?evt=1295 PEER Data Center]<br /> <br /> == La Habra References ==<br /> *[http://www.scsn.org/2014lahabra.html SCSN La Habra Event Summary]<br /> *[http://www.data.scec.org/MomentTensor/solutions/web_15481673/ci15481673_MT.html SCSN La Habra Moment Tensor Solution]<br /> <br /> == References ==<br /> # Bielak, J., H. Karaoglu, and R. Taborda, 2011. Memory-efficient displacement-based internal friction for wave propagation simulation, Geophysics, 76(6):T131-T145.<br /> # Taborda, R., Lopez, J., Karaoglu, H., Urbanic, J., and Bielak, J. (2010). Speeding up finite element wave propagation for large-scale earthquake simulations. Technical Report CMU-PDL-10-109, Carnegie Mellon University, Parallel Data Lab. <br /> # Tu, T., Yu, H., Ramírez-Guzmán, L., Bielak, J., Ghattas, O., Ma, K.-L., &amp; O’Hallaron, D.R., 2006. From mesh generation to scientific visualization: an end-to-end approach to parallel supercomputing, in Proceedings of the 2006 ACM/IEEE International Conference for High Performance Computing, Networking, Storage and Analysis, p. 15, IEEE Computer Society, Tampa, Florida.</div> Patrices https://strike.scec.org/scecwiki/index.php?title=La_Habra_Simulations_on_Titan&diff=10389 La Habra Simulations on Titan 2014-06-23T20:46:54Z <p>Patrices: </p> <hr /> <div>== Overview ==<br /> <br /> A series of simulations modelling the La Habra 5.1 event will be performed on ORNL Titan with in order to address these scientific and computational goals:<br /> <br /> * Demonstrate that Hercules-GPU software is in production status and evaluate its performance versus the CPU version<br /> * Evaluate goodness of fit for synthetic waveforms versus observed at 1.0 Hz, using Po Chen's updated CVM-S4 velocity model as the material properties source for the simulation.<br /> * [Optionally] Validate the simulation results generated by Hercules-GPU and AWP-GPU<br /> <br /> <br /> == Solver Parameters ==<br /> <br /> <br /> {| class=&quot;wikitable&quot; border=&quot;1&quot;<br /> |-<br /> ! Parameter<br /> ! Value<br /> ! Notes<br /> |-<br /> | Frequency<br /> | 1.0 Hz<br /> | <br /> |-<br /> | Simulation Length<br /> | 100 s<br /> | <br /> |-<br /> | Delta T<br /> | 0.005<br /> | <br /> |-<br /> | Plane Output Resolution<br /> | 250m<br /> | <br /> |-<br /> | I/O Print Rate<br /> | every 10 steps<br /> | <br /> |-<br /> | Station List<br /> | [[File:LH_stations.txt]]<br /> | Merged from En-Jui's 0.2Hz station list and Ricardo's CH master list<br /> |-<br /> | Software Version<br /> | Hercules-GPU i3<br /> | GPU codes, no frequency dependent Q<br /> |}<br /> <br /> <br /> <br /> == Simulation Box / Velocity Model ==<br /> <br /> {| class=&quot;wikitable&quot; border=&quot;1&quot;<br /> |-<br /> ! Parameter<br /> ! Value<br /> ! Notes<br /> |-<br /> | Dimensions (km)<br /> | 180 x 135 x 61.875<br /> | <br /> |-<br /> | Bounding Box (LL)<br /> | -119.288842 34.120549, -118.354016 35.061096, -116.846030 34.025873, -117.780976 33.096503<br /> | <br /> |-<br /> | UCVM Version<br /> | 13.9.0<br /> | No heterogeneities<br /> |-<br /> | Velocity Model Versions<br /> | CVM-S4, CVM-S4 v26, CVM-S5<br /> | <br /> |- <br /> |Miniumum Vs<br /> | 200 m/s<br /> | <br /> |-<br /> | Samples per wavelength<br /> | 8<br /> |<br /> |-<br /> | Hercules Etree<br /> | ch-cvms400-100-4hz-200ms.e, ch-cvms426-223-4hz-200ms.e<br /> | CVM-S5 etree?<br /> |}<br /> <br /> <br /> == Sources ==<br /> <br /> The simulation will be repeated for two point sources and one extended source.<br /> <br /> <br /> === Point Source Parameters ===<br /> <br /> {| class=&quot;wikitable&quot; border=&quot;1&quot;<br /> |-<br /> ! Parameter<br /> ! Value<br /> ! Notes<br /> |-<br /> | Event Name<br /> | La Habra<br /> | <br /> |-<br /> | Origin Time<br /> | 2014/03/29 04:09:42.97<br /> | Source: En-Jui<br /> |-<br /> | Origin Location<br /> | -117.930; 33.922; 5.0km<br /> | Source: En-Jui<br /> |-<br /> | Strike/Dip/Rake 1<br /> | 134/55/155<br /> | Source: En-Jui, initial<br /> |-<br /> | Strike/Dip/Rake 2<br /> | 239/70/38<br /> | Source: En-Jui, based on review of aftershock sequence<br /> |-<br /> | Rise Time<br /> | 0.75 s<br /> | <br /> |}<br /> <br /> <br /> === SRC Format La Habra Source ===<br /> *MAGNITUDE = 5.12<br /> *FAULT_LENGTH = 5.0<br /> *FAULT_WIDTH = 2.25<br /> *DEPTH_TO_TOP = 4.7125<br /> *STRIKE = 239<br /> *RAKE = 38<br /> *DIP = 79<br /> *LAT_TOP_CENTER = 33.9119<br /> *LON_TOP_CENTER = -117.940<br /> *HYPO_ALONG_STK = 0.0<br /> *HYPO_DOWN_DIP = 1.125<br /> *DLEN = 0.1<br /> *DWID = 0.1<br /> <br /> == BBP Run for La Habra ==<br /> *[http://bbpvault.usc.edu/bbp/tests/la_habra/run1/la_habra_2014_06_19.src SRC for this event]<br /> <br /> *[http://bbpvault.usc.edu/bbp/tests/la_habra/run1/la_habra_2014_06_19.png SRF Image]<br /> *[http://bbpvault.usc.edu/bbp/tests/la_habra/run1/la_habra_2014_06_19.srf SRF for this SRC]<br /> <br /> == La Habra Earthquake Observations ==<br /> *[http://strongmotioncenter.org/vdc/scripts/event.plx?evt=1295 PEER Data Center]<br /> <br /> == La Habra References ==<br /> *[http://www.scsn.org/2014lahabra.html SCSN La Habra Event Summary]<br /> *[http://www.data.scec.org/MomentTensor/solutions/web_15481673/ci15481673_MT.html SCSN La Habra Moment Tensor Solution]<br /> <br /> == References ==<br /> # Bielak, J., H. Karaoglu, and R. Taborda, 2011. Memory-efficient displacement-based internal friction for wave propagation simulation, Geophysics, 76(6):T131-T145.<br /> # Taborda, R., Lopez, J., Karaoglu, H., Urbanic, J., and Bielak, J. (2010). Speeding up finite element wave propagation for large-scale earthquake simulations. Technical Report CMU-PDL-10-109, Carnegie Mellon University, Parallel Data Lab. <br /> # Tu, T., Yu, H., Ramírez-Guzmán, L., Bielak, J., Ghattas, O., Ma, K.-L., &amp; O’Hallaron, D.R., 2006. From mesh generation to scientific visualization: an end-to-end approach to parallel supercomputing, in Proceedings of the 2006 ACM/IEEE International Conference for High Performance Computing, Networking, Storage and Analysis, p. 15, IEEE Computer Society, Tampa, Florida.</div> Patrices https://strike.scec.org/scecwiki/index.php?title=La_Habra_Simulations_on_Titan&diff=10388 La Habra Simulations on Titan 2014-06-23T20:44:22Z <p>Patrices: </p> <hr /> <div>== Overview ==<br /> <br /> A series of simulations modelling the La Habra 5.1 event will be performed on ORNL Titan with in order to address these scientific and computational goals:<br /> <br /> * Demonstrate that Hercules-GPU software is in production status and evaluate its performance versus the CPU version<br /> * Evaluate goodness of fit for synthetic waveforms versus observed at 1.0 Hz, using Po Chen's updated CVM-S4 velocity model as the material properties source for the simulation.<br /> * [Optionally] Validate the simulation results generated by Hercules-GPU and AWP-GPU<br /> <br /> <br /> == Solver Parameters ==<br /> <br /> <br /> {| class=&quot;wikitable&quot; border=&quot;1&quot;<br /> |-<br /> ! Parameter<br /> ! Value<br /> ! Notes<br /> |-<br /> | Frequency<br /> | 1.0 Hz<br /> | <br /> |-<br /> | Simulation Length<br /> | 100 s<br /> | <br /> |-<br /> | Delta T<br /> | 0.005<br /> | <br /> |-<br /> | Plane Output Resolution<br /> | 250m<br /> | <br /> |-<br /> | I/O Print Rate<br /> | every 10 steps<br /> | <br /> |-<br /> | Station List<br /> | [[File:LH_stations.list]]<br /> | Merged from En-Jui's 0.2Hz station list and Ricardo's CH master list<br /> |-<br /> | Software Version<br /> | Hercules-GPU i3<br /> | GPU codes, no frequency dependent Q<br /> |}<br /> <br /> <br /> <br /> == Simulation Box / Velocity Model ==<br /> <br /> {| class=&quot;wikitable&quot; border=&quot;1&quot;<br /> |-<br /> ! Parameter<br /> ! Value<br /> ! Notes<br /> |-<br /> | Dimensions (km)<br /> | 180 x 135 x 61.875<br /> | <br /> |-<br /> | Bounding Box (LL)<br /> | -119.288842 34.120549, -118.354016 35.061096, -116.846030 34.025873, -117.780976 33.096503<br /> | <br /> |-<br /> | UCVM Version<br /> | 13.9.0<br /> | No heterogeneities<br /> |-<br /> | Velocity Model Versions<br /> | CVM-S4, CVM-S4 v26, CVM-S5<br /> | <br /> |- <br /> |Miniumum Vs<br /> | 200 m/s<br /> | <br /> |-<br /> | Samples per wavelength<br /> | 8<br /> |<br /> |-<br /> | Hercules Etree<br /> | ch-cvms400-100-4hz-200ms.e, ch-cvms426-223-4hz-200ms.e<br /> | CVM-S5 etree?<br /> |}<br /> <br /> <br /> == Sources ==<br /> <br /> The simulation will be repeated for two point sources and one extended source.<br /> <br /> <br /> === Point Source Parameters ===<br /> <br /> {| class=&quot;wikitable&quot; border=&quot;1&quot;<br /> |-<br /> ! Parameter<br /> ! Value<br /> ! Notes<br /> |-<br /> | Event Name<br /> | La Habra<br /> | <br /> |-<br /> | Origin Time<br /> | 2014/03/29 04:09:42.97<br /> | Source: En-Jui<br /> |-<br /> | Origin Location<br /> | -117.930; 33.922; 5.0km<br /> | Source: En-Jui<br /> |-<br /> | Strike/Dip/Rake 1<br /> | 134/55/155<br /> | Source: En-Jui, initial<br /> |-<br /> | Strike/Dip/Rake 2<br /> | 239/70/38<br /> | Source: En-Jui, based on review of aftershock sequence<br /> |-<br /> | Rise Time<br /> | 0.75 s<br /> | <br /> |}<br /> <br /> <br /> === SRC Format La Habra Source ===<br /> *MAGNITUDE = 5.12<br /> *FAULT_LENGTH = 5.0<br /> *FAULT_WIDTH = 2.25<br /> *DEPTH_TO_TOP = 4.7125<br /> *STRIKE = 239<br /> *RAKE = 38<br /> *DIP = 79<br /> *LAT_TOP_CENTER = 33.9119<br /> *LON_TOP_CENTER = -117.940<br /> *HYPO_ALONG_STK = 0.0<br /> *HYPO_DOWN_DIP = 1.125<br /> *DLEN = 0.1<br /> *DWID = 0.1<br /> <br /> == BBP Run for La Habra ==<br /> *[http://bbpvault.usc.edu/bbp/tests/la_habra/run1/la_habra_2014_06_19.src SRC for this event]<br /> <br /> *[http://bbpvault.usc.edu/bbp/tests/la_habra/run1/la_habra_2014_06_19.png SRF Image]<br /> *[http://bbpvault.usc.edu/bbp/tests/la_habra/run1/la_habra_2014_06_19.srf SRF for this SRC]<br /> <br /> == La Habra Earthquake Observations ==<br /> *[http://strongmotioncenter.org/vdc/scripts/event.plx?evt=1295 PEER Data Center]<br /> <br /> == La Habra References ==<br /> *[http://www.scsn.org/2014lahabra.html SCSN La Habra Event Summary]<br /> *[http://www.data.scec.org/MomentTensor/solutions/web_15481673/ci15481673_MT.html SCSN La Habra Moment Tensor Solution]<br /> <br /> == References ==<br /> # Bielak, J., H. Karaoglu, and R. Taborda, 2011. Memory-efficient displacement-based internal friction for wave propagation simulation, Geophysics, 76(6):T131-T145.<br /> # Taborda, R., Lopez, J., Karaoglu, H., Urbanic, J., and Bielak, J. (2010). Speeding up finite element wave propagation for large-scale earthquake simulations. Technical Report CMU-PDL-10-109, Carnegie Mellon University, Parallel Data Lab. <br /> # Tu, T., Yu, H., Ramírez-Guzmán, L., Bielak, J., Ghattas, O., Ma, K.-L., &amp; O’Hallaron, D.R., 2006. From mesh generation to scientific visualization: an end-to-end approach to parallel supercomputing, in Proceedings of the 2006 ACM/IEEE International Conference for High Performance Computing, Networking, Storage and Analysis, p. 15, IEEE Computer Society, Tampa, Florida.</div> Patrices https://strike.scec.org/scecwiki/index.php?title=La_Habra_Simulations_on_Titan&diff=10387 La Habra Simulations on Titan 2014-06-23T20:42:48Z <p>Patrices: </p> <hr /> <div>== Overview ==<br /> <br /> A series of simulations modelling the La Habra 5.1 event will be performed on ORNL Titan with in order to address these scientific and computational goals:<br /> <br /> * Demonstrate that Hercules-GPU software is in production status and evaluate its performance versus the CPU version<br /> * Evaluate goodness of fit for synthetic waveforms versus observed at 1.0 Hz, using Po Chen's updated CVM-S4 velocity model as the material properties source for the simulation.<br /> * [Optionally] Validate the simulation results generated by Hercules-GPU and AWP-GPU<br /> <br /> <br /> == Solver Parameters ==<br /> <br /> <br /> {| class=&quot;wikitable&quot; border=&quot;1&quot;<br /> |-<br /> ! Parameter<br /> ! Value<br /> ! Notes<br /> |-<br /> | Frequency<br /> | 1.0 Hz<br /> | <br /> |-<br /> | Simulation Length<br /> | 100 s<br /> | <br /> |-<br /> | Delta T<br /> | 0.005<br /> | <br /> |-<br /> | Plane Output Resolution<br /> | 250m<br /> | <br /> |-<br /> | I/O Print Rate<br /> | every 10 steps<br /> | <br /> |-<br /> | Station List<br /> | [[File:LH_master.list]]<br /> | Merged from En-Jui's 0.2Hz station list and Ricardo's CH master list<br /> |-<br /> | Software Version<br /> | Hercules-GPU i3<br /> | GPU codes, no frequency dependent Q<br /> |}<br /> <br /> <br /> <br /> == Simulation Box / Velocity Model ==<br /> <br /> {| class=&quot;wikitable&quot; border=&quot;1&quot;<br /> |-<br /> ! Parameter<br /> ! Value<br /> ! Notes<br /> |-<br /> | Dimensions (km)<br /> | 180 x 135 x 61.875<br /> | <br /> |-<br /> | Bounding Box (LL)<br /> | -119.288842 34.120549, -118.354016 35.061096, -116.846030 34.025873, -117.780976 33.096503<br /> | <br /> |-<br /> | UCVM Version<br /> | 13.9.0<br /> | No heterogeneities<br /> |-<br /> | Velocity Model Versions<br /> | CVM-S4, CVM-S4 v26, CVM-S5<br /> | <br /> |- <br /> |Miniumum Vs<br /> | 200 m/s<br /> | <br /> |-<br /> | Samples per wavelength<br /> | 8<br /> |<br /> |-<br /> | Hercules Etree<br /> | ch-cvms400-100-4hz-200ms.e, ch-cvms426-223-4hz-200ms.e<br /> | CVM-S5 etree?<br /> |}<br /> <br /> <br /> == Sources ==<br /> <br /> The simulation will be repeated for two point sources and one extended source.<br /> <br /> <br /> === Point Source Parameters ===<br /> <br /> {| class=&quot;wikitable&quot; border=&quot;1&quot;<br /> |-<br /> ! Parameter<br /> ! Value<br /> ! Notes<br /> |-<br /> | Event Name<br /> | La Habra<br /> | <br /> |-<br /> | Origin Time<br /> | 2014/03/29 04:09:42.97<br /> | Source: En-Jui<br /> |-<br /> | Origin Location<br /> | -117.930; 33.922; 5.0km<br /> | Source: En-Jui<br /> |-<br /> | Strike/Dip/Rake 1<br /> | 134/55/155<br /> | Source: En-Jui, initial<br /> |-<br /> | Strike/Dip/Rake 2<br /> | 239/70/38<br /> | Source: En-Jui, based on review of aftershock sequence<br /> |-<br /> | Rise Time<br /> | 0.75 s<br /> | <br /> |}<br /> <br /> <br /> === SRC Format La Habra Source ===<br /> *MAGNITUDE = 5.12<br /> *FAULT_LENGTH = 5.0<br /> *FAULT_WIDTH = 2.25<br /> *DEPTH_TO_TOP = 4.7125<br /> *STRIKE = 239<br /> *RAKE = 38<br /> *DIP = 79<br /> *LAT_TOP_CENTER = 33.9119<br /> *LON_TOP_CENTER = -117.940<br /> *HYPO_ALONG_STK = 0.0<br /> *HYPO_DOWN_DIP = 1.125<br /> *DLEN = 0.1<br /> *DWID = 0.1<br /> <br /> == BBP Run for La Habra ==<br /> *[http://bbpvault.usc.edu/bbp/tests/la_habra/run1/la_habra_2014_06_19.src SRC for this event]<br /> <br /> *[http://bbpvault.usc.edu/bbp/tests/la_habra/run1/la_habra_2014_06_19.png SRF Image]<br /> *[http://bbpvault.usc.edu/bbp/tests/la_habra/run1/la_habra_2014_06_19.srf SRF for this SRC]<br /> <br /> == La Habra Earthquake Observations ==<br /> *[http://strongmotioncenter.org/vdc/scripts/event.plx?evt=1295 PEER Data Center]<br /> <br /> == La Habra References ==<br /> *[http://www.scsn.org/2014lahabra.html SCSN La Habra Event Summary]<br /> *[http://www.data.scec.org/MomentTensor/solutions/web_15481673/ci15481673_MT.html SCSN La Habra Moment Tensor Solution]<br /> <br /> == References ==<br /> # Bielak, J., H. Karaoglu, and R. Taborda, 2011. Memory-efficient displacement-based internal friction for wave propagation simulation, Geophysics, 76(6):T131-T145.<br /> # Taborda, R., Lopez, J., Karaoglu, H., Urbanic, J., and Bielak, J. (2010). Speeding up finite element wave propagation for large-scale earthquake simulations. Technical Report CMU-PDL-10-109, Carnegie Mellon University, Parallel Data Lab. <br /> # Tu, T., Yu, H., Ramírez-Guzmán, L., Bielak, J., Ghattas, O., Ma, K.-L., &amp; O’Hallaron, D.R., 2006. From mesh generation to scientific visualization: an end-to-end approach to parallel supercomputing, in Proceedings of the 2006 ACM/IEEE International Conference for High Performance Computing, Networking, Storage and Analysis, p. 15, IEEE Computer Society, Tampa, Florida.</div> Patrices https://strike.scec.org/scecwiki/index.php?title=La_Habra_Simulations_on_Titan&diff=10386 La Habra Simulations on Titan 2014-06-23T20:40:02Z <p>Patrices: </p> <hr /> <div>== Overview ==<br /> <br /> A series of simulations modelling the La Habra 5.1 event will be performed on ORNL Titan with in order to address these scientific and computational goals:<br /> <br /> * Demonstrate that Hercules-GPU software is in production status and evaluate its performance versus the CPU version<br /> * Evaluate goodness of fit for synthetic waveforms versus observed at 1.0 Hz, using Po Chen's updated CVM-S4 velocity model as the material properties source for the simulation.<br /> * [Optionally] Validate the simulation results generated by Hercules-GPU and AWP-GPU<br /> <br /> <br /> == Solver Parameters ==<br /> <br /> <br /> {| class=&quot;wikitable&quot; border=&quot;1&quot;<br /> |-<br /> ! Parameter<br /> ! Value<br /> ! Notes<br /> |-<br /> | Frequency<br /> | 1.0 Hz<br /> | <br /> |-<br /> | Simulation Length<br /> | 100 s<br /> | <br /> |-<br /> | Delta T<br /> | 0.005<br /> | <br /> |-<br /> | Plane Output Resolution<br /> | 250m<br /> | <br /> |-<br /> | I/O Print Rate<br /> | every 10 steps<br /> | <br /> |-<br /> | Station List<br /> | [[File:LH_master.list]]<br /> | ?<br /> |-<br /> | Software Version<br /> | Hercules-GPU i3<br /> | GPU codes, no frequency dependent Q<br /> |}<br /> <br /> <br /> <br /> == Simulation Box / Velocity Model ==<br /> <br /> {| class=&quot;wikitable&quot; border=&quot;1&quot;<br /> |-<br /> ! Parameter<br /> ! Value<br /> ! Notes<br /> |-<br /> | Dimensions (km)<br /> | 180 x 135 x 61.875<br /> | <br /> |-<br /> | Bounding Box (LL)<br /> | -119.288842 34.120549, -118.354016 35.061096, -116.846030 34.025873, -117.780976 33.096503<br /> | <br /> |-<br /> | UCVM Version<br /> | 13.9.0<br /> | No heterogeneities<br /> |-<br /> | Velocity Model Versions<br /> | CVM-S4, CVM-S4 v26, CVM-S5<br /> | <br /> |- <br /> |Miniumum Vs<br /> | 200 m/s<br /> | <br /> |-<br /> | Samples per wavelength<br /> | 8<br /> |<br /> |-<br /> | Hercules Etree<br /> | ch-cvms400-100-4hz-200ms.e, ch-cvms426-223-4hz-200ms.e<br /> | CVM-S5 etree?<br /> |}<br /> <br /> <br /> == Sources ==<br /> <br /> The simulation will be repeated for two point sources and one extended source.<br /> <br /> <br /> === Point Source Parameters ===<br /> <br /> {| class=&quot;wikitable&quot; border=&quot;1&quot;<br /> |-<br /> ! Parameter<br /> ! Value<br /> ! Notes<br /> |-<br /> | Event Name<br /> | La Habra<br /> | <br /> |-<br /> | Origin Time<br /> | 2014/03/29 04:09:42.97<br /> | Source: En-Jui<br /> |-<br /> | Origin Location<br /> | -117.930; 33.922; 5.0km<br /> | Source: En-Jui<br /> |-<br /> | Strike/Dip/Rake 1<br /> | 134/55/155<br /> | Source: En-Jui, initial<br /> |-<br /> | Strike/Dip/Rake 2<br /> | 239/70/38<br /> | Source: En-Jui, based on review of aftershock sequence<br /> |-<br /> | Rise Time<br /> | 0.75 s<br /> | <br /> |}<br /> <br /> <br /> === SRC Format La Habra Source ===<br /> *MAGNITUDE = 5.12<br /> *FAULT_LENGTH = 5.0<br /> *FAULT_WIDTH = 2.25<br /> *DEPTH_TO_TOP = 4.7125<br /> *STRIKE = 239<br /> *RAKE = 38<br /> *DIP = 79<br /> *LAT_TOP_CENTER = 33.9119<br /> *LON_TOP_CENTER = -117.940<br /> *HYPO_ALONG_STK = 0.0<br /> *HYPO_DOWN_DIP = 1.125<br /> *DLEN = 0.1<br /> *DWID = 0.1<br /> <br /> == BBP Run for La Habra ==<br /> *[http://bbpvault.usc.edu/bbp/tests/la_habra/run1/la_habra_2014_06_19.src SRC for this event]<br /> <br /> *[http://bbpvault.usc.edu/bbp/tests/la_habra/run1/la_habra_2014_06_19.png SRF Image]<br /> *[http://bbpvault.usc.edu/bbp/tests/la_habra/run1/la_habra_2014_06_19.srf SRF for this SRC]<br /> <br /> == La Habra Earthquake Observations ==<br /> *[http://strongmotioncenter.org/vdc/scripts/event.plx?evt=1295 PEER Data Center]<br /> <br /> == La Habra References ==<br /> *[http://www.scsn.org/2014lahabra.html SCSN La Habra Event Summary]<br /> *[http://www.data.scec.org/MomentTensor/solutions/web_15481673/ci15481673_MT.html SCSN La Habra Moment Tensor Solution]<br /> <br /> == References ==<br /> # Bielak, J., H. Karaoglu, and R. Taborda, 2011. Memory-efficient displacement-based internal friction for wave propagation simulation, Geophysics, 76(6):T131-T145.<br /> # Taborda, R., Lopez, J., Karaoglu, H., Urbanic, J., and Bielak, J. (2010). Speeding up finite element wave propagation for large-scale earthquake simulations. Technical Report CMU-PDL-10-109, Carnegie Mellon University, Parallel Data Lab. <br /> # Tu, T., Yu, H., Ramírez-Guzmán, L., Bielak, J., Ghattas, O., Ma, K.-L., &amp; O’Hallaron, D.R., 2006. From mesh generation to scientific visualization: an end-to-end approach to parallel supercomputing, in Proceedings of the 2006 ACM/IEEE International Conference for High Performance Computing, Networking, Storage and Analysis, p. 15, IEEE Computer Society, Tampa, Florida.</div> Patrices https://strike.scec.org/scecwiki/index.php?title=La_Habra_Simulations_on_Titan&diff=10385 La Habra Simulations on Titan 2014-06-23T19:17:28Z <p>Patrices: </p> <hr /> <div>== Overview ==<br /> <br /> A series of simulations modelling the La Habra 5.1 event will be performed on ORNL Titan with in order to address these scientific and computational goals:<br /> <br /> * Demonstrate that Hercules-GPU software is in production status and evaluate its performance versus the CPU version<br /> * Evaluate goodness of fit for synthetic waveforms versus observed at 1.0 Hz, using Po Chen's updated CVM-S4 velocity model as the material properties source for the simulation.<br /> * [Optionally] Validate the simulation results generated by Hercules-GPU and AWP-GPU<br /> <br /> <br /> == Solver Parameters ==<br /> <br /> <br /> {| class=&quot;wikitable&quot; border=&quot;1&quot;<br /> |-<br /> ! Parameter<br /> ! Value<br /> ! Notes<br /> |-<br /> | Frequency<br /> | 1.0 Hz<br /> | <br /> |-<br /> | Simulation Length<br /> | 100 s<br /> | <br /> |-<br /> | Delta T<br /> | 0.005<br /> | <br /> |-<br /> | Plane Output Resolution<br /> | 250m<br /> | <br /> |-<br /> | I/O Print Rate<br /> | every 10 steps<br /> | <br /> |-<br /> | Station List<br /> | [[File:lahabra_titan_stations.txt]]<br /> | ?<br /> |-<br /> | Software Version<br /> | Hercules-GPU i3<br /> | GPU codes, no frequency dependent Q<br /> |}<br /> <br /> <br /> <br /> == Simulation Box / Velocity Model ==<br /> <br /> {| class=&quot;wikitable&quot; border=&quot;1&quot;<br /> |-<br /> ! Parameter<br /> ! Value<br /> ! Notes<br /> |-<br /> | Dimensions (km)<br /> | 180 x 135 x 61.875<br /> | <br /> |-<br /> | Bounding Box (LL)<br /> | -119.288842 34.120549, -118.354016 35.061096, -116.846030 34.025873, -117.780976 33.096503<br /> | <br /> |-<br /> | UCVM Version<br /> | 13.9.0<br /> | No heterogeneities<br /> |-<br /> | Velocity Model Versions<br /> | CVM-S4, CVM-S4 v26, CVM-S5<br /> | <br /> |- <br /> |Miniumum Vs<br /> | 200 m/s<br /> | <br /> |-<br /> | Samples per wavelength<br /> | 8<br /> |<br /> |-<br /> | Hercules Etree<br /> | ch-cvms400-100-4hz-200ms.e, ch-cvms426-223-4hz-200ms.e<br /> | CVM-S5 etree?<br /> |}<br /> <br /> <br /> == Sources ==<br /> <br /> The simulation will be repeated for two point sources and one extended source.<br /> <br /> <br /> === Point Source Parameters ===<br /> <br /> {| class=&quot;wikitable&quot; border=&quot;1&quot;<br /> |-<br /> ! Parameter<br /> ! Value<br /> ! Notes<br /> |-<br /> | Event Name<br /> | La Habra<br /> | <br /> |-<br /> | Origin Time<br /> | 2014/03/29 04:09:42.97<br /> | Source: En-Jui<br /> |-<br /> | Origin Location<br /> | -117.930; 33.922; 5.0km<br /> | Source: En-Jui<br /> |-<br /> | Strike/Dip/Rake 1<br /> | 134/55/155<br /> | Source: En-Jui, initial<br /> |-<br /> | Strike/Dip/Rake 2<br /> | 239/70/38<br /> | Source: En-Jui, based on review of aftershock sequence<br /> |-<br /> | Rise Time<br /> | 0.75 s<br /> | <br /> |}<br /> <br /> <br /> === SRC Format La Habra Source ===<br /> *MAGNITUDE = 5.12<br /> *FAULT_LENGTH = 5.0<br /> *FAULT_WIDTH = 2.25<br /> *DEPTH_TO_TOP = 4.7125<br /> *STRIKE = 239<br /> *RAKE = 38<br /> *DIP = 79<br /> *LAT_TOP_CENTER = 33.9119<br /> *LON_TOP_CENTER = -117.940<br /> *HYPO_ALONG_STK = 0.0<br /> *HYPO_DOWN_DIP = 1.125<br /> *DLEN = 0.1<br /> *DWID = 0.1<br /> <br /> == BBP Run for La Habra ==<br /> *[http://bbpvault.usc.edu/bbp/tests/la_habra/run1/la_habra_2014_06_19.src SRC for this event]<br /> <br /> *[http://bbpvault.usc.edu/bbp/tests/la_habra/run1/la_habra_2014_06_19.png SRF Image]<br /> *[http://bbpvault.usc.edu/bbp/tests/la_habra/run1/la_habra_2014_06_19.srf SRF for this SRC]<br /> <br /> == La Habra Earthquake Observations ==<br /> *[http://strongmotioncenter.org/vdc/scripts/event.plx?evt=1295 PEER Data Center]<br /> <br /> == La Habra References ==<br /> *[http://www.scsn.org/2014lahabra.html SCSN La Habra Event Summary]<br /> *[http://www.data.scec.org/MomentTensor/solutions/web_15481673/ci15481673_MT.html SCSN La Habra Moment Tensor Solution]<br /> <br /> == References ==<br /> # Bielak, J., H. Karaoglu, and R. Taborda, 2011. Memory-efficient displacement-based internal friction for wave propagation simulation, Geophysics, 76(6):T131-T145.<br /> # Taborda, R., Lopez, J., Karaoglu, H., Urbanic, J., and Bielak, J. (2010). Speeding up finite element wave propagation for large-scale earthquake simulations. Technical Report CMU-PDL-10-109, Carnegie Mellon University, Parallel Data Lab. <br /> # Tu, T., Yu, H., Ramírez-Guzmán, L., Bielak, J., Ghattas, O., Ma, K.-L., &amp; O’Hallaron, D.R., 2006. From mesh generation to scientific visualization: an end-to-end approach to parallel supercomputing, in Proceedings of the 2006 ACM/IEEE International Conference for High Performance Computing, Networking, Storage and Analysis, p. 15, IEEE Computer Society, Tampa, Florida.</div> Patrices https://strike.scec.org/scecwiki/index.php?title=La_Habra_Simulations_on_Titan&diff=10371 La Habra Simulations on Titan 2014-06-18T18:46:53Z <p>Patrices: </p> <hr /> <div>== Overview ==<br /> <br /> A series of simulations modelling the La Habra 5.1 event will be performed on ORNL Titan with in order to address these scientific and computational goals:<br /> <br /> * Demonstrate that Hercules-GPU software is in production status and evaluate its performance versus the CPU version<br /> * Evaluate goodness of fit for synthetic waveforms versus observed at 1.0 Hz, using Po Chen's updated CVM-S4 velocity model as the material properties source for the simulation.<br /> * [Optionally] Validate the simulation results generated by Hercules-GPU and AWP-GPU<br /> <br /> <br /> == Solver Parameters ==<br /> <br /> <br /> {| class=&quot;wikitable&quot; border=&quot;1&quot;<br /> |-<br /> ! Parameter<br /> ! Value<br /> ! Notes<br /> |-<br /> | Frequency<br /> | 1.0 Hz<br /> | <br /> |-<br /> | Simulation Length<br /> | 100 s<br /> | <br /> |-<br /> | Delta T<br /> | 0.005<br /> | Tentative - subject to stability check<br /> |-<br /> | Plane Output Resolution<br /> | 250m<br /> | <br /> |-<br /> | I/O Print Rate<br /> | every 10 steps<br /> | <br /> |-<br /> | Station List<br /> | [[File:lahabra_titan_stations.txt]]<br /> | ?<br /> |-<br /> | Software Version<br /> | Hercules-GPU i3<br /> | GPU codes, no frequency dependent Q<br /> |}<br /> <br /> <br /> <br /> == Simulation Box / Velocity Model ==<br /> <br /> {| class=&quot;wikitable&quot; border=&quot;1&quot;<br /> |-<br /> ! Parameter<br /> ! Value<br /> ! Notes<br /> |-<br /> | Dimensions (km)<br /> | 180 x 135 x 61.875<br /> | <br /> |-<br /> | Bounding Box (LL)<br /> | -119.288842 34.120549, -118.354016 35.061096, -116.846030 34.025873, -117.780976 33.096503<br /> | <br /> |-<br /> | UCVM Version<br /> | 13.9.0<br /> | No heterogeneities<br /> |-<br /> | Velocity Model Versions<br /> | CVM-S4, CVM-S4 v26, CVM-S5<br /> | <br /> |- <br /> |Miniumum Vs<br /> | 200 m/s<br /> | <br /> |-<br /> | Samples per wavelength<br /> | 8<br /> |<br /> |-<br /> | Hercules Etree<br /> | ch-cvms400-100-4hz-200ms.e, ch-cvms426-223-4hz-200ms.e<br /> | CVM-S5 etree?<br /> |}<br /> <br /> <br /> == Source Parameters ==<br /> <br /> {| class=&quot;wikitable&quot; border=&quot;1&quot;<br /> |-<br /> ! Parameter<br /> ! Value<br /> ! Notes<br /> |-<br /> | Event Name<br /> | La Habra<br /> | <br /> |-<br /> | Origin Time<br /> | 2014/03/29 04:09:42.97<br /> | Source: En-Jui<br /> |-<br /> | Origin Location<br /> | -117.930; 33.922; 5.0km<br /> | Source: En-Jui<br /> |-<br /> | Strike/Dip/Rake<br /> | 134/55/155<br /> | Source: En-Jui<br /> |-<br /> | Slip Function<br /> | ?<br /> | ?<br /> |}<br /> <br /> <br /> == SRC Format La Habra Source ==<br /> <br /> Example information we need:<br /> <br /> *MAGNITUDE = 5.39<br /> *FAULT_LENGTH = 6.30<br /> *FAULT_WIDTH = 4.60<br /> *DEPTH_TO_TOP = 12.79<br /> *STRIKE = 296<br /> *RAKE = 146<br /> *DIP = 66<br /> *LAT_TOP_CENTER = 33.939<br /> *LON_TOP_CENTER = -117.771<br /> *HYPO_ALONG_STK = 0.0<br /> *HYPO_DOWN_DIP = 2.30<br /> <br /> <br /> == References ==<br /> <br /> # Bielak, J., H. Karaoglu, and R. Taborda, 2011. Memory-efficient displacement-based internal friction for wave propagation simulation, Geophysics, 76(6):T131-T145.<br /> # Taborda, R., Lopez, J., Karaoglu, H., Urbanic, J., and Bielak, J. (2010). Speeding up finite element wave propagation for large-scale earthquake simulations. Technical Report CMU-PDL-10-109, Carnegie Mellon University, Parallel Data Lab. <br /> # Tu, T., Yu, H., Ramírez-Guzmán, L., Bielak, J., Ghattas, O., Ma, K.-L., &amp; O’Hallaron, D.R., 2006. From mesh generation to scientific visualization: an end-to-end approach to parallel supercomputing, in Proceedings of the 2006 ACM/IEEE International Conference for High Performance Computing, Networking, Storage and Analysis, p. 15, IEEE Computer Society, Tampa, Florida.</div> Patrices https://strike.scec.org/scecwiki/index.php?title=La_Habra_Simulations_on_Titan&diff=10370 La Habra Simulations on Titan 2014-06-18T18:37:23Z <p>Patrices: </p> <hr /> <div>== Overview ==<br /> <br /> A series of simulations modelling the La Habra 5.1 event will be performed on ORNL Titan with in order to address these scientific and computational goals:<br /> <br /> * Demonstrate that Hercules-GPU software is in production status and evaluate its performance versus the CPU version<br /> * Evaluate goodness of fit for synthetic waveforms versus observed at 1.0 Hz, using Po Chen's updated CVM-S4 velocity model as the material properties source for the simulation.<br /> * [Optionally] Validate the simulation results generated by Hercules-GPU and AWP-GPU<br /> <br /> <br /> == Solver Parameters ==<br /> <br /> <br /> {| class=&quot;wikitable&quot; border=&quot;1&quot;<br /> |-<br /> ! Parameter<br /> ! Value<br /> ! Notes<br /> |-<br /> | Frequency<br /> | 1.0 Hz<br /> | <br /> |-<br /> | Simulation Length<br /> | 100 s<br /> | <br /> |-<br /> | Delta T<br /> | 0.005<br /> | Tentative - subject to stability check<br /> |-<br /> | Plane Output Resolution<br /> | 250m<br /> | <br /> |-<br /> | I/O Print Rate<br /> | every 10 steps<br /> | <br /> |-<br /> | Station List<br /> | [[File:lahabra_titan_stations.txt]]<br /> | ?<br /> |-<br /> | Software Version<br /> | Hercules-GPU i3<br /> | GPU codes, no frequency dependent Q<br /> |}<br /> <br /> <br /> <br /> == Simulation Box / Velocity Model ==<br /> <br /> {| class=&quot;wikitable&quot; border=&quot;1&quot;<br /> |-<br /> ! Parameter<br /> ! Value<br /> ! Notes<br /> |-<br /> | Dimensions (km)<br /> | 180 x 135 x 61.875<br /> | <br /> |-<br /> | Bounding Box (LL)<br /> | -119.288842 34.120549, -118.354016 35.061096, -116.846030 34.025873, -117.780976 33.096503<br /> | <br /> |-<br /> | UCVM Version<br /> | 13.9.0<br /> | No heterogeneities<br /> |-<br /> | Velocity Model Versions<br /> | CVM-S4, CVM-S4 v26, CVM-S5<br /> | <br /> |- <br /> |Miniumum Vs<br /> | 200 m/s<br /> | <br /> |-<br /> | Samples per wavelength<br /> | 8<br /> |<br /> |-<br /> | Hercules Etree<br /> | ch-cvms400-100-4hz-200ms.e, ch-cvms426-223-4hz-200ms.e<br /> | CVM-S5 etree?<br /> |}<br /> <br /> <br /> == Source Parameters ==<br /> <br /> {| class=&quot;wikitable&quot; border=&quot;1&quot;<br /> |-<br /> ! Parameter<br /> ! Value<br /> ! Notes<br /> |-<br /> | Event Name<br /> | La Habra<br /> | <br /> |-<br /> | Origin Time<br /> | 2014/03/29 04:09:42.97<br /> | Source: En-Jui<br /> |-<br /> | Origin Location<br /> | -117.930; 33.922; 5.0km<br /> | Source: En-Jui<br /> |-<br /> | Strike/Dip/Rake<br /> | 134/55/155<br /> | Source: En-Jui<br /> |-<br /> | Slip Function<br /> | ?<br /> | ?<br /> |}<br /> <br /> <br /> == SRC Format La Habra Source ==<br /> *MAGNITUDE = 5.39<br /> *FAULT_LENGTH = 6.30<br /> *FAULT_WIDTH = 4.60<br /> *DEPTH_TO_TOP = 12.79<br /> *STRIKE = 296<br /> *RAKE = 146<br /> *DIP = 66<br /> *LAT_TOP_CENTER = 33.939<br /> *LON_TOP_CENTER = -117.771<br /> *HYPO_ALONG_STK = 0.0<br /> *HYPO_DOWN_DIP = 2.30<br /> <br /> <br /> == References ==<br /> <br /> # Bielak, J., H. Karaoglu, and R. Taborda, 2011. Memory-efficient displacement-based internal friction for wave propagation simulation, Geophysics, 76(6):T131-T145.<br /> # Taborda, R., Lopez, J., Karaoglu, H., Urbanic, J., and Bielak, J. (2010). Speeding up finite element wave propagation for large-scale earthquake simulations. Technical Report CMU-PDL-10-109, Carnegie Mellon University, Parallel Data Lab. <br /> # Tu, T., Yu, H., Ramírez-Guzmán, L., Bielak, J., Ghattas, O., Ma, K.-L., &amp; O’Hallaron, D.R., 2006. From mesh generation to scientific visualization: an end-to-end approach to parallel supercomputing, in Proceedings of the 2006 ACM/IEEE International Conference for High Performance Computing, Networking, Storage and Analysis, p. 15, IEEE Computer Society, Tampa, Florida.</div> Patrices https://strike.scec.org/scecwiki/index.php?title=La_Habra_Simulations_on_Titan&diff=10369 La Habra Simulations on Titan 2014-06-18T18:35:09Z <p>Patrices: </p> <hr /> <div>== Overview ==<br /> <br /> A series of simulations modelling the La Habra 5.1 event will be performed on ORNL Titan with in order to address these scientific and computational goals:<br /> <br /> * Demonstrate that Hercules-GPU software is in production status and evaluate its performance versus the CPU version<br /> * Evaluate goodness of fit for synthetic waveforms versus observed at 1.0 Hz, using Po Chen's updated CVM-S4 velocity model as the material properties source for the simulation.<br /> * [Optionally] Validate the simulation results generated by Hercules-GPU and AWP-GPU<br /> <br /> <br /> == Solver Parameters ==<br /> <br /> <br /> {| class=&quot;wikitable&quot; border=&quot;1&quot;<br /> |-<br /> ! Parameter<br /> ! Value<br /> ! Notes<br /> |-<br /> | Frequency<br /> | 1.0 Hz<br /> | <br /> |-<br /> | Simulation Length<br /> | 100 s<br /> | <br /> |-<br /> | Delta T<br /> | 0.005<br /> | <br /> |-<br /> | Plane Output Resolution<br /> | 250m<br /> | <br /> |-<br /> | I/O Print Rate<br /> | every 10 steps<br /> | <br /> |-<br /> | Station List<br /> | [[File:lahabra_titan_stations.txt]]<br /> | ?<br /> |-<br /> | Software Version<br /> | Hercules-GPU i3<br /> | GPU codes, no frequency dependent Q<br /> |}<br /> <br /> <br /> <br /> == Simulation Box / Velocity Model ==<br /> <br /> {| class=&quot;wikitable&quot; border=&quot;1&quot;<br /> |-<br /> ! Parameter<br /> ! Value<br /> ! Notes<br /> |-<br /> | Dimensions (km)<br /> | 180 x 135 x 61.875<br /> | <br /> |-<br /> | Bounding Box (LL)<br /> | -119.288842 34.120549, -118.354016 35.061096, -116.846030 34.025873, -117.780976 33.096503<br /> | <br /> |-<br /> | UCVM Version<br /> | 13.9.0<br /> | No heterogeneities<br /> |-<br /> | Velocity Model Versions<br /> | CVM-S4, CVM-S4 v26, CVM-S5<br /> | <br /> |- <br /> |Miniumum Vs<br /> | 200 m/s<br /> | <br /> |-<br /> | Samples per wavelength<br /> | 8<br /> |<br /> |-<br /> | Hercules Etree<br /> | ch-cvms400-100-4hz-200ms.e, ch-cvms426-223-4hz-200ms.e<br /> | CVM-S5 etree?<br /> |}<br /> <br /> <br /> == Source Parameters ==<br /> <br /> {| class=&quot;wikitable&quot; border=&quot;1&quot;<br /> |-<br /> ! Parameter<br /> ! Value<br /> ! Notes<br /> |-<br /> | Event Name<br /> | La Habra<br /> | <br /> |-<br /> | Origin Time<br /> | 2014/03/29 04:09:42.97<br /> | Source: En-Jui<br /> |-<br /> | Origin Location<br /> | -117.930; 33.922; 5.0km<br /> | Source: En-Jui<br /> |-<br /> | Strike/Dip/Rake<br /> | 134/55/155<br /> | Source: En-Jui<br /> |-<br /> | Slip Function<br /> | ?<br /> | ?<br /> |}<br /> <br /> <br /> == SRC Format La Habra Source ==<br /> *MAGNITUDE = 5.39<br /> *FAULT_LENGTH = 6.30<br /> *FAULT_WIDTH = 4.60<br /> *DEPTH_TO_TOP = 12.79<br /> *STRIKE = 296<br /> *RAKE = 146<br /> *DIP = 66<br /> *LAT_TOP_CENTER = 33.939<br /> *LON_TOP_CENTER = -117.771<br /> *HYPO_ALONG_STK = 0.0<br /> *HYPO_DOWN_DIP = 2.30<br /> <br /> <br /> == References ==<br /> <br /> # Bielak, J., H. Karaoglu, and R. Taborda, 2011. Memory-efficient displacement-based internal friction for wave propagation simulation, Geophysics, 76(6):T131-T145.<br /> # Taborda, R., Lopez, J., Karaoglu, H., Urbanic, J., and Bielak, J. (2010). Speeding up finite element wave propagation for large-scale earthquake simulations. Technical Report CMU-PDL-10-109, Carnegie Mellon University, Parallel Data Lab. <br /> # Tu, T., Yu, H., Ramírez-Guzmán, L., Bielak, J., Ghattas, O., Ma, K.-L., &amp; O’Hallaron, D.R., 2006. From mesh generation to scientific visualization: an end-to-end approach to parallel supercomputing, in Proceedings of the 2006 ACM/IEEE International Conference for High Performance Computing, Networking, Storage and Analysis, p. 15, IEEE Computer Society, Tampa, Florida.</div> Patrices https://strike.scec.org/scecwiki/index.php?title=La_Habra_Simulations_on_Titan&diff=10368 La Habra Simulations on Titan 2014-06-18T18:17:32Z <p>Patrices: </p> <hr /> <div>== Overview ==<br /> <br /> A series of simulations modelling the La Habra 5.1 event will be performed on ORNL Titan with in order to address these scientific and computational goals:<br /> <br /> * Demonstrate that Hercules-GPU software is in production status and evaluate its performance versus the CPU version<br /> * Evaluate goodness of fit for synthetic waveforms versus observed at 1.0 Hz, using Po Chen's updated CVM-S4 velocity model as the material properties source for the simulation.<br /> * [Optionally] Validate the simulation results generated by Hercules-GPU and AWP-GPU<br /> <br /> <br /> == Solver Parameters ==<br /> <br /> <br /> {| class=&quot;wikitable&quot; border=&quot;1&quot;<br /> |-<br /> ! Parameter<br /> ! Value<br /> ! Notes<br /> |-<br /> | Frequency<br /> | 1.0 Hz<br /> | <br /> |-<br /> | Simulation Length<br /> | 100 s<br /> | <br /> |-<br /> | Delta T<br /> | 0.005<br /> | <br /> |-<br /> | Plane Output Resolution<br /> | 250m<br /> | <br /> |-<br /> | I/O Print Rate<br /> | every 10 steps<br /> | <br /> |-<br /> | Station List<br /> | [[File:lahabra_titan_stations.txt]]<br /> | ?<br /> |-<br /> | Software Version<br /> | Hercules-GPU i3<br /> | GPU codes, no freqency dependent Q<br /> |}<br /> <br /> <br /> <br /> == Simulation Box / Velocity Model ==<br /> <br /> {| class=&quot;wikitable&quot; border=&quot;1&quot;<br /> |-<br /> ! Parameter<br /> ! Value<br /> ! Notes<br /> |-<br /> | Dimensions (km)<br /> | 180 x 135 x 61.875<br /> | <br /> |-<br /> | Bounding Box (LL)<br /> | -119.288842 34.120549, -118.354016 35.061096, -116.846030 34.025873, -117.780976 33.096503<br /> | <br /> |-<br /> | UCVM Version<br /> | 13.9.0<br /> | No heterogeneities<br /> |-<br /> | Velocity Model Versions<br /> | CVM-S4, CVM-S4 v26, CVM-S5<br /> | <br /> |- <br /> |Miniumum Vs<br /> | 200 m/s<br /> | <br /> |-<br /> | Samples per wavelength<br /> | 8<br /> |<br /> |-<br /> | Hercules Etree<br /> | ch-cvms400-100-4hz-200ms.e, ch-cvms426-223-4hz-200ms.e<br /> | CVM-S5 etree?<br /> |}<br /> <br /> <br /> == Source Parameters ==<br /> <br /> {| class=&quot;wikitable&quot; border=&quot;1&quot;<br /> |-<br /> ! Parameter<br /> ! Value<br /> ! Notes<br /> |-<br /> | Event Name<br /> | La Habra<br /> | <br /> |-<br /> | Origin Time<br /> | 2014/03/29 04:09:42.97<br /> | Source: En-Jui<br /> |-<br /> | Origin Location<br /> | -117.930; 33.922; 5.0km<br /> | Source: En-Jui<br /> |-<br /> | Strike/Dip/Rake<br /> | 134/55/155<br /> | Source: En-Jui<br /> |-<br /> | Slip Function<br /> | ?<br /> | ?<br /> |}<br /> <br /> <br /> == SRC Format La Habra Source ==<br /> *MAGNITUDE = 5.39<br /> *FAULT_LENGTH = 6.30<br /> *FAULT_WIDTH = 4.60<br /> *DEPTH_TO_TOP = 12.79<br /> *STRIKE = 296<br /> *RAKE = 146<br /> *DIP = 66<br /> *LAT_TOP_CENTER = 33.939<br /> *LON_TOP_CENTER = -117.771<br /> *HYPO_ALONG_STK = 0.0<br /> *HYPO_DOWN_DIP = 2.30<br /> <br /> <br /> == References ==<br /> <br /> # Bielak, J., H. Karaoglu, and R. Taborda, 2011. Memory-efficient displacement-based internal friction for wave propagation simulation, Geophysics, 76(6):T131-T145.<br /> # Taborda, R., Lopez, J., Karaoglu, H., Urbanic, J., and Bielak, J. (2010). Speeding up finite element wave propagation for large-scale earthquake simulations. Technical Report CMU-PDL-10-109, Carnegie Mellon University, Parallel Data Lab. <br /> # Tu, T., Yu, H., Ramírez-Guzmán, L., Bielak, J., Ghattas, O., Ma, K.-L., &amp; O’Hallaron, D.R., 2006. From mesh generation to scientific visualization: an end-to-end approach to parallel supercomputing, in Proceedings of the 2006 ACM/IEEE International Conference for High Performance Computing, Networking, Storage and Analysis, p. 15, IEEE Computer Society, Tampa, Florida.</div> Patrices https://strike.scec.org/scecwiki/index.php?title=La_Habra_Simulations_on_Titan&diff=10367 La Habra Simulations on Titan 2014-06-18T18:13:31Z <p>Patrices: </p> <hr /> <div>== Overview ==<br /> <br /> A series of simulations modelling the La Habra 5.1 event will be performed on ORNL Titan with in order to address these scientific and computational goals:<br /> <br /> * Demonstrate that Hercules-GPU software is in production status and evaluate its performance versus the CPU version<br /> * Evaluate goodness of fit for synthetic waveforms versus observed at 1.0 Hz, using Po Chen's updated CVM-S4 velocity model as the material properties source for the simulation.<br /> * [Optionally] Validate the simulation results generated by Hercules-GPU and AWP-GPU<br /> <br /> <br /> == Solver Parameters ==<br /> <br /> <br /> {| class=&quot;wikitable&quot; border=&quot;1&quot;<br /> |-<br /> ! Parameter<br /> ! Value<br /> ! Notes<br /> |-<br /> | Frequency<br /> | 1.0 Hz<br /> | <br /> |-<br /> | Simulation Length<br /> | 100 s<br /> | <br /> |-<br /> | Delta T<br /> | 0.005<br /> | <br /> |-<br /> | Plane Output Resolution<br /> | 250m<br /> | <br /> |-<br /> | I/O Print Rate<br /> | every 10 steps<br /> | <br /> |-<br /> | Station List<br /> | [[File:lahabra_titan_stations.txt]]<br /> | ?<br /> |-<br /> | Software Version<br /> | Hercules-GPU i3<br /> | GPU codes, no freqency dependent Q<br /> |}<br /> <br /> <br /> <br /> == Simulation Box / Velocity Model ==<br /> <br /> {| class=&quot;wikitable&quot; border=&quot;1&quot;<br /> |-<br /> ! Parameter<br /> ! Value<br /> ! Notes<br /> |-<br /> | Dimensions (km)<br /> | 180 x 135 x 61.875<br /> | <br /> |-<br /> | Bounding Box (LL)<br /> | -119.288842 34.120549, -118.354016 35.061096, -116.846030 34.025873, -117.780976 33.096503<br /> | <br /> |-<br /> | UCVM Version<br /> | 13.9.0<br /> | No heterogeneities<br /> |-<br /> | Velocity Model Versions<br /> | CVM-S4, CVM-S4 v26, CVM-S5<br /> | <br /> |- <br /> |Miniumum Vs<br /> | 200 m/s<br /> | <br /> |-<br /> | Samples per wavelength<br /> | 8<br /> |<br /> |-<br /> | Hercules Etree<br /> | TBD<br /> |<br /> |}<br /> <br /> <br /> == Source Parameters ==<br /> <br /> {| class=&quot;wikitable&quot; border=&quot;1&quot;<br /> |-<br /> ! Parameter<br /> ! Value<br /> ! Notes<br /> |-<br /> | Event Name<br /> | La Habra<br /> | <br /> |-<br /> | Origin Time<br /> | 2014/03/29 04:09:42.97<br /> | Source: En-Jui<br /> |-<br /> | Origin Location<br /> | -117.930; 33.922; 5.0km<br /> | Source: En-Jui<br /> |-<br /> | Strike/Dip/Rake<br /> | 134/55/155<br /> | Source: En-Jui<br /> |-<br /> | Slip Function<br /> | ?<br /> | ?<br /> |}<br /> <br /> <br /> == SRC Format La Habra Source ==<br /> *MAGNITUDE = 5.39<br /> *FAULT_LENGTH = 6.30<br /> *FAULT_WIDTH = 4.60<br /> *DEPTH_TO_TOP = 12.79<br /> *STRIKE = 296<br /> *RAKE = 146<br /> *DIP = 66<br /> *LAT_TOP_CENTER = 33.939<br /> *LON_TOP_CENTER = -117.771<br /> *HYPO_ALONG_STK = 0.0<br /> *HYPO_DOWN_DIP = 2.30<br /> <br /> <br /> == References ==<br /> <br /> # Bielak, J., H. Karaoglu, and R. Taborda, 2011. Memory-efficient displacement-based internal friction for wave propagation simulation, Geophysics, 76(6):T131-T145.<br /> # Taborda, R., Lopez, J., Karaoglu, H., Urbanic, J., and Bielak, J. (2010). Speeding up finite element wave propagation for large-scale earthquake simulations. Technical Report CMU-PDL-10-109, Carnegie Mellon University, Parallel Data Lab. <br /> # Tu, T., Yu, H., Ramírez-Guzmán, L., Bielak, J., Ghattas, O., Ma, K.-L., &amp; O’Hallaron, D.R., 2006. From mesh generation to scientific visualization: an end-to-end approach to parallel supercomputing, in Proceedings of the 2006 ACM/IEEE International Conference for High Performance Computing, Networking, Storage and Analysis, p. 15, IEEE Computer Society, Tampa, Florida.</div> Patrices https://strike.scec.org/scecwiki/index.php?title=La_Habra_Simulations_on_Titan&diff=10366 La Habra Simulations on Titan 2014-06-18T18:12:40Z <p>Patrices: </p> <hr /> <div>== Overview ==<br /> <br /> A series of simulations modelling the La Habra 5.1 event will be performed on ORNL Titan with in order to address these scientific and computational goals:<br /> <br /> * Demonstrate that Hercules-GPU software is in production status and evaluate its performance versus the CPU version<br /> * Evaluate goodness of fit for synthetic waveforms versus observed at 1.0 Hz, using Po Chen's updated CVM-S4 velocity model as the material properties source for the simulation.<br /> * [Optionally] Validate the simulation results generated by Hercules-GPU and AWP-GPU<br /> <br /> <br /> == Solver Parameters ==<br /> <br /> <br /> {| class=&quot;wikitable&quot; border=&quot;1&quot;<br /> |-<br /> ! Parameter<br /> ! Value<br /> ! Notes<br /> |-<br /> | Frequency<br /> | 1.0 Hz<br /> | <br /> |-<br /> | Simulation Length<br /> | 100 s<br /> | <br /> |-<br /> | Delta T<br /> | 0.005<br /> | <br /> |-<br /> | Plane Output Resolution<br /> | 250m<br /> | <br /> |-<br /> | I/O Print Rate<br /> | every 10 steps<br /> | <br /> |-<br /> | Station List<br /> | [[File:lahabra_titan_stations.txt]]<br /> | ?<br /> |-<br /> | Software Version<br /> | Hercules-GPU i3<br /> | GPU codes, no freqency dependent Q<br /> |}<br /> <br /> <br /> <br /> == Simulation Box / Velocity Model ==<br /> <br /> {| class=&quot;wikitable&quot; border=&quot;1&quot;<br /> |-<br /> ! Parameter<br /> ! Value<br /> ! Notes<br /> |-<br /> | Dimensions (km)<br /> | 180 x 135 x 61.875<br /> | <br /> |-<br /> | Bounding Box (LL)<br /> | -119.288842 34.120549, -118.354016 35.061096, -116.846030 34.025873, -117.780976 33.096503<br /> | <br /> |-<br /> | UCVM Version<br /> | 13.9.0<br /> | No heterogeneities<br /> |-<br /> | Velocity Model Versions<br /> | CVM-S4, CVM-S4 v26, CVM-S5<br /> | <br /> |- <br /> |Miniumum Vs<br /> | 200 m/s<br /> | <br /> |-<br /> | Samples per wavelength<br /> | 8<br /> |<br /> |-<br /> | Hercules Etree<br /> | TBD<br /> |<br /> |}<br /> <br /> <br /> == Source Parameters ==<br /> <br /> {| class=&quot;wikitable&quot; border=&quot;1&quot;<br /> |-<br /> ! Parameter<br /> ! Value<br /> ! Notes<br /> |-<br /> | Origin Time<br /> | 2014/03/29 04:09:42.97<br /> | Source: En-Jui<br /> |-<br /> | Origin Location<br /> | -117.930; 33.922; 5.0km<br /> | Source: En-Jui<br /> |-<br /> | Strike/Dip/Rake<br /> | 134/55/155<br /> | Source: En-Jui<br /> |-<br /> | Slip Function<br /> | ?<br /> | ?<br /> |}<br /> <br /> <br /> == SRC Format La Habra Source ==<br /> *MAGNITUDE = 5.39<br /> *FAULT_LENGTH = 6.30<br /> *FAULT_WIDTH = 4.60<br /> *DEPTH_TO_TOP = 12.79<br /> *STRIKE = 296<br /> *RAKE = 146<br /> *DIP = 66<br /> *LAT_TOP_CENTER = 33.939<br /> *LON_TOP_CENTER = -117.771<br /> *HYPO_ALONG_STK = 0.0<br /> *HYPO_DOWN_DIP = 2.30<br /> <br /> <br /> == References ==<br /> <br /> # Bielak, J., H. Karaoglu, and R. Taborda, 2011. Memory-efficient displacement-based internal friction for wave propagation simulation, Geophysics, 76(6):T131-T145.<br /> # Taborda, R., Lopez, J., Karaoglu, H., Urbanic, J., and Bielak, J. (2010). Speeding up finite element wave propagation for large-scale earthquake simulations. Technical Report CMU-PDL-10-109, Carnegie Mellon University, Parallel Data Lab. <br /> # Tu, T., Yu, H., Ramírez-Guzmán, L., Bielak, J., Ghattas, O., Ma, K.-L., &amp; O’Hallaron, D.R., 2006. From mesh generation to scientific visualization: an end-to-end approach to parallel supercomputing, in Proceedings of the 2006 ACM/IEEE International Conference for High Performance Computing, Networking, Storage and Analysis, p. 15, IEEE Computer Society, Tampa, Florida.</div> Patrices https://strike.scec.org/scecwiki/index.php?title=La_Habra_Simulations_on_Titan&diff=10365 La Habra Simulations on Titan 2014-06-18T18:12:25Z <p>Patrices: </p> <hr /> <div>== Overview ==<br /> <br /> A series of simulations modelling the La Habra 5.1 event will be performed on ORNL Titan with in order to address these scientific and computational goals:<br /> <br /> * Demonstrate that Hercules-GPU software is in production status and evaluate its performance versus the CPU version<br /> * Evaluate goodness of fit for synthetic waveforms versus observed at 1.0 Hz, using Po Chen's updated CVM-S4 velocity model as the material properties source for the simulation.<br /> * [Optionally] Validate the simulation results generated by Hercules-GPU and AWP-GPU<br /> <br /> <br /> == Solver Parameters ==<br /> <br /> <br /> {| class=&quot;wikitable&quot; border=&quot;1&quot;<br /> |-<br /> ! Parameter<br /> ! Value<br /> ! Notes<br /> |-<br /> | Frequency<br /> | 1.0 Hz<br /> | <br /> |-<br /> | Simulation Length<br /> | 100 s<br /> | <br /> |-<br /> | Delta T<br /> | 0.005<br /> | <br /> |-<br /> | Plane Output Resolution<br /> | 250m<br /> | <br /> |-<br /> | I/O Print Rate<br /> | every 10 steps<br /> | <br /> |-<br /> | Station List<br /> | [[File:lahabra_titan_stations.txt]]<br /> | ?<br /> |-<br /> | Software Version<br /> | Hercules-GPU i3<br /> | GPU codes, no freqency dependent Q<br /> |}<br /> <br /> <br /> <br /> == Simulation Box / Velocity Model ==<br /> <br /> {| class=&quot;wikitable&quot; border=&quot;1&quot;<br /> |-<br /> ! Parameter<br /> ! Value<br /> ! Notes<br /> |-<br /> | Dimensions (km)<br /> | 180 x 135 x 61.875<br /> | <br /> |-<br /> | Bounding Box (LL)<br /> | -119.288842 34.120549, -118.354016 35.061096, -116.846030 34.025873, -117.780976 33.096503<br /> | <br /> |-<br /> | UCVM Version<br /> | 13.9.0<br /> | No heterogeneities<br /> |-<br /> | Velocity Model Versions<br /> | CVM-S4, CVM-S4 v26, CVM-S5<br /> | <br /> |- <br /> |Miniumum Vs<br /> | 200 m/s<br /> | <br /> |-<br /> | Samples per wavelength<br /> | 8<br /> |<br /> |-<br /> | Hercules Etree<br /> | TBD<br /> |<br /> |}<br /> <br /> <br /> == Source Parameters ==<br /> <br /> {| class=&quot;wikitable&quot; border=&quot;1&quot;<br /> |-<br /> ! Parameter<br /> ! Value<br /> ! Notes<br /> |-<br /> | Origin Time<br /> | 2014/03/29 04:09:42.97<br /> | Source: En-Jui<br /> |-<br /> | Origin Location<br /> | -117.930; 33.922; 5.0km<br /> | Source: En-Jui<br /> |-<br /> | Strike/Dip/Rake<br /> | 134/55/155<br /> | Source: En-Jui<br /> |-<br /> | Slip Function<br /> | ?<br /> | ?<br /> |}<br /> <br /> <br /> == SRC Format La Habra Source ==<br /> *MAGNITUDE = 5.39<br /> *FAULT_LENGTH = 6.30<br /> *FAULT_WIDTH = 4.60<br /> *DEPTH_TO_TOP = 12.79<br /> *STRIKE = 296<br /> *RAKE = 146<br /> *DIP = 66<br /> *LAT_TOP_CENTER = 33.939<br /> *LON_TOP_CENTER = -117.771<br /> *HYPO_ALONG_STK = 0.0<br /> *HYPO_DOWN_DIP = 2.30<br /> <br /> == References ==<br /> <br /> # Bielak, J., H. Karaoglu, and R. Taborda, 2011. Memory-efficient displacement-based internal friction for wave propagation simulation, Geophysics, 76(6):T131-T145.<br /> # Taborda, R., Lopez, J., Karaoglu, H., Urbanic, J., and Bielak, J. (2010). Speeding up finite element wave propagation for large-scale earthquake simulations. Technical Report CMU-PDL-10-109, Carnegie Mellon University, Parallel Data Lab. <br /> # Tu, T., Yu, H., Ramírez-Guzmán, L., Bielak, J., Ghattas, O., Ma, K.-L., &amp; O’Hallaron, D.R., 2006. From mesh generation to scientific visualization: an end-to-end approach to parallel supercomputing, in Proceedings of the 2006 ACM/IEEE International Conference for High Performance Computing, Networking, Storage and Analysis, p. 15, IEEE Computer Society, Tampa, Florida.</div> Patrices https://strike.scec.org/scecwiki/index.php?title=La_Habra_Simulations_on_Titan&diff=10361 La Habra Simulations on Titan 2014-06-18T00:56:00Z <p>Patrices: </p> <hr /> <div>== Overview ==<br /> <br /> A series of simulations modelling the La Habra 5.1 event will be performed on ORNL Titan with in order to address these scientific and computational goals:<br /> <br /> * Demonstrate that Hercules-GPU software is in production status and evaluate its performance versus the CPU version<br /> * Evaluate goodness of fit for synthetic waveforms versus observed at 1.0 Hz, using Po Chen's updated CVM-S4 velocity model as the material properties source for the simulation.<br /> * [Optionally] Validate the simulation results generated by Hercules-GPU and AWP-GPU<br /> <br /> <br /> == Solver Parameters ==<br /> <br /> <br /> {| class=&quot;wikitable&quot; border=&quot;1&quot;<br /> |-<br /> ! Parameter<br /> ! Value<br /> ! Notes<br /> |-<br /> | Frequency<br /> | 1.0 Hz<br /> | <br /> |-<br /> | Simulation Length<br /> | 100 s<br /> | <br /> |-<br /> | Delta T<br /> | 0.001<br /> | ?<br /> |-<br /> | Plane Output Resolution<br /> | 250m<br /> | ?<br /> |-<br /> | I/O Print Rate<br /> | every 10 steps<br /> | ?<br /> |-<br /> | Station List<br /> | [[File:lahabra_titan_stations.txt]]<br /> | ?<br /> |-<br /> | Software Version<br /> | Hercules-GPU i3<br /> |<br /> |}<br /> <br /> <br /> <br /> == Simulation Box / Velocity Model ==<br /> <br /> {| class=&quot;wikitable&quot; border=&quot;1&quot;<br /> |-<br /> ! Parameter<br /> ! Value<br /> ! Notes<br /> |-<br /> | Dimensions (km)<br /> | 180 x 135 x 61.875<br /> | <br /> |-<br /> | Bounding Box (LL)<br /> | ?<br /> | <br /> |-<br /> | UCVM Version<br /> | ?<br /> | No heterogeneities<br /> |-<br /> | Velocity Model Version<br /> | CVM-S4 v26<br /> | ?<br /> |- <br /> |Miniumum Vs<br /> | 500 m/s<br /> | ?<br /> |-<br /> | Samples per wavelength<br /> | 8<br /> |<br /> |-<br /> | Hercules Etree<br /> | TBD<br /> |<br /> |}<br /> <br /> <br /> == Source Parameters ==<br /> <br /> {| class=&quot;wikitable&quot; border=&quot;1&quot;<br /> |-<br /> ! Parameter<br /> ! Value<br /> ! Notes<br /> |-<br /> | Origin Time<br /> | 2014/03/29 04:09:42.97<br /> | Source: En-Jui<br /> |-<br /> | Origin Location<br /> | -117.930; 33.922; 5.0km<br /> | Source: En-Jui<br /> |-<br /> | Strike/Dip/Rake<br /> | 134/55/155<br /> | Source: En-Jui<br /> |-<br /> | Slip Function<br /> | ?<br /> | ?<br /> |}<br /> <br /> <br /> == References ==<br /> <br /> # Bielak, J., H. Karaoglu, and R. Taborda, 2011. Memory-efficient displacement-based internal friction for wave propagation simulation, Geophysics, 76(6):T131-T145.<br /> # Taborda, R., Lopez, J., Karaoglu, H., Urbanic, J., and Bielak, J. (2010). Speeding up finite element wave propagation for large-scale earthquake simulations. Technical Report CMU-PDL-10-109, Carnegie Mellon University, Parallel Data Lab. <br /> # Tu, T., Yu, H., Ramírez-Guzmán, L., Bielak, J., Ghattas, O., Ma, K.-L., &amp; O’Hallaron, D.R., 2006. From mesh generation to scientific visualization: an end-to-end approach to parallel supercomputing, in Proceedings of the 2006 ACM/IEEE International Conference for High Performance Computing, Networking, Storage and Analysis, p. 15, IEEE Computer Society, Tampa, Florida.</div> Patrices https://strike.scec.org/scecwiki/index.php?title=La_Habra_Simulations_on_Titan&diff=10360 La Habra Simulations on Titan 2014-06-18T00:47:03Z <p>Patrices: Created page with '== Overview == A series of simulations modelling the La Habra 5.1 event will be performed on ORNL Titan with in order to address these scientific and computational goals: * Dem…'</p> <hr /> <div>== Overview ==<br /> <br /> A series of simulations modelling the La Habra 5.1 event will be performed on ORNL Titan with in order to address these scientific and computational goals:<br /> <br /> * Demonstrate that Hercules-GPU software is in production status and evaluate its performance versus the CPU version<br /> * Evaluate goodness of fit for synthetic waveforms versus observed at 1.0 Hz, using Po Chen's updated CVM-S4 velocity model as the material properties source for the simulation.<br /> * [Optionally] Validate the simulation results generated by Hercules-GPU and AWP-GPU<br /> <br /> <br /> == Solver Parameters ==<br /> <br /> <br /> {| class=&quot;wikitable&quot; border=&quot;1&quot;<br /> |-<br /> ! Parameter<br /> ! Value<br /> ! Notes<br /> |-<br /> | Frequency<br /> | 1.0 Hz<br /> | <br /> |-<br /> | Simulation Length<br /> | 100 s<br /> | <br /> |-<br /> | Delta T<br /> | 0.001<br /> | ?<br /> |-<br /> | Plane Output Resolution<br /> | 250m<br /> | ?<br /> |-<br /> | I/O Print Rate<br /> | every 10 steps<br /> | ?<br /> |-<br /> | Station List<br /> | [[File:lahabra_titan_stations.txt]]<br /> | <br /> |-<br /> | Software Version<br /> | Hercules-GPU i3<br /> |<br /> |}<br /> <br /> <br /> <br /> == Simulation Box / Velocity Model ==<br /> <br /> {| class=&quot;wikitable&quot; border=&quot;1&quot;<br /> |-<br /> ! Parameter<br /> ! Value<br /> ! Notes<br /> |-<br /> | Dimensions (km)<br /> | 180 x 135 x 61.875<br /> | <br /> |-<br /> | Bounding Box (LL)<br /> | ?<br /> | <br /> |-<br /> | Velocity Model<br /> | CVM-S4 v26<br /> | No heterogeneities<br /> |}<br /> <br /> <br /> == Source Parameters ==<br /> <br /> {| class=&quot;wikitable&quot; border=&quot;1&quot;<br /> |-<br /> ! Parameter<br /> ! Value<br /> ! Notes<br /> |-<br /> | Origin Time<br /> | 2014/03/29 04:09:42.97<br /> | Source: En-Jui<br /> |-<br /> | Origin Location<br /> | -117.930; 33.922; 5.0km<br /> | Source: En-Jui<br /> |-<br /> | Strike/Dip/Rake<br /> | 134/55/155<br /> | Source: En-Jui<br /> |-<br /> | Slip Function<br /> | ?<br /> | ?<br /> |}<br /> <br /> <br /> == References ==<br /> <br /> # Bielak, J., H. Karaoglu, and R. Taborda, 2011. Memory-efficient displacement-based internal friction for wave propagation simulation, Geophysics, 76(6):T131-T145.<br /> # Taborda, R., Lopez, J., Karaoglu, H., Urbanic, J., and Bielak, J. (2010). Speeding up finite element wave propagation for large-scale earthquake simulations. Technical Report CMU-PDL-10-109, Carnegie Mellon University, Parallel Data Lab. <br /> # Tu, T., Yu, H., Ramírez-Guzmán, L., Bielak, J., Ghattas, O., Ma, K.-L., &amp; O’Hallaron, D.R., 2006. From mesh generation to scientific visualization: an end-to-end approach to parallel supercomputing, in Proceedings of the 2006 ACM/IEEE International Conference for High Performance Computing, Networking, Storage and Analysis, p. 15, IEEE Computer Society, Tampa, Florida.</div> Patrices https://strike.scec.org/scecwiki/index.php?title=Main_Page&diff=10359 Main Page 2014-06-18T00:15:23Z <p>Patrices: </p> <hr /> <div>[[Image:SCEC_NSF-USGS-words_logom.png|left|150px]][[Image:nsf1.jpg|right|100px]][[Image:usgs-logo-color.jpg|right|150px]]<br /> <br /> == Community Modeling Environment (CME) ==<br /> <br /> This is a collaborative wiki site for SCEC's Community Modeling Environment (CME). The CME is a collaborative, interdisciplinary research group that applies advanced computer science technology to the problem of seismic hazard analysis. This SCEC community wiki is configured to support our distributed research by providing a collection point for information about SCEC scientific computing research projects.<br /> <br /> == List of All SCECpedia Pages ==<br /> The following link will take you to an alphabetically sorted list of all SCECpedia pages.<br /> *[http://scec.usc.edu/scecpedia/Special:AllPages List of All SCECpedia Pages]<br /> <br /> The following link will take you to a list of the most frequently visited SCECpedia pages .<br /> *[http://scec.usc.edu/scecpedia/Special:PopularPages Most Frequently Visited Pages]<br /> <br /> == Recent CME Wiki Entries ==<br /> The following list of SCECpedia topics are sorted chronologically with new and recently updated entries shown at the top of the list. This list of topics is not complete, so we recommend you use the [http://scec.usc.edu/scecpedia/Special:AllPages List of All SCECpedia Pages] link if you want a comprehensive list of all entries.<br /> <br /> == Recently Update Entries ==<br /> *[[La Habra Simulations on Titan]]<br /> *[[Kraken]]<br /> *[[UseIT]]<br /> *[[SSA]]<br /> **[[SSA_2014]]<br /> *[[UCVM]]<br /> *[[Broadband Platform]]<br /> *[[UCERF3]]<br /> *[[SCEC Data Storage]]<br /> *[[UGMS]]<br /> *[[F3DT]]<br /> *[[CVM-S5]]<br /> *[[XP Bill of Rights]]<br /> *[[IRIS DMS Meeting March 2014]]<br /> <br /> == CME Project Information ==<br /> *[[SI2_2014]]<br /> *[[Domain Reduction Method]]<br /> *[[Geoinformatics Project]]<br /> *[[Geoinformatics Phase II Project]]<br /> *[[High-F Project]]<br /> *[[SEISM Project]]<br /> *[[PetaSHA3 Project]]<br /> *[[High-F]]<br /> *[[CyberShake Project]]<br /> *[[Blue Waters]]<br /> *[[INCITE]]<br /> *[[CME Project]]<br /> <br /> == CME Software ==<br /> <br /> *[[Broadband Platform]]<br /> *[[UCVM 14.3.0]]<br /> *[[UCERF3.0]]<br /> *[[CSEP Distribution]]<br /> <br /> == CME Studies ==<br /> *[[CyberShake Study 14.2]]<br /> *[[UCVM_v14.3]]<br /> *[[Northridge 10Hz]]<br /> <br /> == CME Outcomes ==<br /> *[[Publications]]<br /> *[[Press Coverage]]<br /> <br /> == CME Activities ==<br /> *[[SCEC UGMS Committee Meeting]]<br /> *[[SI2 PI Meetings]]<br /> *[[CISN]]<br /> *[[SCEC Web Site]]<br /> *[[SCEC Software]]<br /> *[[CyberShake 1D Model]]<br /> *[[UCVM]]<br /> **[[UCVM - Latest Version]]<br /> **[[UCVM Workshop]]<br /> **[[UCVM User Guide]]<br /> **[[CVM-H]]<br /> **[[CVM-SI]]<br /> **[[Community Velocity Model]]<br /> **[[Z1.0 and Z2.5 SoCal Values]]<br /> **[[Cvmbycols]]<br /> **[[Lin Thurber CVM]]<br /> **[[CVM-H User Guide]]<br /> **[[CVM Evaluation]]<br /> *[[SWUS Project]]<br /> *[[Hadley-Kanamori]]<br /> *[[Northridge 10Hz]]<br /> *[[Earthquake Simulation Animations]]<br /> *[[SSA]]<br /> *[[Credits]]<br /> *[[CMM4]]<br /> *[[AGU]]<br /> **[[AGU Fall 2013]]<br /> **[[AGU Fall 2012]]<br /> **[[AGU Fall 2011]]<br /> *[[SC]]<br /> **[[SC13]] SC'13 Denver<br /> **[[SC12]] SC'12 Salt Lake City<br /> **[[UCERF3 Extended Earthquake Rupture Forecast]]<br /> *[[CVM-S4.26 Proposed Final Model]]<br /> *[[MFA]]<br /> *[[GTL]]<br /> *[[ShakeOut 2013 Response Planning]]<br /> **[[CME Meeting 2013]]<br /> **[[Broadband User Guide v13.9.0]]<br /> **[https://scec.usc.edu/it/Broadband_Platform Broadband Internal Wiki]<br /> *[[UCVM 13.9.0]]<br /> **[[UCVM 13.9.0 User Guide]]<br /> **[[UCVM 13.9.0 Advanced User Guide]]<br /> **[[UCVM 13.9.0 Developer Guide]]<br /> *[[CVM-H]]<br /> **[https://scec.usc.edu/it/SEISM SEISM Project Internal Wiki]<br /> **[[Software Documentation]]<br /> **[https://scec.usc.edu/it/Geoinformatics_Project Geoinformatics Project Internal wiki]<br /> *[[CISN Testing Center]]<br /> *[[AWP ODC GPU]]<br /> <br /> *[[SCEC Technical Activity Groups]]<br /> **[http://collaborate.scec.org/gmsv Ground Motion Simulation Validation (GMSV) Coordination Meeting]<br /> *[[Related Project Sites]]<br /> *[[Staff]]<br /> *[[Wiki Statistics]]<br /> *[[Usability]]<br /> *[[XSEDE/PRACE Workflow Workshop]]<br /> *[[California CVM Meeting - 3 April 2012]]<br /> *[[Data Management]]<br /> **[[Data Management Meeting - 24 Feb 2012]]<br /> *[[SCEC Visualization Projects]]<br /> **[[GlyphSea]]<br /> *[[Cloud Computing]]<br /> *[[Geoinformatics Project]]<br /> **[[CIG/Quest/IRIS Seismic Imaging Workshop]]<br /> *[[NWSC ASD]]<br /> **[https://scec.usc.edu/it/SI2_Metrics_Information SI2 Metrics]<br /> *[[CME Project]]<br /> **[[CME Meeting 2013]]<br /> **[[CME Meeting 2012]]<br /> **[[CME Meeting 2011]]<br /> **[[CME Meeting 2010]]<br /> *[[Broadband Platform]]<br /> **[https://scec.usc.edu/it/Broadband_Platform Broadband Internal Wiki]<br /> **[https://scec.usc.edu/it/Broadband_Study_13.5 Broadband Study 13.5 Internal Wiki Page]<br /> **[https://scec.usc.edu/it/Broadband_Study_13.6 Broadband Study 13.6 Internal Wiki Page]<br /> *[[ALCF Early Science Program Investigators Meeting]]<br /> *[https://www.xsede.org/web/xsede13 XSEDE13 Meeting Web Site - San Diego, California]<br /> *[http://sc13.supercomputing.org SC13 Meeting Web Site - Denver, Colorado]<br /> *[[CyberShake Study 13.4]]<br /> <br /> **[[CyberShake Data Request]]<br /> **[[Project Discussion Calls]]<br /> **[[CyberShake PBR Study]]<br /> **[[CyberShake Data]]<br /> *[[Software Metrics]]<br /> *[[CME Project]]<br /> **[[CME Meeting 2013]]<br /> **[[CME Meeting 2012]]<br /> **[[CME Meeting 2011]]<br /> **[[CME Meeting 2010]]<br /> *[[Dublin Core Metadata]]<br /> *[[UCVM]]<br /> **[[CVM-H]]<br /> **[[CVM-S]]<br /> **[[CVM-SI]]<br /> **[[CVM Evaluation]]<br /> **[https://scec.usc.edu/it/UCVM_13_Proposal Next Gen UCVM Design Notes]<br /> **[[UCVM User Guide]]<br /> **[[GTL]]<br /> *[http://scec.usc.edu/scecpedia/CVM_Geoinformatics_Slices CVMS4 versus CVMSI22 plots]<br /> *[[UCERF3 Images]]<br /> *[https://scec.usc.edu/it/CyberShake CyberShake Wiki - Internal]<br /> **[http://scec.usc.edu/scecpedia/CyberShake_Study_2.2 CyberShake_Study_2.2 - Completed 6 March 2013]<br /> **[http://scec.usc.edu/scecpedia/CyberShake_Study_2.3 CyberShake Study 2.3 - In Progress]<br /> **[https://scec.usc.edu/it/CyberShake_Wiki CyberShake Modules - Internal]<br /> **[https://scec.usc.edu/it/Post-processing_options CyberShake Post Processing - Internal]<br /> **[[CTC Results]]<br /> *[http://scec.usc.edu/scecpedia/Main_Page SCECpedia Public Wiki]<br /> **[https://scec.usc.edu/it/Main_Page SCEC Internal Wiki]<br /> *[[Broadband Platform]]<br /> **[[Broadband Release Info]]<br /> **[https://scec.usc.edu/it/Broadband_Platform Broadband Internal Wiki]<br /> **[[Broadband User Guide v13.9.0]]<br /> **[[Production Run Readiness Review]]<br /> **[[Broadband Platform on HPCC]]<br /> **[[Broadband Sprints]]<br /> **[[Fling Study]]<br /> **[[Broadband Platform on HPCC]]<br /> **[[Broadband Validation Events]]<br /> **[[Broadband Platform Meeting - 7 March 2012]]<br /> **[[Broadband User Guide Current]]<br /> **[[PEER Data Format]]<br /> **[[Broadband Platform Working Group]]<br /> *[[Blue Waters]]<br /> *[[CyberShake]]<br /> **[[CyberShake Study 2.2]]<br /> **[[CyberShake Meeting - 4 April 2012]]<br /> **[[CyberShake Science Plan]]<br /> **[[CyberShake Software Plan]]<br /> <br /> <br /> [[File:pathways.png|256px|thumb|right|Fig 1: SCEC/CME computational pathways provide a scientific framework for improving seismic ground motion forecasts. The SCEC/CME Project began as an NSF information technology research (ITR) project in 2001. (Image Credit: Thomas H. Jordan) ]]<br /> <br /> == Recent Earthquake Information ==<br /> An important goal of SCEC earthquake research is to reduce the hazard from future earthquakes by developing physics-based predictive models of earthquake processes. <br /> *[http://earthquake.usgs.gov/earthquakes/map/ USGS Recent California Earthquakes]<br /> *[http://earthquake.usgs.gov/earthquakes/recenteqsww/ USGS Recent Worldwide Earthquakes]<br /> <br /> == SCEC and CME-related Web Sites ==<br /> [[Image:A04_p10_lrg.jpg|256px|thumb|right|Fig 2: Petascale wave propagation simulation was run in April 2013 on NCCS Titan.]]<br /> <br /> [[Image:kraken.jpg|256px|thumb|right|Fig 3: M8 Dynamic Rupture simulation was run in March 2010 on NICS Kraken.]]<br /> <br /> [[Image:jaguar.jpg|256px|thumb|right|Fig 4: M8 Wave propagation simulation was run in April 2010 on NCCS Jaguar.]]<br /> <br /> [[File:SDSC Viz p2.png|256px|thumb|right|Fig 5: Two minutes after origin time for the SCEC M8 simulation showing velocity magnitude through local elevation. (Image Credit: Amit Chourasia)]]<br /> <br /> [[File:SCECpedia_2013.png|256px|thumb|right|Fig 6: Geographical distribution of SCECpedia visitors between Jan 2013 and Jan 2014 (Image Credit: Google Analytics)]]<br /> <br /> * [http://www.scec.org/cme Public CME Website]<br /> * [http://scec.usc.edu/scecpedia Collaborative SCEC Wiki]<br /> * [http://www.scec.org SCEC Home Page]<br /> * [http://hpgeoc.sdsc.edu/ SDSC High Performance Geocomputing Laboratory]<br /> * [[PetaSHA3 Project]]<br /> * [http://scec.usc.edu/scecpedia/SCEC_Visualization_Projects CME Movies and Animations]<br /> * [http://scec.usc.edu/scecpedia/CVM-Toolkit_(CVM-T) CVM-Toolkit]<br /> * [http://scec.usc.edu/websims/ SCEC Websims Data Management Site]<br /> * [http://www.cseptesting.org/ SCEC CSEP Testing Center]<br /> <br /> == SCEC Computer Science Collaborative Organizations and Resource Providers ==<br /> * [http://www.sdsc.edu/ SDSC]<br /> * [http://hpgeoc.sdsc.edu/ SDSC HPGeoC]<br /> * [http://visservices.sdsc.edu/projects/scec/ SDSC Visualization Services]<br /> * [http://www.isi.edu/~deelman/ Scientific Workflows at USC/ISI]<br /> * [http://inside.mines.edu/~zchen/ Fault Tolerant Computing at CSM]<br /> * [http://www.usc.edu/hpcc/ USC HPCC]<br /> * [http://www.psc.edu/ PSC]<br /> * [http://www.nics.tennessee.edu/ NICS]<br /> * [http://www.nccs.gov/ NCCS]<br /> * [http://www.tacc.utexas.edu/ TACC]<br /> * [http://www.ncsa.illinois.edu/ NCSA]<br /> * [http://www.ncsa.illinois.edu/BlueWaters/ Blue Waters]<br /> * [http://www.opensciencegrid.org/ Open Science Grid]<br /> <br /> == Overviews and Summaries ==<br /> <br /> [[Image:m8-domain.png|256px|thumb|right|Fig 5:SCEC's M8 simulation of a Mag 8.0 rupture on southern San Andreas modeled wave propagation throughout a large region in Southern California as shown. (Image Credit: Geoff Ely) ]]<br /> <br /> *[[CME Project]]<br /> *[[PetaSHA3 Project]]<br /> *[[CME Scientific Software Projects]]<br /> <br /> *[[SCEC People]]<br /> *[[SCEC Special Projects]]<br /> *[[SCEC Organizations]]<br /> <br /> == CME Research Support ==<br /> <br /> [http://www.scec.org Southern California Earthquake Center (SCEC)] and [http://www.scec.org/cme SCEC/CME] research is funded by [http://www.nsf.gov National Science Foundation (NSF)] Cooperative Agreements EAR-0106924 and USGS Cooperative Agreement 02HQAG0008, and NSF awards EAR- 074493, EAR-0949443, OCI-0832698, and OCI-0832698. This research is supported by an allocation of advanced computing resources provided by the National Science Foundation (NSF). Computations are performed on Kraken (a Cray XT5) at the [http://www.nics.tennessee.edu National Institute for Computational Sciences]. Computations and data management are performed at [http://www.sdsc.edu San Diego Supercomputer Center], where the [http://www.diceresearch.org iRODS Data System] is used. The [http://www.tacc.utexas.edu Texas Advanced Computing Center (TACC)] at The University of Texas at Austin, the [http://www.ncsa.illinois.edu National Center for Supercomputer Applications (NCSA)] and the [http://www.psc.edu Pittsburgh Supercomputer Center (PSC)] provide HPC resources. Computations are supported by the [http://www.usc.edu University of Southern California] Center for [http://www.usc.edu/hpcc High-Performance Computing and Communications (HPCC)]. Our research uses HPC resources provided by the [http://www.energy.gov/ U.S. Department of Energy (DOE)] through an [http://www.science.doe.gov/ascr/incite/index.html Innovative and Novel Computational Impact on Theory and Experiment (INCITE)] program allocation award. Computations were performed on [http://www.nccs.gov/computing-resources/jaguar/ Jaguar], which is part of the [http://www.nccs.gov/ National Center for Computational Science (NCCS)] at the Oak Ridge National Laboratory which is supported by under DOE Contract No. DE-AC05-00OR22725. This research uses resources of the [http://www.alcf.anl.gov/ Argonne Leadership Computing Facility] at Argonne National Laboratory, which is supported by the Office of Science of the U.S. Department of Energy under contract DE-AC02- 06CH11357. The [http://www.osc.edu/ Ohio State University] one-sided MPI Communication research was supported through NSF HECURA-1 (CCF- 0833169/139/155). This research received technical and user support through the Advanced Support for [http://www.teragrid.org TeraGrid Applications (ASTA) program].<br /> <br /> == See Also ==<br /> Additional information about SCEC earthquake system science research is available on related SCEC web sites including:<br /> <br /> *[http://www.scec.org/ SCEC Home Page]<br /> *[http://scec.usc.edu/scecpedia/Special:AllPages List of All SCECpedia Pages]<br /> *[[Getting Wiki Help]]<br /> <br /> == License ==<br /> [[image:Cc3_88x31.png]] &lt;br /&gt;<br /> Work on this site is licensed under a [http://creativecommons.org/licenses/by/3.0/deed.en_US Creative Commons Attribution 3.0 Unported License].</div> Patrices https://strike.scec.org/scecwiki/index.php?title=AWP-ODC_GPU&diff=5229 AWP-ODC GPU 2012-05-23T17:58:30Z <p>Patrices: </p> <hr /> <div>== Overview ==<br /> <br /> Jun has a CUDA-MPI code more or less ready to explore the full capability. The current code is based on AWP-ODC Fortran version, but restructured to C and CUDA over the last a year or so. The code uses Cerjan et al. boundary method, capable to read partitioned mesh, but no direct MPI-IO for mesh partitioning so far. You have expertise in mesh generation, and are ideal to help us develop the mesh partitioning feature. Technically the IO is the same as we used for Fortran code, but will need to port current Fortran version structure.f to C, the IO in the GPU code is done on CPU side, that means no direct GPU porting is needed for this project.<br /> <br /> <br /> == Software ==<br /> <br /> I put the latest AWP-ODC on kraken:<br /> <br /> &lt;pre&gt;<br /> /lustre/scratch/junz/For_Patrick/AWP-ODC-v2.0<br /> &lt;/pre&gt;<br /> <br /> # Document is located at /lustre/scratch/junz/For_Patrick/AWP-ODC-v2.0/doc/README, you can start to read and got some idea about what the code looks like.<br /> # Source code is located at /lustre/scratch/junz/For_Patrick/AWP-ODC-v2.0/src-v1.1<br /> # The mesh I/O is mainly in structure.f. The subroutine &quot;inimesh&quot;. We have four options to read the mesh. &quot;readoption=2&quot; is the large scale MPI-IO. And I think your work is to help us translate this part to C code.<br /> <br /> <br /> == Current Progress ==<br /> <br /> * Translate existing AWP-ODC Fortran mesh reading routines (structure.f) to C<br /> <br /> <br /> == Notes ==<br /> <br /> * Found bug in original AWP-ODC structure.f, aproximately line 659. The mu/d1 value for one corner was being incorrectly assigned to lam. The corrected version follows:<br /> &lt;pre&gt;<br /> ! 8 Corners<br /> lam(0,0,0)= lam(1,1,1)<br /> mu(0,0,0)= mu(1,1,1)<br /> d1(0,0,0)= d1(1,1,1)<br /> C fixed bug here<br /> lam(nxt+1,0,0)= lam(nxt,1,1)<br /> mu(nxt+1,0,0)= mu(nxt,1,1)<br /> d1(nxt+1,0,0)= d1(nxt,1,1)<br /> C fixed bug here<br /> &lt;/pre&gt;</div> Patrices https://strike.scec.org/scecwiki/index.php?title=AWP-ODC_GPU&diff=5228 AWP-ODC GPU 2012-05-23T17:54:40Z <p>Patrices: </p> <hr /> <div>== Overview ==<br /> <br /> Jun has a CUDA-MPI code more or less ready to explore the full capability. The current code is based on AWP-ODC Fortran version, but restructured to C and CUDA over the last a year or so. The code uses Cerjan et al. boundary method, capable to read partitioned mesh, but no direct MPI-IO for mesh partitioning so far. You have expertise in mesh generation, and are ideal to help us develop the mesh partitioning feature. Technically the IO is the same as we used for Fortran code, but will need to port current Fortran version structure.f to C, the IO in the GPU code is done on CPU side, that means no direct GPU porting is needed for this project.<br /> <br /> == Software ==<br /> <br /> I put the latest AWP-ODC on kraken:<br /> <br /> &lt;pre&gt;<br /> /lustre/scratch/junz/For_Patrick/AWP-ODC-v2.0<br /> &lt;/pre&gt;<br /> <br /> # Document is located at /lustre/scratch/junz/For_Patrick/AWP-ODC-v2.0/doc/README, you can start to read and got some idea about what the code looks like.<br /> # Source code is located at /lustre/scratch/junz/For_Patrick/AWP-ODC-v2.0/src-v1.1<br /> # The mesh I/O is mainly in structure.f. The subroutine &quot;inimesh&quot;. We have four options to read the mesh. &quot;readoption=2&quot; is the large scale MPI-IO. And I think your work is to help us translate this part to C code.<br /> <br /> <br /> == Current Progress ==<br /> <br /> * Translate existing AWP-ODC Fortran mesh reading routines (structure.f) to C</div> Patrices https://strike.scec.org/scecwiki/index.php?title=AWP-ODC_GPU&diff=5227 AWP-ODC GPU 2012-05-23T17:54:15Z <p>Patrices: Created page with '= Overview = Jun has a CUDA-MPI code more or less ready to explore the full capability. The current code is based on AWP-ODC Fortran version, but restructured to C and CUDA over…'</p> <hr /> <div>= Overview =<br /> <br /> Jun has a CUDA-MPI code more or less ready to explore the full capability. The current code is based on AWP-ODC Fortran version, but restructured to C and CUDA over the last a year or so. The code uses Cerjan et al. boundary method, capable to read partitioned mesh, but no direct MPI-IO for mesh partitioning so far. You have expertise in mesh generation, and are ideal to help us develop the mesh partitioning feature. Technically the IO is the same as we used for Fortran code, but will need to port current Fortran version structure.f to C, the IO in the GPU code is done on CPU side, that means no direct GPU porting is needed for this project.<br /> <br /> = Software =<br /> <br /> I put the latest AWP-ODC on kraken:<br /> <br /> &lt;pre&gt;<br /> /lustre/scratch/junz/For_Patrick/AWP-ODC-v2.0<br /> &lt;/pre&gt;<br /> <br /> # Document is located at /lustre/scratch/junz/For_Patrick/AWP-ODC-v2.0/doc/README, you can start to read and got some idea about what the code looks like.<br /> # Source code is located at /lustre/scratch/junz/For_Patrick/AWP-ODC-v2.0/src-v1.1<br /> # The mesh I/O is mainly in structure.f. The subroutine &quot;inimesh&quot;. We have four options to read the mesh. &quot;readoption=2&quot; is the large scale MPI-IO. And I think your work is to help us translate this part to C code.<br /> <br /> <br /> = Current Progress =<br /> <br /> * Translate existing AWP-ODC Fortran mesh reading routines (structure.f) to C</div> Patrices https://strike.scec.org/scecwiki/index.php?title=Fling_Study&diff=5091 Fling Study 2012-05-11T00:18:31Z <p>Patrices: </p> <hr /> <div>== Overview ==<br /> <br /> The Fling study is a set of broadband platform simulations defined by PG&amp;E and PEER researchers and run by SCEC Broadband platform group. Full specification of the Fling study will be posted when available.<br /> <br /> == Certification of USC HPCC Cluster for Broadband Calculations ==<br /> <br /> The verification and validation of the currently released Broadband platform is based on results generated on a SCEC server called broadband.usc.edu. When we move the Broadband platform software, re-build it, and re-run it in a different computing environment, the results the platform produces can be slightly different than results produced on the SCEC server. Differences can come from computing hardware, from operating system characteristics, from compiler version, and other sources.<br /> <br /> Before accepting results generated in a new computing environment, we must first certify that the new computing environment produces results that are equivalent to the results from the original server where the platform was originally developed and tested.<br /> <br /> To speed up execution of the Fling study, we plan to run it on the USC HPCC cluster, so we must certify that USC HPCC cluster results are valid and comparable to those generated on broadband.usc.edu.<br /> <br /> Here are results from our initial certification tests. A researcher ran a small subset of the Fling study on the SCEC broadband server. Then, we ran the same subset on the USC HPCC cluster. Below we compare the output seismograms from both runs, showing that the two results are very similar.<br /> <br /> In our discussions, we decided that the certification criteria for this study will include a number of small magnitude ruptures, and a number of large magnitude ruptures, which we will post when they are available.<br /> <br /> == Fling Study Scenario List ==<br /> <br /> &lt;pre&gt;<br /> scenario_id magnitude dip rake Ztor fault_length fault_width Priority<br /> <br /> 101 6 90 180 0 14 8 1<br /> 102 6.5 90 180 0 24 13 <br /> 103 7 90 180 0 68 15 <br /> 104 7.5 90 180 0 210 15 <br /> 105 7.8 90 180 0 420 15 <br /> 106 8.2 90 180 0 470 15 <br /> <br /> 107 6 70 180 0 14 8 2<br /> 108 6.5 70 180 0 24 13 <br /> 109 7 70 180 0 68 15 <br /> 110 7.5 70 180 0 210 15 <br /> 111 7.8 70 180 0 420 15 <br /> 112 8.2 70 180 0 470 15 <br /> <br /> 113 6 70 180 0 14 8 3<br /> 114 6.5 70 180 0 24 13 <br /> 115 7 70 180 0 40 25 <br /> 116 7.5 70 180 0 100 32 <br /> 117 7.8 70 180 0 160 40 <br /> 118 8.2 70 180 0 400 40 <br /> <br /> 119 6 90 180 0 14 8 4<br /> 120 6.5 90 180 0 24 13 <br /> 121 7 90 180 0 40 25 <br /> 122 7.5 90 180 0 100 32 <br /> 123 7.8 90 180 0 160 40 <br /> 124 8.2 90 180 0 400 40 <br /> <br /> 125 6 45 90 0 10 10 5<br /> 126 6 45 90 5 10 10 <br /> 127 6.5 45 90 0 18 18 <br /> 128 6.5 45 90 5 18 18 <br /> 129 7 45 90 0 44 23 <br /> 130 7.5 45 90 0 126 25 <br /> 131 7.8 45 90 0 180 25 <br /> <br /> 132 6 60 90 0 10 10 <br /> 133 6 60 90 5 10 10 <br /> 134 6.5 60 90 0 18 18 <br /> 135 6.5 60 90 5 18 18 <br /> 136 7 60 90 0 50 20 <br /> 137 7.5 60 90 0 150 20 <br /> 138 7.8 60 90 0 200 20<br /> <br /> 139 7.0 45 90 0 18 18<br /> 140 6.5 45 90 0 18 18<br /> 141 6.5 45 90 5 18 18<br /> 142 7.0 45 90 0 44 23<br /> <br /> <br /> &lt;/pre&gt;<br /> <br /> == Notes ==<br /> Engineers have put together a subset of fling simulations to submit to the BB Platform. The list above contains all of the scenarios that we will eventually be providing. <br /> <br /> Scenarios 140, 141 and 142 were identified as high priority simulations at our NGA-West2 meeting last Friday. If possible, we would like to get them running right away.<br /> <br /> Scenarios 140 – 142 can be found in my directory, with a separate folder for each of the Scenarios.<br /> <br /> == Running on USC HPCC ==<br /> <br /> A sample set of simulations from the Fling study were run on USC HPCC. The original fling generation scripts, source descriptions, station lists, and batch scripts were copied over from broadband.usc.edu to /home/rcf-104. Then small modifications were made to update paths and block the actual execution of the platform (the platform will be run in a PBS job):<br /> <br /> Sample scripts can be found at the following locations:<br /> <br /> {| class=&quot;wikitable&quot; | border=&quot;1&quot;<br /> |-<br /> ! Script<br /> ! Location<br /> ! Description<br /> ! Modified<br /> |-<br /> | build_xml.py<br /> | /auto/rcf-104/patrices/bbp/batch_tools<br /> | Builds XML workflows for a simulation<br /> | No<br /> |-<br /> | batch_run_bbp.py<br /> | /auto/rcf-104/patrices/bbp/batch_tools<br /> | Executes BBP workflow<br /> | Modified to only write BBP command-lines for simulations to a log for later execution by run_parallel.py. BBP invocations are saved in batch_run_bbp_sims.log and bbp output directory moves are saved in batch_run_bbp_moves.log<br /> |-<br /> | run_parallel.py<br /> | /auto/rcf-104/patrices/bbp/batch_tools<br /> | Helper script to run N programs on a set of M cores<br /> | New script<br /> |- <br /> | gen_source_input.csh<br /> | /auto/rcf-104/patrices/bbp/fling<br /> | Generate full study inputs<br /> | No<br /> |-<br /> | run_bbp-parallel.csh<br /> | /auto/rcf-104/patrices/bbp/fling<br /> | Originally intended to execute the study with the platform. After modifications, only generates XML and execution lists for run_parallel.py.<br /> | Some paths changed, also added ${ROOT_PATH} to some relative path locations to make them absolute paths<br /> |}<br /> <br /> <br /> General steps for running the Fling study:<br /> <br /> * Generate inputs<br /> &lt;pre&gt;<br /> $ ./gen_source_input.csh<br /> &lt;/pre&gt;<br /> * Generate XML workflows<br /> &lt;pre&gt;<br /> $ ./run_bbp-parallel.csh<br /> &lt;/pre&gt;<br /> * Create PBS job submission script (example below)<br /> * Submit PBS job to USC HPCC<br /> <br /> <br /> Example PBS script running the sample Fling simulations on 16 cores:<br /> <br /> &lt;pre&gt;<br /> #!/bin/bash<br /> <br /> #PBS -q nbns<br /> #PBS -l arch=x86_64,pmem=2000mb,pvmem=3000mb,walltime=6:00:00,nodes=4:ppn=4<br /> #PBS -V<br /> #PBS -e /home/rcf-104/patrices/bbp/fling/Xml1/Set1/run_set1.err<br /> #PBS -o /home/rcf-104/patrices/bbp/fling/Xml1/Set1/run_set1.out<br /> <br /> PYTHONPATH=/home/rcf-104/patrices/bbp/11.2.2/bbp_2g/comps<br /> <br /> HOME=/home/rcf-104/patrices/bbp/fling<br /> <br /> echo &quot;Jobs start&quot;<br /> date<br /> <br /> cd $HOME<br /> <br /> python $HOME/Xml1/Set1/run_parallel.py /home/rcf-104/patrices/bbp/11.2.2/setup_bbp_env.sh $HOME<br /> /Xml1/Set1/batch_run_bbp_sims.log $PBS_NODEFILE 1<br /> <br /> python $HOME/Xml1/Set1/run_parallel.py /home/rcf-104/patrices/bbp/11.2.2/setup_bbp_env.sh $HOME<br /> /Xml1/Set1/batch_run_bbp_moves.log $PBS_NODEFILE 1<br /> <br /> echo &quot;Jobs end&quot;<br /> date<br /> &lt;/pre&gt;<br /> <br /> == Comparison of Seismogram from Server and Cluster ==<br /> <br /> {| class=&quot;wikitable&quot; border=&quot;1&quot;<br /> |-<br /> ! Simulation<br /> ! broadband.usc.edu<br /> ! USC HPCC cluster<br /> |-<br /> | 10010116<br /> | [[File: 10010116_ref.p015p000_velocity_seis.png|256px|thumb]]<br /> | [[File: 10010116_hpcc.p015p000_velocity_seis.png|256px|thumb]]<br /> |-<br /> | 10010129<br /> | [[File: 10010129_ref.p035p008_velocity_seis.png|256px|thumb]]<br /> | [[File: 10010129_hpcc.p035p008_velocity_seis.png|256px|thumb]]<br /> |}</div> Patrices https://strike.scec.org/scecwiki/index.php?title=Fling_Study&diff=5087 Fling Study 2012-05-10T23:19:04Z <p>Patrices: </p> <hr /> <div>== Overview ==<br /> <br /> The Fling study is a set of broadband platform simulations defined by PG&amp;E and PEER researchers and run by SCEC Broadband platform group. Full specification of the Fling study will be posted when available.<br /> <br /> == Certification of USC HPCC Cluster for Broadband Calculations ==<br /> <br /> The verification and validation of the currently released Broadband platform is based on results generated on a SCEC server called broadband.usc.edu. When we move the Broadband platform software, re-build it, and re-run it in a different computing environment, the results the platform produces can be slightly different than results produced on the SCEC server. Differences can come from computing hardware, from operating system characteristics, from compiler version, and other sources.<br /> <br /> Before accepting results generated in a new computing environment, we must first certify that the new computing environment produces results that are equivalent to the results from the original server where the platform was originally developed and tested.<br /> <br /> To speed up execution of the Fling study, we plan to run it on the USC HPCC cluster, so we must certify that USC HPCC cluster results are valid and comparable to those generated on broadband.usc.edu.<br /> <br /> Here are results from our initial certification tests. A researcher ran a small subset of the Fling study on the SCEC broadband server. Then, we ran the same subset on the USC HPCC cluster. Below we compare the output seismograms from both runs, showing that the two results are very similar.<br /> <br /> In our discussions, we decided that the certification criteria for this study will include a number of small magnitude ruptures, and a number of large magnitude ruptures, which we will post when they are available.<br /> <br /> == Comparison of Seismogram from Server and Cluster ==<br /> <br /> {| class=&quot;wikitable&quot; border=&quot;1&quot;<br /> |-<br /> ! Simulation<br /> ! broadband.usc.edu<br /> ! USC HPCC cluster<br /> |-<br /> | 10010116<br /> | [[File: 10010116_ref.p015p000_velocity_seis.png|256px|thumb]]<br /> | [[File: 10010116_hpcc.p015p000_velocity_seis.png|256px|thumb]]<br /> |-<br /> | 10010129<br /> | [[File: 10010129_ref.p035p008_velocity_seis.png|256px|thumb]]<br /> | [[File: 10010129_hpcc.p035p008_velocity_seis.png|256px|thumb]]<br /> |}<br /> <br /> &lt;pre&gt;<br /> scenario_id magnitude dip rake Ztor fault_length fault_width Priority<br /> <br /> 101 6 90 180 0 14 8 1<br /> 102 6.5 90 180 0 24 13 <br /> 103 7 90 180 0 68 15 <br /> 104 7.5 90 180 0 210 15 <br /> 105 7.8 90 180 0 420 15 <br /> 106 8.2 90 180 0 470 15 <br /> <br /> 107 6 70 180 0 14 8 2<br /> 108 6.5 70 180 0 24 13 <br /> 109 7 70 180 0 68 15 <br /> 110 7.5 70 180 0 210 15 <br /> 111 7.8 70 180 0 420 15 <br /> 112 8.2 70 180 0 470 15 <br /> <br /> 113 6 70 180 0 14 8 3<br /> 114 6.5 70 180 0 24 13 <br /> 115 7 70 180 0 40 25 <br /> 116 7.5 70 180 0 100 32 <br /> 117 7.8 70 180 0 160 40 <br /> 118 8.2 70 180 0 400 40 <br /> <br /> 119 6 90 180 0 14 8 4<br /> 120 6.5 90 180 0 24 13 <br /> 121 7 90 180 0 40 25 <br /> 122 7.5 90 180 0 100 32 <br /> 123 7.8 90 180 0 160 40 <br /> 124 8.2 90 180 0 400 40 <br /> <br /> 125 6 45 90 0 10 10 5<br /> 126 6 45 90 5 10 10 <br /> 127 6.5 45 90 0 18 18 <br /> 128 6.5 45 90 5 18 18 <br /> 129 7 45 90 0 44 23 <br /> 130 7.5 45 90 0 126 25 <br /> 131 7.8 45 90 0 180 25 <br /> <br /> 132 6 60 90 0 10 10 <br /> 133 6 60 90 5 10 10 <br /> 134 6.5 60 90 0 18 18 <br /> 135 6.5 60 90 5 18 18 <br /> 136 7 60 90 0 50 20 <br /> 137 7.5 60 90 0 150 20 <br /> 138 7.8 60 90 0 200 20<br /> <br /> 139 7.0 45 90 0 18 18<br /> 140 6.5 45 90 0 18 18<br /> 141 6.5 45 90 5 18 18<br /> 142 7.0 45 90 0 44 23<br /> <br /> <br /> &lt;/pre&gt;<br /> <br /> == Notes ==<br /> Ronnie and I have put together a subset of fling simulations to submit to the BB Platform. Attached, please find a list containing all of the scenarios that we will eventually be providing. However, Scenarios 140, 141 and 142 were identified as high priority simulations at our NGA-West2 meeting last Friday. If possible, we would like to get them running right away.<br /> <br /> <br /> <br /> Scenarios 140 – 142 can be found in my directory:<br /> <br /> /home/scec-01/Wooddell/broadband/fling<br /> <br /> <br /> <br /> I have created a separate folder for each of the Scenarios.<br /> <br /> <br /> <br /> I would like to submit the remainder of the fling simulations all at once, but I have not yet had the opportunity to finalize them all. I will send you a message when they are completed, probably sometime tomorrow or Thursday.<br /> <br /> == Running on USC HPCC ==<br /> <br /> A sample set of simulations from the Fling study were run on USC HPCC. The original fling generation scripts, source descriptions, station lists, and batch scripts were copied over from broadband.usc.edu to /home/rcf-104. Then small modifications were made to update paths and block the actual execution of the platform (the platform will be run in a PBS job):<br /> <br /> Sample scripts can be found at the following locations:<br /> <br /> {| class=&quot;wikitable&quot; | border=&quot;1&quot;<br /> |-<br /> ! Script<br /> ! Location<br /> ! Description<br /> ! Modified<br /> |-<br /> | build_xml.py<br /> | /auto/rcf-104/patrices/bbp/batch_tools<br /> | Builds XML workflows for a simulation<br /> | No<br /> |-<br /> | batch_run_bbp.py<br /> | /auto/rcf-104/patrices/bbp/batch_tools<br /> | Executes BBP workflow<br /> | Modified to only write BBP command-lines for simulations to a log for later execution by run_parallel.py. BBP invocations are saved in batch_run_bbp_sims.log and bbp output directory moves are saved in batch_run_bbp_moves.log<br /> |-<br /> | run_parallel.py<br /> | /auto/rcf-104/patrices/bbp/batch_tools<br /> | Helper script to run N programs on a set of M cores<br /> | New script<br /> |- <br /> | gen_source_input.csh<br /> | /auto/rcf-104/patrices/bbp/fling<br /> | Generate full study inputs<br /> | No<br /> |-<br /> | run_bbp-parallel.csh<br /> | /auto/rcf-104/patrices/bbp/fling<br /> | Originally intended to execute the study with the platform. After modifications, only generates XML and execution lists for run_parallel.py.<br /> | Some paths changed, also added ${ROOT_PATH} to some relative path locations to make them absolute paths<br /> |}<br /> <br /> <br /> General steps for running the Fling study:<br /> <br /> * Generate inputs<br /> &lt;pre&gt;<br /> $ gen_source_input.csh<br /> &lt;/pre&gt;<br /> * Generate XML workflows<br /> &lt;pre&gt;<br /> $ run_bbp-parallel.csh<br /> &lt;/pre&gt;<br /> * Create PBS job submission script (example below)<br /> * Submit PBS job to USC HPCC<br /> <br /> <br /> Example PBS script running the sample Fling simulations on 16 cores:<br /> <br /> &lt;pre&gt;<br /> #!/bin/bash<br /> <br /> #PBS -q nbns<br /> #PBS -l arch=x86_64,pmem=2000mb,pvmem=3000mb,walltime=6:00:00,nodes=4:ppn=4<br /> #PBS -V<br /> #PBS -e /home/rcf-104/patrices/bbp/fling/Xml1/Set1/run_set1.err<br /> #PBS -o /home/rcf-104/patrices/bbp/fling/Xml1/Set1/run_set1.out<br /> <br /> PYTHONPATH=/home/rcf-104/patrices/bbp/11.2.2/bbp_2g/comps<br /> <br /> HOME=/home/rcf-104/patrices/bbp/fling<br /> <br /> echo &quot;Jobs start&quot;<br /> date<br /> <br /> cd $HOME<br /> <br /> python $HOME/Xml1/Set1/run_parallel.py /home/rcf-104/patrices/bbp/11.2.2/setup_bbp_env.sh $HOME<br /> /Xml1/Set1/batch_run_bbp_sims.log $PBS_NODEFILE 1<br /> <br /> python $HOME/Xml1/Set1/run_parallel.py /home/rcf-104/patrices/bbp/11.2.2/setup_bbp_env.sh $HOME<br /> /Xml1/Set1/batch_run_bbp_moves.log $PBS_NODEFILE 1<br /> <br /> echo &quot;Jobs end&quot;<br /> date<br /> &lt;/pre&gt;</div> Patrices https://strike.scec.org/scecwiki/index.php?title=Fling_Study&diff=5086 Fling Study 2012-05-10T23:02:15Z <p>Patrices: </p> <hr /> <div>== Overview ==<br /> <br /> The Fling study is a set of broadband platform simulations defined by PG&amp;E and PEER researchers and run by SCEC Broadband platform group. Full specification of the Fling study will be posted when available.<br /> <br /> == Certification of USC HPCC Cluster for Broadband Calculations ==<br /> <br /> The verification and validation of the currently released Broadband platform is based on results generated on a SCEC server called broadband.usc.edu. When we move the Broadband platform software, re-build it, and re-run it in a different computing environment, the results the platform produces can be slightly different than results produced on the SCEC server. Differences can come from computing hardware, from operating system characteristics, from compiler version, and other sources.<br /> <br /> Before accepting results generated in a new computing environment, we must first certify that the new computing environment produces results that are equivalent to the results from the original server where the platform was originally developed and tested.<br /> <br /> To speed up execution of the Fling study, we plan to run it on the USC HPCC cluster, so we must certify that USC HPCC cluster results are valid and comparable to those generated on broadband.usc.edu.<br /> <br /> Here are results from our initial certification tests. A researcher ran a small subset of the Fling study on the SCEC broadband server. Then, we ran the same subset on the USC HPCC cluster. Below we compare the output seismograms from both runs, showing that the two results are very similar.<br /> <br /> In our discussions, we decided that the certification criteria for this study will include a number of small magnitude ruptures, and a number of large magnitude ruptures, which we will post when they are available.<br /> <br /> == Comparison of Seismogram from Server and Cluster ==<br /> <br /> {| class=&quot;wikitable&quot; border=&quot;1&quot;<br /> |-<br /> ! Simulation<br /> ! broadband.usc.edu<br /> ! USC HPCC cluster<br /> |-<br /> | 10010116<br /> | [[File: 10010116_ref.p015p000_velocity_seis.png|256px|thumb]]<br /> | [[File: 10010116_hpcc.p015p000_velocity_seis.png|256px|thumb]]<br /> |-<br /> | 10010129<br /> | [[File: 10010129_ref.p035p008_velocity_seis.png|256px|thumb]]<br /> | [[File: 10010129_hpcc.p035p008_velocity_seis.png|256px|thumb]]<br /> |}<br /> <br /> &lt;pre&gt;<br /> scenario_id magnitude dip rake Ztor fault_length fault_width Priority<br /> <br /> 101 6 90 180 0 14 8 1<br /> 102 6.5 90 180 0 24 13 <br /> 103 7 90 180 0 68 15 <br /> 104 7.5 90 180 0 210 15 <br /> 105 7.8 90 180 0 420 15 <br /> 106 8.2 90 180 0 470 15 <br /> <br /> 107 6 70 180 0 14 8 2<br /> 108 6.5 70 180 0 24 13 <br /> 109 7 70 180 0 68 15 <br /> 110 7.5 70 180 0 210 15 <br /> 111 7.8 70 180 0 420 15 <br /> 112 8.2 70 180 0 470 15 <br /> <br /> 113 6 70 180 0 14 8 3<br /> 114 6.5 70 180 0 24 13 <br /> 115 7 70 180 0 40 25 <br /> 116 7.5 70 180 0 100 32 <br /> 117 7.8 70 180 0 160 40 <br /> 118 8.2 70 180 0 400 40 <br /> <br /> 119 6 90 180 0 14 8 4<br /> 120 6.5 90 180 0 24 13 <br /> 121 7 90 180 0 40 25 <br /> 122 7.5 90 180 0 100 32 <br /> 123 7.8 90 180 0 160 40 <br /> 124 8.2 90 180 0 400 40 <br /> <br /> 125 6 45 90 0 10 10 5<br /> 126 6 45 90 5 10 10 <br /> 127 6.5 45 90 0 18 18 <br /> 128 6.5 45 90 5 18 18 <br /> 129 7 45 90 0 44 23 <br /> 130 7.5 45 90 0 126 25 <br /> 131 7.8 45 90 0 180 25 <br /> <br /> 132 6 60 90 0 10 10 <br /> 133 6 60 90 5 10 10 <br /> 134 6.5 60 90 0 18 18 <br /> 135 6.5 60 90 5 18 18 <br /> 136 7 60 90 0 50 20 <br /> 137 7.5 60 90 0 150 20 <br /> 138 7.8 60 90 0 200 20<br /> <br /> 139 7.0 45 90 0 18 18<br /> 140 6.5 45 90 0 18 18<br /> 141 6.5 45 90 5 18 18<br /> 142 7.0 45 90 0 44 23<br /> <br /> <br /> &lt;/pre&gt;<br /> <br /> == Notes ==<br /> Ronnie and I have put together a subset of fling simulations to submit to the BB Platform. Attached, please find a list containing all of the scenarios that we will eventually be providing. However, Scenarios 140, 141 and 142 were identified as high priority simulations at our NGA-West2 meeting last Friday. If possible, we would like to get them running right away.<br /> <br /> <br /> <br /> Scenarios 140 – 142 can be found in my directory:<br /> <br /> /home/scec-01/Wooddell/broadband/fling<br /> <br /> <br /> <br /> I have created a separate folder for each of the Scenarios.<br /> <br /> <br /> <br /> I would like to submit the remainder of the fling simulations all at once, but I have not yet had the opportunity to finalize them all. I will send you a message when they are completed, probably sometime tomorrow or Thursday.<br /> <br /> == Running on USC HPCC ==<br /> <br /> A sample set of simulations from the Fling study were run on USC HPCC. The original fling generation scripts, source descriptions, station lists, and batch scripts were copied over from broadband.usc.edu to /home/rcf-104. Then small modifications were made to update paths and block the actual execution of the platform (the platform will be run in a PBS job):<br /> <br /> Sample scripts can be found at the following locations:<br /> <br /> {| class=&quot;wikitable&quot; | border=&quot;1&quot;<br /> |-<br /> ! Script<br /> ! Location<br /> ! Description<br /> ! Modified<br /> |-<br /> | build_xml.py<br /> | /auto/rcf-104/patrices/bbp/batch_tools<br /> | Builds XML workflows for a simulation<br /> | No<br /> |-<br /> | batch_run_bbp.py<br /> | /auto/rcf-104/patrices/bbp/batch_tools<br /> | Executes BBP workflow<br /> | Modified to only write BBP command-lines for simulations to a log for later execution by run_parallel.py. BBP invocations are saved in batch_run_bbp_sims.log and bbp output directory moves are saved in batch_run_bbp_moves.log<br /> |-<br /> | run_parallel.py<br /> | /auto/rcf-104/patrices/bbp/batch_tools<br /> | Helper script to run N programs on a set of M cores<br /> | New script<br /> |- <br /> | gen_source_input.csh<br /> | /auto/rcf-104/patrices/bbp/fling<br /> | Generate full study inputs<br /> | No<br /> |-<br /> | run_bbp-parallel.csh<br /> | /auto/rcf-104/patrices/bbp/fling<br /> | Execute the study with the platform<br /> | Some paths changed, also added ${ROOT_PATH} to some relative path locations to make them absolute paths<br /> |}<br /> <br /> <br /> General steps for running the Fling study:<br /> <br /> * Generate inputs<br /> &lt;pre&gt;<br /> $ gen_source_input.csh<br /> &lt;/pre&gt;<br /> * Generate XML workflows<br /> &lt;pre&gt;<br /> $ run_bbp-parallel.csh<br /> &lt;/pre&gt;<br /> * Create PBS job submission script (example below)<br /> * Submit PBS job to USC HPCC<br /> <br /> <br /> Example PBS script running the sample Fling simulations on 16 cores:<br /> <br /> &lt;pre&gt;<br /> #!/bin/bash<br /> <br /> #PBS -q nbns<br /> #PBS -l arch=x86_64,pmem=2000mb,pvmem=3000mb,walltime=6:00:00,nodes=4:ppn=4<br /> #PBS -V<br /> #PBS -e /home/rcf-104/patrices/bbp/fling/Xml1/Set1/run_set1.err<br /> #PBS -o /home/rcf-104/patrices/bbp/fling/Xml1/Set1/run_set1.out<br /> <br /> PYTHONPATH=/home/rcf-104/patrices/bbp/11.2.2/bbp_2g/comps<br /> <br /> HOME=/home/rcf-104/patrices/bbp/fling<br /> <br /> echo &quot;Jobs start&quot;<br /> date<br /> <br /> cd $HOME<br /> <br /> python $HOME/Xml1/Set1/run_parallel.py /home/rcf-104/patrices/bbp/11.2.2/setup_bbp_env.sh $HOME<br /> /Xml1/Set1/batch_run_bbp_sims.log $PBS_NODEFILE 1<br /> <br /> python $HOME/Xml1/Set1/run_parallel.py /home/rcf-104/patrices/bbp/11.2.2/setup_bbp_env.sh $HOME<br /> /Xml1/Set1/batch_run_bbp_moves.log $PBS_NODEFILE 1<br /> <br /> echo &quot;Jobs end&quot;<br /> date<br /> &lt;/pre&gt;</div> Patrices https://strike.scec.org/scecwiki/index.php?title=Fling_Study&diff=5085 Fling Study 2012-05-10T23:02:03Z <p>Patrices: </p> <hr /> <div>== Overview ==<br /> <br /> The Fling study is a set of broadband platform simulations defined by PG&amp;E and PEER researchers and run by SCEC Broadband platform group. Full specification of the Fling study will be posted when available.<br /> <br /> == Certification of USC HPCC Cluster for Broadband Calculations ==<br /> <br /> The verification and validation of the currently released Broadband platform is based on results generated on a SCEC server called broadband.usc.edu. When we move the Broadband platform software, re-build it, and re-run it in a different computing environment, the results the platform produces can be slightly different than results produced on the SCEC server. Differences can come from computing hardware, from operating system characteristics, from compiler version, and other sources.<br /> <br /> Before accepting results generated in a new computing environment, we must first certify that the new computing environment produces results that are equivalent to the results from the original server where the platform was originally developed and tested.<br /> <br /> To speed up execution of the Fling study, we plan to run it on the USC HPCC cluster, so we must certify that USC HPCC cluster results are valid and comparable to those generated on broadband.usc.edu.<br /> <br /> Here are results from our initial certification tests. A researcher ran a small subset of the Fling study on the SCEC broadband server. Then, we ran the same subset on the USC HPCC cluster. Below we compare the output seismograms from both runs, showing that the two results are very similar.<br /> <br /> In our discussions, we decided that the certification criteria for this study will include a number of small magnitude ruptures, and a number of large magnitude ruptures, which we will post when they are available.<br /> <br /> == Comparison of Seismogram from Server and Cluster ==<br /> <br /> {| class=&quot;wikitable&quot; border=&quot;1&quot;<br /> |-<br /> ! Simulation<br /> ! broadband.usc.edu<br /> ! USC HPCC cluster<br /> |-<br /> | 10010116<br /> | [[File: 10010116_ref.p015p000_velocity_seis.png|256px|thumb]]<br /> | [[File: 10010116_hpcc.p015p000_velocity_seis.png|256px|thumb]]<br /> |-<br /> | 10010129<br /> | [[File: 10010129_ref.p035p008_velocity_seis.png|256px|thumb]]<br /> | [[File: 10010129_hpcc.p035p008_velocity_seis.png|256px|thumb]]<br /> |}<br /> <br /> &lt;pre&gt;<br /> scenario_id magnitude dip rake Ztor fault_length fault_width Priority<br /> <br /> 101 6 90 180 0 14 8 1<br /> 102 6.5 90 180 0 24 13 <br /> 103 7 90 180 0 68 15 <br /> 104 7.5 90 180 0 210 15 <br /> 105 7.8 90 180 0 420 15 <br /> 106 8.2 90 180 0 470 15 <br /> <br /> 107 6 70 180 0 14 8 2<br /> 108 6.5 70 180 0 24 13 <br /> 109 7 70 180 0 68 15 <br /> 110 7.5 70 180 0 210 15 <br /> 111 7.8 70 180 0 420 15 <br /> 112 8.2 70 180 0 470 15 <br /> <br /> 113 6 70 180 0 14 8 3<br /> 114 6.5 70 180 0 24 13 <br /> 115 7 70 180 0 40 25 <br /> 116 7.5 70 180 0 100 32 <br /> 117 7.8 70 180 0 160 40 <br /> 118 8.2 70 180 0 400 40 <br /> <br /> 119 6 90 180 0 14 8 4<br /> 120 6.5 90 180 0 24 13 <br /> 121 7 90 180 0 40 25 <br /> 122 7.5 90 180 0 100 32 <br /> 123 7.8 90 180 0 160 40 <br /> 124 8.2 90 180 0 400 40 <br /> <br /> 125 6 45 90 0 10 10 5<br /> 126 6 45 90 5 10 10 <br /> 127 6.5 45 90 0 18 18 <br /> 128 6.5 45 90 5 18 18 <br /> 129 7 45 90 0 44 23 <br /> 130 7.5 45 90 0 126 25 <br /> 131 7.8 45 90 0 180 25 <br /> <br /> 132 6 60 90 0 10 10 <br /> 133 6 60 90 5 10 10 <br /> 134 6.5 60 90 0 18 18 <br /> 135 6.5 60 90 5 18 18 <br /> 136 7 60 90 0 50 20 <br /> 137 7.5 60 90 0 150 20 <br /> 138 7.8 60 90 0 200 20<br /> <br /> 139 7.0 45 90 0 18 18<br /> 140 6.5 45 90 0 18 18<br /> 141 6.5 45 90 5 18 18<br /> 142 7.0 45 90 0 44 23<br /> <br /> <br /> &lt;/pre&gt;<br /> <br /> == Notes ==<br /> Ronnie and I have put together a subset of fling simulations to submit to the BB Platform. Attached, please find a list containing all of the scenarios that we will eventually be providing. However, Scenarios 140, 141 and 142 were identified as high priority simulations at our NGA-West2 meeting last Friday. If possible, we would like to get them running right away.<br /> <br /> <br /> <br /> Scenarios 140 – 142 can be found in my directory:<br /> <br /> /home/scec-01/Wooddell/broadband/fling<br /> <br /> <br /> <br /> I have created a separate folder for each of the Scenarios.<br /> <br /> <br /> <br /> I would like to submit the remainder of the fling simulations all at once, but I have not yet had the opportunity to finalize them all. I will send you a message when they are completed, probably sometime tomorrow or Thursday.<br /> <br /> == Running on USC HPCC ==<br /> <br /> A sample set of simulations from the Fling study were run on USC HPCC. The original fling generation scripts, source descriptions, station lists, and batch scripts were copied over from broadband.usc.edu to /home/rcf-104. Then small modifications were made to update paths and block the actual execution of the platform (the platform will be run in a PBS job):<br /> <br /> Sample scripts can be found at the following locations:<br /> <br /> {| class=&quot;wikitable&quot; | border=&quot;1&quot;<br /> |-<br /> ! Script<br /> ! Location<br /> ! Description<br /> ! Modified<br /> |-<br /> | build_xml.py<br /> | /auto/rcf-104/patrices/bbp/batch_tools<br /> | Builds XML workflows for a simulation<br /> | No<br /> |-<br /> | batch_run_bbp.py<br /> | /auto/rcf-104/patrices/bbp/batch_tools<br /> | Executes BBP workflow<br /> | Modified to only write BBP command-lines for simulations to a log for later execution by run_parallel.py. BBP invocations are saved in batch_run_bbp_sims.log and bbp output directory moves are saved in batch_run_bbp_moves.log<br /> |-<br /> | run_parallel.py<br /> | /auto/rcf-104/patrices/bbp/batch_tools<br /> | Helper script to run N programs on a set of M cores<br /> | New script<br /> |- <br /> | gen_source_input.csh<br /> | /auto/rcf-104/patrices/bbp/fling<br /> | Generate full study inputs<br /> | No<br /> |-<br /> | run_bbp-parallel.csh<br /> | /auto/rcf-104/patrices/bbp/fling<br /> | Execute the study with the platform<br /> | Some paths changed, also added ${ROOT_PATH} to some relative path locations to make them absolute paths<br /> |}<br /> <br /> <br /> General steps for running the Fling study:<br /> <br /> * Generate inputs<br /> &lt;pre&gt;<br /> $ gen_source_input.csh<br /> &lt;/pre&gt;<br /> * Generate XML workflows<br /> &lt;pre&gt;<br /> $ run_bbp-parallel.csh<br /> &lt;/pre&gt;<br /> * Create PBS job submission script (example below)<br /> * Submit PBS job to USC HPCC<br /> <br /> Example PBS script running the sample Fling simulations on 16 cores:<br /> <br /> &lt;pre&gt;<br /> #!/bin/bash<br /> <br /> #PBS -q nbns<br /> #PBS -l arch=x86_64,pmem=2000mb,pvmem=3000mb,walltime=6:00:00,nodes=4:ppn=4<br /> #PBS -V<br /> #PBS -e /home/rcf-104/patrices/bbp/fling/Xml1/Set1/run_set1.err<br /> #PBS -o /home/rcf-104/patrices/bbp/fling/Xml1/Set1/run_set1.out<br /> <br /> PYTHONPATH=/home/rcf-104/patrices/bbp/11.2.2/bbp_2g/comps<br /> <br /> HOME=/home/rcf-104/patrices/bbp/fling<br /> <br /> echo &quot;Jobs start&quot;<br /> date<br /> <br /> cd $HOME<br /> <br /> python $HOME/Xml1/Set1/run_parallel.py /home/rcf-104/patrices/bbp/11.2.2/setup_bbp_env.sh $HOME<br /> /Xml1/Set1/batch_run_bbp_sims.log $PBS_NODEFILE 1<br /> <br /> python $HOME/Xml1/Set1/run_parallel.py /home/rcf-104/patrices/bbp/11.2.2/setup_bbp_env.sh $HOME<br /> /Xml1/Set1/batch_run_bbp_moves.log $PBS_NODEFILE 1<br /> <br /> echo &quot;Jobs end&quot;<br /> date<br /> &lt;/pre&gt;</div> Patrices https://strike.scec.org/scecwiki/index.php?title=Fling_Study&diff=5084 Fling Study 2012-05-10T23:01:43Z <p>Patrices: </p> <hr /> <div>== Overview ==<br /> <br /> The Fling study is a set of broadband platform simulations defined by PG&amp;E and PEER researchers and run by SCEC Broadband platform group. Full specification of the Fling study will be posted when available.<br /> <br /> == Certification of USC HPCC Cluster for Broadband Calculations ==<br /> <br /> The verification and validation of the currently released Broadband platform is based on results generated on a SCEC server called broadband.usc.edu. When we move the Broadband platform software, re-build it, and re-run it in a different computing environment, the results the platform produces can be slightly different than results produced on the SCEC server. Differences can come from computing hardware, from operating system characteristics, from compiler version, and other sources.<br /> <br /> Before accepting results generated in a new computing environment, we must first certify that the new computing environment produces results that are equivalent to the results from the original server where the platform was originally developed and tested.<br /> <br /> To speed up execution of the Fling study, we plan to run it on the USC HPCC cluster, so we must certify that USC HPCC cluster results are valid and comparable to those generated on broadband.usc.edu.<br /> <br /> Here are results from our initial certification tests. A researcher ran a small subset of the Fling study on the SCEC broadband server. Then, we ran the same subset on the USC HPCC cluster. Below we compare the output seismograms from both runs, showing that the two results are very similar.<br /> <br /> In our discussions, we decided that the certification criteria for this study will include a number of small magnitude ruptures, and a number of large magnitude ruptures, which we will post when they are available.<br /> <br /> == Comparison of Seismogram from Server and Cluster ==<br /> <br /> {| class=&quot;wikitable&quot; border=&quot;1&quot;<br /> |-<br /> ! Simulation<br /> ! broadband.usc.edu<br /> ! USC HPCC cluster<br /> |-<br /> | 10010116<br /> | [[File: 10010116_ref.p015p000_velocity_seis.png|256px|thumb]]<br /> | [[File: 10010116_hpcc.p015p000_velocity_seis.png|256px|thumb]]<br /> |-<br /> | 10010129<br /> | [[File: 10010129_ref.p035p008_velocity_seis.png|256px|thumb]]<br /> | [[File: 10010129_hpcc.p035p008_velocity_seis.png|256px|thumb]]<br /> |}<br /> <br /> &lt;pre&gt;<br /> scenario_id magnitude dip rake Ztor fault_length fault_width Priority<br /> <br /> 101 6 90 180 0 14 8 1<br /> 102 6.5 90 180 0 24 13 <br /> 103 7 90 180 0 68 15 <br /> 104 7.5 90 180 0 210 15 <br /> 105 7.8 90 180 0 420 15 <br /> 106 8.2 90 180 0 470 15 <br /> <br /> 107 6 70 180 0 14 8 2<br /> 108 6.5 70 180 0 24 13 <br /> 109 7 70 180 0 68 15 <br /> 110 7.5 70 180 0 210 15 <br /> 111 7.8 70 180 0 420 15 <br /> 112 8.2 70 180 0 470 15 <br /> <br /> 113 6 70 180 0 14 8 3<br /> 114 6.5 70 180 0 24 13 <br /> 115 7 70 180 0 40 25 <br /> 116 7.5 70 180 0 100 32 <br /> 117 7.8 70 180 0 160 40 <br /> 118 8.2 70 180 0 400 40 <br /> <br /> 119 6 90 180 0 14 8 4<br /> 120 6.5 90 180 0 24 13 <br /> 121 7 90 180 0 40 25 <br /> 122 7.5 90 180 0 100 32 <br /> 123 7.8 90 180 0 160 40 <br /> 124 8.2 90 180 0 400 40 <br /> <br /> 125 6 45 90 0 10 10 5<br /> 126 6 45 90 5 10 10 <br /> 127 6.5 45 90 0 18 18 <br /> 128 6.5 45 90 5 18 18 <br /> 129 7 45 90 0 44 23 <br /> 130 7.5 45 90 0 126 25 <br /> 131 7.8 45 90 0 180 25 <br /> <br /> 132 6 60 90 0 10 10 <br /> 133 6 60 90 5 10 10 <br /> 134 6.5 60 90 0 18 18 <br /> 135 6.5 60 90 5 18 18 <br /> 136 7 60 90 0 50 20 <br /> 137 7.5 60 90 0 150 20 <br /> 138 7.8 60 90 0 200 20<br /> <br /> 139 7.0 45 90 0 18 18<br /> 140 6.5 45 90 0 18 18<br /> 141 6.5 45 90 5 18 18<br /> 142 7.0 45 90 0 44 23<br /> <br /> <br /> &lt;/pre&gt;<br /> <br /> == Notes ==<br /> Ronnie and I have put together a subset of fling simulations to submit to the BB Platform. Attached, please find a list containing all of the scenarios that we will eventually be providing. However, Scenarios 140, 141 and 142 were identified as high priority simulations at our NGA-West2 meeting last Friday. If possible, we would like to get them running right away.<br /> <br /> <br /> <br /> Scenarios 140 – 142 can be found in my directory:<br /> <br /> /home/scec-01/Wooddell/broadband/fling<br /> <br /> <br /> <br /> I have created a separate folder for each of the Scenarios.<br /> <br /> <br /> <br /> I would like to submit the remainder of the fling simulations all at once, but I have not yet had the opportunity to finalize them all. I will send you a message when they are completed, probably sometime tomorrow or Thursday.<br /> <br /> == Running on USC HPCC ==<br /> <br /> A sample set of simulations from the Fling study were run on USC HPCC. The original fling generation scripts, source descriptions, station lists, and batch scripts were copied over from broadband.usc.edu to /home/rcf-104. Then small modifications were made to update paths and block the actual execution of the platform (the platform will be run in a PBS job):<br /> <br /> Sample scripts can be found at the following locations:<br /> <br /> {| class=&quot;wikitable&quot; | border=&quot;1&quot;<br /> |-<br /> ! Script<br /> ! Location<br /> ! Description<br /> ! Modified<br /> |-<br /> | build_xml.py<br /> | /auto/rcf-104/patrices/bbp/batch_tools<br /> | Builds XML workflows for a simulation<br /> | No<br /> |-<br /> | batch_run_bbp.py<br /> | /auto/rcf-104/patrices/bbp/batch_tools<br /> | Executes BBP workflow<br /> | Modified to only write BBP command-lines for simulations to a log for later execution by run_parallel.py. BBP invocations are saved in batch_run_bbp_sims.log and bbp output directory moves are saved in batch_run_bbp_moves.log<br /> |-<br /> | run_parallel.py<br /> | /auto/rcf-104/patrices/bbp/batch_tools<br /> | Helper script to run N programs on a set of M cores<br /> | New script<br /> |- <br /> | gen_source_input.csh<br /> | /auto/rcf-104/patrices/bbp/fling<br /> | Generate full study inputs<br /> | No<br /> |-<br /> | run_bbp-parallel.csh<br /> | /auto/rcf-104/patrices/bbp/fling<br /> | Execute the study with the platform<br /> | Some paths changed, also added ${ROOT_PATH} to some relative path locations to make them absolute paths<br /> |}<br /> <br /> General steps for running the Fling study:<br /> <br /> # Generate inputs<br /> &lt;pre&gt;<br /> $ gen_source_input.csh<br /> &lt;/pre&gt;<br /> # Generate XML workflows<br /> &lt;pre&gt;<br /> $ run_bbp-parallel.csh<br /> &lt;/pre&gt;<br /> # Create PBS job submission script (example below)<br /> # Submit PBS job to USC HPCC<br /> <br /> Example PBS script running the sample Fling simulations on 16 cores:<br /> <br /> &lt;pre&gt;<br /> #!/bin/bash<br /> <br /> #PBS -q nbns<br /> #PBS -l arch=x86_64,pmem=2000mb,pvmem=3000mb,walltime=6:00:00,nodes=4:ppn=4<br /> #PBS -V<br /> #PBS -e /home/rcf-104/patrices/bbp/fling/Xml1/Set1/run_set1.err<br /> #PBS -o /home/rcf-104/patrices/bbp/fling/Xml1/Set1/run_set1.out<br /> <br /> PYTHONPATH=/home/rcf-104/patrices/bbp/11.2.2/bbp_2g/comps<br /> <br /> HOME=/home/rcf-104/patrices/bbp/fling<br /> <br /> echo &quot;Jobs start&quot;<br /> date<br /> <br /> cd $HOME<br /> <br /> python $HOME/Xml1/Set1/run_parallel.py /home/rcf-104/patrices/bbp/11.2.2/setup_bbp_env.sh $HOME<br /> /Xml1/Set1/batch_run_bbp_sims.log $PBS_NODEFILE 1<br /> <br /> python $HOME/Xml1/Set1/run_parallel.py /home/rcf-104/patrices/bbp/11.2.2/setup_bbp_env.sh $HOME<br /> /Xml1/Set1/batch_run_bbp_moves.log $PBS_NODEFILE 1<br /> <br /> echo &quot;Jobs end&quot;<br /> date<br /> &lt;/pre&gt;</div> Patrices https://strike.scec.org/scecwiki/index.php?title=Fling_Study&diff=5083 Fling Study 2012-05-10T22:58:37Z <p>Patrices: </p> <hr /> <div>== Overview ==<br /> <br /> The Fling study is a set of broadband platform simulations defined by PG&amp;E and PEER researchers and run by SCEC Broadband platform group. Full specification of the Fling study will be posted when available.<br /> <br /> == Certification of USC HPCC Cluster for Broadband Calculations ==<br /> <br /> The verification and validation of the currently released Broadband platform is based on results generated on a SCEC server called broadband.usc.edu. When we move the Broadband platform software, re-build it, and re-run it in a different computing environment, the results the platform produces can be slightly different than results produced on the SCEC server. Differences can come from computing hardware, from operating system characteristics, from compiler version, and other sources.<br /> <br /> Before accepting results generated in a new computing environment, we must first certify that the new computing environment produces results that are equivalent to the results from the original server where the platform was originally developed and tested.<br /> <br /> To speed up execution of the Fling study, we plan to run it on the USC HPCC cluster, so we must certify that USC HPCC cluster results are valid and comparable to those generated on broadband.usc.edu.<br /> <br /> Here are results from our initial certification tests. A researcher ran a small subset of the Fling study on the SCEC broadband server. Then, we ran the same subset on the USC HPCC cluster. Below we compare the output seismograms from both runs, showing that the two results are very similar.<br /> <br /> In our discussions, we decided that the certification criteria for this study will include a number of small magnitude ruptures, and a number of large magnitude ruptures, which we will post when they are available.<br /> <br /> == Comparison of Seismogram from Server and Cluster ==<br /> <br /> {| class=&quot;wikitable&quot; border=&quot;1&quot;<br /> |-<br /> ! Simulation<br /> ! broadband.usc.edu<br /> ! USC HPCC cluster<br /> |-<br /> | 10010116<br /> | [[File: 10010116_ref.p015p000_velocity_seis.png|256px|thumb]]<br /> | [[File: 10010116_hpcc.p015p000_velocity_seis.png|256px|thumb]]<br /> |-<br /> | 10010129<br /> | [[File: 10010129_ref.p035p008_velocity_seis.png|256px|thumb]]<br /> | [[File: 10010129_hpcc.p035p008_velocity_seis.png|256px|thumb]]<br /> |}<br /> <br /> &lt;pre&gt;<br /> scenario_id magnitude dip rake Ztor fault_length fault_width Priority<br /> <br /> 101 6 90 180 0 14 8 1<br /> 102 6.5 90 180 0 24 13 <br /> 103 7 90 180 0 68 15 <br /> 104 7.5 90 180 0 210 15 <br /> 105 7.8 90 180 0 420 15 <br /> 106 8.2 90 180 0 470 15 <br /> <br /> 107 6 70 180 0 14 8 2<br /> 108 6.5 70 180 0 24 13 <br /> 109 7 70 180 0 68 15 <br /> 110 7.5 70 180 0 210 15 <br /> 111 7.8 70 180 0 420 15 <br /> 112 8.2 70 180 0 470 15 <br /> <br /> 113 6 70 180 0 14 8 3<br /> 114 6.5 70 180 0 24 13 <br /> 115 7 70 180 0 40 25 <br /> 116 7.5 70 180 0 100 32 <br /> 117 7.8 70 180 0 160 40 <br /> 118 8.2 70 180 0 400 40 <br /> <br /> 119 6 90 180 0 14 8 4<br /> 120 6.5 90 180 0 24 13 <br /> 121 7 90 180 0 40 25 <br /> 122 7.5 90 180 0 100 32 <br /> 123 7.8 90 180 0 160 40 <br /> 124 8.2 90 180 0 400 40 <br /> <br /> 125 6 45 90 0 10 10 5<br /> 126 6 45 90 5 10 10 <br /> 127 6.5 45 90 0 18 18 <br /> 128 6.5 45 90 5 18 18 <br /> 129 7 45 90 0 44 23 <br /> 130 7.5 45 90 0 126 25 <br /> 131 7.8 45 90 0 180 25 <br /> <br /> 132 6 60 90 0 10 10 <br /> 133 6 60 90 5 10 10 <br /> 134 6.5 60 90 0 18 18 <br /> 135 6.5 60 90 5 18 18 <br /> 136 7 60 90 0 50 20 <br /> 137 7.5 60 90 0 150 20 <br /> 138 7.8 60 90 0 200 20<br /> <br /> 139 7.0 45 90 0 18 18<br /> 140 6.5 45 90 0 18 18<br /> 141 6.5 45 90 5 18 18<br /> 142 7.0 45 90 0 44 23<br /> <br /> <br /> &lt;/pre&gt;<br /> <br /> == Notes ==<br /> Ronnie and I have put together a subset of fling simulations to submit to the BB Platform. Attached, please find a list containing all of the scenarios that we will eventually be providing. However, Scenarios 140, 141 and 142 were identified as high priority simulations at our NGA-West2 meeting last Friday. If possible, we would like to get them running right away.<br /> <br /> <br /> <br /> Scenarios 140 – 142 can be found in my directory:<br /> <br /> /home/scec-01/Wooddell/broadband/fling<br /> <br /> <br /> <br /> I have created a separate folder for each of the Scenarios.<br /> <br /> <br /> <br /> I would like to submit the remainder of the fling simulations all at once, but I have not yet had the opportunity to finalize them all. I will send you a message when they are completed, probably sometime tomorrow or Thursday.<br /> <br /> == Running on USC HPCC ==<br /> <br /> A sample set of simulations from the Fling study were run on USC HPCC. The original fling generation scripts, source descriptions, station lists, and batch scripts were copied over from broadband.usc.edu to /home/rcf-104. Then small modifications were made to update paths and block the actual execution of the platform (the platform will be run in a PBS job):<br /> <br /> Sample scripts can be found at the following locations:<br /> <br /> {| class=&quot;wikitable&quot; | border=&quot;1&quot;<br /> |-<br /> ! Script<br /> ! Location<br /> ! Description<br /> ! Modified<br /> |-<br /> | build_xml.py<br /> | /auto/rcf-104/patrices/bbp/batch_tools<br /> | Builds XML workflows for a simulation<br /> | No<br /> |-<br /> | batch_run_bbp.py<br /> | /auto/rcf-104/patrices/bbp/batch_tools<br /> | Executes BBP workflow<br /> | Modified to only write BBP command-lines for simulations to a log for later execution by run_parallel.py. BBP invocations are saved in batch_run_bbp_sims.log and bbp output directory moves are saved in batch_run_bbp_moves.log<br /> |-<br /> | run_parallel.py<br /> | /auto/rcf-104/patrices/bbp/batch_tools<br /> | Helper script to run N programs on a set of M cores<br /> | New script<br /> |- <br /> | gen_source_input.csh<br /> | /auto/rcf-104/patrices/bbp/fling<br /> | Generate full study inputs<br /> | No<br /> |-<br /> | run_bbp-parallel.csh<br /> | /auto/rcf-104/patrices/bbp/fling<br /> | Execute the study with the platform<br /> | Some paths changed, also added ${ROOT_PATH} to some relative path locations to make them absolute paths<br /> |}<br /> <br /> <br /> Example PBS script running the sample Fling simulations on 16 cores:<br /> <br /> &lt;pre&gt;<br /> #!/bin/bash<br /> <br /> #PBS -q nbns<br /> #PBS -l arch=x86_64,pmem=2000mb,pvmem=3000mb,walltime=6:00:00,nodes=4:ppn=4<br /> #PBS -V<br /> #PBS -e /home/rcf-104/patrices/bbp/fling/Xml1/Set1/run_set1.err<br /> #PBS -o /home/rcf-104/patrices/bbp/fling/Xml1/Set1/run_set1.out<br /> <br /> PYTHONPATH=/home/rcf-104/patrices/bbp/11.2.2/bbp_2g/comps<br /> <br /> HOME=/home/rcf-104/patrices/bbp/fling<br /> <br /> echo &quot;Jobs start&quot;<br /> date<br /> <br /> cd $HOME<br /> <br /> python $HOME/Xml1/Set1/run_parallel.py /home/rcf-104/patrices/bbp/11.2.2/setup_bbp_env.sh $HOME<br /> /Xml1/Set1/batch_run_bbp_sims.log $PBS_NODEFILE 1<br /> <br /> python $HOME/Xml1/Set1/run_parallel.py /home/rcf-104/patrices/bbp/11.2.2/setup_bbp_env.sh $HOME<br /> /Xml1/Set1/batch_run_bbp_moves.log $PBS_NODEFILE 1<br /> <br /> echo &quot;Jobs end&quot;<br /> date<br /> &lt;/pre&gt;</div> Patrices https://strike.scec.org/scecwiki/index.php?title=Fling_Study&diff=5082 Fling Study 2012-05-10T22:56:13Z <p>Patrices: </p> <hr /> <div>== Overview ==<br /> <br /> The Fling study is a set of broadband platform simulations defined by PG&amp;E and PEER researchers and run by SCEC Broadband platform group. Full specification of the Fling study will be posted when available.<br /> <br /> == Certification of USC HPCC Cluster for Broadband Calculations ==<br /> <br /> The verification and validation of the currently released Broadband platform is based on results generated on a SCEC server called broadband.usc.edu. When we move the Broadband platform software, re-build it, and re-run it in a different computing environment, the results the platform produces can be slightly different than results produced on the SCEC server. Differences can come from computing hardware, from operating system characteristics, from compiler version, and other sources.<br /> <br /> Before accepting results generated in a new computing environment, we must first certify that the new computing environment produces results that are equivalent to the results from the original server where the platform was originally developed and tested.<br /> <br /> To speed up execution of the Fling study, we plan to run it on the USC HPCC cluster, so we must certify that USC HPCC cluster results are valid and comparable to those generated on broadband.usc.edu.<br /> <br /> Here are results from our initial certification tests. A researcher ran a small subset of the Fling study on the SCEC broadband server. Then, we ran the same subset on the USC HPCC cluster. Below we compare the output seismograms from both runs, showing that the two results are very similar.<br /> <br /> In our discussions, we decided that the certification criteria for this study will include a number of small magnitude ruptures, and a number of large magnitude ruptures, which we will post when they are available.<br /> <br /> == Comparison of Seismogram from Server and Cluster ==<br /> <br /> {| class=&quot;wikitable&quot; border=&quot;1&quot;<br /> |-<br /> ! Simulation<br /> ! broadband.usc.edu<br /> ! USC HPCC cluster<br /> |-<br /> | 10010116<br /> | [[File: 10010116_ref.p015p000_velocity_seis.png|256px|thumb]]<br /> | [[File: 10010116_hpcc.p015p000_velocity_seis.png|256px|thumb]]<br /> |-<br /> | 10010129<br /> | [[File: 10010129_ref.p035p008_velocity_seis.png|256px|thumb]]<br /> | [[File: 10010129_hpcc.p035p008_velocity_seis.png|256px|thumb]]<br /> |}<br /> <br /> &lt;pre&gt;<br /> scenario_id magnitude dip rake Ztor fault_length fault_width Priority<br /> <br /> 101 6 90 180 0 14 8 1<br /> 102 6.5 90 180 0 24 13 <br /> 103 7 90 180 0 68 15 <br /> 104 7.5 90 180 0 210 15 <br /> 105 7.8 90 180 0 420 15 <br /> 106 8.2 90 180 0 470 15 <br /> <br /> 107 6 70 180 0 14 8 2<br /> 108 6.5 70 180 0 24 13 <br /> 109 7 70 180 0 68 15 <br /> 110 7.5 70 180 0 210 15 <br /> 111 7.8 70 180 0 420 15 <br /> 112 8.2 70 180 0 470 15 <br /> <br /> 113 6 70 180 0 14 8 3<br /> 114 6.5 70 180 0 24 13 <br /> 115 7 70 180 0 40 25 <br /> 116 7.5 70 180 0 100 32 <br /> 117 7.8 70 180 0 160 40 <br /> 118 8.2 70 180 0 400 40 <br /> <br /> 119 6 90 180 0 14 8 4<br /> 120 6.5 90 180 0 24 13 <br /> 121 7 90 180 0 40 25 <br /> 122 7.5 90 180 0 100 32 <br /> 123 7.8 90 180 0 160 40 <br /> 124 8.2 90 180 0 400 40 <br /> <br /> 125 6 45 90 0 10 10 5<br /> 126 6 45 90 5 10 10 <br /> 127 6.5 45 90 0 18 18 <br /> 128 6.5 45 90 5 18 18 <br /> 129 7 45 90 0 44 23 <br /> 130 7.5 45 90 0 126 25 <br /> 131 7.8 45 90 0 180 25 <br /> <br /> 132 6 60 90 0 10 10 <br /> 133 6 60 90 5 10 10 <br /> 134 6.5 60 90 0 18 18 <br /> 135 6.5 60 90 5 18 18 <br /> 136 7 60 90 0 50 20 <br /> 137 7.5 60 90 0 150 20 <br /> 138 7.8 60 90 0 200 20<br /> <br /> 139 7.0 45 90 0 18 18<br /> 140 6.5 45 90 0 18 18<br /> 141 6.5 45 90 5 18 18<br /> 142 7.0 45 90 0 44 23<br /> <br /> <br /> &lt;/pre&gt;<br /> <br /> == Notes ==<br /> Ronnie and I have put together a subset of fling simulations to submit to the BB Platform. Attached, please find a list containing all of the scenarios that we will eventually be providing. However, Scenarios 140, 141 and 142 were identified as high priority simulations at our NGA-West2 meeting last Friday. If possible, we would like to get them running right away.<br /> <br /> <br /> <br /> Scenarios 140 – 142 can be found in my directory:<br /> <br /> /home/scec-01/Wooddell/broadband/fling<br /> <br /> <br /> <br /> I have created a separate folder for each of the Scenarios.<br /> <br /> <br /> <br /> I would like to submit the remainder of the fling simulations all at once, but I have not yet had the opportunity to finalize them all. I will send you a message when they are completed, probably sometime tomorrow or Thursday.<br /> <br /> == Running on USC HPCC ==<br /> <br /> A sample set of simulations from the Fling study were run on USC HPCC. The original fling generation scripts, source descriptions, station lists, and batch scripts were copied over from broadband.usc.edu to /home/rcf-104. Then small modifications were made to update paths and block the actual execution of the platform (the platform will be run in a PBS job):<br /> <br /> Sample scripts can be found at the following locations:<br /> <br /> {| class=&quot;wikitable&quot; | border=&quot;1&quot;<br /> |-<br /> ! Script<br /> ! Location<br /> ! Description<br /> ! Modified<br /> |-<br /> | build_xml.py<br /> | /auto/rcf-104/patrices/bbp/batch_tools<br /> | Builds XML workflows for a simulation<br /> | No<br /> |-<br /> | batch_run_bbp.py<br /> | /auto/rcf-104/patrices/bbp/batch_tools<br /> | Executes BBP workflow<br /> | Modified to only write BBP command-lines for simulations to a log for later execution by run_parallel.py<br /> |-<br /> | run_parallel.py<br /> | /auto/rcf-104/patrices/bbp/batch_tools<br /> | Helper script to run N programs on a set of M cores<br /> | New script<br /> |- <br /> | gen_source_input.csh<br /> | /auto/rcf-104/patrices/bbp/fling<br /> | Generate full study inputs<br /> | No<br /> |-<br /> | run_bbp-parallel.csh<br /> | /auto/rcf-104/patrices/bbp/fling<br /> | Execute the study with the platform<br /> | Some paths changed, also added ${ROOT_PATH} to some relative path locations to make them absolute paths<br /> |}<br /> <br /> <br /> Example PBS script running the sample Fling simulations on 16 cores:<br /> <br /> &lt;pre&gt;<br /> #!/bin/bash<br /> <br /> #PBS -q nbns<br /> #PBS -l arch=x86_64,pmem=2000mb,pvmem=3000mb,walltime=6:00:00,nodes=4:ppn=4<br /> #PBS -V<br /> #PBS -e /home/rcf-104/patrices/bbp/fling/Xml1/Set1/run_set1.err<br /> #PBS -o /home/rcf-104/patrices/bbp/fling/Xml1/Set1/run_set1.out<br /> <br /> PYTHONPATH=/home/rcf-104/patrices/bbp/11.2.2/bbp_2g/comps<br /> <br /> HOME=/home/rcf-104/patrices/bbp/fling<br /> <br /> echo &quot;Jobs start&quot;<br /> date<br /> <br /> cd $HOME<br /> <br /> python $HOME/Xml1/Set1/run_parallel.py /home/rcf-104/patrices/bbp/11.2.2/setup_bbp_env.sh $HOME<br /> /Xml1/Set1/batch_run_bbp_sims.log $PBS_NODEFILE 1<br /> <br /> python $HOME/Xml1/Set1/run_parallel.py /home/rcf-104/patrices/bbp/11.2.2/setup_bbp_env.sh $HOME<br /> /Xml1/Set1/batch_run_bbp_moves.log $PBS_NODEFILE 1<br /> <br /> echo &quot;Jobs end&quot;<br /> date<br /> &lt;/pre&gt;<br /> <br /> <br /> # gen_source_input.csh<br /> # run_bbp-parallel.csh<br /> #</div> Patrices https://strike.scec.org/scecwiki/index.php?title=Fling_Study&diff=5081 Fling Study 2012-05-10T22:52:47Z <p>Patrices: </p> <hr /> <div>== Overview ==<br /> <br /> The Fling study is a set of broadband platform simulations defined by PG&amp;E and PEER researchers and run by SCEC Broadband platform group. Full specification of the Fling study will be posted when available.<br /> <br /> == Certification of USC HPCC Cluster for Broadband Calculations ==<br /> <br /> The verification and validation of the currently released Broadband platform is based on results generated on a SCEC server called broadband.usc.edu. When we move the Broadband platform software, re-build it, and re-run it in a different computing environment, the results the platform produces can be slightly different than results produced on the SCEC server. Differences can come from computing hardware, from operating system characteristics, from compiler version, and other sources.<br /> <br /> Before accepting results generated in a new computing environment, we must first certify that the new computing environment produces results that are equivalent to the results from the original server where the platform was originally developed and tested.<br /> <br /> To speed up execution of the Fling study, we plan to run it on the USC HPCC cluster, so we must certify that USC HPCC cluster results are valid and comparable to those generated on broadband.usc.edu.<br /> <br /> Here are results from our initial certification tests. A researcher ran a small subset of the Fling study on the SCEC broadband server. Then, we ran the same subset on the USC HPCC cluster. Below we compare the output seismograms from both runs, showing that the two results are very similar.<br /> <br /> In our discussions, we decided that the certification criteria for this study will include a number of small magnitude ruptures, and a number of large magnitude ruptures, which we will post when they are available.<br /> <br /> == Comparison of Seismogram from Server and Cluster ==<br /> <br /> {| class=&quot;wikitable&quot; border=&quot;1&quot;<br /> |-<br /> ! Simulation<br /> ! broadband.usc.edu<br /> ! USC HPCC cluster<br /> |-<br /> | 10010116<br /> | [[File: 10010116_ref.p015p000_velocity_seis.png|256px|thumb]]<br /> | [[File: 10010116_hpcc.p015p000_velocity_seis.png|256px|thumb]]<br /> |-<br /> | 10010129<br /> | [[File: 10010129_ref.p035p008_velocity_seis.png|256px|thumb]]<br /> | [[File: 10010129_hpcc.p035p008_velocity_seis.png|256px|thumb]]<br /> |}<br /> <br /> &lt;pre&gt;<br /> scenario_id magnitude dip rake Ztor fault_length fault_width Priority<br /> <br /> 101 6 90 180 0 14 8 1<br /> 102 6.5 90 180 0 24 13 <br /> 103 7 90 180 0 68 15 <br /> 104 7.5 90 180 0 210 15 <br /> 105 7.8 90 180 0 420 15 <br /> 106 8.2 90 180 0 470 15 <br /> <br /> 107 6 70 180 0 14 8 2<br /> 108 6.5 70 180 0 24 13 <br /> 109 7 70 180 0 68 15 <br /> 110 7.5 70 180 0 210 15 <br /> 111 7.8 70 180 0 420 15 <br /> 112 8.2 70 180 0 470 15 <br /> <br /> 113 6 70 180 0 14 8 3<br /> 114 6.5 70 180 0 24 13 <br /> 115 7 70 180 0 40 25 <br /> 116 7.5 70 180 0 100 32 <br /> 117 7.8 70 180 0 160 40 <br /> 118 8.2 70 180 0 400 40 <br /> <br /> 119 6 90 180 0 14 8 4<br /> 120 6.5 90 180 0 24 13 <br /> 121 7 90 180 0 40 25 <br /> 122 7.5 90 180 0 100 32 <br /> 123 7.8 90 180 0 160 40 <br /> 124 8.2 90 180 0 400 40 <br /> <br /> 125 6 45 90 0 10 10 5<br /> 126 6 45 90 5 10 10 <br /> 127 6.5 45 90 0 18 18 <br /> 128 6.5 45 90 5 18 18 <br /> 129 7 45 90 0 44 23 <br /> 130 7.5 45 90 0 126 25 <br /> 131 7.8 45 90 0 180 25 <br /> <br /> 132 6 60 90 0 10 10 <br /> 133 6 60 90 5 10 10 <br /> 134 6.5 60 90 0 18 18 <br /> 135 6.5 60 90 5 18 18 <br /> 136 7 60 90 0 50 20 <br /> 137 7.5 60 90 0 150 20 <br /> 138 7.8 60 90 0 200 20<br /> <br /> 139 7.0 45 90 0 18 18<br /> 140 6.5 45 90 0 18 18<br /> 141 6.5 45 90 5 18 18<br /> 142 7.0 45 90 0 44 23<br /> <br /> <br /> &lt;/pre&gt;<br /> <br /> == Notes ==<br /> Ronnie and I have put together a subset of fling simulations to submit to the BB Platform. Attached, please find a list containing all of the scenarios that we will eventually be providing. However, Scenarios 140, 141 and 142 were identified as high priority simulations at our NGA-West2 meeting last Friday. If possible, we would like to get them running right away.<br /> <br /> <br /> <br /> Scenarios 140 – 142 can be found in my directory:<br /> <br /> /home/scec-01/Wooddell/broadband/fling<br /> <br /> <br /> <br /> I have created a separate folder for each of the Scenarios.<br /> <br /> <br /> <br /> I would like to submit the remainder of the fling simulations all at once, but I have not yet had the opportunity to finalize them all. I will send you a message when they are completed, probably sometime tomorrow or Thursday.<br /> <br /> == Running on USC HPCC ==<br /> <br /> A sample set of simulations from the Fling study were run on USC HPCC. The original fling generation scripts, source descriptions, station lists, and batch scripts were copied over from broadband.usc.edu to /home/rcf-104. Then small modifications were made to update paths and block the actual execution of the platform (the platform will be run in a PBS job):<br /> <br /> Sample scripts can be found at the following locations:<br /> <br /> {| class=&quot;wikitable&quot; | border=&quot;1&quot;<br /> |-<br /> ! Script<br /> ! Location<br /> ! Description<br /> ! Modified<br /> |-<br /> | build_xml.py<br /> | /auto/rcf-104/patrices/bbp/batch_tools<br /> | Builds XML workflows for a simulation<br /> | No<br /> |-<br /> | batch_run_bbp.py<br /> | /auto/rcf-104/patrices/bbp/batch_tools<br /> | Executes BBP workflow<br /> | Modified to only write BBP command-lines for simulations to a log for later execution by run_parallel.py<br /> |-<br /> | run_parallel.py<br /> | /auto/rcf-104/patrices/bbp/batch_tools<br /> | Helper script to run N programs on a set of M cores<br /> | New script<br /> |- <br /> | gen_source_input.csh<br /> | /auto/rcf-104/patrices/bbp/fling<br /> | Generate full study inputs<br /> | No<br /> |-<br /> | run_bbp-parallel.csh<br /> | /auto/rcf-104/patrices/bbp/fling<br /> | Execute the study with the platform<br /> | Some paths changed, also added ${ROOT_PATH} to some relative path locations to make them absolute paths<br /> |}<br /> <br /> Example PBS script running the sample Fling simulations:<br /> <br /> &lt;pre&gt;<br /> #!/bin/bash<br /> <br /> #PBS -q nbns<br /> #PBS -l arch=x86_64,pmem=2000mb,pvmem=3000mb,walltime=6:00:00,nodes=4:ppn=4<br /> #PBS -V<br /> #PBS -e /home/rcf-104/patrices/bbp/fling/Xml1/Set1/run_set1.err<br /> #PBS -o /home/rcf-104/patrices/bbp/fling/Xml1/Set1/run_set1.out<br /> <br /> PYTHONPATH=/home/rcf-104/patrices/bbp/11.2.2/bbp_2g/comps<br /> <br /> HOME=/home/rcf-104/patrices/bbp/fling<br /> <br /> echo &quot;Jobs start&quot;<br /> date<br /> <br /> cd $HOME<br /> <br /> python $HOME/Xml1/Set1/run_parallel.py /home/rcf-104/patrices/bbp/11.2.2/setup_bbp_env.sh $HOME<br /> /Xml1/Set1/batch_run_bbp_sims.log $PBS_NODEFILE 1<br /> <br /> python $HOME/Xml1/Set1/run_parallel.py /home/rcf-104/patrices/bbp/11.2.2/setup_bbp_env.sh $HOME<br /> /Xml1/Set1/batch_run_bbp_moves.log $PBS_NODEFILE 1<br /> <br /> echo &quot;Jobs end&quot;<br /> date<br /> &lt;/pre&gt;<br /> <br /> <br /> # gen_source_input.csh<br /> # run_bbp-parallel.csh<br /> #</div> Patrices https://strike.scec.org/scecwiki/index.php?title=Fling_Study&diff=5080 Fling Study 2012-05-10T22:51:26Z <p>Patrices: </p> <hr /> <div>== Overview ==<br /> <br /> The Fling study is a set of broadband platform simulations defined by PG&amp;E and PEER researchers and run by SCEC Broadband platform group. Full specification of the Fling study will be posted when available.<br /> <br /> == Certification of USC HPCC Cluster for Broadband Calculations ==<br /> <br /> The verification and validation of the currently released Broadband platform is based on results generated on a SCEC server called broadband.usc.edu. When we move the Broadband platform software, re-build it, and re-run it in a different computing environment, the results the platform produces can be slightly different than results produced on the SCEC server. Differences can come from computing hardware, from operating system characteristics, from compiler version, and other sources.<br /> <br /> Before accepting results generated in a new computing environment, we must first certify that the new computing environment produces results that are equivalent to the results from the original server where the platform was originally developed and tested.<br /> <br /> To speed up execution of the Fling study, we plan to run it on the USC HPCC cluster, so we must certify that USC HPCC cluster results are valid and comparable to those generated on broadband.usc.edu.<br /> <br /> Here are results from our initial certification tests. A researcher ran a small subset of the Fling study on the SCEC broadband server. Then, we ran the same subset on the USC HPCC cluster. Below we compare the output seismograms from both runs, showing that the two results are very similar.<br /> <br /> In our discussions, we decided that the certification criteria for this study will include a number of small magnitude ruptures, and a number of large magnitude ruptures, which we will post when they are available.<br /> <br /> == Comparison of Seismogram from Server and Cluster ==<br /> <br /> {| class=&quot;wikitable&quot; border=&quot;1&quot;<br /> |-<br /> ! Simulation<br /> ! broadband.usc.edu<br /> ! USC HPCC cluster<br /> |-<br /> | 10010116<br /> | [[File: 10010116_ref.p015p000_velocity_seis.png|256px|thumb]]<br /> | [[File: 10010116_hpcc.p015p000_velocity_seis.png|256px|thumb]]<br /> |-<br /> | 10010129<br /> | [[File: 10010129_ref.p035p008_velocity_seis.png|256px|thumb]]<br /> | [[File: 10010129_hpcc.p035p008_velocity_seis.png|256px|thumb]]<br /> |}<br /> <br /> &lt;pre&gt;<br /> scenario_id magnitude dip rake Ztor fault_length fault_width Priority<br /> <br /> 101 6 90 180 0 14 8 1<br /> 102 6.5 90 180 0 24 13 <br /> 103 7 90 180 0 68 15 <br /> 104 7.5 90 180 0 210 15 <br /> 105 7.8 90 180 0 420 15 <br /> 106 8.2 90 180 0 470 15 <br /> <br /> 107 6 70 180 0 14 8 2<br /> 108 6.5 70 180 0 24 13 <br /> 109 7 70 180 0 68 15 <br /> 110 7.5 70 180 0 210 15 <br /> 111 7.8 70 180 0 420 15 <br /> 112 8.2 70 180 0 470 15 <br /> <br /> 113 6 70 180 0 14 8 3<br /> 114 6.5 70 180 0 24 13 <br /> 115 7 70 180 0 40 25 <br /> 116 7.5 70 180 0 100 32 <br /> 117 7.8 70 180 0 160 40 <br /> 118 8.2 70 180 0 400 40 <br /> <br /> 119 6 90 180 0 14 8 4<br /> 120 6.5 90 180 0 24 13 <br /> 121 7 90 180 0 40 25 <br /> 122 7.5 90 180 0 100 32 <br /> 123 7.8 90 180 0 160 40 <br /> 124 8.2 90 180 0 400 40 <br /> <br /> 125 6 45 90 0 10 10 5<br /> 126 6 45 90 5 10 10 <br /> 127 6.5 45 90 0 18 18 <br /> 128 6.5 45 90 5 18 18 <br /> 129 7 45 90 0 44 23 <br /> 130 7.5 45 90 0 126 25 <br /> 131 7.8 45 90 0 180 25 <br /> <br /> 132 6 60 90 0 10 10 <br /> 133 6 60 90 5 10 10 <br /> 134 6.5 60 90 0 18 18 <br /> 135 6.5 60 90 5 18 18 <br /> 136 7 60 90 0 50 20 <br /> 137 7.5 60 90 0 150 20 <br /> 138 7.8 60 90 0 200 20<br /> <br /> 139 7.0 45 90 0 18 18<br /> 140 6.5 45 90 0 18 18<br /> 141 6.5 45 90 5 18 18<br /> 142 7.0 45 90 0 44 23<br /> <br /> <br /> &lt;/pre&gt;<br /> <br /> == Notes ==<br /> Ronnie and I have put together a subset of fling simulations to submit to the BB Platform. Attached, please find a list containing all of the scenarios that we will eventually be providing. However, Scenarios 140, 141 and 142 were identified as high priority simulations at our NGA-West2 meeting last Friday. If possible, we would like to get them running right away.<br /> <br /> <br /> <br /> Scenarios 140 – 142 can be found in my directory:<br /> <br /> /home/scec-01/Wooddell/broadband/fling<br /> <br /> <br /> <br /> I have created a separate folder for each of the Scenarios.<br /> <br /> <br /> <br /> I would like to submit the remainder of the fling simulations all at once, but I have not yet had the opportunity to finalize them all. I will send you a message when they are completed, probably sometime tomorrow or Thursday.<br /> <br /> == Running on USC HPCC ==<br /> <br /> A sample set of simulations from the Fling study were run on USC HPCC. The original fling generation scripts, source descriptions, station lists, and batch scripts were copied over from broadband.usc.edu to /home/rcf-104. Then small modifications were made to update paths and block the actual execution of the platform (the platform will be run in a PBS job):<br /> <br /> Sample scripts can be found at the following locations:<br /> <br /> {| class=&quot;wikitable&quot; | border=&quot;1&quot;<br /> |-<br /> ! Script<br /> ! Location<br /> ! Description<br /> ! Modified<br /> |-<br /> | build_xml.py<br /> | /auto/rcf-104/patrices/bbp/batch_tools<br /> | Builds XML workflows for a simulation<br /> | No<br /> |-<br /> | batch_run_bbp.py<br /> | /auto/rcf-104/patrices/bbp/batch_tools<br /> | Executes BBP workflow<br /> | Modified to only write BBP command-lines for simulations to a log for later execution by run_parallel.py<br /> |-<br /> | run_parallel.py<br /> | /auto/rcf-104/patrices/bbp/batch_tools<br /> | Helper script to run N programs on a set of M cores<br /> | New script<br /> |- <br /> | gen_source_input.csh<br /> | /auto/rcf-104/patrices/bbp/fling<br /> | Generate full study inputs<br /> | No<br /> |-<br /> | run_bbp-parallel.csh<br /> | /auto/rcf-104/patrices/bbp/fling<br /> | Execute the study with the platform<br /> | Some paths changed, also added ${ROOT_PATH} to some relative path locations to make them absolute paths<br /> |}<br /> <br /> <br /> <br /> <br /> # gen_source_input.csh<br /> # run_bbp-parallel.csh<br /> #</div> Patrices https://strike.scec.org/scecwiki/index.php?title=Broadband_Platform_v11.2.3&diff=5068 Broadband Platform v11.2.3 2012-05-09T18:12:08Z <p>Patrices: </p> <hr /> <div>[[File:Bbp.jpg|256px|thumb|right|Fig 1: Broadband Platform.]]<br /> <br /> The SCEC Broadband Platform is a software system which generates 0-10 Hz seismograms for historical and scenario earthquakes in California.<br /> <br /> == Overview == <br /> <br /> The goal of the SCEC Broadband Simulation Platform is to generate broadband (0-10 Hz) ground motions for earthquakes using deterministic low-frequency and stochastic high-frequency simulations. The SCEC Broadband Platform is a collaborative software development project involving SCEC researchers, graduate students, and the SCEC/CME software development group. SCEC scientific groups have contributed modules to the Broadband Platform including rupture generation, low-frequency deterministic seismogram synthesis, high-frequency stochastic seismogram synthesis, and non-linear site effects. 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.<br /> <br /> Users may calculate broadband seismograms for both historical earthquakes (validation events including Northridge, Loma Prieta, and Landers) and user-defined earthquakes. The platform produces a variety of data products, including broadband seismograms, rupture visualizations, and 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, and the Mojave. Users may select among various codebases for 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.<br /> <br /> 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. <br /> <br /> == Current Release ==<br /> <br /> The current official release of Broadband Platform is v11.2.3. This distribution was posted online on Wednesday, 09 May 2012. This is a &quot;bug-fix&quot; version of the platform that fixes a small number of bugs discovered in v11.2.2 since its release in October 2011. Details of the bugs fixes are provided in the release notes. No new features are introduced in this version of the platform. New 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.<br /> <br /> == Dependencies ==<br /> <br /> Broadband has the following dependencies:<br /> <br /> *[http://www.python.org/download/ Python 2.5+] with<br /> **[http://new.scipy.org/download.html NumPy]<br /> **[http://matplotlib.sourceforge.net/ matplotlib]<br /> *[http://software.intel.com/en-us/articles/non-commercial-software-download/ Intel compilers]<br /> A non-commercial copy of Intel c and FORTRAN compilers can be obtained by registering for a [http://software.intel.com/en-us/articles/non-commercial-software-development/ non-commercial account with Intel] and downloading the compilers from the Intel website.<br /> <br /> and the following optional dependencies for additional functionality:<br /> <br /> *[http://gmt.soest.hawaii.edu/ GMT] (for plotting)<br /> *Matlab with map toolbox (for certain platform modules)<br /> *[http://www.pygtk.org/downloads.html PyGTK] (for interactive plotting)<br /> <br /> == Documentation ==<br /> <br /> User Guide Wiki (includes installation instructions): <br /> *[[Broadband User Guide Current]]<br /> <br /> == Downloads ==<br /> <br /> To install and use the Broadband platform, you need both the source code and the data files. 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.<br /> <br /> Users that are upgrading from V11.2.0 to v11.2.3 should retrieve new versions of both the Broadband Platform data files and the Broadband Platform source code. Both were changed in this latest release.<br /> <br /> There are detailed installation instructions in the [[Broadband User Guide Current]].<br /> <br /> The main steps involved in installing the platform as a local installation on Linux machine include:<br /> # The software can be installed in an account on a Linux computer with at least 4GB of disk storage and C, Fortran, and Python software installed.<br /> # 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.<br /> # Download the following four files (source, source md5sum, data, data md5sum) into a directory and run the md5sum program to confirm you have an undamaged version of the distribution files.<br /> # Uncompress the distribution (tgz) files into data and source directory structures. The data files are nearly 3GB, but they are static and will not be modified and will not grow in size during use of the platform. The source directory is small, but this directory will increase as the platform is used, since the results produced by the platform will be stored here.<br /> # Configure your environment to add broadband platform directories into your python path and define other useful environment variables.<br /> # Build the executables by running the top level makefile.<br /> # Confirm the code is built correctly by running UnitTests.<br /> # Confirm the code runs correctly on your system by running AcceptanceTests.<br /> # Use the platform for research purposes.<br /> <br /> == Current Broadband Platform Release == <br /> <br /> The current SCEC Broadband platform release is v11.2.3. Links to the source code and data distributions are listed in the table below:<br /> <br /> {| class=&quot;wikitable&quot; border=&quot;1&quot; cellpadding=&quot;5&quot; cellspacing=&quot;0&quot;<br /> |-<br /> ! rowspan=&quot;2&quot;| Version<br /> ! rowspan=&quot;2&quot;| Release Date<br /> ! colspan=&quot;2&quot;| Files<br /> ! rowspan=&quot;2&quot;| User Guide<br /> |-<br /> ! Source Code<br /> ! Data<br /> |-<br /> ! scope=&quot;row&quot; rowspan=&quot;1&quot; | 11.2.3<br /> | 05/09/2012<br /> | [http://hypocenter.usc.edu/research/broadband/11.2.3/bbp_dist_v11.2.3.tgz bbp_dist_v11.2.3.tgz]<br /> [http://hypocenter.usc.edu/research/broadband/11.2.3/bbp_dist_v11.2.3.tgz.md5 bbp_dist_v11.2.3.tgz.md5]<br /> |[http://hypocenter.usc.edu/research/broadband/11.2.3/bbp_data_v11.2.3.tgz bbp_data_v11.2.3.tgz]<br /> [http://hypocenter.usc.edu/research/broadband/11.2.3/bbp_data_v11.2.3.tgz.md5 bbp_data_v11.2.3.tgz.md5]<br /> |[[Broadband User Guide v11.2.3]]<br /> [[Broadband v11.2.3 Release Notes]]<br /> |}<br /> <br /> == Optional Broadband Platform Patches ==<br /> <br /> There are currently no optional patches available for 11.2.3.<br /> <br /> == Previous Broadband Platform Release ==<br /> <br /> 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.<br /> <br /> {| class=&quot;wikitable&quot; border=&quot;1&quot; cellpadding=&quot;5&quot; cellspacing=&quot;0&quot;<br /> |-<br /> ! rowspan=&quot;2&quot;| Version<br /> ! rowspan=&quot;2&quot;| Release Date<br /> ! colspan=&quot;3&quot;| Files<br /> ! rowspan=&quot;2&quot;| User Guide<br /> |-<br /> ! Source Code<br /> ! Data<br /> ! Patches<br /> |-<br /> ! scope=&quot;row&quot; rowspan=&quot;1&quot; | 11.2.2<br /> | 10/21/2011<br /> | [http://hypocenter.usc.edu/research/broadband/11.2.1/bbp_dist_v11.2.2.tgz bbp_dist_v11.2.2.tgz]<br /> [http://hypocenter.usc.edu/research/broadband/11.2.1/bbp_dist_v11.2.2.tgz.md5 bbp_dist_v11.2.2.tgz.md5]<br /> |[http://hypocenter.usc.edu/research/broadband/11.2.1/bbp_data_v11.2.2.tgz bbp_data_v11.2.2.tgz]<br /> [http://hypocenter.usc.edu/research/broadband/11.2.1/bbp_data_v11.2.2.tgz.md5 bbp_data_v11.2.2.tgz.md5]<br /> |[http://hypocenter.usc.edu/research/broadband/11.2.2_patch/bbp_patch_v11.2.2.1.tgz bbp_patch_v11.2.2.1.tgz]<br /> [http://hypocenter.usc.edu/research/broadband/11.2.2_patch/bbp_patch_v11.2.2.2.tgz bbp_patch_v11.2.2.2.tgz]<br /> |[[Broadband User Guide v11.2.2]]<br /> [[Broadband v11.2.2 Release Notes]]<br /> |-<br /> ! scope=&quot;row&quot; rowspan=&quot;1&quot; | 11.2.1<br /> | 09/29/2011<br /> | [http://hypocenter.usc.edu/research/broadband/11.2.1/bbp_dist_v11.2.1.tgz bbp_dist_v11.2.1.tgz]<br /> [http://hypocenter.usc.edu/research/broadband/11.2.1/bbp_dist_v11.2.1.tgz.md5 bbp_dist_v11.2.1.tgz.md5]<br /> |[http://hypocenter.usc.edu/research/broadband/11.2.1/bbp_data_v11.2.1.tgz bbp_data_v11.2.1.tgz]<br /> [http://hypocenter.usc.edu/research/broadband/11.2.1/bbp_data_v11.2.1.tgz.md5 bbp_data_v11.2.1.tgz.md5]<br /> |<br /> |[[Broadband User Guide v11.2.1]]<br /> [[Broadband v11.2.1 Release Notes]]<br /> |-<br /> ! scope=&quot;row&quot; rowspan=&quot;1&quot; | 11.2.0<br /> | 02/18/2011<br /> | [http://hypocenter.usc.edu/research/broadband/11.2.0/bbp_dist_v11.2.0.tgz bbp_dist_v11.2.0.tgz]<br /> [http://hypocenter.usc.edu/research/broadband/11.2.0/bbp_dist_v11.2.0.tgz.md5 bbp_dist_v11.2.0.tgz.md5]<br /> |[http://hypocenter.usc.edu/research/broadband/11.2.0/bbp_data_v11.2.0.tgz bbp_data_v11.2.0.tgz]<br /> [http://hypocenter.usc.edu/research/broadband/11.2.0/bbp_data_v11.2.0.tgz.md5 bbp_data_v11.2.0.tgz.md5]<br /> |<br /> |[[Broadband User Guide v11.2]] <br /> |}<br /> <br /> == Supporting Materials ==<br /> *[http://hypocenter.usc.edu/research/broadband/bbp_ssa2011-v1.pptx Broadband Platform Presentation - SSA 2011 - Robert Graves (5MB pptx file)]<br /> *[http://hypocenter.usc.edu/research/broadband/documents/Broadband_AGU_poster.pdf Broadband poster from AGU 2010 (PDF, 882 KB)]<br /> *[http://hypocenter.usc.edu/research/broadband/documents/Broadband_overview.ppt Broadband overview talk from SC10 (PPT, 3.7 MB)] <br /> *[http://hypocenter.usc.edu/research/broadband/documents/Broadband_module_schematics.pptx Technical diagrams of Broadband module relationships (PPTX, 16 KB)]<br /> <br /> == Development version ==<br /> <br /> If you're interested in working with the latest development version of the platform, you can check it out from<br /> svn co https://source.usc.edu/svn/broadband/trunk<br /> <br /> Details about working with the development version are provided in the User Guide.<br /> <br /> The next version of Broadband, v 11.7, is expected to be released in Q4 of 2012. Additional details about this version is available here:<br /> *[[Broadband Development Version]]<br /> *[[Broadband User Guide v11.7.0]]<br /> <br /> == Help ==<br /> <br /> For assistance with the Broadband Platform, you may<br /> * Email software @ scec.org with specific questions<br /> * Browse and submit new trouble tickets, or feature requests, at [http://northridge.usc.edu/trac/broadband Broadband Trac site]. SCEC user login is required to submit trouble tickets this way.<br /> <br /> == License ==<br /> <br /> SCEC Broadband Platform software distributions are released under an Apache 2.0 open-source license as described here [[Broadband License]].<br /> <br /> == Changes in Broadband Platform v11.2.3 ==<br /> <br /> 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.<br /> <br /> * Trac # 30 Change tolerance depending on acceptance test combo<br /> * Trac # 69 UCSB high and low frequency modules don't work for Loma Prieta validation<br /> * Trac # 70 UCSB src/ucsb/Converter/utlFault.h srf name buffer length too short<br /> * Trac # 71 Allow tolerance checks to be disabled in unit/acceptance tests<br /> * Trac # 72 run_bbp_2G.py option file parsing exception when selecting a file among two or more choices<br /> * Trac # 74 Minor bug in a routine that is used for geographic conversions in the URS simulations on the BB platform<br /> * Trac # 75 Update Green's function data file with fixes and new datasets<br /> * Trac # 76 Change DEFAULT_KAPPA from 0.02 to 0.01 in ./comps/stas2files.py<br /> * Trac # 77 Remove station &quot;olem&quot; vs30 value from from UCSB Loma Prieta stations.vs30 in 11.7.0/trunk data sets<br /> * Trac # 78 Updated geobb_srf.py to use URS ll2xy coordinate conversion routines on trunk<br /> <br /> 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.<br /> <br /> * Trac # 56 Convert BBP Matlab scripts to Python<br /> * Trac # 67 Rename the cleanup.py so that people do not run it accidentally<br /> * Trac # 68 Build Broadband with latest (2011) Intel and GNU compilers<br /> <br /> 11.2.1 - September 2011 - Bug-fix release<br /> List of Trac items fixed in this release: <br /> * Trac # 41 - Add License file (EULA) to Broadband distribution.<br /> * Trac # 42 - Add a file manifest to the distribution archives.<br /> * Trac # 46 - Remove Hardcoded Green_Bank.inf entries.<br /> * Trac # 47 - Syn1d Module fails with IO error due to missing file.<br /> * Trac # 54 - plot_SRF.csh fails with &quot;Newline in variable name&quot;.<br /> * Trac # 61 - Provide an option to remove temporary folders at end of Broadband simulation run.<br /> * Trac # 62 - Add a warning and user prompt to comps/cleanup.py script.<br /> * Trac # 63 - Acceptance resume.txt should not be created in ref_data/accept_inputs.<br /> * Trac # 64 - Simulations with URS HF module fail with IOError and segmentation faults.<br /> * Trac # 65 - Add the XML file generated during a Broadband simulation to the output directory as metadata. <br /> <br /> 11.2.0 - February 2011 - Initial release.<br /> <br /> == Collaborators ==<br /> <br /> *[http://www.erdw.ethz.ch/index_EN ETH Zurich - Swiss Federal Institute of Technology Zurich]<br /> *[http://www.geology.sdsu.edu/ San Diego State University Dept of Geological Sciences]<br /> *[http://www.geol.ucsb.edu/ U.C. Santa Barbara Dept of Earth Sciences]<br /> *[http://www.crustal.ucsb.edu/ UCSB Institute for Crustal Studies]<br /> *[http://www.urscorp.com/ URS Corporation]<br /> *[http://www.scec.org SCEC]<br /> *[http://scec.usc.edu/scecpedia SCEC/CME Project]<br /> <br /> == See Also ==<br /> *[[Broadband Platform 2007]]<br /> *[http://scec.usc.edu/scecpedia/software SCEC Software Downloads]<br /> *[http://scec.usc.edu/scecpedia SCEC Wiki Main]<br /> *[http://www.scec.org SCEC Home Page]<br /> *[[Broadband User Guide Current]]<br /> *[[Broadband User Guide Development]]<br /> *[[Broadband Server]]<br /> *[[Broadband Hanging Wall Simulation]]<br /> *[[Broadband Development]]<br /> *[[Broadband Platform Installation Guide Current]]<br /> *[[Broadband Platform User Guide Current]]<br /> <br /> ==References==<br /> <br /> #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. [http://hypocenter.usc.edu/research/broadband/documents/Graves_Pitarka_2010.pdf link]<br /> #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. [http://hypocenter.usc.edu/research/broadband/documents/Mai_Imperatori_Olsen_2010.pdf link]<br /> #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. [http://hypocenter.usc.edu/research/broadband/documents/Schmedes_Archuleta_Lavallee_2010.pdf link]</div> Patrices https://strike.scec.org/scecwiki/index.php?title=Broadband_Platform_v11.2.3&diff=5067 Broadband Platform v11.2.3 2012-05-09T18:11:39Z <p>Patrices: </p> <hr /> <div>[[File:Bbp.jpg|256px|thumb|right|Fig 1: Broadband Platform.]]<br /> <br /> The SCEC Broadband Platform is a software system which generates 0-10 Hz seismograms for historical and scenario earthquakes in California.<br /> <br /> == Overview == <br /> <br /> The goal of the SCEC Broadband Simulation Platform is to generate broadband (0-10 Hz) ground motions for earthquakes using deterministic low-frequency and stochastic high-frequency simulations. The SCEC Broadband Platform is a collaborative software development project involving SCEC researchers, graduate students, and the SCEC/CME software development group. SCEC scientific groups have contributed modules to the Broadband Platform including rupture generation, low-frequency deterministic seismogram synthesis, high-frequency stochastic seismogram synthesis, and non-linear site effects. 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.<br /> <br /> Users may calculate broadband seismograms for both historical earthquakes (validation events including Northridge, Loma Prieta, and Landers) and user-defined earthquakes. The platform produces a variety of data products, including broadband seismograms, rupture visualizations, and 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, and the Mojave. Users may select among various codebases for 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.<br /> <br /> 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. <br /> <br /> == Current Release ==<br /> <br /> The current official release of Broadband Platform is v11.2.3. This distribution was posted online on Wednesday, 09 May 2012. This is a &quot;bug-fix&quot; version of the platform that fixes a small number of bugs discovered in v11.2.2 since its release in October 2011. Details of the bugs fixes are provided in the release notes. No new features are introduced in this version of the platform. New 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.<br /> <br /> == Dependencies ==<br /> <br /> Broadband has the following dependencies:<br /> <br /> *[http://www.python.org/download/ Python 2.5+] with<br /> **[http://new.scipy.org/download.html NumPy]<br /> **[http://matplotlib.sourceforge.net/ matplotlib]<br /> *[http://software.intel.com/en-us/articles/non-commercial-software-download/ Intel compilers]<br /> A non-commercial copy of Intel c and FORTRAN compilers can be obtained by registering for a [http://software.intel.com/en-us/articles/non-commercial-software-development/ non-commercial account with Intel] and downloading the compilers from the Intel website.<br /> <br /> and the following optional dependencies for additional functionality:<br /> <br /> *[http://gmt.soest.hawaii.edu/ GMT] (for plotting)<br /> *Matlab with map toolbox (for certain platform modules)<br /> *[http://www.pygtk.org/downloads.html PyGTK] (for interactive plotting)<br /> <br /> == Documentation ==<br /> <br /> User Guide Wiki (includes installation instructions): <br /> *[[Broadband User Guide Current]]<br /> <br /> == Downloads ==<br /> <br /> To install and use the Broadband platform, you need both the source code and the data files. 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.<br /> <br /> Users that are upgrading from V11.2.0 to v11.2.3 should retrieve new versions of both the Broadband Platform data files and the Broadband Platform source code. Both were changed in this latest release.<br /> <br /> There are detailed installation instructions in the [[Broadband User Guide Current]].<br /> <br /> The main steps involved in installing the platform as a local installation on Linux machine include:<br /> # The software can be installed in an account on a Linux computer with at least 4GB of disk storage and C, Fortran, and Python software installed.<br /> # 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.<br /> # Download the following four files (source, source md5sum, data, data md5sum) into a directory and run the md5sum program to confirm you have an undamaged version of the distribution files.<br /> # Uncompress the distribution (tgz) files into data and source directory structures. The data files are nearly 3GB, but they are static and will not be modified and will not grow in size during use of the platform. The source directory is small, but this directory will increase as the platform is used, since the results produced by the platform will be stored here.<br /> # Configure your environment to add broadband platform directories into your python path and define other useful environment variables.<br /> # Build the executables by running the top level makefile.<br /> # Confirm the code is built correctly by running UnitTests.<br /> # Confirm the code runs correctly on your system by running AcceptanceTests.<br /> # Use the platform for research purposes.<br /> <br /> == Current Broadband Platform Release == <br /> <br /> The current SCEC Broadband platform release is v11.2.3. Links to the source code and data distributions are listed in the table below:<br /> <br /> {| class=&quot;wikitable&quot; border=&quot;1&quot; cellpadding=&quot;5&quot; cellspacing=&quot;0&quot;<br /> |-<br /> ! rowspan=&quot;2&quot;| Version<br /> ! rowspan=&quot;2&quot;| Release Date<br /> ! colspan=&quot;2&quot;| Files<br /> ! rowspan=&quot;2&quot;| User Guide<br /> |-<br /> ! Source Code<br /> ! Data<br /> |-<br /> ! scope=&quot;row&quot; rowspan=&quot;1&quot; | 11.2.3<br /> | 05/09/2012<br /> | [http://hypocenter.usc.edu/research/broadband/11.2.3/bbp_dist_v11.2.3.tgz bbp_dist_v11.2.3.tgz]<br /> [http://hypocenter.usc.edu/research/broadband/11.2.3/bbp_dist_v11.2.3.tgz.md5 bbp_dist_v11.2.3.tgz.md5]<br /> |[http://hypocenter.usc.edu/research/broadband/11.2.3/bbp_data_v11.2.3.tgz bbp_data_v11.2.3.tgz]<br /> [http://hypocenter.usc.edu/research/broadband/11.2.3/bbp_data_v11.2.3.tgz.md5 bbp_data_v11.2.3.tgz.md5]<br /> |[[Broadband User Guide v11.2.3]]<br /> [[Broadband v11.2.3 Release Notes]]<br /> |}<br /> <br /> == Optional Broadband Platform Patches ==<br /> <br /> There are currently no optional patches available for 11.2.3.<br /> <br /> == Previous Broadband Platform Release ==<br /> <br /> 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.<br /> <br /> {| class=&quot;wikitable&quot; border=&quot;1&quot; cellpadding=&quot;5&quot; cellspacing=&quot;0&quot;<br /> |-<br /> ! rowspan=&quot;2&quot;| Version<br /> ! rowspan=&quot;2&quot;| Release Date<br /> ! colspan=&quot;3&quot;| Files<br /> ! rowspan=&quot;2&quot;| User Guide<br /> |-<br /> ! Source Code<br /> ! Data<br /> ! Patches<br /> |-<br /> ! scope=&quot;row&quot; rowspan=&quot;1&quot; | 11.2.2<br /> | 10/21/2011<br /> | [http://hypocenter.usc.edu/research/broadband/11.2.1/bbp_dist_v11.2.2.tgz bbp_dist_v11.2.2.tgz]<br /> [http://hypocenter.usc.edu/research/broadband/11.2.1/bbp_dist_v11.2.2.tgz.md5 bbp_dist_v11.2.2.tgz.md5]<br /> |[http://hypocenter.usc.edu/research/broadband/11.2.1/bbp_data_v11.2.2.tgz bbp_data_v11.2.2.tgz]<br /> [http://hypocenter.usc.edu/research/broadband/11.2.1/bbp_data_v11.2.2.tgz.md5 bbp_data_v11.2.2.tgz.md5]<br /> |[http://hypocenter.usc.edu/research/broadband/11.2.2_patch/bbp_patch_v11.2.2.1.tgz bbp_patch_v11.2.2.1.tgz]<br /> [http://hypocenter.usc.edu/research/broadband/11.2.2_patch/bbp_patch_v11.2.2.2.tgz bbp_patch_v11.2.2.2.tgz]<br /> |[[Broadband User Guide v11.2.2]]<br /> [[Broadband v11.2.2 Release Notes]]<br /> |-<br /> ! scope=&quot;row&quot; rowspan=&quot;1&quot; | 11.2.1<br /> | 09/29/2011<br /> | [http://hypocenter.usc.edu/research/broadband/11.2.1/bbp_dist_v11.2.1.tgz bbp_dist_v11.2.1.tgz]<br /> [http://hypocenter.usc.edu/research/broadband/11.2.1/bbp_dist_v11.2.1.tgz.md5 bbp_dist_v11.2.1.tgz.md5]<br /> |[http://hypocenter.usc.edu/research/broadband/11.2.1/bbp_data_v11.2.1.tgz bbp_data_v11.2.1.tgz]<br /> [http://hypocenter.usc.edu/research/broadband/11.2.1/bbp_data_v11.2.1.tgz.md5 bbp_data_v11.2.1.tgz.md5]<br /> |<br /> |[[Broadband User Guide v11.2.1]]<br /> [[Broadband v11.2.1 Release Notes]]<br /> |-<br /> ! scope=&quot;row&quot; rowspan=&quot;1&quot; | 11.2.0<br /> | 02/18/2011<br /> | [http://hypocenter.usc.edu/research/broadband/11.2.0/bbp_dist_v11.2.0.tgz bbp_dist_v11.2.0.tgz]<br /> [http://hypocenter.usc.edu/research/broadband/11.2.0/bbp_dist_v11.2.0.tgz.md5 bbp_dist_v11.2.0.tgz.md5]<br /> |[http://hypocenter.usc.edu/research/broadband/11.2.0/bbp_data_v11.2.0.tgz bbp_data_v11.2.0.tgz]<br /> [http://hypocenter.usc.edu/research/broadband/11.2.0/bbp_data_v11.2.0.tgz.md5 bbp_data_v11.2.0.tgz.md5]<br /> |<br /> |[[Broadband User Guide v11.2]] <br /> |}<br /> <br /> == Supporting Materials ==<br /> *[http://hypocenter.usc.edu/research/broadband/bbp_ssa2011-v1.pptx Broadband Platform Presentation - SSA 2011 - Robert Graves (5MB pptx file)]<br /> *[http://hypocenter.usc.edu/research/broadband/documents/Broadband_AGU_poster.pdf Broadband poster from AGU 2010 (PDF, 882 KB)]<br /> *[http://hypocenter.usc.edu/research/broadband/documents/Broadband_overview.ppt Broadband overview talk from SC10 (PPT, 3.7 MB)] <br /> *[http://hypocenter.usc.edu/research/broadband/documents/Broadband_module_schematics.pptx Technical diagrams of Broadband module relationships (PPTX, 16 KB)]<br /> <br /> == Development version ==<br /> <br /> If you're interested in working with the latest development version of the platform, you can check it out from<br /> svn co https://source.usc.edu/svn/broadband/trunk<br /> <br /> Details about working with the development version are provided in the User Guide.<br /> <br /> The next version of Broadband, v 11.7, is expected to be released in Q4 of 2011. Additional details about this version is available here:<br /> *[[Broadband Development Version]]<br /> *[[Broadband User Guide v11.7.0]]<br /> <br /> == Help ==<br /> <br /> For assistance with the Broadband Platform, you may<br /> * Email software @ scec.org with specific questions<br /> * Browse and submit new trouble tickets, or feature requests, at [http://northridge.usc.edu/trac/broadband Broadband Trac site]. SCEC user login is required to submit trouble tickets this way.<br /> <br /> == License ==<br /> <br /> SCEC Broadband Platform software distributions are released under an Apache 2.0 open-source license as described here [[Broadband License]].<br /> <br /> == Changes in Broadband Platform v11.2.3 ==<br /> <br /> 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.<br /> <br /> * Trac # 30 Change tolerance depending on acceptance test combo<br /> * Trac # 69 UCSB high and low frequency modules don't work for Loma Prieta validation<br /> * Trac # 70 UCSB src/ucsb/Converter/utlFault.h srf name buffer length too short<br /> * Trac # 71 Allow tolerance checks to be disabled in unit/acceptance tests<br /> * Trac # 72 run_bbp_2G.py option file parsing exception when selecting a file among two or more choices<br /> * Trac # 74 Minor bug in a routine that is used for geographic conversions in the URS simulations on the BB platform<br /> * Trac # 75 Update Green's function data file with fixes and new datasets<br /> * Trac # 76 Change DEFAULT_KAPPA from 0.02 to 0.01 in ./comps/stas2files.py<br /> * Trac # 77 Remove station &quot;olem&quot; vs30 value from from UCSB Loma Prieta stations.vs30 in 11.7.0/trunk data sets<br /> * Trac # 78 Updated geobb_srf.py to use URS ll2xy coordinate conversion routines on trunk<br /> <br /> 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.<br /> <br /> * Trac # 56 Convert BBP Matlab scripts to Python<br /> * Trac # 67 Rename the cleanup.py so that people do not run it accidentally<br /> * Trac # 68 Build Broadband with latest (2011) Intel and GNU compilers<br /> <br /> 11.2.1 - September 2011 - Bug-fix release<br /> List of Trac items fixed in this release: <br /> * Trac # 41 - Add License file (EULA) to Broadband distribution.<br /> * Trac # 42 - Add a file manifest to the distribution archives.<br /> * Trac # 46 - Remove Hardcoded Green_Bank.inf entries.<br /> * Trac # 47 - Syn1d Module fails with IO error due to missing file.<br /> * Trac # 54 - plot_SRF.csh fails with &quot;Newline in variable name&quot;.<br /> * Trac # 61 - Provide an option to remove temporary folders at end of Broadband simulation run.<br /> * Trac # 62 - Add a warning and user prompt to comps/cleanup.py script.<br /> * Trac # 63 - Acceptance resume.txt should not be created in ref_data/accept_inputs.<br /> * Trac # 64 - Simulations with URS HF module fail with IOError and segmentation faults.<br /> * Trac # 65 - Add the XML file generated during a Broadband simulation to the output directory as metadata. <br /> <br /> 11.2.0 - February 2011 - Initial release.<br /> <br /> == Collaborators ==<br /> <br /> *[http://www.erdw.ethz.ch/index_EN ETH Zurich - Swiss Federal Institute of Technology Zurich]<br /> *[http://www.geology.sdsu.edu/ San Diego State University Dept of Geological Sciences]<br /> *[http://www.geol.ucsb.edu/ U.C. Santa Barbara Dept of Earth Sciences]<br /> *[http://www.crustal.ucsb.edu/ UCSB Institute for Crustal Studies]<br /> *[http://www.urscorp.com/ URS Corporation]<br /> *[http://www.scec.org SCEC]<br /> *[http://scec.usc.edu/scecpedia SCEC/CME Project]<br /> <br /> == See Also ==<br /> *[[Broadband Platform 2007]]<br /> *[http://scec.usc.edu/scecpedia/software SCEC Software Downloads]<br /> *[http://scec.usc.edu/scecpedia SCEC Wiki Main]<br /> *[http://www.scec.org SCEC Home Page]<br /> *[[Broadband User Guide Current]]<br /> *[[Broadband User Guide Development]]<br /> *[[Broadband Server]]<br /> *[[Broadband Hanging Wall Simulation]]<br /> *[[Broadband Development]]<br /> *[[Broadband Platform Installation Guide Current]]<br /> *[[Broadband Platform User Guide Current]]<br /> <br /> ==References==<br /> <br /> #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. [http://hypocenter.usc.edu/research/broadband/documents/Graves_Pitarka_2010.pdf link]<br /> #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. [http://hypocenter.usc.edu/research/broadband/documents/Mai_Imperatori_Olsen_2010.pdf link]<br /> #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. [http://hypocenter.usc.edu/research/broadband/documents/Schmedes_Archuleta_Lavallee_2010.pdf link]</div> Patrices https://strike.scec.org/scecwiki/index.php?title=Broadband_Platform_v11.2.3&diff=5066 Broadband Platform v11.2.3 2012-05-09T18:11:01Z <p>Patrices: </p> <hr /> <div>[[File:Bbp.jpg|256px|thumb|right|Fig 1: Broadband Platform.]]<br /> <br /> The SCEC Broadband Platform is a software system which generates 0-10 Hz seismograms for historical and scenario earthquakes in California.<br /> <br /> == Overview == <br /> <br /> The goal of the SCEC Broadband Simulation Platform is to generate broadband (0-10 Hz) ground motions for earthquakes using deterministic low-frequency and stochastic high-frequency simulations. The SCEC Broadband Platform is a collaborative software development project involving SCEC researchers, graduate students, and the SCEC/CME software development group. SCEC scientific groups have contributed modules to the Broadband Platform including rupture generation, low-frequency deterministic seismogram synthesis, high-frequency stochastic seismogram synthesis, and non-linear site effects. 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.<br /> <br /> Users may calculate broadband seismograms for both historical earthquakes (validation events including Northridge, Loma Prieta, and Landers) and user-defined earthquakes. The platform produces a variety of data products, including broadband seismograms, rupture visualizations, and 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, and the Mojave. Users may select among various codebases for 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.<br /> <br /> 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. <br /> <br /> == Current Release ==<br /> <br /> The current official release of Broadband Platform is v11.2.3. This distribution was posted online on Wednesday, 09 May 2012. This is a &quot;bug-fix&quot; version of the platform that fixes a small number of bugs discovered in v11.2.2 since its release in October 2011. Details of the bugs fixes are provided in the release notes. No new features are introduced in this version of the platform. New 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.<br /> <br /> == Dependencies ==<br /> <br /> Broadband has the following dependencies:<br /> <br /> *[http://www.python.org/download/ Python 2.5+] with<br /> **[http://new.scipy.org/download.html NumPy]<br /> **[http://matplotlib.sourceforge.net/ matplotlib]<br /> *[http://software.intel.com/en-us/articles/non-commercial-software-download/ Intel compilers]<br /> A non-commercial copy of Intel c and FORTRAN compilers can be obtained by registering for a [http://software.intel.com/en-us/articles/non-commercial-software-development/ non-commercial account with Intel] and downloading the compilers from the Intel website.<br /> <br /> and the following optional dependencies for additional functionality:<br /> <br /> *[http://gmt.soest.hawaii.edu/ GMT] (for plotting)<br /> *Matlab with map toolbox (for certain platform modules)<br /> *[http://www.pygtk.org/downloads.html PyGTK] (for interactive plotting)<br /> <br /> == Documentation ==<br /> <br /> User Guide Wiki (includes installation instructions): <br /> *[[Broadband User Guide Current]]<br /> <br /> == Downloads ==<br /> <br /> To install and use the Broadband platform, you need both the source code and the data files. 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.<br /> <br /> Users that are upgrading from V11.2.0 to v11.2.3 should retrieve new versions of both the Broadband Platform data files and the Broadband Platform source code. Both were changed in this latest release.<br /> <br /> There are detailed installation instructions in the [[Broadband User Guide Current]].<br /> <br /> The main steps involved in installing the platform as a local installation on Linux machine include:<br /> # The software can be installed in an account on a Linux computer with at least 4GB of disk storage and C, Fortran, and Python software installed.<br /> # 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.<br /> # Download the following four files (source, source md5sum, data, data md5sum) into a directory and run the md5sum program to confirm you have an undamaged version of the distribution files.<br /> # Uncompress the distribution (tgz) files into data and source directory structures. The data files are nearly 3GB, but they are static and will not be modified and will not grow in size during use of the platform. The source directory is small, but this directory will increase as the platform is used, since the results produced by the platform will be stored here.<br /> # Configure your environment to add broadband platform directories into your python path and define other useful environment variables.<br /> # Build the executables by running the top level makefile.<br /> # Confirm the code is built correctly by running UnitTests.<br /> # Confirm the code runs correctly on your system by running AcceptanceTests.<br /> # Use the platform for research purposes.<br /> <br /> == Current Broadband Platform Release == <br /> <br /> The current SCEC Broadband platform release is v11.2.3. Links to the source code and data distributions are listed in the table below:<br /> <br /> {| class=&quot;wikitable&quot; border=&quot;1&quot; cellpadding=&quot;5&quot; cellspacing=&quot;0&quot;<br /> |-<br /> ! rowspan=&quot;2&quot;| Version<br /> ! rowspan=&quot;2&quot;| Release Date<br /> ! colspan=&quot;2&quot;| Files<br /> ! rowspan=&quot;2&quot;| User Guide<br /> |-<br /> ! Source Code<br /> ! Data<br /> |-<br /> ! scope=&quot;row&quot; rowspan=&quot;1&quot; | 11.2.3<br /> | 05/09/2012<br /> | [http://hypocenter.usc.edu/research/broadband/11.2.3/bbp_dist_v11.2.3.tgz bbp_dist_v11.2.3.tgz]<br /> [http://hypocenter.usc.edu/research/broadband/11.2.3/bbp_dist_v11.2.3.tgz.md5 bbp_dist_v11.2.3.tgz.md5]<br /> |[http://hypocenter.usc.edu/research/broadband/11.2.3/bbp_data_v11.2.3.tgz bbp_data_v11.2.3.tgz]<br /> [http://hypocenter.usc.edu/research/broadband/11.2.3/bbp_data_v11.2.3.tgz.md5 bbp_data_v11.2.3.tgz.md5]<br /> |[[Broadband User Guide v11.2.3]]<br /> [[Broadband v11.2.3 Release Notes]]<br /> |}<br /> <br /> == Optional Broadband Platform Patches ==<br /> <br /> There are currently no optional patches available for 11.2.3.<br /> <br /> == Previous Broadband Platform Release ==<br /> <br /> 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.<br /> <br /> {| class=&quot;wikitable&quot; border=&quot;1&quot; cellpadding=&quot;5&quot; cellspacing=&quot;0&quot;<br /> |-<br /> ! rowspan=&quot;2&quot;| Version<br /> ! rowspan=&quot;2&quot;| Release Date<br /> ! colspan=&quot;3&quot;| Files<br /> ! rowspan=&quot;2&quot;| User Guide<br /> |-<br /> ! Source Code<br /> ! Data<br /> ! Patches<br /> |-<br /> ! scope=&quot;row&quot; rowspan=&quot;1&quot; | 11.2.2<br /> | 10/21/2011<br /> | [http://hypocenter.usc.edu/research/broadband/11.2.1/bbp_dist_v11.2.2.tgz bbp_dist_v11.2.2.tgz]<br /> [http://hypocenter.usc.edu/research/broadband/11.2.1/bbp_dist_v11.2.2.tgz.md5 bbp_dist_v11.2.2.tgz.md5]<br /> |[http://hypocenter.usc.edu/research/broadband/11.2.1/bbp_data_v11.2.2.tgz bbp_data_v11.2.2.tgz]<br /> [http://hypocenter.usc.edu/research/broadband/11.2.1/bbp_data_v11.2.2.tgz.md5 bbp_data_v11.2.2.tgz.md5]<br /> |[http://hypocenter.usc.edu/research/broadband/11.2.2_patch/bbp_patch_v11.2.2.1.tgz bbp_patch_v11.2.2.1.tgz]<br /> [http://hypocenter.usc.edu/research/broadband/11.2.2_patch/bbp_patch_v11.2.2.2.tgz bbp_patch_v11.2.2.2.tgz]<br /> |[[Broadband User Guide v11.2.2]]<br /> [[Broadband v11.2.2 Release Notes]]<br /> |-<br /> ! scope=&quot;row&quot; rowspan=&quot;1&quot; | 11.2.1<br /> | 09/29/2011<br /> | [http://hypocenter.usc.edu/research/broadband/11.2.1/bbp_dist_v11.2.1.tgz bbp_dist_v11.2.1.tgz]<br /> [http://hypocenter.usc.edu/research/broadband/11.2.1/bbp_dist_v11.2.1.tgz.md5 bbp_dist_v11.2.1.tgz.md5]<br /> |[http://hypocenter.usc.edu/research/broadband/11.2.1/bbp_data_v11.2.1.tgz bbp_data_v11.2.1.tgz]<br /> [http://hypocenter.usc.edu/research/broadband/11.2.1/bbp_data_v11.2.1.tgz.md5 bbp_data_v11.2.1.tgz.md5]<br /> |<br /> |[[Broadband User Guide v11.2.1]]<br /> [[Broadband v11.2.1 Release Notes]]<br /> |-<br /> ! scope=&quot;row&quot; rowspan=&quot;1&quot; | 11.2.0<br /> | 02/18/2011<br /> | [http://hypocenter.usc.edu/research/broadband/11.2.0/bbp_dist_v11.2.0.tgz bbp_dist_v11.2.0.tgz]<br /> [http://hypocenter.usc.edu/research/broadband/11.2.0/bbp_dist_v11.2.0.tgz.md5 bbp_dist_v11.2.0.tgz.md5]<br /> |[http://hypocenter.usc.edu/research/broadband/11.2.0/bbp_data_v11.2.0.tgz bbp_data_v11.2.0.tgz]<br /> [http://hypocenter.usc.edu/research/broadband/11.2.0/bbp_data_v11.2.0.tgz.md5 bbp_data_v11.2.0.tgz.md5]<br /> |<br /> |[[Broadband User Guide v11.2]] <br /> |}<br /> <br /> == Supporting Materials ==<br /> *[http://hypocenter.usc.edu/research/broadband/bbp_ssa2011-v1.pptx Broadband Platform Presentation - SSA 2011 - Robert Graves (5MB pptx file)]<br /> *[http://hypocenter.usc.edu/research/broadband/documents/Broadband_AGU_poster.pdf Broadband poster from AGU 2010 (PDF, 882 KB)]<br /> *[http://hypocenter.usc.edu/research/broadband/documents/Broadband_overview.ppt Broadband overview talk from SC10 (PPT, 3.7 MB)] <br /> *[http://hypocenter.usc.edu/research/broadband/documents/Broadband_module_schematics.pptx Technical diagrams of Broadband module relationships (PPTX, 16 KB)]<br /> <br /> == Development version ==<br /> <br /> If you're interested in working with the latest development version of the platform, you can check it out from<br /> svn co https://source.usc.edu/svn/broadband/trunk<br /> <br /> Details about working with the development version are provided in the User Guide.<br /> <br /> The next version of Broadband, v 11.7, is expected to be released in Q4 of 2011. Additional details about this version is available here:<br /> *[[Broadband Development Version]]<br /> *[[Broadband User Guide v11.7.0]]<br /> <br /> == Help ==<br /> <br /> For assistance with the Broadband Platform, you may<br /> * Email software @ scec.org with specific questions<br /> * Browse and submit new trouble tickets, or feature requests, at [http://northridge.usc.edu/trac/broadband Broadband Trac site]. SCEC user login is required to submit trouble tickets this way.<br /> <br /> == License ==<br /> <br /> SCEC Broadband Platform software distributions are released under an Apache 2.0 open-source license as described here [[Broadband License]].<br /> <br /> == Changes in Broadband Platform v11.2.3 ==<br /> <br /> 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.<br /> <br /> # Trac # 30 Change tolerance depending on acceptance test combo<br /> # Trac # 69 UCSB high and low frequency modules don't work for Loma Prieta validation<br /> # Trac # 70 UCSB src/ucsb/Converter/utlFault.h srf name buffer length too short<br /> # Trac # 71 Allow tolerance checks to be disabled in unit/acceptance tests<br /> # Trac # 72 run_bbp_2G.py option file parsing exception when selecting a file among two or more choices<br /> # Trac # 74 Minor bug in a routine that is used for geographic conversions in the URS simulations on the BB platform<br /> # Trac # 75 Update Green's function data file with fixes and new datasets<br /> # Trac # 76 Change DEFAULT_KAPPA from 0.02 to 0.01 in ./comps/stas2files.py<br /> # Trac # 77 Remove station &quot;olem&quot; vs30 value from from UCSB Loma Prieta stations.vs30 in 11.7.0/trunk data sets<br /> # Trac # 78 Updated geobb_srf.py to use URS ll2xy coordinate conversion routines on trunk<br /> <br /> 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.<br /> <br /> * Trac # 56 Convert BBP Matlab scripts to Python<br /> * Trac # 67 Rename the cleanup.py so that people do not run it accidentally<br /> * Trac # 68 Build Broadband with latest (2011) Intel and GNU compilers<br /> <br /> 11.2.1 - September 2011 - Bug-fix release<br /> List of Trac items fixed in this release: <br /> * Trac # 41 - Add License file (EULA) to Broadband distribution.<br /> * Trac # 42 - Add a file manifest to the distribution archives.<br /> * Trac # 46 - Remove Hardcoded Green_Bank.inf entries.<br /> * Trac # 47 - Syn1d Module fails with IO error due to missing file.<br /> * Trac # 54 - plot_SRF.csh fails with &quot;Newline in variable name&quot;.<br /> * Trac # 61 - Provide an option to remove temporary folders at end of Broadband simulation run.<br /> * Trac # 62 - Add a warning and user prompt to comps/cleanup.py script.<br /> * Trac # 63 - Acceptance resume.txt should not be created in ref_data/accept_inputs.<br /> * Trac # 64 - Simulations with URS HF module fail with IOError and segmentation faults.<br /> * Trac # 65 - Add the XML file generated during a Broadband simulation to the output directory as metadata. <br /> <br /> 11.2.0 - February 2011 - Initial release.<br /> <br /> == Collaborators ==<br /> <br /> *[http://www.erdw.ethz.ch/index_EN ETH Zurich - Swiss Federal Institute of Technology Zurich]<br /> *[http://www.geology.sdsu.edu/ San Diego State University Dept of Geological Sciences]<br /> *[http://www.geol.ucsb.edu/ U.C. Santa Barbara Dept of Earth Sciences]<br /> *[http://www.crustal.ucsb.edu/ UCSB Institute for Crustal Studies]<br /> *[http://www.urscorp.com/ URS Corporation]<br /> *[http://www.scec.org SCEC]<br /> *[http://scec.usc.edu/scecpedia SCEC/CME Project]<br /> <br /> == See Also ==<br /> *[[Broadband Platform 2007]]<br /> *[http://scec.usc.edu/scecpedia/software SCEC Software Downloads]<br /> *[http://scec.usc.edu/scecpedia SCEC Wiki Main]<br /> *[http://www.scec.org SCEC Home Page]<br /> *[[Broadband User Guide Current]]<br /> *[[Broadband User Guide Development]]<br /> *[[Broadband Server]]<br /> *[[Broadband Hanging Wall Simulation]]<br /> *[[Broadband Development]]<br /> *[[Broadband Platform Installation Guide Current]]<br /> *[[Broadband Platform User Guide Current]]<br /> <br /> ==References==<br /> <br /> #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. [http://hypocenter.usc.edu/research/broadband/documents/Graves_Pitarka_2010.pdf link]<br /> #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. [http://hypocenter.usc.edu/research/broadband/documents/Mai_Imperatori_Olsen_2010.pdf link]<br /> #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. [http://hypocenter.usc.edu/research/broadband/documents/Schmedes_Archuleta_Lavallee_2010.pdf link]</div> Patrices https://strike.scec.org/scecwiki/index.php?title=Broadband_Platform_v11.2.3&diff=5065 Broadband Platform v11.2.3 2012-05-09T17:52:17Z <p>Patrices: </p> <hr /> <div>[[File:Bbp.jpg|256px|thumb|right|Fig 1: Broadband Platform.]]<br /> <br /> The SCEC Broadband Platform is a software system which generates 0-10 Hz seismograms for historical and scenario earthquakes in California.<br /> <br /> == Overview == <br /> <br /> The goal of the SCEC Broadband Simulation Platform is to generate broadband (0-10 Hz) ground motions for earthquakes using deterministic low-frequency and stochastic high-frequency simulations. The SCEC Broadband Platform is a collaborative software development project involving SCEC researchers, graduate students, and the SCEC/CME software development group. SCEC scientific groups have contributed modules to the Broadband Platform including rupture generation, low-frequency deterministic seismogram synthesis, high-frequency stochastic seismogram synthesis, and non-linear site effects. 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.<br /> <br /> Users may calculate broadband seismograms for both historical earthquakes (validation events including Northridge, Loma Prieta, and Landers) and user-defined earthquakes. The platform produces a variety of data products, including broadband seismograms, rupture visualizations, and 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, and the Mojave. Users may select among various codebases for 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.<br /> <br /> 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. <br /> <br /> == Current Release ==<br /> <br /> The current official release of Broadband Platform is v11.2.3. This distribution was posted online on Wednesday, 09 May 2012. This is a &quot;bug-fix&quot; version of the platform that fixes a small number of bugs discovered in v11.2.2 since its release in October 2011. Details of the bugs fixes are provided in the release notes. No new features are introduced in this version of the platform. New 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.<br /> <br /> == Dependencies ==<br /> <br /> Broadband has the following dependencies:<br /> <br /> *[http://www.python.org/download/ Python 2.5+] with<br /> **[http://new.scipy.org/download.html NumPy]<br /> **[http://matplotlib.sourceforge.net/ matplotlib]<br /> *[http://software.intel.com/en-us/articles/non-commercial-software-download/ Intel compilers]<br /> A non-commercial copy of Intel c and FORTRAN compilers can be obtained by registering for a [http://software.intel.com/en-us/articles/non-commercial-software-development/ non-commercial account with Intel] and downloading the compilers from the Intel website.<br /> <br /> and the following optional dependencies for additional functionality:<br /> <br /> *[http://gmt.soest.hawaii.edu/ GMT] (for plotting)<br /> *Matlab with map toolbox (for certain platform modules)<br /> *[http://www.pygtk.org/downloads.html PyGTK] (for interactive plotting)<br /> <br /> == Documentation ==<br /> <br /> User Guide Wiki (includes installation instructions): <br /> *[[Broadband User Guide Current]]<br /> <br /> == Downloads ==<br /> <br /> To install and use the Broadband platform, you need both the source code and the data files. 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.<br /> <br /> Users that are upgrading from V11.2.0 to v11.2.3 should retrieve new versions of both the Broadband Platform data files and the Broadband Platform source code. Both were changed in this latest release.<br /> <br /> There are detailed installation instructions in the [[Broadband User Guide Current]].<br /> <br /> The main steps involved in installing the platform as a local installation on Linux machine include:<br /> # The software can be installed in an account on a Linux computer with at least 4GB of disk storage and C, Fortran, and Python software installed.<br /> # 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.<br /> # Download the following four files (source, source md5sum, data, data md5sum) into a directory and run the md5sum program to confirm you have an undamaged version of the distribution files.<br /> # Uncompress the distribution (tgz) files into data and source directory structures. The data files are nearly 3GB, but they are static and will not be modified and will not grow in size during use of the platform. The source directory is small, but this directory will increase as the platform is used, since the results produced by the platform will be stored here.<br /> # Configure your environment to add broadband platform directories into your python path and define other useful environment variables.<br /> # Build the executables by running the top level makefile.<br /> # Confirm the code is built correctly by running UnitTests.<br /> # Confirm the code runs correctly on your system by running AcceptanceTests.<br /> # Use the platform for research purposes.<br /> <br /> == Current Broadband Platform Release == <br /> <br /> The current SCEC Broadband platform release is v11.2.3. Links to the source code and data distributions are listed in the table below:<br /> <br /> {| class=&quot;wikitable&quot; border=&quot;1&quot; cellpadding=&quot;5&quot; cellspacing=&quot;0&quot;<br /> |-<br /> ! rowspan=&quot;2&quot;| Version<br /> ! rowspan=&quot;2&quot;| Release Date<br /> ! colspan=&quot;2&quot;| Files<br /> ! rowspan=&quot;2&quot;| User Guide<br /> |-<br /> ! Source Code<br /> ! Data<br /> |-<br /> ! scope=&quot;row&quot; rowspan=&quot;1&quot; | 11.2.3<br /> | 05/09/2012<br /> | [http://hypocenter.usc.edu/research/broadband/11.2.3/bbp_dist_v11.2.3.tgz bbp_dist_v11.2.3.tgz]<br /> [http://hypocenter.usc.edu/research/broadband/11.2.3/bbp_dist_v11.2.3.tgz.md5 bbp_dist_v11.2.3.tgz.md5]<br /> |[http://hypocenter.usc.edu/research/broadband/11.2.3/bbp_data_v11.2.3.tgz bbp_data_v11.2.3.tgz]<br /> [http://hypocenter.usc.edu/research/broadband/11.2.3/bbp_data_v11.2.3.tgz.md5 bbp_data_v11.2.3.tgz.md5]<br /> |[[Broadband User Guide v11.2.3]]<br /> [[Broadband v11.2.3 Release Notes]]<br /> |}<br /> <br /> <br /> == Optional Broadband Platform Patches ==<br /> <br /> There are currently no optional patches available for 11.2.3.<br /> <br /> == Previous Broadband Platform Release ==<br /> <br /> 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.<br /> <br /> {| class=&quot;wikitable&quot; border=&quot;1&quot; cellpadding=&quot;5&quot; cellspacing=&quot;0&quot;<br /> |-<br /> ! rowspan=&quot;2&quot;| Version<br /> ! rowspan=&quot;2&quot;| Release Date<br /> ! colspan=&quot;3&quot;| Files<br /> ! rowspan=&quot;2&quot;| User Guide<br /> |-<br /> ! Source Code<br /> ! Data<br /> ! Patches<br /> |-<br /> ! scope=&quot;row&quot; rowspan=&quot;1&quot; | 11.2.2<br /> | 10/21/2011<br /> | [http://hypocenter.usc.edu/research/broadband/11.2.1/bbp_dist_v11.2.2.tgz bbp_dist_v11.2.2.tgz]<br /> [http://hypocenter.usc.edu/research/broadband/11.2.1/bbp_dist_v11.2.2.tgz.md5 bbp_dist_v11.2.2.tgz.md5]<br /> |[http://hypocenter.usc.edu/research/broadband/11.2.1/bbp_data_v11.2.2.tgz bbp_data_v11.2.2.tgz]<br /> [http://hypocenter.usc.edu/research/broadband/11.2.1/bbp_data_v11.2.2.tgz.md5 bbp_data_v11.2.2.tgz.md5]<br /> |[http://hypocenter.usc.edu/research/broadband/11.2.2_patch/bbp_patch_v11.2.2.1.tgz bbp_patch_v11.2.2.1.tgz]<br /> [http://hypocenter.usc.edu/research/broadband/11.2.2_patch/bbp_patch_v11.2.2.2.tgz bbp_patch_v11.2.2.2.tgz]<br /> |[[Broadband User Guide v11.2.2]]<br /> [[Broadband v11.2.2 Release Notes]]<br /> |-<br /> ! scope=&quot;row&quot; rowspan=&quot;1&quot; | 11.2.1<br /> | 09/29/2011<br /> | [http://hypocenter.usc.edu/research/broadband/11.2.1/bbp_dist_v11.2.1.tgz bbp_dist_v11.2.1.tgz]<br /> [http://hypocenter.usc.edu/research/broadband/11.2.1/bbp_dist_v11.2.1.tgz.md5 bbp_dist_v11.2.1.tgz.md5]<br /> |[http://hypocenter.usc.edu/research/broadband/11.2.1/bbp_data_v11.2.1.tgz bbp_data_v11.2.1.tgz]<br /> [http://hypocenter.usc.edu/research/broadband/11.2.1/bbp_data_v11.2.1.tgz.md5 bbp_data_v11.2.1.tgz.md5]<br /> |<br /> |[[Broadband User Guide v11.2.1]]<br /> [[Broadband v11.2.1 Release Notes]]<br /> |-<br /> ! scope=&quot;row&quot; rowspan=&quot;1&quot; | 11.2.0<br /> | 02/18/2011<br /> | [http://hypocenter.usc.edu/research/broadband/11.2.0/bbp_dist_v11.2.0.tgz bbp_dist_v11.2.0.tgz]<br /> [http://hypocenter.usc.edu/research/broadband/11.2.0/bbp_dist_v11.2.0.tgz.md5 bbp_dist_v11.2.0.tgz.md5]<br /> |[http://hypocenter.usc.edu/research/broadband/11.2.0/bbp_data_v11.2.0.tgz bbp_data_v11.2.0.tgz]<br /> [http://hypocenter.usc.edu/research/broadband/11.2.0/bbp_data_v11.2.0.tgz.md5 bbp_data_v11.2.0.tgz.md5]<br /> |<br /> |[[Broadband User Guide v11.2]] <br /> |}<br /> <br /> == Supporting Materials ==<br /> *[http://hypocenter.usc.edu/research/broadband/bbp_ssa2011-v1.pptx Broadband Platform Presentation - SSA 2011 - Robert Graves (5MB pptx file)]<br /> *[http://hypocenter.usc.edu/research/broadband/documents/Broadband_AGU_poster.pdf Broadband poster from AGU 2010 (PDF, 882 KB)]<br /> *[http://hypocenter.usc.edu/research/broadband/documents/Broadband_overview.ppt Broadband overview talk from SC10 (PPT, 3.7 MB)] <br /> *[http://hypocenter.usc.edu/research/broadband/documents/Broadband_module_schematics.pptx Technical diagrams of Broadband module relationships (PPTX, 16 KB)]<br /> <br /> == Development version ==<br /> <br /> If you're interested in working with the latest development version of the platform, you can check it out from<br /> svn co https://source.usc.edu/svn/broadband/trunk<br /> <br /> Details about working with the development version are provided in the User Guide.<br /> <br /> The next version of Broadband, v 11.7, is expected to be released in Q4 of 2011. Additional details about this version is available here:<br /> *[[Broadband Development Version]]<br /> *[[Broadband User Guide v11.7.0]]<br /> <br /> == Help ==<br /> <br /> For assistance with the Broadband Platform, you may<br /> * Email software @ scec.org with specific questions<br /> * Browse and submit new trouble tickets, or feature requests, at [http://northridge.usc.edu/trac/broadband Broadband Trac site]. SCEC user login is required to submit trouble tickets this way.<br /> <br /> == License ==<br /> <br /> SCEC Broadband Platform software distributions are released under an Apache 2.0 open-source license as described here [[Broadband License]].<br /> <br /> == Changes in Broadband Platform v11.2.2 ==<br /> 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.<br /> <br /> * Trac # 56 Convert BBP Matlab scripts to Python<br /> * Trac # 67 Rename the cleanup.py so that people do not run it accidentally<br /> * Trac # 68 Build Broadband with latest (2011) Intel and GNU compilers<br /> <br /> 11.2.1 - September 2011 - Bug-fix release<br /> List of Trac items fixed in this release: <br /> * Trac # 41 - Add License file (EULA) to Broadband distribution.<br /> * Trac # 42 - Add a file manifest to the distribution archives.<br /> * Trac # 46 - Remove Hardcoded Green_Bank.inf entries.<br /> * Trac # 47 - Syn1d Module fails with IO error due to missing file.<br /> * Trac # 54 - plot_SRF.csh fails with &quot;Newline in variable name&quot;.<br /> * Trac # 61 - Provide an option to remove temporary folders at end of Broadband simulation run.<br /> * Trac # 62 - Add a warning and user prompt to comps/cleanup.py script.<br /> * Trac # 63 - Acceptance resume.txt should not be created in ref_data/accept_inputs.<br /> * Trac # 64 - Simulations with URS HF module fail with IOError and segmentation faults.<br /> * Trac # 65 - Add the XML file generated during a Broadband simulation to the output directory as metadata. <br /> <br /> 11.2.0 - February 2011 - Initial release.<br /> <br /> == Collaborators ==<br /> <br /> <br /> *[http://www.erdw.ethz.ch/index_EN ETH Zurich - Swiss Federal Institute of Technology Zurich]<br /> *[http://www.geology.sdsu.edu/ San Diego State University Dept of Geological Sciences]<br /> *[http://www.geol.ucsb.edu/ U.C. Santa Barbara Dept of Earth Sciences]<br /> *[http://www.crustal.ucsb.edu/ UCSB Institute for Crustal Studies]<br /> *[http://www.urscorp.com/ URS Corporation]<br /> *[http://www.scec.org SCEC]<br /> *[http://scec.usc.edu/scecpedia SCEC/CME Project]<br /> <br /> == See Also ==<br /> *[[Broadband Platform 2007]]<br /> *[http://scec.usc.edu/scecpedia/software SCEC Software Downloads]<br /> *[http://scec.usc.edu/scecpedia SCEC Wiki Main]<br /> *[http://www.scec.org SCEC Home Page]<br /> *[[Broadband User Guide Current]]<br /> *[[Broadband User Guide Development]]<br /> *[[Broadband Server]]<br /> *[[Broadband Hanging Wall Simulation]]<br /> *[[Broadband Development]]<br /> *[[Broadband Platform Installation Guide Current]]<br /> *[[Broadband Platform User Guide Current]]<br /> <br /> ==References==<br /> <br /> #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. [http://hypocenter.usc.edu/research/broadband/documents/Graves_Pitarka_2010.pdf link]<br /> #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. [http://hypocenter.usc.edu/research/broadband/documents/Mai_Imperatori_Olsen_2010.pdf link]<br /> #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. [http://hypocenter.usc.edu/research/broadband/documents/Schmedes_Archuleta_Lavallee_2010.pdf link]</div> Patrices https://strike.scec.org/scecwiki/index.php?title=Broadband_Platform_v11.2.3&diff=5064 Broadband Platform v11.2.3 2012-05-09T17:50:10Z <p>Patrices: </p> <hr /> <div>[[File:Bbp.jpg|256px|thumb|right|Fig 1: Broadband Platform.]]<br /> <br /> The SCEC Broadband Platform is a software system which generates 0-10 Hz seismograms for historical and scenario earthquakes in California.<br /> <br /> == Overview == <br /> <br /> The goal of the SCEC Broadband Simulation Platform is to generate broadband (0-10 Hz) ground motions for earthquakes using deterministic low-frequency and stochastic high-frequency simulations. The SCEC Broadband Platform is a collaborative software development project involving SCEC researchers, graduate students, and the SCEC/CME software development group. SCEC scientific groups have contributed modules to the Broadband Platform including rupture generation, low-frequency deterministic seismogram synthesis, high-frequency stochastic seismogram synthesis, and non-linear site effects. 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.<br /> <br /> Users may calculate broadband seismograms for both historical earthquakes (validation events including Northridge, Loma Prieta, and Landers) and user-defined earthquakes. The platform produces a variety of data products, including broadband seismograms, rupture visualizations, and 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, and the Mojave. Users may select among various codebases for 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.<br /> <br /> 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. <br /> <br /> == Current Release ==<br /> <br /> The current official release of Broadband Platform is v11.2.3. This distribution was posted online on Wednesday, 09 May 2012. This is a &quot;bug-fix&quot; version of the platform that fixes a small number of bugs discovered in v11.2.2 since its release in October 2011. Details of the bugs fixes are provided in the release notes. No new features are introduced in this version of the platform. New 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.<br /> <br /> == Dependencies ==<br /> <br /> Broadband has the following dependencies:<br /> <br /> *[http://www.python.org/download/ Python 2.5+] with<br /> **[http://new.scipy.org/download.html NumPy]<br /> **[http://matplotlib.sourceforge.net/ matplotlib]<br /> *[http://software.intel.com/en-us/articles/non-commercial-software-download/ Intel compilers]<br /> A non-commercial copy of Intel c and FORTRAN compilers can be obtained by registering for a [http://software.intel.com/en-us/articles/non-commercial-software-development/ non-commercial account with Intel] and downloading the compilers from the Intel website.<br /> <br /> and the following optional dependencies for additional functionality:<br /> <br /> *[http://gmt.soest.hawaii.edu/ GMT] (for plotting)<br /> *Matlab with map toolbox (for certain platform modules)<br /> *[http://www.pygtk.org/downloads.html PyGTK] (for interactive plotting)<br /> <br /> == Documentation ==<br /> <br /> User Guide Wiki (includes installation instructions): <br /> *[[Broadband User Guide Current]]<br /> <br /> == Downloads ==<br /> <br /> To install and use the Broadband platform, you need both the source code and the data files. 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.<br /> <br /> Users that are upgrading from V11.2.0 to v11.2.3 should retrieve new versions of both the Broadband Platform data files and the Broadband Platform source code. Both were changed in this latest release.<br /> <br /> There are detailed installation instructions in the [[Broadband User Guide Current]].<br /> <br /> The main steps involved in installing the platform as a local installation on Linux machine include:<br /> # The software can be installed in an account on a Linux computer with at least 4GB of disk storage and C, Fortran, and Python software installed.<br /> # 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.<br /> # Download the following four files (source, source md5sum, data, data md5sum) into a directory and run the md5sum program to confirm you have an undamaged version of the distribution files.<br /> # Uncompress the distribution (tgz) files into data and source directory structures. The data files are nearly 3GB, but they are static and will not be modified and will not grow in size during use of the platform. The source directory is small, but this directory will increase as the platform is used, since the results produced by the platform will be stored here.<br /> # Configure your environment to add broadband platform directories into your python path and define other useful environment variables.<br /> # Build the executables by running the top level makefile.<br /> # Confirm the code is built correctly by running UnitTests.<br /> # Confirm the code runs correctly on your system by running AcceptanceTests.<br /> # Use the platform for research purposes.<br /> <br /> == Current Broadband Platform Release == <br /> <br /> The current SCEC Broadband platform release is v11.2.3. Links to the source code and data distributions are listed in the table below:<br /> <br /> {| class=&quot;wikitable&quot; border=&quot;1&quot; cellpadding=&quot;5&quot; cellspacing=&quot;0&quot;<br /> |-<br /> ! rowspan=&quot;2&quot;| Version<br /> ! rowspan=&quot;2&quot;| Release Date<br /> ! colspan=&quot;2&quot;| Files<br /> ! rowspan=&quot;2&quot;| User Guide<br /> |-<br /> ! Source Code<br /> ! Data<br /> |-<br /> ! scope=&quot;row&quot; rowspan=&quot;1&quot; | 11.2.3<br /> | 05/09/2012<br /> | [http://hypocenter.usc.edu/research/broadband/11.2.3/bbp_dist_v11.2.3.tgz bbp_dist_v11.2.3.tgz]<br /> [http://hypocenter.usc.edu/research/broadband/11.2.3/bbp_dist_v11.2.3.tgz.md5 bbp_dist_v11.2.3.tgz.md5]<br /> |[http://hypocenter.usc.edu/research/broadband/11.2.3/bbp_data_v11.2.3.tgz bbp_data_v11.2.3.tgz]<br /> [http://hypocenter.usc.edu/research/broadband/11.2.3/bbp_data_v11.2.3.tgz.md5 bbp_data_v11.2.3.tgz.md5]<br /> |[[Broadband User Guide v11.2.3]]<br /> [[Broadband v11.2.3 Release Notes]]<br /> |}<br /> <br /> <br /> == Optional Broadband Platform Patches ==<br /> <br /> There are currently no optional patches available for 11.2.3.<br /> <br /> == Previous Broadband Platform Release ==<br /> <br /> 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.<br /> <br /> {| class=&quot;wikitable&quot; border=&quot;1&quot; cellpadding=&quot;5&quot; cellspacing=&quot;0&quot;<br /> |-<br /> ! rowspan=&quot;2&quot;| Version<br /> ! rowspan=&quot;2&quot;| Release Date<br /> ! colspan=&quot;3&quot;| Files<br /> ! rowspan=&quot;2&quot;| User Guide<br /> |-<br /> ! Source Code<br /> ! Data<br /> ! Patches<br /> |-<br /> ! scope=&quot;row&quot; rowspan=&quot;1&quot; | 11.2.2<br /> | 10/21/2011<br /> | [http://hypocenter.usc.edu/research/broadband/11.2.1/bbp_dist_v11.2.2.tgz bbp_dist_v11.2.2.tgz]<br /> [http://hypocenter.usc.edu/research/broadband/11.2.1/bbp_dist_v11.2.2.tgz.md5 bbp_dist_v11.2.2.tgz.md5]<br /> |[http://hypocenter.usc.edu/research/broadband/11.2.1/bbp_data_v11.2.2.tgz bbp_data_v11.2.2.tgz]<br /> [http://hypocenter.usc.edu/research/broadband/11.2.1/bbp_data_v11.2.2.tgz.md5 bbp_data_v11.2.2.tgz.md5]<br /> |[http://hypocenter.usc.edu/research/broadband/11.2.2_patch/bbp_patch_v11.2.2.1.tgz bbp_patch_v11.2.2.1.tgz]<br /> [http://hypocenter.usc.edu/research/broadband/11.2.2_patch/bbp_patch_v11.2.2.2.tgz bbp_patch_v11.2.2.2.tgz]<br /> |[[Broadband User Guide v11.2.1]]<br /> [[Broadband v11.2.1 Release Notes]]<br /> |-<br /> ! scope=&quot;row&quot; rowspan=&quot;1&quot; | 11.2.1<br /> | 09/29/2011<br /> | [http://hypocenter.usc.edu/research/broadband/11.2.1/bbp_dist_v11.2.1.tgz bbp_dist_v11.2.1.tgz]<br /> [http://hypocenter.usc.edu/research/broadband/11.2.1/bbp_dist_v11.2.1.tgz.md5 bbp_dist_v11.2.1.tgz.md5]<br /> |[http://hypocenter.usc.edu/research/broadband/11.2.1/bbp_data_v11.2.1.tgz bbp_data_v11.2.1.tgz]<br /> [http://hypocenter.usc.edu/research/broadband/11.2.1/bbp_data_v11.2.1.tgz.md5 bbp_data_v11.2.1.tgz.md5]<br /> |<br /> |[[Broadband User Guide v11.2.1]]<br /> [[Broadband v11.2.1 Release Notes]]<br /> |-<br /> ! scope=&quot;row&quot; rowspan=&quot;1&quot; | 11.2.0<br /> | 02/18/2011<br /> | [http://hypocenter.usc.edu/research/broadband/11.2.0/bbp_dist_v11.2.0.tgz bbp_dist_v11.2.0.tgz]<br /> [http://hypocenter.usc.edu/research/broadband/11.2.0/bbp_dist_v11.2.0.tgz.md5 bbp_dist_v11.2.0.tgz.md5]<br /> |[http://hypocenter.usc.edu/research/broadband/11.2.0/bbp_data_v11.2.0.tgz bbp_data_v11.2.0.tgz]<br /> [http://hypocenter.usc.edu/research/broadband/11.2.0/bbp_data_v11.2.0.tgz.md5 bbp_data_v11.2.0.tgz.md5]<br /> |<br /> |[[Broadband User Guide v11.2]] <br /> |}<br /> <br /> == Supporting Materials ==<br /> *[http://hypocenter.usc.edu/research/broadband/bbp_ssa2011-v1.pptx Broadband Platform Presentation - SSA 2011 - Robert Graves (5MB pptx file)]<br /> *[http://hypocenter.usc.edu/research/broadband/documents/Broadband_AGU_poster.pdf Broadband poster from AGU 2010 (PDF, 882 KB)]<br /> *[http://hypocenter.usc.edu/research/broadband/documents/Broadband_overview.ppt Broadband overview talk from SC10 (PPT, 3.7 MB)] <br /> *[http://hypocenter.usc.edu/research/broadband/documents/Broadband_module_schematics.pptx Technical diagrams of Broadband module relationships (PPTX, 16 KB)]<br /> <br /> == Development version ==<br /> <br /> If you're interested in working with the latest development version of the platform, you can check it out from<br /> svn co https://source.usc.edu/svn/broadband/trunk<br /> <br /> Details about working with the development version are provided in the User Guide.<br /> <br /> The next version of Broadband, v 11.7, is expected to be released in Q4 of 2011. Additional details about this version is available here:<br /> *[[Broadband Development Version]]<br /> *[[Broadband User Guide v11.7.0]]<br /> <br /> == Help ==<br /> <br /> For assistance with the Broadband Platform, you may<br /> * Email software @ scec.org with specific questions<br /> * Browse and submit new trouble tickets, or feature requests, at [http://northridge.usc.edu/trac/broadband Broadband Trac site]. SCEC user login is required to submit trouble tickets this way.<br /> <br /> == License ==<br /> <br /> SCEC Broadband Platform software distributions are released under an Apache 2.0 open-source license as described here [[Broadband License]].<br /> <br /> == Changes in Broadband Platform v11.2.2 ==<br /> 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.<br /> <br /> * Trac # 56 Convert BBP Matlab scripts to Python<br /> * Trac # 67 Rename the cleanup.py so that people do not run it accidentally<br /> * Trac # 68 Build Broadband with latest (2011) Intel and GNU compilers<br /> <br /> 11.2.1 - September 2011 - Bug-fix release<br /> List of Trac items fixed in this release: <br /> * Trac # 41 - Add License file (EULA) to Broadband distribution.<br /> * Trac # 42 - Add a file manifest to the distribution archives.<br /> * Trac # 46 - Remove Hardcoded Green_Bank.inf entries.<br /> * Trac # 47 - Syn1d Module fails with IO error due to missing file.<br /> * Trac # 54 - plot_SRF.csh fails with &quot;Newline in variable name&quot;.<br /> * Trac # 61 - Provide an option to remove temporary folders at end of Broadband simulation run.<br /> * Trac # 62 - Add a warning and user prompt to comps/cleanup.py script.<br /> * Trac # 63 - Acceptance resume.txt should not be created in ref_data/accept_inputs.<br /> * Trac # 64 - Simulations with URS HF module fail with IOError and segmentation faults.<br /> * Trac # 65 - Add the XML file generated during a Broadband simulation to the output directory as metadata. <br /> <br /> 11.2.0 - February 2011 - Initial release.<br /> <br /> == Collaborators ==<br /> <br /> <br /> *[http://www.erdw.ethz.ch/index_EN ETH Zurich - Swiss Federal Institute of Technology Zurich]<br /> *[http://www.geology.sdsu.edu/ San Diego State University Dept of Geological Sciences]<br /> *[http://www.geol.ucsb.edu/ U.C. Santa Barbara Dept of Earth Sciences]<br /> *[http://www.crustal.ucsb.edu/ UCSB Institute for Crustal Studies]<br /> *[http://www.urscorp.com/ URS Corporation]<br /> *[http://www.scec.org SCEC]<br /> *[http://scec.usc.edu/scecpedia SCEC/CME Project]<br /> <br /> == See Also ==<br /> *[[Broadband Platform 2007]]<br /> *[http://scec.usc.edu/scecpedia/software SCEC Software Downloads]<br /> *[http://scec.usc.edu/scecpedia SCEC Wiki Main]<br /> *[http://www.scec.org SCEC Home Page]<br /> *[[Broadband User Guide Current]]<br /> *[[Broadband User Guide Development]]<br /> *[[Broadband Server]]<br /> *[[Broadband Hanging Wall Simulation]]<br /> *[[Broadband Development]]<br /> *[[Broadband Platform Installation Guide Current]]<br /> *[[Broadband Platform User Guide Current]]<br /> <br /> ==References==<br /> <br /> #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. [http://hypocenter.usc.edu/research/broadband/documents/Graves_Pitarka_2010.pdf link]<br /> #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. [http://hypocenter.usc.edu/research/broadband/documents/Mai_Imperatori_Olsen_2010.pdf link]<br /> #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. [http://hypocenter.usc.edu/research/broadband/documents/Schmedes_Archuleta_Lavallee_2010.pdf link]</div> Patrices https://strike.scec.org/scecwiki/index.php?title=Broadband_User_Guide_v11.2.3&diff=5059 Broadband User Guide v11.2.3 2012-05-08T22:09:03Z <p>Patrices: </p> <hr /> <div>'''Version 11.2.3.'''<br /> <br /> If you find errors in this document or sections to be unclear, please either fix them yourself or contact software@scec.org.<br /> <br /> = Installing the Second-Generation Broadband Platform =<br /> Installing the Broadband Platform involves obtaining a copy of the code and building the required executables. You can either download the platform from the Broadband web site ([http://www.scec.org/research/broadband http://www.scec.org/research/broadband]) or check the code out of SCEC's Subversion repository. Most users should download the platform.<br /> <br /> == System Dependencies ==<br /> The current version of the Broadband Platform is designed to run on standard 64-bit Linux machines. Testing has been performed on SCEC's development servers running Fedora Core 10 (kernel version 2.6.27.41-170.2.117.fc10.x86_64). In this guide we outline how to install the platform into your own account on a Linux computer using the simplest approach.<br /> <br /> == Software Dependencies ==<br /> The Broadband Platform has certain software dependencies.<br /> <br /> Required:<br /> <br /> *Python v2.7 with<br /> **PyGTK<br /> **Matplotlib<br /> **Numpy<br /> **Pyproj<br /> <br /> *Intel compilers (64-bit) v12.0.4<br /> *GNU compilers (gcc, gfortran) v4.5.1<br /> *GNU Fortran 77 v3.4.6<br /> *GMT (Generic Mapping Toolkit)<br /> *ImageMagick<br /> <br /> == Setting Up Your Account ==<br /> For simplicity of installation, we recommend users use a bash shell for the Broadband Platform account. It is possible to get the platform running using other shell's, but we will focus on a bash shell installation. The user environment is a common source of problems since certain environment variables must be defined for the platform to work correctly.<br /> <br /> To check your account, make sure you can run basic commands like ''ls'' and ''cd'' before proceeding.<br /> <br /> == Downloading the Platform ==<br /> &lt;nowiki&gt;Download 4 files from the Broadband website, the code (bbp_dist_&lt;version&gt;.tgz), the data (bbp_data_&lt;version&gt;.tgz), and their checksum files (bbp_dist_&lt;version&gt;.tgz.md5 and bbp_data_&lt;version&gt;.tgz.md5). &lt;/nowiki&gt;The code file is about 100 MB, the data file about 3 GB. After you've downloaded the files to your local Linux system, the next step is to calculate the checksums yourself and compare them to the checksums you downloaded.<br /> <br /> First, verify that the ''md5sum'' command is in your path:<br /> <br /> $&gt; which md5sum<br /> <br /> You should get something like /usr/bin/md5sum. If you see the message 'no md5sum in...', contact your Linux system administrator and ask to have md5sum added to your path.<br /> <br /> Once you can run the ''md5sum'' command, run:<br /> <br /> $&gt; md5sum -c bbp_dist_&lt;version&gt;.tgz.md5<br /> $&gt; md5sum -c bbp_data_&lt;version&gt;.tgz.md5<br /> <br /> You should get the messages<br /> bbp_dist_&lt;version&gt;.tgz.md5: OK<br /> bbp_data_&lt;version&gt;.tgz.md5: OK<br /> <br /> If you get FAILED instead, re-download the tgz files and try again. When it passes, that means the files were downloaded without error.<br /> <br /> Once both files have passed the checksum test, untar the files.<br /> <br /> $&gt; tar xzvf bbp_dist_&lt;version&gt;.tgz file<br /> $&gt; tar xzvf bbp_data_&lt;version&gt;.tgz file<br /> <br /> If multiple users are planning to use the platform on the same system, you only need one copy of the data files per machine. Each user will still need his or her own copy of the code files.<br /> <br /> Alternatively, if you would like access to the latest version of the platform and get frequent but less thoroughly tested improvements, you can check out the platform from SCEC's Subversion repository. Only advanced users should take this approach, outlined in detail in the [[#Advanced Users| Advanced Users section]].<br /> <br /> == User Account Setup ==<br /> <br /> The Broadband platform installation is divided into two parts (1) input Green Functions (GF) data directory (9.3Gb), and (2) BBP home directory (366Mb). <br /> <br /> First, the Green's function libraries are larger, but they are static. The broadband platform reads the data files, but does not change them. <br /> <br /> Second, the remainder of the broadband platform is organized in the BBP home directory. The BBP home directory has a specific directory structure that includes the source code for the scientific programs, the python scripts that link the scientific programs, simulation input directory, temporary and log file directories, and the output data directory where all the platform results are written.<br /> <br /> The BBP home directory will increase in size as you run the platform, because both output data and output log files are written to the home directory. Running the acceptance tests will produce nearly ( 10Gb) of input data (5.2Gb), output data (500Mb), temporary files (2.7Gb), and output log files (250Mb). Once these tests have passed much of this data can be removed. However, the BBP home directory should have at least 10Gb of disk space to insure the acceptance tests can be run when a particular broadband platform software distribution is first installed on a system.<br /> <br /> == Data Directory ==<br /> Input data files called Greens Functions are distributed with the platform. These files are generated using specific velocity structures, so they are often considered region specific. We have GF for three regions including near Loma Prieta, near Landers, and near Northridge.<br /> <br /> The data directory is static, and the data directories are read-only. A single copy can be installed in a shared disk, which can then be shared by multiple users.<br /> <br /> == Setting Environment Variables ==<br /> The BBP source codes and scripts are organized under the broadband platform home directory. The broadband platform home directory is specified in a couple of places during Broadband Platform installation. <br /> <br /> Internal to the Broadband platform software, all broadband platform files (except the Greens Function data files) are in sub-directories of the BBP home directory.<br /> <br /> == BBP Environment Variable ==<br /> We recommend setting both an alias and a environment variable to the BBP home directory. This will help avoid typing it many times.<br /> <br /> If you're running a Bash shell, add the following line to your .bash_profile with your favorite text editor:<br /> <br /> export BBP=/home/scec-00/kumar/bbp_2g<br /> <br /> If you're running a C-shell, add the following line to your .cshrc with your favorite text editor:<br /> <br /> setenv BBP /home/scec-00/kumar/bbp_2g<br /> <br /> * PYTHONPATH<br /> After you've obtained a copy of the project, you'll need to make sure the comps directory is on Python's path so Python can find all the project modules. If you're running a Bash shell, add the following line to your .bash_profile with your favorite text editor:<br /> <br /> export PYTHONPATH=$BBP/comps:$PYTHONPATH<br /> <br /> If you're running a C-shell, add the following line to your .cshrc with your favorite text editor:<br /> <br /> setenv PYTHONPATH $BBP/comps:$PYTHONPATH<br /> <br /> * PATH<br /> In order to successfully compile the project, you'll need to make sure the required compilers directories are in your PATH variable. Broadband requires Intel 64-bit compilers, icc and ifort and GNU Compilers, gcc, g77 and f77 to compile the scientific code.<br /> <br /> If you are planning to run Broadband on SCEC Development servers, make sure you have the following directories in your PATH:<br /> <br /> For Bash Shell (in .bash_profile)<br /> <br /> export PATH=/usr/usc/intel/composerxe-2011.4.191/bin/intel64:/usr/usc/intel/composerxe-2011.4.191/mpirt/bin/intel64:$PATH<br /> <br /> For C-shell (in .cshrc)<br /> <br /> setenv PATH /usr/usc/intel/composerxe-2011.4.191/bin/intel64:/usr/usc/intel/composerxe-2011.4.191/mpirt/bin/intel64:$PATH<br /> <br /> When running elements of the platform over ssh, be sure to enable ssh forwarding (with the -X or -Y options).<br /> <br /> After modifying your login script above, log out and log back into the machine so the changes are reflected in your environment.<br /> <br /> == Edit Install_cfg.py with Installation Directory Paths ==<br /> <br /> You need to tell the platform where it's installed by editing a single python file called &quot;install_cfg.py&quot;. Edit the file bbp_2g/comps/install_cfg.py with your favorite text editor, and edit the lines:<br /> <br /> self.A_INSTALL_ROOT = &lt;bbp_2g directory&gt;<br /> self.A_GF_DIR = &lt;bbp_2g_gf directory&gt;<br /> <br /> as one example:<br /> <br /> self.A_INSTALL_ROOT = /home/scec-00/kumar/bbp_2g<br /> self.A_GF_DIR = /home/scec-00/kumar/bbp_2g_gf<br /> <br /> with the paths on your system to the bbp_2g directory (the source) and the bbp_2g_gf directory (the data) that you unzipped. For example, it could be /home/scottcal/broadband_platform/bbp_2g and /home/scottcal/broadband_platform/bbp_2g_gf.<br /> <br /> Here is some information about these two directories that may be useful as you decide how, and where, to install these two parts of the Broadband Platform on your computer disk system. The data files, and therefore the &lt;bbp_2g_gf directory&gt; are nearly 3GB, but they are static and will not be modified and will not grow in size during use of the platform. The source directory is small to begin. However, this directory will increase as the platform is used, since the results produced by the platform will be stored here.<br /> <br /> == Directory Structure ==<br /> The platform consists of two top-level directories, bbp_2g and bbp_2g_gf. bbp_2g contains the source code, executables, scripts, tests, input, working, and output directories. bbp_2g_gf contains the Green's Functions, input files for the validation events, and other required input files for the various code bases. Note that indata, logs, outdata, tmpdata, and xml are created when the platform is first run, so they will be missing when you first install the platform.<br /> <br /> bbp_2g has the following directories:<br /> *checksums: Contains checksums for bbp_2g_gf files<br /> *comps: The Python scripts to run the platform<br /> *docs: Documentation for the platform<br /> *etc: Miscellaneous utility scripts<br /> *examples: Contains example input files<br /> *indata: An internal directory, used to stage input files<br /> *logs: Contains logs from BBP runs<br /> *outdata: Contains output files from a run<br /> *ref_data: Contains reference files for BBP tests<br /> *start: Put input files for an interactive run here<br /> *src: Source code for BBP modules<br /> *tests: Contains unit and acceptance tests<br /> *tmpdata: An internal directory, used during a run<br /> *xml: Contains XML files which describe simulations and can be used as input<br /> <br /> bbp_2g_gf has the following directories:<br /> *compare: Contains observed seismograms for validation events<br /> *plot: Data files for GMT plots<br /> *sdsu, ucsb, urs: Contains Green's functions, velocity files, and other required inputs for the codebases.<br /> <br /> In general, you will be interacting with the start directory for input files, comps to run the platform, tests to test the platform, and outdata to examine data products.<br /> <br /> === Adding aliases ===<br /> <br /> You may find it helpful to add aliases, so you can quickly and easily move to different broadband directories with a single command. We recommend creating aliases for the home, start, and outdata directories.<br /> <br /> If you are using the Bash shell, you can create aliases by adding the following lines to ~/.bash_profile:<br /> <br /> alias bbp= 'cd &lt;path to bbp_2g directory&gt;'<br /> alias start='cd &lt;path to bbp_2g directory&gt;/start'<br /> alias outdata='cd &lt;path to bbp_2g directory&gt;/outdata'<br /> <br /> If you're using a C shell, edit your ~/.cshrc and add:<br /> <br /> alias bbp cd &lt;path to bbp_2g directory&gt;<br /> alias start cd &lt;path to bbp_2g directory&gt;/start<br /> alias outdata cd &lt;path to bbp_2g directory&gt;/outdata<br /> <br /> Log out and log back in. You'll notice that now you can type the alias command as a shortcut to change directories:<br /> <br /> $&gt; pwd<br /> /home/scec-00/scottcal<br /> $&gt; start<br /> $&gt; pwd<br /> /home/scec-00/scottcal/bband/bbp_2g/start<br /> <br /> This can be a useful way to navigate around the broadband platform directories.<br /> <br /> == Building the Platform ==<br /> Once you have checked out the code, you need to build it. By default, every executable is compiled using the compiler recommended by the code developer. However, if you have limited compiler options or are building the codes on an untested system, you may need to specify non-standard alternative compilers, as described below.<br /> <br /> Before you can build the platform, you need to make sure that the Intel compilers are in your path. This is done automatically on broadband.usc.edu, but on other systems you can check by typing:<br /> <br /> $&gt;which icc<br /> <br /> If you get the message &quot;no icc in ...&quot;, then you'll need to add the Intel compilers to your path. Once the Intel compilers are in your path, you can make the code by cd-ing to the bbp_2g/src directory and typing make:<br /> <br /> $&gt; cd src<br /> $&gt; make<br /> <br /> It takes a minute or two to build the code. You may encounter build warnings; these are fine. However, if you get any build errors, this is a problem and should be investigated.<br /> <br /> By default, every executable is compiled using the compiler recommended by the code developer. Depending on the system, some compilers may not be available to you. You can override the C and Fortran compilers used by editing<br /> <br /> src/makefile<br /> <br /> Uncomment USER_C and set FC and CC to the compilers you wish. For example:<br /> <br /> Before:<br /> <br /> #USER_C=1<br /> FC=f77<br /> CC=gcc<br /> <br /> After (an example, you may choose different compilers):<br /> <br /> USER_C=1<br /> FC=gfortran<br /> CC=gcc<br /> <br /> Note that not all compiler combinations have been thoroughly tested. You may encounter build errors with untested compiler combinations. If you encounter any errors while building the platform, consult the Troubleshooting section at the end of this user guide for know issues and their solutions.<br /> <br /> Once the platform has been successfully built, you can move on to running the tests to verify that all components are working correctly.<br /> <br /> == Advanced Users ==<br /> Alternatively, if you would like access to the latest version of the platform, to get frequent but less thoroughly tested improvements, you can check out the platform from SCEC's Subversion version control repository on source.usc.edu. Only advanced users should follow this approach. If you are unsure, you should download the code as outlined in [[#Downloading the Platform|Downloading the Platform]] and skip this section.<br /> <br /> You may need to request access from the SCEC system administrator, John Yu ([mailto:johnyu@usc.edu johnyu@usc.edu]). Make sure you have subversion in your path before beginning.<br /> <br /> Once you have access, you'll need to decide if you want a stable tagged version, or the latest version in the repository. For a stable version, open a terminal window on the system of your choice and type:<br /> <br /> $&gt; svn checkout https://source.usc.edu/svn/broadband/tags/&lt;stable version&gt; bbp_2g<br /> <br /> For the latest version, type:<br /> <br /> $&gt; svn checkout https://source.usc.edu/svn/broadband/trunk bbp_2g<br /> <br /> This will check out the project to your local machine. It contains the source code, tests, and some example files. You also need to obtain a copy of the Broadband Platform data files, containing the Green's tensors. They are too large to be stored in version control. You can obtain a copy from SCEC software distribution server. If you are working on SCEC development server, you might be able to create a symbolic link to data folder. Please contact [[#User_Support|User Support]] to get a location of the data folder on the SCEC development server. If you are not working on SCEC development server, or don't have an SCEC Linux login account, you can get a archive (.tgz) file of the Green's functions from the same download site you obtained this guide.<br /> <br /> If you know where a read-accessible installation of the green functions data directories you can create a link to that location. This can save disk space in some cases.<br /> <br /> ln -s /home/scec-00/scottcal/bband/bbp_2g_gf &lt;path to your gf directory&gt;<br /> <br /> Periodically you should check for updates to the code. To do so, go to your bbp_2g directory and type<br /> <br /> $&gt; svn update<br /> <br /> This will pull down any code updates that have been made in the repository. After you update, make the code again (detailed in [[#Building the Platform|Building the Platform]]) so that any code changes are captured in the executables.<br /> <br /> == Running the Broadband Platform ==<br /> We recommend users initiate all Broadband Platform runs from the &quot;start&quot; directory. The start directory is a collection point for input files for a particular simulation.<br /> <br /> Assuming the user is starting at BBP home directory, the user should move to the start directory and then run the Checksum, Unit and Acceptance tests to confirm the Broadband Platform software installation is operating as expected.<br /> <br /> $&gt; cd start<br /> <br /> == Running Checksum, Unit, and Acceptance Tests ==<br /> The broadband platform contains three kinds of tests. The checksum tests verify that the data files were copied correctly and you have all the files that are expected. Unit tests run each module using a set of input files, and compare the results against known outputs. They verify that each module has been built and is working correctly. Acceptance tests verify that the modules are working correctly together. They test the platform end-to-end using different combinations with known inputs and compare the results. All the possible module combinations for both user-defined and validation events are tested as checks against integration errors.<br /> <br /> Begin with the checksum tests. Once they past, run the unit tests and finally the acceptance tests.<br /> <br /> == Running Checksum Tests ==<br /> To run the checksum tests, change to the checksums directory and run md5sum_check.py.<br /> <br /> From the BBP home directory:<br /> <br /> $&gt; cd checksums<br /> $&gt; ./md5sum_check.py<br /> <br /> It takes about 5 minutes to compute the checksums. If a checksum disagrees, that means that the contents of the datafile were not what was expected. Try reinstalling the data files and try again. If you continue to get a checksum error, contact support.<br /> <br /> Once the checksums agree, move on to the unit tests.<br /> <br /> == Running Unit Tests ==<br /> To run the unit tests, change to the tests directory and run UnitTests.py.<br /> <br /> From the BBP home directory:<br /> <br /> $&gt; cd tests<br /> $&gt; ./UnitTests.py<br /> <br /> The unit tests take about 15 minutes to run. When they're complete, the console will either print &quot;OK&quot; or how many tests failed. If a test has failed, first check that you have built the executables.You can rerun just the specific test that failed (test_&lt;module&gt;.py). If the test is still failing, also verify that you have the ref_data directory, since it contains the input and reference files. If you're looking for more information about the failure, you can consult the Unit Tests log file in bbp_2g/logs/unit_test.log . If you can't determine the reason for the failure, contact support.<br /> <br /> Once the unit tests all pass, proceed to the acceptance tests. If there are any failure or errors while running the unit tests, consult the Troubleshooting section at the end of this user guide for know issues and their solutions.<br /> <br /> == Running Acceptance Tests ==<br /> Make sure the unit tests pass before moving on to the acceptance tests. To run the acceptance tests, change to the tests directory (if you're not there already) and run AcceptTests.py. <br /> The acceptance tests take a long time to run, around 20 hours<br /> <br /> From the BBP home directory:<br /> <br /> $&gt; cd tests<br /> $&gt; ./AcceptTests.py &amp;&gt; accept.out &amp;<br /> <br /> Since the tests take so long to run (twenty hours), you should run them as a background process, and redirect their output to a log file, as shown in the command above.<br /> <br /> You can check the progress by tailing the log file.<br /> <br /> $&gt; tail accept.out<br /> <br /> When all the acceptance tests are completed, the AcceptTests.py script will either print &quot;OK&quot; or how many tests failed. <br /> <br /> Acceptance test failures indicate that the modules are not integrated correctly. Like with the unit tests, verify that you have the ref_data directory. If a certain acceptance test fails, you can get more information by consulting the acceptance test logs in bbp_2g/logs/acceptance_tests_logs/&lt;test that failed&gt;.log . If you can't determine the reason for the failure, contact [[support]].<br /> <br /> Since the acceptance tests can take a long time to run, you may wish to resume where you left off. This feature is supported automatically. If you do not wish to resume, delete the resume file in ref_data/accept_inputs/resume.txt. If there are any failure or errors while running the acceptance tests, consult the Troubleshooting section at the end of this user guide for know issues and their solutions.<br /> <br /> = Types of Broadband Platform Simulations =<br /> <br /> The platform supports two kinds of simulations, validation events and user-defined events. Validation simulations are performed using a historical event, and are directly compared to observed seismograms using goodness-of-fit. User-defined events are run using a rupture description provided by the user which may not necessarily be a historical earthquake.<br /> <br /> When you run a simulation, the platform assigns an ID to it. This ID can be used to track the simulation and locate the output data products.<br /> <br /> To supply input files to the platform, put them in the start directory. Extensions are important - the platform recognizes station lists (.stl), SRF files (.srf), and simple source descriptions (.src). If there are multiple files of a type, the platform will prompt the user to select one.<br /> <br /> To perform a simulation, a user selects between different required and optional modules. Below we present a summary of the various modules.<br /> <br /> == Modules ==<br /> The broadband platform consists of a series of modules. There are two main types of modules, science modules and utility modules. Science modules are those for which the platform has multiple implementations, provided by different coding research groups. Utility modules only have 1 implementation. A schematic of the available modules and their flow relationships is shown below:<br /> <br /> === Science Modules ===<br /> All simulations must include a low-frequency, high-frequency, and site response science module. Simulations may include an optional rupture generation science module. Users may select between the following different implementations of each of these modules:<br /> <br /> Rupture generation:URS, UCSB<br /> <br /> Low-frequency:URS, UCSB<br /> <br /> High-frequency:URS, UCSB, SDSU<br /> <br /> Site response:URS, UCSB, SDSU<br /> <br /> === Utility Modules ===<br /> A spectral response utility module is automatically run after the site response module. Additionally, users may select an optional goodness-of-fit utility module to run at the conclusion of the simulation. In the case of a user-defined event, users select a historical event or previously run simulation to use as the comparison for goodness-of-fit.<br /> <br /> == Platform Directory ==<br /> <br /> A broadband platform distribution is organized in a specific directory structure that separates the input data sets, the python scripts, the simulation configuration files, log files, and output data files.<br /> <br /> When running Broadband Platform simulations, standard procedure is to place the simulation input files in the start directory and invoke the Broadband platform scripts from there.<br /> <br /> From the BBP home directory:<br /> <br /> $&gt; cd start<br /> $&gt; run_bbp_2G.py<br /> <br /> Simulation output results will be written into the bbp_home/output<br /> <br /> == Validation Simulations ==<br /> To run a validation simulation, go to the comps directory and run run_bbp_2G.py. The platform will ask you a series of questions. Answer 'y' to &quot;Do you want to perform a validation run?&quot;<br /> <br /> From the BBP home directory:<br /> <br /> $&gt; cd start<br /> $&gt; run_bbp_2G.py<br /> Welcome to the SCEC Broadband Platform.<br /> Please select the modules you want to run.<br /> Do you want to perform a validation run (y/n)? y<br /> Do you want to validate with:<br /> Northridge (1)<br /> Loma Prieta (2)<br /> Landers (3)<br /> ?<br /> ...<br /> <br /> No input files are required by the user. However, you may wish to run with a reduced station list to speed up the computations. You can put your own station list into the start directory (the format is described in [[#Station File List|section 5.3]]). Note that any stations which do not have observed seismograms will not be included in the automatically generated goodness-of-fit comparison.<br /> <br /> In addition to the low-frequency modules which compute seismograms using 1D Green's Tensors, validation events can also be run using precomputed 3D seismograms to supply the low-frequency.<br /> <br /> == User-defined Simulations ==<br /> To run a user-defined simulation, two input files are required, a rupture description and a station list. The rupture description can either be in SRF format or a simplified source description (the format is described in [[#Simple source description|section 5.1]]). To run a user-defined simulation, run run_bbp_2G.py.<br /> <br /> From the BBP home directory:<br /> <br /> $&gt; cd start<br /> $&gt; run_bbp_2G.py<br /> Welcome to the SCEC Broadband Platform.<br /> Please select the modules you want to run.<br /> Do you want to perform a validation run (y/n)? y<br /> Do you want to run a rupture generator (y/n)? <br /> ...<br /> <br /> You may then choose if you want to run a rupture generator. This is necessary if you're supplying a simple rupture description. If you're supplying an SRF file, you can skip this. Next you can select from different module implementations. Finally, you have the option to run goodness-of-fit against either observed seismograms or another simulation.<br /> <br /> ...<br /> Do you want to run goodness of fit (y/n)? y<br /> What reference files would you like to compare to? Enter a simulation ID or a scenario name: &lt;comparison&gt;<br /> Enter a label to use for the comparison seismograms: &lt;label&gt;<br /> <br /> The label will be used in GoF plots to distinguish one set of results from the other.<br /> <br /> The user-defined events must be within one of the regions supported by the platform - Southern California, Northern California, or the Mojave. The platform will automatically select a region based on the event hypocenter. If the event falls outside of these regions, you'll get an error.<br /> <br /> == Logging ==<br /> During the run, log files will be produced in logs/&lt;simulation ID&gt;/&lt;simulation ID&gt;.&lt;module name&gt;.log. If the platform fails, this is a good place to look to determine the error. Additionally, any fatal errors will be recorded in fatal_error.log.<br /> <br /> Metadata capturing all the executable calls is located in tmpdata/&lt;simulation ID&gt;/metadata.txt for careful tracing of exactly what was called. Both the log files and metadata can be useful if troubleshooting an issue.<br /> <br /> == Data Products ==<br /> The platform produces a variety of data products. &lt;nowiki&gt;All data products are located in outdata/&lt;simulation ID&gt;. &lt;/nowiki&gt;On most Linux systems, you can show images using display:<br /> <br /> $&gt; display &lt;PNG file&gt;<br /> <br /> Make sure you have X11 forwarding enabled.<br /> <br /> === Station map ===<br /> To help visualize the stations in relationship to the fault, the platform produces a PNG file displaying station locations with red circles and the fault plane with a black line, on an image of California. You can find this file in outdata/&lt;simulation ID&gt;/station_map.png.<br /> <br /> === Seismograms ===<br /> When running the platform, you have the option to output velocity and acceleration seismograms, for each station. Plots of these files can be found in outdata/&lt;simulation ID&gt;/&lt;simulation ID&gt;.&lt;station&gt;_&lt;velocity or acceleration&gt;_seis.png.<br /> <br /> The raw seismogram data is available in outdata/&lt;simulation ID&gt;/&lt;simulation ID&gt;.&lt;station&gt;.vel.bbp (velocity) and outdata/&lt;simulation ID&gt;.&lt;station&gt;.acc.bbp (acceleration). Its format is described in [[#BBP seismograms|section 5.4]].<br /> <br /> To compare seismogram data, you can run comps/plotit.py with two seismograms. It will plot them both for comparison. From the comps directory, run:<br /> <br /> $&gt; plotit.py &lt;path to seismogram 1&gt; &lt;path to seismogram 2&gt;<br /> <br /> === Response spectra ===<br /> The respect code, run at the end of each simulation, calculates the response spectra for each station. The raw respect data is located at<br /> <br /> From the BBP home directory:<br /> <br /> outdata/&lt;simulation ID&gt;/&lt;simulation ID&gt;.&lt;station&gt;.rsp<br /> <br /> in the format described in [[#Response spectra|section 5.5]].<br /> <br /> === Goodness-of-fit ===<br /> If you run goodness-of-fit, several additional data products are produced. The goodness-of-fit comparison is performed by comparing the response spectra of a set of calculated seismograms to seismograms from another simulation or observed seismograms. For each station involved in the comparison, a plot comparing the response spectra can be found at outdata/&lt;simulation ID&gt;/&lt;comparison label&gt;_&lt;simulation ID&gt;_&lt;station&gt;_rsp.png. A plot showing the seismograms on top and bottom can be found at outdata/&lt;comparison label&gt;_&lt;simulation ID&gt;_&lt;station&gt;_overlay.png. The goodness-of-fit plot can be found at gof-&lt;comparison label&gt;-&lt;simulation ID&gt;_r0-&lt;cutoff distance&gt;.png.<br /> <br /> Note that at least 3 stations must be run for goodness-of-fit to be valid. If fewer than 3 stations are run, no goodness of fit calculation will be performed.<br /> <br /> === Rupture files ===<br /> When a user-defined event is simulated, the user has the option to run a rupture generator. This generator produces an SRF file, found in outdata/&lt;simulation ID&gt;/*.srf. This file can be put in the start directory and used in future runs. Additionally, the platform produces a plot of the cumulative slip on the fault surface, outdata/&lt;simulation ID&gt;/&lt;SRF prefix&gt;.png.<br /> <br /> = Platform Modes =<br /> The platform can be run in multiple modes. The default is interactive mode, in which the user is prompted to answer a series of questions. Once all the information has been gathered, the run begins.<br /> <br /> For a large number of runs, or if the user is repeating a specific run, this can be tedious. The platform provides two other ways to describe a run, with an option file or an XML description.<br /> <br /> An option file provides responses to all the questions that the platform poses. The format is described in [[#Option File|section 5.6]], but it's basically a text file, 1 entry per line, with support for comments. It can be fed to the platform using the -o option.<br /> <br /> The platform will also accept XML files containing a full description of a run. The schema for these files is given in [[#XML workflow description schema|section 5.7]]. These files are also produced by the platform after every simulation, and placed in xml/&lt;simulation ID&gt;.xml. So if you want to rerun a simulation, you can point the platform to the XML file from that simulation using the -x option. Note that a new simulation ID will be assigned to the run, so there is no risk of overwriting previous simulation results.<br /> <br /> = Available Options =<br /> To get a list of the current available options, run run_bbp_2G.py with the -h flag.<br /> <br /> $&gt; run_bbp_2G.py -h<br /> Usage: run_bbp_2G.py [options]<br /> Options:<br /> -h, --help Show this help message and exit<br /> -x XML_FILE, --xml-file=XML_FILE Run using XML description of workflow<br /> -s SIM_ID, --simID=SIM_ID Force a simID<br /> -o OPTFILE, --option-file=OPTFILE File containing responses to interactive platform prompts<br /> -v, --version Broadband platform version<br /> -c, --compact Compact output results. Remove temporary files for simulations that complete successfully.<br /> -g, --generate-xml Generates the XML description but does not run the platform<br /> -l LOG_FILE, --log=LOG_FILE Store all output in a file<br /> <br /> = Cleanup =<br /> After a while, you may find that your indata, tmpdata, outdata, and logs directories are getting cluttered with files from past runs. If you wish to delete these old files, you can use the clean_directories.sh script in the etc directory.<br /> <br /> From the BBP home directory:<br /> <br /> $&gt; cd etc<br /> $&gt; ./clean_directories &lt;days&gt;<br /> <br /> Any simulation ID directories in the indata, tmpdata, outdata, and logs directories which were last accessed &lt;days&gt; days or longer ago will be deleted. If you have a few directories you want to keep, either copy them somewhere else, or copy them to a directory name that's not all digits and they won't be deleted.<br /> <br /> = Examples =<br /> Below are some examples that you can try using the sample files in the examples directory. Make sure all the tests pass before you try this. You should be in the comps directory when you start these examples:<br /> <br /> From the BBP home directory:<br /> <br /> $&gt; cd comps<br /> <br /> == Sample Validation Run ==<br /> You don't need to move any files for this. Notice that 3D seismograms are a low-frequency option, since you're running a validation event.<br /> <br /> From the BBP home directory:<br /> <br /> $&gt; cd start<br /> $&gt; run_bbp_2G.py <br /> Welcome to the SCEC Broadband Platform.<br /> Please select the modules you want to run.<br /> Do you want to perform a validation run (y/n)? y<br /> Do you want to validate with:<br /> Northridge (1)<br /> Loma Prieta (2)<br /> Landers (3)<br /> ?1<br /> Do you want to<br /> run all validation stations (1)<br /> select a station list (2)<br /> ?1<br /> Choose a source of low frequency seismograms:<br /> URS module (1)<br /> URS 3D seismograms (2)<br /> UCSB module (3)<br /> SDSU module (4)<br /> SDSU 3D seismograms (5)<br /> ?2<br /> Choose a high frequency module:<br /> URS (1)<br /> UCSB (2)<br /> SDSU (3)<br /> ?1<br /> Choose a site response module:<br /> URS (1)<br /> UCSB (2)<br /> SDSU (3)<br /> ?1<br /> Do you want to plot velocity seismograms (y/n)? y<br /> Do you want to plot acceleration seismograms (y/n)? y<br /> <br /> This simulation takes about 10 minutes. Once it's complete the platform will tell you:<br /> <br /> You can find results in &lt;path to bbp_2g install&gt;/outdata/&lt;simulation ID&gt; .<br /> <br /> In that directory you will find:<br /> <br /> *Velocity seismograms (&lt;simulation ID&gt;.&lt;station&gt;.bbp)<br /> *Acceleration seismograms (&lt;simulation ID&gt;.&lt;station&gt;.acc.bbp)<br /> *Plots of velocity seismograms (&lt;simulation ID&gt;.&lt;station&gt;_velocity_seis.png)<br /> *Plots of acceleration seismograms (&lt;simulation ID&gt;.&lt;station&gt;_acceleration_seis.png)<br /> *Response spectra files (&lt;simulation ID&gt;.&lt;station&gt;.rsp)<br /> *Plots comparing simulated and observed seismograms (Northridge_&lt;simulation ID&gt;_&lt;station&gt;_overlay.png)<br /> *Plots comparing simulated and observed response spectra (Northridge_&lt;simulation ID&gt;_&lt;station&gt;_rsp.png)<br /> *Overall goodness-of-fit plots (gof-Northridge-&lt;simulation ID&gt;_r0-25.png)<br /> <br /> == Sample Validation run, custom stations ==<br /> If the validation runs aren't performed with 3D low-frequency, it can take a long time, up to 10 minutes per station. Sometimes you might want to run with a reduced station list so the simulation will run faster.<br /> <br /> Copy the files in example/valid_custom_stations into the start directory. Take a look at the format of the station file:<br /> <br /> $&gt; more valid_test_stat.stl <br /> #Required: lon, lat, station name, distance to fault plane, Vs30<br /> #Optional: low freq corner, high freq corner<br /> #Unused: station information<br /> #lon lat stationdist Vs30 LF corner HF corner station information<br /> -118.6417 34.5640 cast 20.47 450 0.120 23.0 CSMIP peer.berkeley.edu/nga<br /> -118.4180 34.0628 lacn 22.82 278 0.140 23.0 CSMIP peer.berkeley.edu/nga<br /> -118.8811 34.2886 moor 24.16 405 0.160 23.0 CSMIP peer.berkeley.edu/nga<br /> <br /> Now, run the platform, using a station list:<br /> <br /> From the BBP Home directory<br /> <br /> $&gt; cd start<br /> $&gt; run_bbp_2G.py <br /> Welcome to the SCEC Broadband Platform.<br /> Please select the modules you want to run.<br /> Do you want to perform a validation run (y/n)? y<br /> Do you want to validate with:<br /> Northridge (1)<br /> Loma Prieta (2)<br /> Landers (3)<br /> ?1<br /> Do you want to<br /> run all validation stations (1)<br /> select a station list (2)<br /> ?2<br /> <br /> If you have multiple station list files in your start directory, you may see the following prompt asking you to select one. If you only have one, the platform will select it automatically.<br /> <br /> Found multiple BBP station list files in the start directory. Please select one:<br /> nr_one_stat.stl (1)<br /> valid_test_stat.stl (2)<br /> ?2<br /> Choose a source of low frequency seismograms:<br /> URS module (1)<br /> URS 3D seismograms (2)<br /> UCSB module (3)<br /> SDSU module (4)<br /> SDSU 3D seismograms (5)<br /> ?3<br /> Choose a high frequency module:<br /> URS (1)<br /> UCSB (2)<br /> SDSU (3)<br /> ?2<br /> Choose a site response module:<br /> URS (1)<br /> UCSB (2)<br /> SDSU (3)<br /> ?2<br /> Do you want to plot velocity seismograms (y/n)? y<br /> Do you want to plot acceleration seismograms (y/n)? y<br /> <br /> Again, when the run completes in about 15 minutes you can find results in the output directory. You'll notice far fewer files, as only 3 stations were run instead of 133. The goodness-of-fit plots won't look very good - more stations are really needed to get an accurate plot.<br /> <br /> == Sample User-defined run with source description ==<br /> Next let's try running a user-defined event. Copy examples/user_rup_gen/nr_one_stat.stl and examples/user_rup_gen/user_eq.src to the start directory. user_eq.src is a simple source description. Its format is outlined in [[#XML workflow description schema|section 5.1]]. Since this is a user-defined event, precomputed 3D seismograms aren't a valid option.<br /> <br /> $&gt; run_bbp_2G.py <br /> Welcome to the SCEC Broadband Platform.<br /> Please select the modules you want to run.<br /> Do you want to perform a validation run (y/n)? n<br /> Do you want to run a rupture generator (y/n)? y<br /> Rupture generators:<br /> URS (1)<br /> UCSB (2)<br /> ?1<br /> Using region: Southern California<br /> Choose a low frequency module:<br /> URS (1)<br /> UCSB (2)<br /> ?2<br /> Found multiple BBP station list files in the start directory. Please select one:<br /> nr_one_stat.stl (1)<br /> valid_test_stat.stl (2)<br /> ?1<br /> Choose a high frequency module:<br /> URS (1)<br /> UCSB (2)<br /> SDSU (3)<br /> ?2<br /> Choose a site response module:<br /> URS (1)<br /> UCSB (2)<br /> SDSU (3)<br /> ?1<br /> Do you want to plot velocity seismograms (y/n)? y<br /> Do you want to plot acceleration seismograms (y/n)? y<br /> Do you want to run goodness of fit (y/n)? n<br /> <br /> Since this run only includes one station, it will run in about 5 minutes. In the output directory you'll notice there are no goodness-of-fit or files, since we didn't run goodness-of-fit. However, there is also a map file (station_map.png), showing the fault plane and the stations, and a plot of the rupture slip (user_eq.png). The SRF generated by the rupture generator is in user_eq.srf; this file could be used in future runs. The filenames of the rupture slip plot and SRF are taken from the rupture description filename.<br /> <br /> == Sample User-defined run with SRF file and goodness-of-fit ==<br /> Finally, try a run with an SRF file and run goodness-of-fit on the results. Copy in examples/user_no_rup_gen/ucsb_modSRF_0.srf and examples/user_no_rup_gen/nr_three_stat.stl<br /> <br /> $&gt; run_bbp_2G.py <br /> Welcome to the SCEC Broadband Platform.<br /> Please select the modules you want to run.<br /> Do you want to perform a validation run (y/n)? n<br /> Do you want to run a rupture generator (y/n)? n<br /> Using region: Southern California<br /> Choose a low frequency module:<br /> URS (1)<br /> UCSB (2)<br /> ?1<br /> Found multiple BBP station list files in the start directory. Please select one:<br /> nr_one_stat.stl (1)<br /> valid_test_stat.stl (2)<br /> nr_three_stat.stl (3)<br /> ?3<br /> Choose a high frequency module:<br /> URS (1)<br /> UCSB (2)<br /> SDSU (3)<br /> ?3<br /> Choose a site response module:<br /> URS (1)<br /> UCSB (2)<br /> SDSU (3)<br /> ?1<br /> Do you want to plot velocity seismograms (y/n)? y<br /> Do you want to plot acceleration seismograms (y/n)? y<br /> Do you want to run goodness of fit (y/n)? y<br /> What reference files would you like to compare to? Enter a simulation ID or a scenario name: Northridge<br /> Enter a label to use for the comparison seismograms: nr<br /> <br /> The reference files can either be a scenario event or a simulation ID previously run. The label is just for the figures when comparisons are plotted.<br /> <br /> This run will take about 15 minutes, and the results can be found in the appropriate outdir. Again, the goodness of fit measures will look poor due to the few stations involved in the comparison. If you had fewer than 3 stations, no goodness-of-fit plots would be produced. However, response spectra comparison plots will still be generated.<br /> <br /> = File Formats =<br /> This section offers descriptions of various file formats in the broadband platform.<br /> <br /> == Simple source description ==<br /> This is the format for the simple source description. It is not whitespace sensitive. The filename must end in .src for the platform to identify it as a source description.<br /> <br /> MAGNITUDE = &lt;magnitude&gt;<br /> FAULT_LENGTH = &lt;length of fault&gt;<br /> DLEN = &lt;DX, along length&gt;<br /> FAULT_WIDTH = &lt;down-dip fault width&gt;<br /> DWID = &lt;DY, along width&gt;<br /> DEPTH_TO_TOP = &lt;depth of fault below surface&gt;<br /> STRIKE = &lt;nowiki&gt;&lt;strike&gt;&lt;/nowiki&gt;<br /> RAKE = &lt;rake&gt;<br /> DIP = &lt;dip&gt;<br /> LAT_TOP_CENTER = &lt;latitude of top center point in fault plane&gt;<br /> LON_TOP_CENTER = &lt;longitude of top center point in fault plane&gt;<br /> HYPO_ALONG_STK = &lt;along strike location of hypocenter (0.0 = middle)&gt;<br /> HYPO_DOWN_DIP = &lt;down dip location of hypocenter (0.0 = top)&gt;<br /> DT = &lt;nowiki&gt;&lt;dt&gt;&lt;/nowiki&gt;<br /> SEED = &lt;random seed used in calculations&gt;<br /> CORNER_FREQ = &lt;corner frequency to use&gt;<br /> <br /> == SRF rupture description ==<br /> Details of the Standard Rupture Format (SRF) are given in more detail in the accompanying document. The general fault surface is represented by a distribution of point sources, and it can support one or more planes. The platform produces SRFs as output from rupture generators, but a user can also supply an SRF file as input for user-defined simulations. SRF filenames must end with the suffix .srf for the platform to correctly identify them.<br /> <br /> == Station File List ==<br /> The user may specify a list of stations, matching the following format:<br /> <br /> #optional<br /> %comment<br /> # lines<br /> &lt;nowiki&gt;&lt;lon&gt; &lt;lat&gt; &lt;stat name&gt; &lt;distance to fault trace&gt; &lt;Vs30&gt; &lt;LF corner&gt; &lt;HF corner&gt; &lt;stat info&gt;&lt;/nowiki&gt;<br /> ...<br /> <br /> The station list filename needs to end in .stl for the platform to recognize it as a station list.<br /> <br /> == BBP seismograms ==<br /> All intermediate and output seismograms are produced in a 4-column text format, whether velocity or acceleration.<br /> <br /> # optional<br /> % comment<br /> # lines<br /> &lt;nowiki&gt;&lt;timestamp&gt; &lt;North/South&gt; &lt;East/West&gt; &lt;Up/Down&gt;&lt;/nowiki&gt;<br /> ...<br /> <br /> Time is in seconds and motion is in cm/s (velocity) or cm/s/s (acceleration) unless otherwise specified in the header. Velocity filenames end in .vel.bbp; accelerations in .acc.bbp.<br /> <br /> == Response spectra ==<br /> The response spectra file is in 4-column text format.<br /> <br /> # optional<br /> % comment<br /> # lines<br /> &lt;nowiki&gt;&lt;period (sec)&gt; &lt;North/South&gt; &lt;East/West&gt; &lt;Up/Down&gt;&lt;/nowiki&gt;<br /> ...<br /> <br /> The platform samples response spectra at 112 periods, 0.01-20 sec and outputs pseudo spectral acceleration in units of g.<br /> <br /> == Option File ==<br /> Option files contain responses to the prompts in the platform. You can use them with the -o option to run_bbp_2G.py. The responses have to match the prompts exactly. For example, if you craft an option file assuming there is only one station list in the start directory (and therefore the user isn't prompted to select one) but then it is run with multiple station lists in the start directory, this will cause the run to abort. Option files are recommended to perform a series of runs with different inputs or different modules. If you have a run you perform regularly, it's better practice to run the platform with the -g option and the option file to produce an XML description, which are more complete descriptions of the workflow.<br /> <br /> #optional comments<br /> %using either symbol<br /> n #comments<br /> y % can go<br /> 1 # here<br /> ...<br /> <br /> Use with:<br /> <br /> $&gt; run_bbp_2G.py -o &lt;option file&gt;<br /> <br /> == XML workflow description schema ==<br /> Each time the platform is invoked, an XML file is produced describing the workflow, obeying the following schema:<br /> <br /> &lt;nowiki&gt;&lt;xs:schema xmlns:xs=&quot;http://www.w3.org/2001/XMLSchema&quot;&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:element name= &quot;BBP_Run_Specification&quot; minOccurs= &quot;1&quot; maxOccurs= &quot;1&quot;&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:attribute name=&quot;version&quot; type = &quot;xs:string&quot; use = &quot;required&quot; /&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:complexType&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:sequence&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:element name= &quot;Validation_Run&quot; minOccurs= &quot;0&quot; maxOccurs = &quot;1&quot;&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:attribute name= &quot;event&quot; type= &quot;xs:string&quot; use= &quot;required&quot; /&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:attribute name= &quot;input_station_file&quot; type = &quot;xs:string&quot; /&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:attribute name= &quot;subset&quot; type = &quot;xs:boolean&quot; use = &quot;required&quot; /&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;/xs:element&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:element name= &quot;BBP_Modules&quot;&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:complexType&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:sequence&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:element name = &quot;BBP_Module&quot; maxOccurs = &quot;unbounded&quot; &gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:complexType&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:sequence&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:element name= &quot;name&quot; type=&quot;xs:string&quot; /&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:element name= &quot;staged_files&quot; &gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:complexType&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:sequence&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:element name=&quot;file&quot; type=&quot;xs:string&quot; maxOccurs= &quot;unbounded&quot;/&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;/xs:sequence&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;/xs:complexType&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;/xs:element&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:element name= &quot;arguments&quot; &gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:complexType&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:sequence&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:element name=&quot;argument&quot; type=&quot;xs:string&quot; maxOccurs=&quot;unbounded&quot;&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:attribute name= &quot;type&quot; type= &quot;xs:string&quot; user= &quot;required&quot; /&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;/xs:element&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;/xs:sequence&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;/xs:complexType&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;/xs:element&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;/xs:sequence&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;/xs:complexType&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;/xs:element&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;/xs:sequence&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;/xs:complexType&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;/xs:element&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;/xs:sequence&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;/xs:complexType&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;/xs:element&gt;&lt;/nowiki&gt;<br /> <br /> These files are difficult to construct by hand, but can be generated using the -g flag when running run_bbp_2G.py.<br /> <br /> = User Support =<br /> If you run into bugs with the platform, you can open a trouble ticket at the [http://northridge.usc.edu/trac/broadband Broadband Trac site].<br /> <br /> Check to see if there has already been a ticket opened for the bug. If you are unable to get the platform to run, you can get direct user support by emailing [mailto:software@scec.org software@intensity.usc.edu].<br /> <br /> = Appendix A: Possible Module Permutations =<br /> == Validation Events ==<br /> <br /> {| class=&quot;wikitable&quot; | border=&quot;1&quot;<br /> | Permutation #<br /> | Low-frequency module<br /> | High-frequency module<br /> | Site response<br /> <br /> |-<br /> | &lt;center&gt;1&lt;/center&gt;<br /> | &lt;center&gt;URS 1D&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;2&lt;/center&gt;<br /> | &lt;center&gt;URS 1D&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;3&lt;/center&gt;<br /> | &lt;center&gt;URS 1D&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;4&lt;/center&gt;<br /> | &lt;center&gt;URS 1D&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;5&lt;/center&gt;<br /> | &lt;center&gt;URS 1D&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;6&lt;/center&gt;<br /> | &lt;center&gt;URS 1D&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;7&lt;/center&gt;<br /> | &lt;center&gt;URS 1D&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;8&lt;/center&gt;<br /> | &lt;center&gt;URS 1D&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;9&lt;/center&gt;<br /> | &lt;center&gt;URS 1D&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;10&lt;/center&gt;<br /> | &lt;center&gt;URS 3D precomputed&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;11&lt;/center&gt;<br /> | &lt;center&gt;URS 3D precomputed&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;12&lt;/center&gt;<br /> | &lt;center&gt;URS 3D precomputed&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;13&lt;/center&gt;<br /> | &lt;center&gt;URS 3D precomputed&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;14&lt;/center&gt;<br /> | &lt;center&gt;URS 3D precomputed&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;15&lt;/center&gt;<br /> | &lt;center&gt;URS 3D precomputed&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;16&lt;/center&gt;<br /> | &lt;center&gt;URS 3D precomputed&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;17&lt;/center&gt;<br /> | &lt;center&gt;URS 3D precomputed&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;18&lt;/center&gt;<br /> | &lt;center&gt;URS 3D precomputed&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;19&lt;/center&gt;<br /> | &lt;center&gt;UCSB 1D&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;20&lt;/center&gt;<br /> | &lt;center&gt;UCSB 1D&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;21&lt;/center&gt;<br /> | &lt;center&gt;UCSB 1D&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;22&lt;/center&gt;<br /> | &lt;center&gt;UCSB 1D&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;23&lt;/center&gt;<br /> | &lt;center&gt;UCSB 1D&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;24&lt;/center&gt;<br /> | &lt;center&gt;UCSB 1D&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;25&lt;/center&gt;<br /> | &lt;center&gt;UCSB 1D&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;26&lt;/center&gt;<br /> | &lt;center&gt;UCSB 1D&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;27&lt;/center&gt;<br /> | &lt;center&gt;UCSB 1D&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;28&lt;/center&gt;<br /> | &lt;center&gt;SDSU 1D&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;29&lt;/center&gt;<br /> | &lt;center&gt;SDSU 1D&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;30&lt;/center&gt;<br /> | &lt;center&gt;SDSU 1D&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;31&lt;/center&gt;<br /> | &lt;center&gt;SDSU 1D&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;32&lt;/center&gt;<br /> | &lt;center&gt;SDSU 1D&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;33&lt;/center&gt;<br /> | &lt;center&gt;SDSU 1D&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;34&lt;/center&gt;<br /> | &lt;center&gt;SDSU 1D&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;35&lt;/center&gt;<br /> | &lt;center&gt;SDSU 1D&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;36&lt;/center&gt;<br /> | &lt;center&gt;SDSU 1D&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;37&lt;/center&gt;<br /> | &lt;center&gt;SDSU 3D precomputed&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;38&lt;/center&gt;<br /> | &lt;center&gt;SDSU 3D precomputed&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;39&lt;/center&gt;<br /> | &lt;center&gt;SDSU 3D precomputed&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;40&lt;/center&gt;<br /> | &lt;center&gt;SDSU 3D precomputed&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;41&lt;/center&gt;<br /> | &lt;center&gt;SDSU 3D precomputed&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;42&lt;/center&gt;<br /> | &lt;center&gt;SDSU 3D precomputed&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;43&lt;/center&gt;<br /> | &lt;center&gt;SDSU 3D precomputed&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;44&lt;/center&gt;<br /> | &lt;center&gt;SDSU 3D precomputed&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;45&lt;/center&gt;<br /> | &lt;center&gt;SDSU 3D precomputed&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> |}<br /> <br /> ==User-Defined Events==<br /> <br /> {| class=&quot;wikitable&quot; | border=&quot;1&quot;<br /> | Permutation #<br /> | Rupture generator<br /> | Low-frequency<br /> | High-frequency<br /> | Site response<br /> <br /> |-<br /> | &lt;center&gt;1&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;2&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;3&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;4&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;5&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;6&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;7&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;8&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;9&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;10&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;11&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;12&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;13&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;14&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;15&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;16&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;17&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;18&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;19&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;20&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;21&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;22&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;23&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;24&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;25&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;26&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;27&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;28&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;29&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;30&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;31&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;32&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;33&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;34&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;35&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;36&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;37&lt;/center&gt;<br /> | &lt;center&gt;User-supplied SRF&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;38&lt;/center&gt;<br /> | &lt;center&gt;User-supplied SRF&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;39&lt;/center&gt;<br /> | &lt;center&gt;User-supplied SRF&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;40&lt;/center&gt;<br /> | &lt;center&gt;User-supplied SRF&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;41&lt;/center&gt;<br /> | &lt;center&gt;User-supplied SRF&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;42&lt;/center&gt;<br /> | &lt;center&gt;User-supplied SRF&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;43&lt;/center&gt;<br /> | &lt;center&gt;User-supplied SRF&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;44&lt;/center&gt;<br /> | &lt;center&gt;User-supplied SRF&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;45&lt;/center&gt;<br /> | &lt;center&gt;User-supplied SRF&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;46&lt;/center&gt;<br /> | &lt;center&gt;User-supplied SRF&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;47&lt;/center&gt;<br /> | &lt;center&gt;User-supplied SRF&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;48&lt;/center&gt;<br /> | &lt;center&gt;User-supplied SRF&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;49&lt;/center&gt;<br /> | &lt;center&gt;User-supplied SRF&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;50&lt;/center&gt;<br /> | &lt;center&gt;User-supplied SRF&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;51&lt;/center&gt;<br /> | &lt;center&gt;User-supplied SRF&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;52&lt;/center&gt;<br /> | &lt;center&gt;User-supplied SRF&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;53&lt;/center&gt;<br /> | &lt;center&gt;User-supplied SRF&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;54&lt;/center&gt;<br /> | &lt;center&gt;User-supplied SRF&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> |}<br /> <br /> = Appendix B: Troubleshooting =<br /> If you experience trouble building the platform or successfully running test and simulations, try the following solutions.<br /> <br /> == Build Errors ==<br /> <br /> The instruction for installing Broadband Platform are listed in Section 1: &quot;Installing the Second-Generation Broadband Platform&quot; of the User guide. If after following all steps listed in this section of the user guide the build fails, check if the failure is listed in this section and try the solution to fix the issue you are facing.<br /> <br /> === 64-bit Intel Compiler Issue ===<br /> If you try to compile with:<br /> &lt;pre&gt;<br /> % cd bbp_2g/src<br /> % make<br /> &lt;/pre&gt; <br /> <br /> and you get:<br /> &lt;pre&gt;<br /> ... <br /> make[2]: Entering directory `.../bbp_2g/src/ucsb/getInFile'<br /> icc -o getfaultGlobal getfaultGlobal.c<br /> ld: cannot find -lgcc_s_32<br /> make[2]: *** [getfaultGlobal] Error 1<br /> make[2]: Leaving directory `.../bbp_2g/src/ucsb/getInFile'<br /> make[1]: *** [all] Error 2<br /> make[1]: Leaving directory `.../bbp_2g/src/ucsb'<br /> make: *** [all] Error 2<br /> &lt;/pre&gt;<br /> <br /> '''Cause:''' The Broadband Platform requires Intel 64-bit compilers to build successfully. In this case the 32-bit Intel compilers are being invoked as they are being picked up from the PATH environment variable. The error is due to a missing GNU-GCC 32-bit compatibility pack that has not been installed on your system. This is not required when 64-bit Intel compilers are used.<br /> <br /> '''Solution:''' Ensure that the path Intel 64-bit compilers are listed in you PATH variable and being picked up by running 'which icc' and 'which ifort'. If you are trying to build the platform on SCEC development servers like Intensity, verify your path variable has:<br /> &lt;pre&gt;<br /> PATH=...:/usr/usc/intel/composerxe-2011.4.191/mpirt/bin/intel64:/usr/usc/intel/composerxe-2011.4.191/bin/intel64<br /> &lt;/pre&gt;<br /> <br /> === 32-bit Platform Issue ===<br /> <br /> On trying to build the platform, the build fails with the following message:<br /> &lt;pre&gt;<br /> $ make all<br /> cd urs; make -f makefile FC=gfortran CC=icc USER_C=1;<br /> make[1]: Entering directory `.../bbp_2g/src/urs'<br /> mkdir -p bin;<br /> cd getpar/src; make -f Makefile CC=icc FC=gfortran USER_C=1;<br /> make[2]: Entering directory `.../bbp_2g/src/urs/getpar/src'<br /> icc -O3 -DENVIRONMENT -c -o defpar.o defpar.c<br /> icc -O3 -DENVIRONMENT -c -o getpar.o getpar.c<br /> icc -O3 -DENVIRONMENT -c -o getarg.o getarg.c<br /> getarg.c(112): warning #303: explicit type is missing (&quot;int&quot; assumed)<br /> register i;<br /> ^ <br /> icc -O3 -DENVIRONMENT -c -o getlocation.o getlocation.c<br /> getlocation.c(9): warning #147: declaration is incompatible with &quot;__ssize_t={int} getline(char **restrict, size_t={unsigned int} *restrict, FILE *restrict)&quot; (declared at line 671 of &quot;/usr/include/stdio.h&quot;)<br /> static int getline(FILE *fd, char *line)<br /> <br /> ...<br /> ...<br /> ...<br /> <br /> make[2]: Entering directory `.../bbp_2g/src/sdsu/srcV1.4'<br /> icc -w -Wall -c ray3DJHfor.c<br /> gfortran module_bbtoolbox.f90 module_interface.f90 main_bbtoolbox.f90 coda.f90 composition.f90 convolution.f90 fourier.f90 error.f90 geometry.f90 interpolation.f90 io.f90 random.f90 scattering.f90 source.f90 ray3DJHfor.o -o BBtoolbox.exe<br /> ray3DJHfor.o: In function `raytracing_':<br /> ray3DJHfor.c:(.text+0x8cf): undefined reference to `__libm_sse2_log'<br /> ray3DJHfor.c:(.text+0x96b): undefined reference to `__libm_sse2_asin'<br /> ray3DJHfor.c:(.text+0x9cd): undefined reference to `__libm_sse2_asin'<br /> ray3DJHfor.c:(.text+0xa00): undefined reference to `__libm_sse2_tan'<br /> ray3DJHfor.c:(.text+0xa3d): undefined reference to `__libm_sse2_tan'<br /> ray3DJHfor.c:(.text+0xa52): undefined reference to `__libm_sse2_log'<br /> collect2: ld returned 1 exit status<br /> make[2]: *** [BBtoolbox.exe] Error 1<br /> make[2]: Leaving directory `.../bbp_2g/src/sdsu/srcV1.4'<br /> make[1]: *** [all] Error 2<br /> make[1]: Leaving directory `.../bbp_2g/src/sdsu'<br /> make: *** [all] Error 2<br /> &lt;/pre&gt;<br /> <br /> '''Cause:''' In this case the user tried to build Broadband on a 32-bit platform. Broadband code was designed to be run on 64-bit platform. Any attempt to build Broadband on a 32-bit platform will result in numerous warnings and the build will fail with error messages similar to ones listed above.<br /> <br /> '''Solution:''' Try building Broadband on a 64-bit platform will the all the dependencies listed in Section 1.1: &quot;System Dependencies&quot; and Section 1.2: &quot;Software Dependencies&quot;<br /> <br /> == Unit/Acceptance Test Failures and Errors ==<br /> <br /> Unit and Acceptance tests are provided to verify the Broadband platform and it's supporting modules built by the user are functioning as designed. Under certain circumstances, some of these test might fail. While some of these failure might indicate serious problems that will have to be addressed before the platform can used, it is acceptable to ignore some of the failures. This section lists some failures and their solutions.<br /> <br /> === ERROR: test_syn1d (test_syn1d.Test_syn1D) ===<br /> The Unit test for Syn1d module fails with the following message:<br /> &lt;pre&gt;<br /> ERROR: test_syn1d (test_syn1d.Test_syn1D)<br /> ----------------------------------------------------------------------<br /> Traceback (most recent call last):<br /> File &quot;.../bbp_2g/tests/test_syn1d.py&quot;, line 62, in test_syn1d<br /> synObj.run()<br /> File &quot;.../bbp_2g/comps/syn1D.py&quot;, line 236, in run<br /> shutil.copy2(a_tmpfile, expected_file)<br /> File &quot;/usr/lib/python2.6/shutil.py&quot;, line 99, in copy2<br /> copyfile(src, dst)<br /> File &quot;/usr/lib/python2.6/shutil.py&quot;, line 52, in copyfile<br /> fsrc = open(src, 'rb')<br /> IOError: [Errno 2] No such file or directory: '.../bbp_2g/tmpdata/3310632/s01.3comp'<br /> &lt;/pre&gt;<br /> <br /> '''Cause:''' Syn1d module requires the Green's Function file to run and the path to this file might be incorrect in 'bbp_2g_gf/ucsb/GreenBank/Northridge/GreenBank.inf' file.<br /> <br /> '''Solution:''' This issue can be fixed by correcting the paths listed in the GreenBank.inf files in the Green's Function directory. Here are step by step instructions to fix this issue:<br /> <br /> 1. Locate your Greens Functions directory: 'bbp_2g_gf'<br /> 2. Navigate to bbp_2g_gf/ucsb/GreenBank/Northridge folder.<br /> 3. Open Green_Bank.inf files with a text editor.<br /> 4. Locate the text &quot;The name of file to store Green Bank&quot;<br /> 5. Note the location of the Green Bank file under the line found in step 4, similar to &quot;/home/scec-00/scottcal/bband/bbp_2g_gf/ucsb/GreenBank/Northridge/Green_1d.soil&quot;.<br /> 6. Replace the path found in Step 5 with just the file name, in the case of Northridge it is &quot;Green_1d.soil&quot;<br /> 7. Save and close the Green_Bank.inf.<br /> 8. Navigate to bbp_2g_gf/ucsb/GreenBank/LomaPrieta folder and repeat steps 3-7. The name of the Green Bank file for LomaPrieta is &quot;Green_1d.LoPr&quot;.<br /> 9. Navigate to bbp_2g_gf/ucsb/GreenBank/Landers folder and repeat steps 3-7. The name of the Green Bank file for Landers is &quot;Green1D.Landers&quot;<br /> <br /> === ERROR: test_gensrf (test_genslip.Test_Genslip) ===<br /> The Unit test for Genslip module fails with the following message:<br /> &lt;pre&gt;<br /> ======================================================================<br /> ERROR: test_gensrf (test_genslip.Test_Genslip)<br /> ----------------------------------------------------------------------<br /> Traceback (most recent call last):<br /> File &quot;.../bbp_2g/tests/test_genslip.py&quot;, line 51, in test_gensrf<br /> gen.run()<br /> File &quot;.../bbp_2g/comps/genslip.py&quot;, line 153, in run<br /> ps.run()<br /> File &quot;.../bbp_2g/comps/plot_srf.py&quot;, line 52, in run<br /> shutil.copy2(&quot;%s/%s.ps.png&quot; % (a_tmpdir, self.r_srffile[0:self.r_srffile.find(&quot;.srf&quot;)]), &quot;%s/%s.png&quot; % (a_outdir, self.r_srffile[0:self.r_srffile.find(&quot;.srf&quot;)]))<br /> File &quot;/usr/lib/python2.6/shutil.py&quot;, line 99, in copy2<br /> copyfile(src, dst)<br /> File &quot;/usr/lib/python2.6/shutil.py&quot;, line 52, in copyfile<br /> fsrc = open(src, 'rb')<br /> IOError: [Errno 2] No such file or directory: '.../bbp_2g/tmpdata/3309008/3309008_test_eq.ps.png'<br /> &lt;/pre&gt;<br /> <br /> '''Cause:''' The Genslip module calls the Plot_SRF module to the plot the SRF file. Plot_SRF uses C-shell code to locate and use GMT package to plot the SRF file. This shell code might fail on some flavors of Linux with a message like &quot;Newline in variable name&quot; in the Plot_SRF log file.<br /> <br /> '''Solution:''' This issue can be fixed by editing the plot_SRF.csh file. Here are step by step instructions to fix this issue:<br /> <br /> 1. Locate shell script file: bbp_2g/src/plot/plot_SRF.csh<br /> 2. Open the file in your preferred text editor<br /> 3. Locate the line 'set FIND_GMT = $?'<br /> 4. Replace the line found in step 3 with 'set FIND_GMT = $status'<br /> 5. Locate the section of code that starts with the statement &quot;# FIND MAX. SLIP&quot;<br /> 6. Replace the following line in section found in step 5:<br /> &lt;pre&gt;<br /> set SMAX = `$XYZCODE calc_xy=$CALC_XY type=&quot;${TYPE}&quot; nseg=-1 &lt; $SLIPFILE.srf | \<br /> gawk -v m=$SMAX '{if($3&gt;m)m=$3;}END{printf &quot;%.0f\n&quot;,m;}'`<br /> <br /> with (collapse the statement to a single line by removing '\' at the end of first part of the statement):<br /> <br /> set SMAX = `$XYZCODE calc_xy=$CALC_XY type=&quot;${TYPE}&quot; nseg=-1 &lt; $SLIPFILE.srf | gawk -v m=$SMAX '{if($3&gt;m)m=$3;}END{printf &quot;%.0f\n&quot;,m;}'`<br /> &lt;/pre&gt;<br /> 7. Save the file and exit<br /> <br /> === ERROR: test_ucgen (test_ucrmg.Test_UCrmg) ===<br /> The Unit test for Ucrmg module fails with the following message:<br /> &lt;pre&gt;<br /> ======================================================================<br /> ERROR: test_ucgen (test_ucrmg.Test_UCrmg)<br /> ----------------------------------------------------------------------<br /> Traceback (most recent call last):<br /> File &quot;.../bbp_2g/tests/test_ucrmg.py&quot;, line 59, in test_ucgen<br /> ucObj.run()<br /> File &quot;.../bbp_2g/comps/ucrmg.py&quot;, line 161, in run<br /> ps.run()<br /> File &quot;.../bbp_2g/comps/plot_srf.py&quot;, line 52, in run<br /> shutil.copy2(&quot;%s/%s.ps.png&quot; % (a_tmpdir, self.r_srffile[0:self.r_srffile.find(&quot;.srf&quot;)]), &quot;%s/%s.png&quot; % (a_outdir, self.r_srffile[0:self.r_srffile.find(&quot;.srf&quot;)]))<br /> File &quot;/usr/lib/python2.6/shutil.py&quot;, line 99, in copy2<br /> copyfile(src, dst)<br /> File &quot;/usr/lib/python2.6/shutil.py&quot;, line 52, in copyfile<br /> fsrc = open(src, 'rb')<br /> IOError: [Errno 2] No such file or directory: '.../bbp_2g/tmpdata/3309831/test_ucsb.ps.png'<br /> &lt;/pre&gt;<br /> <br /> '''Cause:''' The Ucrmg module calls the Plot_SRF module to the plot the SRF file. Plot_SRF uses C-shell code to locate and use GMT package to plot the SRF file. This shell code might fail on some flavors of Linux with a message like &quot;Newline in variable name&quot; in the Plot_SRF log file.<br /> <br /> '''Solution:''' This issue can be fixed by editing the plot_SRF.csh file. The steps to fix this issue are listed under the solution for &quot;ERROR: test_gensrf (test_genslip.Test_Genslip)&quot; above.<br /> <br /> === FAIL: test_site_amp (test_uc_site.Test_UC_Site) ===<br /> <br /> The unit test for UC-Site module might fail with the following message:<br /> &lt;pre&gt;<br /> ======================================================================<br /> FAIL: test_site_amp (test_uc_site.Test_UC_Site)<br /> ----------------------------------------------------------------------<br /> Traceback (most recent call last):<br /> File &quot;.../bbp_2g/tests/test_uc_site.py&quot;, line 92, in test_site_amp<br /> self.failIf(cmp_bbp.cmp_bbp(a_ref_file_no_header, test_file_no_header, tolerance=0.035)!=0,errmsg)<br /> AssertionError: Output file .../bbp_2g/tmpdata/3310633/s04.3comp does not match reference file .../bbp_2g/ref_data/ucsb/s04.site.3comp<br /> &lt;/pre&gt;<br /> <br /> '''Cause:''' The synthetic seismogram generated by the UC-Site module on the user system differs from the reference result included in the Broadband release.<br /> <br /> '''Solution:''' The stochastic nature of the high frequency simulations is considered, and a constant random seed as input for our tests. This is the same constant random seed used to generate the reference results included in the release. This ensures that the time-series generated with unit tests agree with reference results. However, the high frequency codes are more sensitive to changes in compilers and machines due to the algorithm, so small differences that cause the test to fail are generally acceptable. The user is however encouraged to plot the two time-series and visually inspect them to verify they look similar. We are trying to come up with a better comparison for these tests.<br /> <br /> = Appendix C: Technical Notes =<br /> <br /> == Running Individual Acceptance Tests ==<br /> <br /> The acceptance test script ./tests/AcceptTest.py attempts to run all of the defined tests when executed. However, sometimes it is useful to run an acceptance test in isolation for troubleshooting purposes:<br /> <br /> * Identify the test you want to run. Eg: user-URS-UCSB-SDSU-SDSU<br /> * Move to the ./comps directory and execute that test's XML workflow with run_bbp_2G.py. Using the above example:<br /> &lt;pre&gt;<br /> $ ./run_bbp_2G.py -x ../ref_data/accept_inputs/user-URS-UCSB-SDSU-SDSU.xml<br /> &lt;/pre&gt;<br /> <br /> Since you are running the test outside of AcceptTest.py, you will not see a PASS/FAIL message once the simulation completes. However, you can review the contents of the ./outdata/&lt;SIMID&gt; directory to verify that the correct seismograms and response spectra tables were produced.<br /> <br /> == Manaully Setting Random Number Generator Seed Values ==<br /> <br /> Several of the platform codebases employ random number generators to produce SRFs and seismograms. These random number generators are generally seeded with an initial value (typically an integer) which are hard-coded in the platform. Advanced users may desire to change these seed values.<br /> <br /> Changing the seeds for seismogram synthesis varies depending on which codebase you want to use:<br /> <br /> * URS: Edit ./comps/hfsims_cfg.py, Line 43 &quot;self.RAND_NUM&quot;<br /> * UCSB: Edit ./src/ucsb/Syn1DSCEC/syn1D_LAH.f, Line 183 &quot;iseed&quot;, and recompile with &quot;make&quot;<br /> * SDSU:<br /> ** User event: Edit ./bbp_2g_gf/sdsu/scattering_generic.dat (seed values annotated in file)<br /> ** Validation event: Edit ./bbp_2g_gf/sdsu/&lt;event&gt;/scattering.dat</div> Patrices https://strike.scec.org/scecwiki/index.php?title=Broadband_User_Guide_v11.2.3&diff=5058 Broadband User Guide v11.2.3 2012-05-08T22:05:48Z <p>Patrices: </p> <hr /> <div>'''Version 11.2.3.'''<br /> <br /> If you find errors in this document or sections to be unclear, please either fix them yourself or contact software@scec.org.<br /> <br /> = Installing the Second-Generation Broadband Platform =<br /> Installing the Broadband Platform involves obtaining a copy of the code and building the required executables. You can either download the platform from the Broadband web site ([http://www.scec.org/research/broadband http://www.scec.org/research/broadband]) or check the code out of SCEC's Subversion repository. Most users should download the platform.<br /> <br /> == System Dependencies ==<br /> The current version of the Broadband Platform is designed to run on standard 64-bit Linux machines. Testing has been performed on SCEC's development servers running Fedora Core 10 (kernel version 2.6.27.41-170.2.117.fc10.x86_64). In this guide we outline how to install the platform into your own account on a Linux computer using the simplest approach.<br /> <br /> == Software Dependencies ==<br /> The Broadband Platform has certain software dependencies.<br /> <br /> Required:<br /> <br /> *Python v2.7 with<br /> **PyGTK<br /> **Matplotlib<br /> **Numpy<br /> **Pyproj<br /> <br /> *Intel compilers (64-bit) v12.0.4<br /> *GNU compilers (gcc, gfortran) v4.5.1<br /> *GNU Fortran 77 v3.4.6<br /> *GMT (Generic Mapping Toolkit)<br /> *ImageMagick<br /> <br /> == Setting Up Your Account ==<br /> For simplicity of installation, we recommend users use a bash shell for the Broadband Platform account. It is possible to get the platform running using other shell's, but we will focus on a bash shell installation. The user environment is a common source of problems since certain environment variables must be defined for the platform to work correctly.<br /> <br /> To check your account, make sure you can run basic commands like ''ls'' and ''cd'' before proceeding.<br /> <br /> == Downloading the Platform ==<br /> &lt;nowiki&gt;Download 4 files from the Broadband website, the code (bbp_dist_&lt;version&gt;.tgz), the data (bbp_data_&lt;version&gt;.tgz), and their checksum files (bbp_dist_&lt;version&gt;.tgz.md5 and bbp_data_&lt;version&gt;.tgz.md5). &lt;/nowiki&gt;The code file is about 100 MB, the data file about 3 GB. After you've downloaded the files to your local Linux system, the next step is to calculate the checksums yourself and compare them to the checksums you downloaded.<br /> <br /> First, verify that the ''md5sum'' command is in your path:<br /> <br /> $&gt; which md5sum<br /> <br /> You should get something like /usr/bin/md5sum. If you see the message 'no md5sum in...', contact your Linux system administrator and ask to have md5sum added to your path.<br /> <br /> Once you can run the ''md5sum'' command, run:<br /> <br /> $&gt; md5sum -c bbp_dist_&lt;version&gt;.tgz.md5<br /> $&gt; md5sum -c bbp_data_&lt;version&gt;.tgz.md5<br /> <br /> You should get the messages<br /> bbp_dist_&lt;version&gt;.tgz.md5: OK<br /> bbp_data_&lt;version&gt;.tgz.md5: OK<br /> <br /> If you get FAILED instead, re-download the tgz files and try again. When it passes, that means the files were downloaded without error.<br /> <br /> Once both files have passed the checksum test, untar the files.<br /> <br /> $&gt; tar xzvf bbp_dist_&lt;version&gt;.tgz file<br /> $&gt; tar xzvf bbp_data_&lt;version&gt;.tgz file<br /> <br /> If multiple users are planning to use the platform on the same system, you only need one copy of the data files per machine. Each user will still need his or her own copy of the code files.<br /> <br /> Alternatively, if you would like access to the latest version of the platform and get frequent but less thoroughly tested improvements, you can check out the platform from SCEC's Subversion repository. Only advanced users should take this approach, outlined in detail in the [[#Advanced Users| Advanced Users section]].<br /> <br /> == User Account Setup ==<br /> <br /> The Broadband platform installation is divided into two parts (1) input Green Functions (GF) data directory (9.3Gb), and (2) BBP home directory (366Mb). <br /> <br /> First, the Green's function libraries are larger, but they are static. The broadband platform reads the data files, but does not change them. <br /> <br /> Second, the remainder of the broadband platform is organized in the BBP home directory. The BBP home directory has a specific directory structure that includes the source code for the scientific programs, the python scripts that link the scientific programs, simulation input directory, temporary and log file directories, and the output data directory where all the platform results are written.<br /> <br /> The BBP home directory will increase in size as you run the platform, because both output data and output log files are written to the home directory. Running the acceptance tests will produce nearly ( 10Gb) of input data (5.2Gb), output data (500Mb), temporary files (2.7Gb), and output log files (250Mb). Once these tests have passed much of this data can be removed. However, the BBP home directory should have at least 10Gb of disk space to insure the acceptance tests can be run when a particular broadband platform software distribution is first installed on a system.<br /> <br /> == Data Directory ==<br /> Input data files called Greens Functions are distributed with the platform. These files are generated using specific velocity structures, so they are often considered region specific. We have GF for three regions including near Loma Prieta, near Landers, and near Northridge.<br /> <br /> The data directory is static, and the data directories are read-only. A single copy can be installed in a shared disk, which can then be shared by multiple users.<br /> <br /> == Setting Environment Variables ==<br /> The BBP source codes and scripts are organized under the broadband platform home directory. The broadband platform home directory is specified in a couple of places during Broadband Platform installation. <br /> <br /> Internal to the Broadband platform software, all broadband platform files (except the Greens Function data files) are in sub-directories of the BBP home directory.<br /> <br /> == BBP Environment Variable ==<br /> We recommend setting both an alias and a environment variable to the BBP home directory. This will help avoid typing it many times.<br /> <br /> If you're running a Bash shell, add the following line to your .bash_profile with your favorite text editor:<br /> <br /> export BBP=/home/scec-00/kumar/bbp_2g<br /> <br /> If you're running a C-shell, add the following line to your .cshrc with your favorite text editor:<br /> <br /> setenv BBP /home/scec-00/kumar/bbp_2g<br /> <br /> * PYTHONPATH<br /> After you've obtained a copy of the project, you'll need to make sure the comps directory is on Python's path so Python can find all the project modules. If you're running a Bash shell, add the following line to your .bash_profile with your favorite text editor:<br /> <br /> export PYTHONPATH=$BBP/comps:$PYTHONPATH<br /> <br /> If you're running a C-shell, add the following line to your .cshrc with your favorite text editor:<br /> <br /> setenv PYTHONPATH $BBP/comps:$PYTHONPATH<br /> <br /> * PATH<br /> In order to successfully compile the project, you'll need to make sure the required compilers directories are in your PATH variable. Broadband requires Intel 64-bit compilers, icc and ifort and GNU Compilers, gcc, g77 and f77 to compile the scientific code.<br /> <br /> If you are planning to run Broadband on SCEC Development servers, make sure you have the following directories in your PATH:<br /> <br /> For Bash Shell (in .bash_profile)<br /> <br /> export PATH=/usr/usc/intel/composerxe-2011.4.191/bin/intel64:/usr/usc/intel/composerxe-2011.4.191/mpirt/bin/intel64:$PATH<br /> <br /> For C-shell (in .cshrc)<br /> <br /> setenv PATH /usr/usc/intel/composerxe-2011.4.191/bin/intel64:/usr/usc/intel/composerxe-2011.4.191/mpirt/bin/intel64:$PATH<br /> <br /> When running elements of the platform over ssh, be sure to enable ssh forwarding (with the -X or -Y options).<br /> <br /> After modifying your login script above, log out and log back into the machine so the changes are reflected in your environment.<br /> <br /> == Edit Install_cfg.py with Installation Directory Paths ==<br /> <br /> You need to tell the platform where it's installed by editing a single python file called &quot;install_cfg.py&quot;. Edit the file bbp_2g/comps/install_cfg.py with your favorite text editor, and edit the lines:<br /> <br /> self.A_INSTALL_ROOT = &lt;bbp_2g directory&gt;<br /> self.A_GF_DIR = &lt;bbp_2g_gf directory&gt;<br /> <br /> as one example:<br /> <br /> self.A_INSTALL_ROOT = /home/scec-00/kumar/bbp_2g<br /> self.A_GF_DIR = /home/scec-00/kumar/bbp_2g_gf<br /> <br /> with the paths on your system to the bbp_2g directory (the source) and the bbp_2g_gf directory (the data) that you unzipped. For example, it could be /home/scottcal/broadband_platform/bbp_2g and /home/scottcal/broadband_platform/bbp_2g_gf.<br /> <br /> Here is some information about these two directories that may be useful as you decide how, and where, to install these two parts of the Broadband Platform on your computer disk system. The data files, and therefore the &lt;bbp_2g_gf directory&gt; are nearly 3GB, but they are static and will not be modified and will not grow in size during use of the platform. The source directory is small to begin. However, this directory will increase as the platform is used, since the results produced by the platform will be stored here.<br /> <br /> == Directory Structure ==<br /> The platform consists of two top-level directories, bbp_2g and bbp_2g_gf. bbp_2g contains the source code, executables, scripts, tests, input, working, and output directories. bbp_2g_gf contains the Green's Functions, input files for the validation events, and other required input files for the various code bases. Note that indata, logs, outdata, tmpdata, and xml are created when the platform is first run, so they will be missing when you first install the platform.<br /> <br /> bbp_2g has the following directories:<br /> *checksums: Contains checksums for bbp_2g_gf files<br /> *comps: The Python scripts to run the platform<br /> *docs: Documentation for the platform<br /> *etc: Miscellaneous utility scripts<br /> *examples: Contains example input files<br /> *indata: An internal directory, used to stage input files<br /> *logs: Contains logs from BBP runs<br /> *outdata: Contains output files from a run<br /> *ref_data: Contains reference files for BBP tests<br /> *start: Put input files for an interactive run here<br /> *src: Source code for BBP modules<br /> *tests: Contains unit and acceptance tests<br /> *tmpdata: An internal directory, used during a run<br /> *xml: Contains XML files which describe simulations and can be used as input<br /> <br /> bbp_2g_gf has the following directories:<br /> *compare: Contains observed seismograms for validation events<br /> *plot: Data files for GMT plots<br /> *sdsu, ucsb, urs: Contains Green's functions, velocity files, and other required inputs for the codebases.<br /> <br /> In general, you will be interacting with the start directory for input files, comps to run the platform, tests to test the platform, and outdata to examine data products.<br /> <br /> === Adding aliases ===<br /> <br /> You may find it helpful to add aliases, so you can quickly and easily move to different broadband directories with a single command. We recommend creating aliases for the home, start, and outdata directories.<br /> <br /> If you are using the Bash shell, you can create aliases by adding the following lines to ~/.bash_profile:<br /> <br /> alias bbp= 'cd &lt;path to bbp_2g directory&gt;'<br /> alias start='cd &lt;path to bbp_2g directory&gt;/start'<br /> alias outdata='cd &lt;path to bbp_2g directory&gt;/outdata'<br /> <br /> If you're using a C shell, edit your ~/.cshrc and add:<br /> <br /> alias bbp cd &lt;path to bbp_2g directory&gt;<br /> alias start cd &lt;path to bbp_2g directory&gt;/start<br /> alias outdata cd &lt;path to bbp_2g directory&gt;/outdata<br /> <br /> Log out and log back in. You'll notice that now you can type the alias command as a shortcut to change directories:<br /> <br /> $&gt; pwd<br /> /home/scec-00/scottcal<br /> $&gt; start<br /> $&gt; pwd<br /> /home/scec-00/scottcal/bband/bbp_2g/start<br /> <br /> This can be a useful way to navigate around the broadband platform directories.<br /> <br /> == Building the Platform ==<br /> Once you have checked out the code, you need to build it. By default, every executable is compiled using the compiler recommended by the code developer. However, if you have limited compiler options or are building the codes on an untested system, you may need to specify non-standard alternative compilers, as described below.<br /> <br /> Before you can build the platform, you need to make sure that the Intel compilers are in your path. This is done automatically on broadband.usc.edu, but on other systems you can check by typing:<br /> <br /> $&gt;which icc<br /> <br /> If you get the message &quot;no icc in ...&quot;, then you'll need to add the Intel compilers to your path. Once the Intel compilers are in your path, you can make the code by cd-ing to the bbp_2g/src directory and typing make:<br /> <br /> $&gt; cd src<br /> $&gt; make<br /> <br /> It takes a minute or two to build the code. You may encounter build warnings; these are fine. However, if you get any build errors, this is a problem and should be investigated.<br /> <br /> By default, every executable is compiled using the compiler recommended by the code developer. Depending on the system, some compilers may not be available to you. You can override the C and Fortran compilers used by editing<br /> <br /> src/makefile<br /> <br /> Uncomment USER_C and set FC and CC to the compilers you wish. For example:<br /> <br /> Before:<br /> <br /> #USER_C=1<br /> FC=f77<br /> CC=gcc<br /> <br /> After (an example, you may choose different compilers):<br /> <br /> USER_C=1<br /> FC=gfortran<br /> CC=gcc<br /> <br /> Note that not all compiler combinations have been thoroughly tested. You may encounter build errors with untested compiler combinations. If you encounter any errors while building the platform, consult the Troubleshooting section at the end of this user guide for know issues and their solutions.<br /> <br /> Once the platform has been successfully built, you can move on to running the tests to verify that all components are working correctly.<br /> <br /> == Advanced Users ==<br /> Alternatively, if you would like access to the latest version of the platform, to get frequent but less thoroughly tested improvements, you can check out the platform from SCEC's Subversion version control repository on source.usc.edu. Only advanced users should follow this approach. If you are unsure, you should download the code as outlined in [[#Downloading the Platform|Downloading the Platform]] and skip this section.<br /> <br /> You may need to request access from the SCEC system administrator, John Yu ([mailto:johnyu@usc.edu johnyu@usc.edu]). Make sure you have subversion in your path before beginning.<br /> <br /> Once you have access, you'll need to decide if you want a stable tagged version, or the latest version in the repository. For a stable version, open a terminal window on the system of your choice and type:<br /> <br /> $&gt; svn checkout https://source.usc.edu/svn/broadband/tags/&lt;stable version&gt; bbp_2g<br /> <br /> For the latest version, type:<br /> <br /> $&gt; svn checkout https://source.usc.edu/svn/broadband/trunk bbp_2g<br /> <br /> This will check out the project to your local machine. It contains the source code, tests, and some example files. You also need to obtain a copy of the Broadband Platform data files, containing the Green's tensors. They are too large to be stored in version control. You can obtain a copy from SCEC software distribution server. If you are working on SCEC development server, you might be able to create a symbolic link to data folder. Please contact [[#User_Support|User Support]] to get a location of the data folder on the SCEC development server. If you are not working on SCEC development server, or don't have an SCEC Linux login account, you can get a archive (.tgz) file of the Green's functions from the same download site you obtained this guide.<br /> <br /> If you know where a read-accessible installation of the green functions data directories you can create a link to that location. This can save disk space in some cases.<br /> <br /> ln -s /home/scec-00/scottcal/bband/bbp_2g_gf &lt;path to your gf directory&gt;<br /> <br /> Periodically you should check for updates to the code. To do so, go to your bbp_2g directory and type<br /> <br /> $&gt; svn update<br /> <br /> This will pull down any code updates that have been made in the repository. After you update, make the code again (detailed in [[#Building the Platform|Building the Platform]]) so that any code changes are captured in the executables.<br /> <br /> == Running the Broadband Platform ==<br /> We recommend users initiate all Broadband Platform runs from the &quot;start&quot; directory. The start directory is a collection point for input files for a particular simulation.<br /> <br /> Assuming the user is starting at BBP home directory, the user should move to the start directory and then run the Checksum, Unit and Acceptance tests to confirm the Broadband Platform software installation is operating as expected.<br /> <br /> $&gt; cd start<br /> <br /> == Running Checksum, Unit, and Acceptance Tests ==<br /> The broadband platform contains three kinds of tests. The checksum tests verify that the data files were copied correctly and you have all the files that are expected. Unit tests run each module using a set of input files, and compare the results against known outputs. They verify that each module has been built and is working correctly. Acceptance tests verify that the modules are working correctly together. They test the platform end-to-end using different combinations with known inputs and compare the results. All the possible module combinations for both user-defined and validation events are tested as checks against integration errors.<br /> <br /> Begin with the checksum tests. Once they past, run the unit tests and finally the acceptance tests.<br /> <br /> == Running Checksum Tests ==<br /> To run the checksum tests, change to the checksums directory and run md5sum_check.py.<br /> <br /> From the BBP home directory:<br /> <br /> $&gt; cd checksums<br /> $&gt; ./md5sum_check.py<br /> <br /> It takes about 5 minutes to compute the checksums. If a checksum disagrees, that means that the contents of the datafile were not what was expected. Try reinstalling the data files and try again. If you continue to get a checksum error, contact support.<br /> <br /> Once the checksums agree, move on to the unit tests.<br /> <br /> == Running Unit Tests ==<br /> To run the unit tests, change to the tests directory and run UnitTests.py.<br /> <br /> From the BBP home directory:<br /> <br /> $&gt; cd tests<br /> $&gt; ./UnitTests.py<br /> <br /> The unit tests take about 15 minutes to run. When they're complete, the console will either print &quot;OK&quot; or how many tests failed. If a test has failed, first check that you have built the executables.You can rerun just the specific test that failed (test_&lt;module&gt;.py). If the test is still failing, also verify that you have the ref_data directory, since it contains the input and reference files. If you're looking for more information about the failure, you can consult the Unit Tests log file in bbp_2g/logs/unit_test.log . If you can't determine the reason for the failure, contact support.<br /> <br /> Once the unit tests all pass, proceed to the acceptance tests. If there are any failure or errors while running the unit tests, consult the Troubleshooting section at the end of this user guide for know issues and their solutions.<br /> <br /> == Running Acceptance Tests ==<br /> Make sure the unit tests pass before moving on to the acceptance tests. To run the acceptance tests, change to the tests directory (if you're not there already) and run AcceptTests.py. <br /> The acceptance tests take a long time to run, around 20 hours<br /> <br /> From the BBP home directory:<br /> <br /> $&gt; cd tests<br /> $&gt; ./AcceptTests.py &amp;&gt; accept.out &amp;<br /> <br /> Since the tests take so long to run (twenty hours), you should run them as a background process, and redirect their output to a log file, as shown in the command above.<br /> <br /> You can check the progress by tailing the log file.<br /> <br /> $&gt; tail accept.out<br /> <br /> When all the acceptance tests are completed, the AcceptTests.py script will either print &quot;OK&quot; or how many tests failed. <br /> <br /> Acceptance test failures indicate that the modules are not integrated correctly. Like with the unit tests, verify that you have the ref_data directory. If a certain acceptance test fails, you can get more information by consulting the acceptance test logs in bbp_2g/logs/acceptance_tests_logs/&lt;test that failed&gt;.log . If you can't determine the reason for the failure, contact [[support]].<br /> <br /> Since the acceptance tests can take a long time to run, you may wish to resume where you left off. This feature is supported automatically. If you do not wish to resume, delete the resume file in ref_data/accept_inputs/resume.txt. If there are any failure or errors while running the acceptance tests, consult the Troubleshooting section at the end of this user guide for know issues and their solutions.<br /> <br /> = Types of Broadband Platform Simulations =<br /> <br /> The platform supports two kinds of simulations, validation events and user-defined events. Validation simulations are performed using a historical event, and are directly compared to observed seismograms using goodness-of-fit. User-defined events are run using a rupture description provided by the user which may not necessarily be a historical earthquake.<br /> <br /> When you run a simulation, the platform assigns an ID to it. This ID can be used to track the simulation and locate the output data products.<br /> <br /> To supply input files to the platform, put them in the start directory. Extensions are important - the platform recognizes station lists (.stl), SRF files (.srf), and simple source descriptions (.src). If there are multiple files of a type, the platform will prompt the user to select one.<br /> <br /> To perform a simulation, a user selects between different required and optional modules. Below we present a summary of the various modules.<br /> <br /> = Modules =<br /> The broadband platform consists of a series of modules. There are two main types of modules, science modules and utility modules. Science modules are those for which the platform has multiple implementations, provided by different coding research groups. Utility modules only have 1 implementation. A schematic of the available modules and their flow relationships is shown below:<br /> <br /> == Science Modules ==<br /> All simulations must include a low-frequency, high-frequency, and site response science module. Simulations may include an optional rupture generation science module. Users may select between the following different implementations of each of these modules:<br /> <br /> Rupture generation:URS, UCSB<br /> <br /> Low-frequency:URS, UCSB<br /> <br /> High-frequency:URS, UCSB, SDSU<br /> <br /> Site response:URS, UCSB, SDSU<br /> <br /> == Utility Modules ==<br /> A spectral response utility module is automatically run after the site response module. Additionally, users may select an optional goodness-of-fit utility module to run at the conclusion of the simulation. In the case of a user-defined event, users select a historical event or previously run simulation to use as the comparison for goodness-of-fit.<br /> <br /> = Platform Directory =<br /> <br /> A broadband platform distribution is organized in a specific directory structure that separates the input data sets, the python scripts, the simulation configuration files, log files, and output data files.<br /> <br /> When running Broadband Platform simulations, standard procedure is to place the simulation input files in the start directory and invoke the Broadband platform scripts from there.<br /> <br /> From the BBP home directory:<br /> <br /> $&gt; cd start<br /> $&gt; run_bbp_2G.py<br /> <br /> Simulation output results will be written into the bbp_home/output<br /> <br /> = Validation Simulations =<br /> To run a validation simulation, go to the comps directory and run run_bbp_2G.py. The platform will ask you a series of questions. Answer 'y' to &quot;Do you want to perform a validation run?&quot;<br /> <br /> From the BBP home directory:<br /> <br /> $&gt; cd start<br /> $&gt; run_bbp_2G.py<br /> Welcome to the SCEC Broadband Platform.<br /> Please select the modules you want to run.<br /> Do you want to perform a validation run (y/n)? y<br /> Do you want to validate with:<br /> Northridge (1)<br /> Loma Prieta (2)<br /> Landers (3)<br /> ?<br /> ...<br /> <br /> No input files are required by the user. However, you may wish to run with a reduced station list to speed up the computations. You can put your own station list into the start directory (the format is described in [[#Station File List|section 5.3]]). Note that any stations which do not have observed seismograms will not be included in the automatically generated goodness-of-fit comparison.<br /> <br /> In addition to the low-frequency modules which compute seismograms using 1D Green's Tensors, validation events can also be run using precomputed 3D seismograms to supply the low-frequency.<br /> <br /> = User-defined Simulations =<br /> To run a user-defined simulation, two input files are required, a rupture description and a station list. The rupture description can either be in SRF format or a simplified source description (the format is described in [[#Simple source description|section 5.1]]). To run a user-defined simulation, run run_bbp_2G.py.<br /> <br /> From the BBP home directory:<br /> <br /> $&gt; cd start<br /> $&gt; run_bbp_2G.py<br /> Welcome to the SCEC Broadband Platform.<br /> Please select the modules you want to run.<br /> Do you want to perform a validation run (y/n)? y<br /> Do you want to run a rupture generator (y/n)? <br /> ...<br /> <br /> You may then choose if you want to run a rupture generator. This is necessary if you're supplying a simple rupture description. If you're supplying an SRF file, you can skip this. Next you can select from different module implementations. Finally, you have the option to run goodness-of-fit against either observed seismograms or another simulation.<br /> <br /> ...<br /> Do you want to run goodness of fit (y/n)? y<br /> What reference files would you like to compare to? Enter a simulation ID or a scenario name: &lt;comparison&gt;<br /> Enter a label to use for the comparison seismograms: &lt;label&gt;<br /> <br /> The label will be used in GoF plots to distinguish one set of results from the other.<br /> <br /> The user-defined events must be within one of the regions supported by the platform - Southern California, Northern California, or the Mojave. The platform will automatically select a region based on the event hypocenter. If the event falls outside of these regions, you'll get an error.<br /> <br /> = Logging =<br /> During the run, log files will be produced in logs/&lt;simulation ID&gt;/&lt;simulation ID&gt;.&lt;module name&gt;.log. If the platform fails, this is a good place to look to determine the error. Additionally, any fatal errors will be recorded in fatal_error.log.<br /> <br /> Metadata capturing all the executable calls is located in tmpdata/&lt;simulation ID&gt;/metadata.txt for careful tracing of exactly what was called. Both the log files and metadata can be useful if troubleshooting an issue.<br /> <br /> = Data Products =<br /> The platform produces a variety of data products. &lt;nowiki&gt;All data products are located in outdata/&lt;simulation ID&gt;. &lt;/nowiki&gt;On most Linux systems, you can show images using display:<br /> <br /> $&gt; display &lt;PNG file&gt;<br /> <br /> Make sure you have X11 forwarding enabled.<br /> <br /> == Station map ==<br /> To help visualize the stations in relationship to the fault, the platform produces a PNG file displaying station locations with red circles and the fault plane with a black line, on an image of California. You can find this file in outdata/&lt;simulation ID&gt;/station_map.png.<br /> <br /> == Seismograms ==<br /> When running the platform, you have the option to output velocity and acceleration seismograms, for each station. Plots of these files can be found in outdata/&lt;simulation ID&gt;/&lt;simulation ID&gt;.&lt;station&gt;_&lt;velocity or acceleration&gt;_seis.png.<br /> <br /> The raw seismogram data is available in outdata/&lt;simulation ID&gt;/&lt;simulation ID&gt;.&lt;station&gt;.vel.bbp (velocity) and outdata/&lt;simulation ID&gt;.&lt;station&gt;.acc.bbp (acceleration). Its format is described in [[#BBP seismograms|section 5.4]].<br /> <br /> To compare seismogram data, you can run comps/plotit.py with two seismograms. It will plot them both for comparison. From the comps directory, run:<br /> <br /> $&gt; plotit.py &lt;path to seismogram 1&gt; &lt;path to seismogram 2&gt;<br /> <br /> == Response spectra ==<br /> The respect code, run at the end of each simulation, calculates the response spectra for each station. The raw respect data is located at<br /> <br /> From the BBP home directory:<br /> <br /> outdata/&lt;simulation ID&gt;/&lt;simulation ID&gt;.&lt;station&gt;.rsp<br /> <br /> in the format described in [[#Response spectra|section 5.5]].<br /> <br /> == Goodness-of-fit ==<br /> If you run goodness-of-fit, several additional data products are produced. The goodness-of-fit comparison is performed by comparing the response spectra of a set of calculated seismograms to seismograms from another simulation or observed seismograms. For each station involved in the comparison, a plot comparing the response spectra can be found at outdata/&lt;simulation ID&gt;/&lt;comparison label&gt;_&lt;simulation ID&gt;_&lt;station&gt;_rsp.png. A plot showing the seismograms on top and bottom can be found at outdata/&lt;comparison label&gt;_&lt;simulation ID&gt;_&lt;station&gt;_overlay.png. The goodness-of-fit plot can be found at gof-&lt;comparison label&gt;-&lt;simulation ID&gt;_r0-&lt;cutoff distance&gt;.png.<br /> <br /> Note that at least 3 stations must be run for goodness-of-fit to be valid. If fewer than 3 stations are run, no goodness of fit calculation will be performed.<br /> <br /> == Rupture files ==<br /> When a user-defined event is simulated, the user has the option to run a rupture generator. This generator produces an SRF file, found in outdata/&lt;simulation ID&gt;/*.srf. This file can be put in the start directory and used in future runs. Additionally, the platform produces a plot of the cumulative slip on the fault surface, outdata/&lt;simulation ID&gt;/&lt;SRF prefix&gt;.png.<br /> <br /> = Platform Modes =<br /> The platform can be run in multiple modes. The default is interactive mode, in which the user is prompted to answer a series of questions. Once all the information has been gathered, the run begins.<br /> <br /> For a large number of runs, or if the user is repeating a specific run, this can be tedious. The platform provides two other ways to describe a run, with an option file or an XML description.<br /> <br /> An option file provides responses to all the questions that the platform poses. The format is described in [[#Option File|section 5.6]], but it's basically a text file, 1 entry per line, with support for comments. It can be fed to the platform using the -o option.<br /> <br /> The platform will also accept XML files containing a full description of a run. The schema for these files is given in [[#XML workflow description schema|section 5.7]]. These files are also produced by the platform after every simulation, and placed in xml/&lt;simulation ID&gt;.xml. So if you want to rerun a simulation, you can point the platform to the XML file from that simulation using the -x option. Note that a new simulation ID will be assigned to the run, so there is no risk of overwriting previous simulation results.<br /> <br /> = Available Options =<br /> To get a list of the current available options, run run_bbp_2G.py with the -h flag.<br /> <br /> $&gt; run_bbp_2G.py -h<br /> Usage: run_bbp_2G.py [options]<br /> Options:<br /> -h, --help Show this help message and exit<br /> -x XML_FILE, --xml-file=XML_FILE Run using XML description of workflow<br /> -s SIM_ID, --simID=SIM_ID Force a simID<br /> -o OPTFILE, --option-file=OPTFILE File containing responses to interactive platform prompts<br /> -v, --version Broadband platform version<br /> -c, --compact Compact output results. Remove temporary files for simulations that complete successfully.<br /> -g, --generate-xml Generates the XML description but does not run the platform<br /> -l LOG_FILE, --log=LOG_FILE Store all output in a file<br /> <br /> = Cleanup =<br /> After a while, you may find that your indata, tmpdata, outdata, and logs directories are getting cluttered with files from past runs. If you wish to delete these old files, you can use the clean_directories.sh script in the etc directory.<br /> <br /> From the BBP home directory:<br /> <br /> $&gt; cd etc<br /> $&gt; ./clean_directories &lt;days&gt;<br /> <br /> Any simulation ID directories in the indata, tmpdata, outdata, and logs directories which were last accessed &lt;days&gt; days or longer ago will be deleted. If you have a few directories you want to keep, either copy them somewhere else, or copy them to a directory name that's not all digits and they won't be deleted.<br /> <br /> = Examples =<br /> Below are some examples that you can try using the sample files in the examples directory. Make sure all the tests pass before you try this. You should be in the comps directory when you start these examples:<br /> <br /> From the BBP home directory:<br /> <br /> $&gt; cd comps<br /> <br /> == Sample Validation Run ==<br /> You don't need to move any files for this. Notice that 3D seismograms are a low-frequency option, since you're running a validation event.<br /> <br /> From the BBP home directory:<br /> <br /> $&gt; cd start<br /> $&gt; run_bbp_2G.py <br /> Welcome to the SCEC Broadband Platform.<br /> Please select the modules you want to run.<br /> Do you want to perform a validation run (y/n)? y<br /> Do you want to validate with:<br /> Northridge (1)<br /> Loma Prieta (2)<br /> Landers (3)<br /> ?1<br /> Do you want to<br /> run all validation stations (1)<br /> select a station list (2)<br /> ?1<br /> Choose a source of low frequency seismograms:<br /> URS module (1)<br /> URS 3D seismograms (2)<br /> UCSB module (3)<br /> SDSU module (4)<br /> SDSU 3D seismograms (5)<br /> ?2<br /> Choose a high frequency module:<br /> URS (1)<br /> UCSB (2)<br /> SDSU (3)<br /> ?1<br /> Choose a site response module:<br /> URS (1)<br /> UCSB (2)<br /> SDSU (3)<br /> ?1<br /> Do you want to plot velocity seismograms (y/n)? y<br /> Do you want to plot acceleration seismograms (y/n)? y<br /> <br /> This simulation takes about 10 minutes. Once it's complete the platform will tell you:<br /> <br /> You can find results in &lt;path to bbp_2g install&gt;/outdata/&lt;simulation ID&gt; .<br /> <br /> In that directory you will find:<br /> <br /> *Velocity seismograms (&lt;simulation ID&gt;.&lt;station&gt;.bbp)<br /> *Acceleration seismograms (&lt;simulation ID&gt;.&lt;station&gt;.acc.bbp)<br /> *Plots of velocity seismograms (&lt;simulation ID&gt;.&lt;station&gt;_velocity_seis.png)<br /> *Plots of acceleration seismograms (&lt;simulation ID&gt;.&lt;station&gt;_acceleration_seis.png)<br /> *Response spectra files (&lt;simulation ID&gt;.&lt;station&gt;.rsp)<br /> *Plots comparing simulated and observed seismograms (Northridge_&lt;simulation ID&gt;_&lt;station&gt;_overlay.png)<br /> *Plots comparing simulated and observed response spectra (Northridge_&lt;simulation ID&gt;_&lt;station&gt;_rsp.png)<br /> *Overall goodness-of-fit plots (gof-Northridge-&lt;simulation ID&gt;_r0-25.png)<br /> <br /> == Sample Validation run, custom stations ==<br /> If the validation runs aren't performed with 3D low-frequency, it can take a long time, up to 10 minutes per station. Sometimes you might want to run with a reduced station list so the simulation will run faster.<br /> <br /> Copy the files in example/valid_custom_stations into the start directory. Take a look at the format of the station file:<br /> <br /> $&gt; more valid_test_stat.stl <br /> #Required: lon, lat, station name, distance to fault plane, Vs30<br /> #Optional: low freq corner, high freq corner<br /> #Unused: station information<br /> #lon lat stationdist Vs30 LF corner HF corner station information<br /> -118.6417 34.5640 cast 20.47 450 0.120 23.0 CSMIP peer.berkeley.edu/nga<br /> -118.4180 34.0628 lacn 22.82 278 0.140 23.0 CSMIP peer.berkeley.edu/nga<br /> -118.8811 34.2886 moor 24.16 405 0.160 23.0 CSMIP peer.berkeley.edu/nga<br /> <br /> Now, run the platform, using a station list:<br /> <br /> From the BBP Home directory<br /> <br /> $&gt; cd start<br /> $&gt; run_bbp_2G.py <br /> Welcome to the SCEC Broadband Platform.<br /> Please select the modules you want to run.<br /> Do you want to perform a validation run (y/n)? y<br /> Do you want to validate with:<br /> Northridge (1)<br /> Loma Prieta (2)<br /> Landers (3)<br /> ?1<br /> Do you want to<br /> run all validation stations (1)<br /> select a station list (2)<br /> ?2<br /> <br /> If you have multiple station list files in your start directory, you may see the following prompt asking you to select one. If you only have one, the platform will select it automatically.<br /> <br /> Found multiple BBP station list files in the start directory. Please select one:<br /> nr_one_stat.stl (1)<br /> valid_test_stat.stl (2)<br /> ?2<br /> Choose a source of low frequency seismograms:<br /> URS module (1)<br /> URS 3D seismograms (2)<br /> UCSB module (3)<br /> SDSU module (4)<br /> SDSU 3D seismograms (5)<br /> ?3<br /> Choose a high frequency module:<br /> URS (1)<br /> UCSB (2)<br /> SDSU (3)<br /> ?2<br /> Choose a site response module:<br /> URS (1)<br /> UCSB (2)<br /> SDSU (3)<br /> ?2<br /> Do you want to plot velocity seismograms (y/n)? y<br /> Do you want to plot acceleration seismograms (y/n)? y<br /> <br /> Again, when the run completes in about 15 minutes you can find results in the output directory. You'll notice far fewer files, as only 3 stations were run instead of 133. The goodness-of-fit plots won't look very good - more stations are really needed to get an accurate plot.<br /> <br /> == Sample User-defined run with source description ==<br /> Next let's try running a user-defined event. Copy examples/user_rup_gen/nr_one_stat.stl and examples/user_rup_gen/user_eq.src to the start directory. user_eq.src is a simple source description. Its format is outlined in [[#XML workflow description schema|section 5.1]]. Since this is a user-defined event, precomputed 3D seismograms aren't a valid option.<br /> <br /> $&gt; run_bbp_2G.py <br /> Welcome to the SCEC Broadband Platform.<br /> Please select the modules you want to run.<br /> Do you want to perform a validation run (y/n)? n<br /> Do you want to run a rupture generator (y/n)? y<br /> Rupture generators:<br /> URS (1)<br /> UCSB (2)<br /> ?1<br /> Using region: Southern California<br /> Choose a low frequency module:<br /> URS (1)<br /> UCSB (2)<br /> ?2<br /> Found multiple BBP station list files in the start directory. Please select one:<br /> nr_one_stat.stl (1)<br /> valid_test_stat.stl (2)<br /> ?1<br /> Choose a high frequency module:<br /> URS (1)<br /> UCSB (2)<br /> SDSU (3)<br /> ?2<br /> Choose a site response module:<br /> URS (1)<br /> UCSB (2)<br /> SDSU (3)<br /> ?1<br /> Do you want to plot velocity seismograms (y/n)? y<br /> Do you want to plot acceleration seismograms (y/n)? y<br /> Do you want to run goodness of fit (y/n)? n<br /> <br /> Since this run only includes one station, it will run in about 5 minutes. In the output directory you'll notice there are no goodness-of-fit or files, since we didn't run goodness-of-fit. However, there is also a map file (station_map.png), showing the fault plane and the stations, and a plot of the rupture slip (user_eq.png). The SRF generated by the rupture generator is in user_eq.srf; this file could be used in future runs. The filenames of the rupture slip plot and SRF are taken from the rupture description filename.<br /> <br /> == Sample User-defined run with SRF file and goodness-of-fit ==<br /> Finally, try a run with an SRF file and run goodness-of-fit on the results. Copy in examples/user_no_rup_gen/ucsb_modSRF_0.srf and examples/user_no_rup_gen/nr_three_stat.stl<br /> <br /> $&gt; run_bbp_2G.py <br /> Welcome to the SCEC Broadband Platform.<br /> Please select the modules you want to run.<br /> Do you want to perform a validation run (y/n)? n<br /> Do you want to run a rupture generator (y/n)? n<br /> Using region: Southern California<br /> Choose a low frequency module:<br /> URS (1)<br /> UCSB (2)<br /> ?1<br /> Found multiple BBP station list files in the start directory. Please select one:<br /> nr_one_stat.stl (1)<br /> valid_test_stat.stl (2)<br /> nr_three_stat.stl (3)<br /> ?3<br /> Choose a high frequency module:<br /> URS (1)<br /> UCSB (2)<br /> SDSU (3)<br /> ?3<br /> Choose a site response module:<br /> URS (1)<br /> UCSB (2)<br /> SDSU (3)<br /> ?1<br /> Do you want to plot velocity seismograms (y/n)? y<br /> Do you want to plot acceleration seismograms (y/n)? y<br /> Do you want to run goodness of fit (y/n)? y<br /> What reference files would you like to compare to? Enter a simulation ID or a scenario name: Northridge<br /> Enter a label to use for the comparison seismograms: nr<br /> <br /> The reference files can either be a scenario event or a simulation ID previously run. The label is just for the figures when comparisons are plotted.<br /> <br /> This run will take about 15 minutes, and the results can be found in the appropriate outdir. Again, the goodness of fit measures will look poor due to the few stations involved in the comparison. If you had fewer than 3 stations, no goodness-of-fit plots would be produced. However, response spectra comparison plots will still be generated.<br /> <br /> = File Formats =<br /> This section offers descriptions of various file formats in the broadband platform.<br /> <br /> == Simple source description ==<br /> This is the format for the simple source description. It is not whitespace sensitive. The filename must end in .src for the platform to identify it as a source description.<br /> <br /> MAGNITUDE = &lt;magnitude&gt;<br /> FAULT_LENGTH = &lt;length of fault&gt;<br /> DLEN = &lt;DX, along length&gt;<br /> FAULT_WIDTH = &lt;down-dip fault width&gt;<br /> DWID = &lt;DY, along width&gt;<br /> DEPTH_TO_TOP = &lt;depth of fault below surface&gt;<br /> STRIKE = &lt;nowiki&gt;&lt;strike&gt;&lt;/nowiki&gt;<br /> RAKE = &lt;rake&gt;<br /> DIP = &lt;dip&gt;<br /> LAT_TOP_CENTER = &lt;latitude of top center point in fault plane&gt;<br /> LON_TOP_CENTER = &lt;longitude of top center point in fault plane&gt;<br /> HYPO_ALONG_STK = &lt;along strike location of hypocenter (0.0 = middle)&gt;<br /> HYPO_DOWN_DIP = &lt;down dip location of hypocenter (0.0 = top)&gt;<br /> DT = &lt;nowiki&gt;&lt;dt&gt;&lt;/nowiki&gt;<br /> SEED = &lt;random seed used in calculations&gt;<br /> CORNER_FREQ = &lt;corner frequency to use&gt;<br /> <br /> == SRF rupture description ==<br /> Details of the Standard Rupture Format (SRF) are given in more detail in the accompanying document. The general fault surface is represented by a distribution of point sources, and it can support one or more planes. The platform produces SRFs as output from rupture generators, but a user can also supply an SRF file as input for user-defined simulations. SRF filenames must end with the suffix .srf for the platform to correctly identify them.<br /> <br /> == Station File List ==<br /> The user may specify a list of stations, matching the following format:<br /> <br /> #optional<br /> %comment<br /> # lines<br /> &lt;nowiki&gt;&lt;lon&gt; &lt;lat&gt; &lt;stat name&gt; &lt;distance to fault trace&gt; &lt;Vs30&gt; &lt;LF corner&gt; &lt;HF corner&gt; &lt;stat info&gt;&lt;/nowiki&gt;<br /> ...<br /> <br /> The station list filename needs to end in .stl for the platform to recognize it as a station list.<br /> <br /> == BBP seismograms ==<br /> All intermediate and output seismograms are produced in a 4-column text format, whether velocity or acceleration.<br /> <br /> # optional<br /> % comment<br /> # lines<br /> &lt;nowiki&gt;&lt;timestamp&gt; &lt;North/South&gt; &lt;East/West&gt; &lt;Up/Down&gt;&lt;/nowiki&gt;<br /> ...<br /> <br /> Time is in seconds and motion is in cm/s (velocity) or cm/s/s (acceleration) unless otherwise specified in the header. Velocity filenames end in .vel.bbp; accelerations in .acc.bbp.<br /> <br /> == Response spectra ==<br /> The response spectra file is in 4-column text format.<br /> <br /> # optional<br /> % comment<br /> # lines<br /> &lt;nowiki&gt;&lt;period (sec)&gt; &lt;North/South&gt; &lt;East/West&gt; &lt;Up/Down&gt;&lt;/nowiki&gt;<br /> ...<br /> <br /> The platform samples response spectra at 112 periods, 0.01-20 sec and outputs pseudo spectral acceleration in units of g.<br /> <br /> == Option File ==<br /> Option files contain responses to the prompts in the platform. You can use them with the -o option to run_bbp_2G.py. The responses have to match the prompts exactly. For example, if you craft an option file assuming there is only one station list in the start directory (and therefore the user isn't prompted to select one) but then it is run with multiple station lists in the start directory, this will cause the run to abort. Option files are recommended to perform a series of runs with different inputs or different modules. If you have a run you perform regularly, it's better practice to run the platform with the -g option and the option file to produce an XML description, which are more complete descriptions of the workflow.<br /> <br /> #optional comments<br /> %using either symbol<br /> n #comments<br /> y % can go<br /> 1 # here<br /> ...<br /> <br /> Use with:<br /> <br /> $&gt; run_bbp_2G.py -o &lt;option file&gt;<br /> <br /> == XML workflow description schema ==<br /> Each time the platform is invoked, an XML file is produced describing the workflow, obeying the following schema:<br /> <br /> &lt;nowiki&gt;&lt;xs:schema xmlns:xs=&quot;http://www.w3.org/2001/XMLSchema&quot;&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:element name= &quot;BBP_Run_Specification&quot; minOccurs= &quot;1&quot; maxOccurs= &quot;1&quot;&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:attribute name=&quot;version&quot; type = &quot;xs:string&quot; use = &quot;required&quot; /&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:complexType&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:sequence&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:element name= &quot;Validation_Run&quot; minOccurs= &quot;0&quot; maxOccurs = &quot;1&quot;&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:attribute name= &quot;event&quot; type= &quot;xs:string&quot; use= &quot;required&quot; /&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:attribute name= &quot;input_station_file&quot; type = &quot;xs:string&quot; /&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:attribute name= &quot;subset&quot; type = &quot;xs:boolean&quot; use = &quot;required&quot; /&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;/xs:element&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:element name= &quot;BBP_Modules&quot;&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:complexType&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:sequence&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:element name = &quot;BBP_Module&quot; maxOccurs = &quot;unbounded&quot; &gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:complexType&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:sequence&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:element name= &quot;name&quot; type=&quot;xs:string&quot; /&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:element name= &quot;staged_files&quot; &gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:complexType&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:sequence&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:element name=&quot;file&quot; type=&quot;xs:string&quot; maxOccurs= &quot;unbounded&quot;/&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;/xs:sequence&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;/xs:complexType&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;/xs:element&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:element name= &quot;arguments&quot; &gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:complexType&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:sequence&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:element name=&quot;argument&quot; type=&quot;xs:string&quot; maxOccurs=&quot;unbounded&quot;&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:attribute name= &quot;type&quot; type= &quot;xs:string&quot; user= &quot;required&quot; /&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;/xs:element&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;/xs:sequence&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;/xs:complexType&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;/xs:element&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;/xs:sequence&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;/xs:complexType&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;/xs:element&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;/xs:sequence&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;/xs:complexType&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;/xs:element&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;/xs:sequence&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;/xs:complexType&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;/xs:element&gt;&lt;/nowiki&gt;<br /> <br /> These files are difficult to construct by hand, but can be generated using the -g flag when running run_bbp_2G.py.<br /> <br /> = User Support =<br /> If you run into bugs with the platform, you can open a trouble ticket at the [http://northridge.usc.edu/trac/broadband Broadband Trac site].<br /> <br /> Check to see if there has already been a ticket opened for the bug. If you are unable to get the platform to run, you can get direct user support by emailing [mailto:software@scec.org software@intensity.usc.edu].<br /> <br /> = Appendix A: Possible Module Permutations =<br /> == Validation Events ==<br /> <br /> {| class=&quot;wikitable&quot; | border=&quot;1&quot;<br /> | Permutation #<br /> | Low-frequency module<br /> | High-frequency module<br /> | Site response<br /> <br /> |-<br /> | &lt;center&gt;1&lt;/center&gt;<br /> | &lt;center&gt;URS 1D&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;2&lt;/center&gt;<br /> | &lt;center&gt;URS 1D&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;3&lt;/center&gt;<br /> | &lt;center&gt;URS 1D&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;4&lt;/center&gt;<br /> | &lt;center&gt;URS 1D&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;5&lt;/center&gt;<br /> | &lt;center&gt;URS 1D&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;6&lt;/center&gt;<br /> | &lt;center&gt;URS 1D&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;7&lt;/center&gt;<br /> | &lt;center&gt;URS 1D&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;8&lt;/center&gt;<br /> | &lt;center&gt;URS 1D&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;9&lt;/center&gt;<br /> | &lt;center&gt;URS 1D&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;10&lt;/center&gt;<br /> | &lt;center&gt;URS 3D precomputed&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;11&lt;/center&gt;<br /> | &lt;center&gt;URS 3D precomputed&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;12&lt;/center&gt;<br /> | &lt;center&gt;URS 3D precomputed&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;13&lt;/center&gt;<br /> | &lt;center&gt;URS 3D precomputed&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;14&lt;/center&gt;<br /> | &lt;center&gt;URS 3D precomputed&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;15&lt;/center&gt;<br /> | &lt;center&gt;URS 3D precomputed&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;16&lt;/center&gt;<br /> | &lt;center&gt;URS 3D precomputed&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;17&lt;/center&gt;<br /> | &lt;center&gt;URS 3D precomputed&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;18&lt;/center&gt;<br /> | &lt;center&gt;URS 3D precomputed&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;19&lt;/center&gt;<br /> | &lt;center&gt;UCSB 1D&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;20&lt;/center&gt;<br /> | &lt;center&gt;UCSB 1D&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;21&lt;/center&gt;<br /> | &lt;center&gt;UCSB 1D&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;22&lt;/center&gt;<br /> | &lt;center&gt;UCSB 1D&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;23&lt;/center&gt;<br /> | &lt;center&gt;UCSB 1D&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;24&lt;/center&gt;<br /> | &lt;center&gt;UCSB 1D&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;25&lt;/center&gt;<br /> | &lt;center&gt;UCSB 1D&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;26&lt;/center&gt;<br /> | &lt;center&gt;UCSB 1D&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;27&lt;/center&gt;<br /> | &lt;center&gt;UCSB 1D&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;28&lt;/center&gt;<br /> | &lt;center&gt;SDSU 1D&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;29&lt;/center&gt;<br /> | &lt;center&gt;SDSU 1D&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;30&lt;/center&gt;<br /> | &lt;center&gt;SDSU 1D&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;31&lt;/center&gt;<br /> | &lt;center&gt;SDSU 1D&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;32&lt;/center&gt;<br /> | &lt;center&gt;SDSU 1D&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;33&lt;/center&gt;<br /> | &lt;center&gt;SDSU 1D&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;34&lt;/center&gt;<br /> | &lt;center&gt;SDSU 1D&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;35&lt;/center&gt;<br /> | &lt;center&gt;SDSU 1D&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;36&lt;/center&gt;<br /> | &lt;center&gt;SDSU 1D&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;37&lt;/center&gt;<br /> | &lt;center&gt;SDSU 3D precomputed&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;38&lt;/center&gt;<br /> | &lt;center&gt;SDSU 3D precomputed&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;39&lt;/center&gt;<br /> | &lt;center&gt;SDSU 3D precomputed&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;40&lt;/center&gt;<br /> | &lt;center&gt;SDSU 3D precomputed&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;41&lt;/center&gt;<br /> | &lt;center&gt;SDSU 3D precomputed&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;42&lt;/center&gt;<br /> | &lt;center&gt;SDSU 3D precomputed&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;43&lt;/center&gt;<br /> | &lt;center&gt;SDSU 3D precomputed&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;44&lt;/center&gt;<br /> | &lt;center&gt;SDSU 3D precomputed&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;45&lt;/center&gt;<br /> | &lt;center&gt;SDSU 3D precomputed&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> |}<br /> <br /> ==User-Defined Events==<br /> <br /> {| class=&quot;wikitable&quot; | border=&quot;1&quot;<br /> | Permutation #<br /> | Rupture generator<br /> | Low-frequency<br /> | High-frequency<br /> | Site response<br /> <br /> |-<br /> | &lt;center&gt;1&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;2&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;3&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;4&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;5&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;6&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;7&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;8&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;9&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;10&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;11&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;12&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;13&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;14&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;15&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;16&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;17&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;18&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;19&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;20&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;21&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;22&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;23&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;24&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;25&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;26&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;27&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;28&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;29&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;30&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;31&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;32&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;33&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;34&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;35&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;36&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;37&lt;/center&gt;<br /> | &lt;center&gt;User-supplied SRF&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;38&lt;/center&gt;<br /> | &lt;center&gt;User-supplied SRF&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;39&lt;/center&gt;<br /> | &lt;center&gt;User-supplied SRF&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;40&lt;/center&gt;<br /> | &lt;center&gt;User-supplied SRF&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;41&lt;/center&gt;<br /> | &lt;center&gt;User-supplied SRF&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;42&lt;/center&gt;<br /> | &lt;center&gt;User-supplied SRF&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;43&lt;/center&gt;<br /> | &lt;center&gt;User-supplied SRF&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;44&lt;/center&gt;<br /> | &lt;center&gt;User-supplied SRF&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;45&lt;/center&gt;<br /> | &lt;center&gt;User-supplied SRF&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;46&lt;/center&gt;<br /> | &lt;center&gt;User-supplied SRF&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;47&lt;/center&gt;<br /> | &lt;center&gt;User-supplied SRF&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;48&lt;/center&gt;<br /> | &lt;center&gt;User-supplied SRF&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;49&lt;/center&gt;<br /> | &lt;center&gt;User-supplied SRF&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;50&lt;/center&gt;<br /> | &lt;center&gt;User-supplied SRF&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;51&lt;/center&gt;<br /> | &lt;center&gt;User-supplied SRF&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;52&lt;/center&gt;<br /> | &lt;center&gt;User-supplied SRF&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;53&lt;/center&gt;<br /> | &lt;center&gt;User-supplied SRF&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;54&lt;/center&gt;<br /> | &lt;center&gt;User-supplied SRF&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> |}<br /> <br /> = Appendix B: Troubleshooting =<br /> If you experience trouble building the platform or successfully running test and simulations, try the following solutions.<br /> <br /> == Build Errors ==<br /> <br /> The instruction for installing Broadband Platform are listed in Section 1: &quot;Installing the Second-Generation Broadband Platform&quot; of the User guide. If after following all steps listed in this section of the user guide the build fails, check if the failure is listed in this section and try the solution to fix the issue you are facing.<br /> <br /> === 64-bit Intel Compiler Issue ===<br /> If you try to compile with:<br /> &lt;pre&gt;<br /> % cd bbp_2g/src<br /> % make<br /> &lt;/pre&gt; <br /> <br /> and you get:<br /> &lt;pre&gt;<br /> ... <br /> make[2]: Entering directory `.../bbp_2g/src/ucsb/getInFile'<br /> icc -o getfaultGlobal getfaultGlobal.c<br /> ld: cannot find -lgcc_s_32<br /> make[2]: *** [getfaultGlobal] Error 1<br /> make[2]: Leaving directory `.../bbp_2g/src/ucsb/getInFile'<br /> make[1]: *** [all] Error 2<br /> make[1]: Leaving directory `.../bbp_2g/src/ucsb'<br /> make: *** [all] Error 2<br /> &lt;/pre&gt;<br /> <br /> '''Cause:''' The Broadband Platform requires Intel 64-bit compilers to build successfully. In this case the 32-bit Intel compilers are being invoked as they are being picked up from the PATH environment variable. The error is due to a missing GNU-GCC 32-bit compatibility pack that has not been installed on your system. This is not required when 64-bit Intel compilers are used.<br /> <br /> '''Solution:''' Ensure that the path Intel 64-bit compilers are listed in you PATH variable and being picked up by running 'which icc' and 'which ifort'. If you are trying to build the platform on SCEC development servers like Intensity, verify your path variable has:<br /> &lt;pre&gt;<br /> PATH=...:/usr/usc/intel/composerxe-2011.4.191/mpirt/bin/intel64:/usr/usc/intel/composerxe-2011.4.191/bin/intel64<br /> &lt;/pre&gt;<br /> <br /> === 32-bit Platform Issue ===<br /> <br /> On trying to build the platform, the build fails with the following message:<br /> &lt;pre&gt;<br /> $ make all<br /> cd urs; make -f makefile FC=gfortran CC=icc USER_C=1;<br /> make[1]: Entering directory `.../bbp_2g/src/urs'<br /> mkdir -p bin;<br /> cd getpar/src; make -f Makefile CC=icc FC=gfortran USER_C=1;<br /> make[2]: Entering directory `.../bbp_2g/src/urs/getpar/src'<br /> icc -O3 -DENVIRONMENT -c -o defpar.o defpar.c<br /> icc -O3 -DENVIRONMENT -c -o getpar.o getpar.c<br /> icc -O3 -DENVIRONMENT -c -o getarg.o getarg.c<br /> getarg.c(112): warning #303: explicit type is missing (&quot;int&quot; assumed)<br /> register i;<br /> ^ <br /> icc -O3 -DENVIRONMENT -c -o getlocation.o getlocation.c<br /> getlocation.c(9): warning #147: declaration is incompatible with &quot;__ssize_t={int} getline(char **restrict, size_t={unsigned int} *restrict, FILE *restrict)&quot; (declared at line 671 of &quot;/usr/include/stdio.h&quot;)<br /> static int getline(FILE *fd, char *line)<br /> <br /> ...<br /> ...<br /> ...<br /> <br /> make[2]: Entering directory `.../bbp_2g/src/sdsu/srcV1.4'<br /> icc -w -Wall -c ray3DJHfor.c<br /> gfortran module_bbtoolbox.f90 module_interface.f90 main_bbtoolbox.f90 coda.f90 composition.f90 convolution.f90 fourier.f90 error.f90 geometry.f90 interpolation.f90 io.f90 random.f90 scattering.f90 source.f90 ray3DJHfor.o -o BBtoolbox.exe<br /> ray3DJHfor.o: In function `raytracing_':<br /> ray3DJHfor.c:(.text+0x8cf): undefined reference to `__libm_sse2_log'<br /> ray3DJHfor.c:(.text+0x96b): undefined reference to `__libm_sse2_asin'<br /> ray3DJHfor.c:(.text+0x9cd): undefined reference to `__libm_sse2_asin'<br /> ray3DJHfor.c:(.text+0xa00): undefined reference to `__libm_sse2_tan'<br /> ray3DJHfor.c:(.text+0xa3d): undefined reference to `__libm_sse2_tan'<br /> ray3DJHfor.c:(.text+0xa52): undefined reference to `__libm_sse2_log'<br /> collect2: ld returned 1 exit status<br /> make[2]: *** [BBtoolbox.exe] Error 1<br /> make[2]: Leaving directory `.../bbp_2g/src/sdsu/srcV1.4'<br /> make[1]: *** [all] Error 2<br /> make[1]: Leaving directory `.../bbp_2g/src/sdsu'<br /> make: *** [all] Error 2<br /> &lt;/pre&gt;<br /> <br /> '''Cause:''' In this case the user tried to build Broadband on a 32-bit platform. Broadband code was designed to be run on 64-bit platform. Any attempt to build Broadband on a 32-bit platform will result in numerous warnings and the build will fail with error messages similar to ones listed above.<br /> <br /> '''Solution:''' Try building Broadband on a 64-bit platform will the all the dependencies listed in Section 1.1: &quot;System Dependencies&quot; and Section 1.2: &quot;Software Dependencies&quot;<br /> <br /> == Unit/Acceptance Test Failures and Errors ==<br /> <br /> Unit and Acceptance tests are provided to verify the Broadband platform and it's supporting modules built by the user are functioning as designed. Under certain circumstances, some of these test might fail. While some of these failure might indicate serious problems that will have to be addressed before the platform can used, it is acceptable to ignore some of the failures. This section lists some failures and their solutions.<br /> <br /> === ERROR: test_syn1d (test_syn1d.Test_syn1D) ===<br /> The Unit test for Syn1d module fails with the following message:<br /> &lt;pre&gt;<br /> ERROR: test_syn1d (test_syn1d.Test_syn1D)<br /> ----------------------------------------------------------------------<br /> Traceback (most recent call last):<br /> File &quot;.../bbp_2g/tests/test_syn1d.py&quot;, line 62, in test_syn1d<br /> synObj.run()<br /> File &quot;.../bbp_2g/comps/syn1D.py&quot;, line 236, in run<br /> shutil.copy2(a_tmpfile, expected_file)<br /> File &quot;/usr/lib/python2.6/shutil.py&quot;, line 99, in copy2<br /> copyfile(src, dst)<br /> File &quot;/usr/lib/python2.6/shutil.py&quot;, line 52, in copyfile<br /> fsrc = open(src, 'rb')<br /> IOError: [Errno 2] No such file or directory: '.../bbp_2g/tmpdata/3310632/s01.3comp'<br /> &lt;/pre&gt;<br /> <br /> '''Cause:''' Syn1d module requires the Green's Function file to run and the path to this file might be incorrect in 'bbp_2g_gf/ucsb/GreenBank/Northridge/GreenBank.inf' file.<br /> <br /> '''Solution:''' This issue can be fixed by correcting the paths listed in the GreenBank.inf files in the Green's Function directory. Here are step by step instructions to fix this issue:<br /> <br /> 1. Locate your Greens Functions directory: 'bbp_2g_gf'<br /> 2. Navigate to bbp_2g_gf/ucsb/GreenBank/Northridge folder.<br /> 3. Open Green_Bank.inf files with a text editor.<br /> 4. Locate the text &quot;The name of file to store Green Bank&quot;<br /> 5. Note the location of the Green Bank file under the line found in step 4, similar to &quot;/home/scec-00/scottcal/bband/bbp_2g_gf/ucsb/GreenBank/Northridge/Green_1d.soil&quot;.<br /> 6. Replace the path found in Step 5 with just the file name, in the case of Northridge it is &quot;Green_1d.soil&quot;<br /> 7. Save and close the Green_Bank.inf.<br /> 8. Navigate to bbp_2g_gf/ucsb/GreenBank/LomaPrieta folder and repeat steps 3-7. The name of the Green Bank file for LomaPrieta is &quot;Green_1d.LoPr&quot;.<br /> 9. Navigate to bbp_2g_gf/ucsb/GreenBank/Landers folder and repeat steps 3-7. The name of the Green Bank file for Landers is &quot;Green1D.Landers&quot;<br /> <br /> === ERROR: test_gensrf (test_genslip.Test_Genslip) ===<br /> The Unit test for Genslip module fails with the following message:<br /> &lt;pre&gt;<br /> ======================================================================<br /> ERROR: test_gensrf (test_genslip.Test_Genslip)<br /> ----------------------------------------------------------------------<br /> Traceback (most recent call last):<br /> File &quot;.../bbp_2g/tests/test_genslip.py&quot;, line 51, in test_gensrf<br /> gen.run()<br /> File &quot;.../bbp_2g/comps/genslip.py&quot;, line 153, in run<br /> ps.run()<br /> File &quot;.../bbp_2g/comps/plot_srf.py&quot;, line 52, in run<br /> shutil.copy2(&quot;%s/%s.ps.png&quot; % (a_tmpdir, self.r_srffile[0:self.r_srffile.find(&quot;.srf&quot;)]), &quot;%s/%s.png&quot; % (a_outdir, self.r_srffile[0:self.r_srffile.find(&quot;.srf&quot;)]))<br /> File &quot;/usr/lib/python2.6/shutil.py&quot;, line 99, in copy2<br /> copyfile(src, dst)<br /> File &quot;/usr/lib/python2.6/shutil.py&quot;, line 52, in copyfile<br /> fsrc = open(src, 'rb')<br /> IOError: [Errno 2] No such file or directory: '.../bbp_2g/tmpdata/3309008/3309008_test_eq.ps.png'<br /> &lt;/pre&gt;<br /> <br /> '''Cause:''' The Genslip module calls the Plot_SRF module to the plot the SRF file. Plot_SRF uses C-shell code to locate and use GMT package to plot the SRF file. This shell code might fail on some flavors of Linux with a message like &quot;Newline in variable name&quot; in the Plot_SRF log file.<br /> <br /> '''Solution:''' This issue can be fixed by editing the plot_SRF.csh file. Here are step by step instructions to fix this issue:<br /> <br /> 1. Locate shell script file: bbp_2g/src/plot/plot_SRF.csh<br /> 2. Open the file in your preferred text editor<br /> 3. Locate the line 'set FIND_GMT = $?'<br /> 4. Replace the line found in step 3 with 'set FIND_GMT = $status'<br /> 5. Locate the section of code that starts with the statement &quot;# FIND MAX. SLIP&quot;<br /> 6. Replace the following line in section found in step 5:<br /> &lt;pre&gt;<br /> set SMAX = `$XYZCODE calc_xy=$CALC_XY type=&quot;${TYPE}&quot; nseg=-1 &lt; $SLIPFILE.srf | \<br /> gawk -v m=$SMAX '{if($3&gt;m)m=$3;}END{printf &quot;%.0f\n&quot;,m;}'`<br /> <br /> with (collapse the statement to a single line by removing '\' at the end of first part of the statement):<br /> <br /> set SMAX = `$XYZCODE calc_xy=$CALC_XY type=&quot;${TYPE}&quot; nseg=-1 &lt; $SLIPFILE.srf | gawk -v m=$SMAX '{if($3&gt;m)m=$3;}END{printf &quot;%.0f\n&quot;,m;}'`<br /> &lt;/pre&gt;<br /> 7. Save the file and exit<br /> <br /> === ERROR: test_ucgen (test_ucrmg.Test_UCrmg) ===<br /> The Unit test for Ucrmg module fails with the following message:<br /> &lt;pre&gt;<br /> ======================================================================<br /> ERROR: test_ucgen (test_ucrmg.Test_UCrmg)<br /> ----------------------------------------------------------------------<br /> Traceback (most recent call last):<br /> File &quot;.../bbp_2g/tests/test_ucrmg.py&quot;, line 59, in test_ucgen<br /> ucObj.run()<br /> File &quot;.../bbp_2g/comps/ucrmg.py&quot;, line 161, in run<br /> ps.run()<br /> File &quot;.../bbp_2g/comps/plot_srf.py&quot;, line 52, in run<br /> shutil.copy2(&quot;%s/%s.ps.png&quot; % (a_tmpdir, self.r_srffile[0:self.r_srffile.find(&quot;.srf&quot;)]), &quot;%s/%s.png&quot; % (a_outdir, self.r_srffile[0:self.r_srffile.find(&quot;.srf&quot;)]))<br /> File &quot;/usr/lib/python2.6/shutil.py&quot;, line 99, in copy2<br /> copyfile(src, dst)<br /> File &quot;/usr/lib/python2.6/shutil.py&quot;, line 52, in copyfile<br /> fsrc = open(src, 'rb')<br /> IOError: [Errno 2] No such file or directory: '.../bbp_2g/tmpdata/3309831/test_ucsb.ps.png'<br /> &lt;/pre&gt;<br /> <br /> '''Cause:''' The Ucrmg module calls the Plot_SRF module to the plot the SRF file. Plot_SRF uses C-shell code to locate and use GMT package to plot the SRF file. This shell code might fail on some flavors of Linux with a message like &quot;Newline in variable name&quot; in the Plot_SRF log file.<br /> <br /> '''Solution:''' This issue can be fixed by editing the plot_SRF.csh file. The steps to fix this issue are listed under the solution for &quot;ERROR: test_gensrf (test_genslip.Test_Genslip)&quot; above.<br /> <br /> === FAIL: test_site_amp (test_uc_site.Test_UC_Site) ===<br /> <br /> The unit test for UC-Site module might fail with the following message:<br /> &lt;pre&gt;<br /> ======================================================================<br /> FAIL: test_site_amp (test_uc_site.Test_UC_Site)<br /> ----------------------------------------------------------------------<br /> Traceback (most recent call last):<br /> File &quot;.../bbp_2g/tests/test_uc_site.py&quot;, line 92, in test_site_amp<br /> self.failIf(cmp_bbp.cmp_bbp(a_ref_file_no_header, test_file_no_header, tolerance=0.035)!=0,errmsg)<br /> AssertionError: Output file .../bbp_2g/tmpdata/3310633/s04.3comp does not match reference file .../bbp_2g/ref_data/ucsb/s04.site.3comp<br /> &lt;/pre&gt;<br /> <br /> '''Cause:''' The synthetic seismogram generated by the UC-Site module on the user system differs from the reference result included in the Broadband release.<br /> <br /> '''Solution:''' The stochastic nature of the high frequency simulations is considered, and a constant random seed as input for our tests. This is the same constant random seed used to generate the reference results included in the release. This ensures that the time-series generated with unit tests agree with reference results. However, the high frequency codes are more sensitive to changes in compilers and machines due to the algorithm, so small differences that cause the test to fail are generally acceptable. The user is however encouraged to plot the two time-series and visually inspect them to verify they look similar. We are trying to come up with a better comparison for these tests.<br /> <br /> = Appendix C: Technical Notes =<br /> <br /> == Running Individual Acceptance Tests ==<br /> <br /> The acceptance test script ./tests/AcceptTest.py attempts to run all of the defined tests when executed. However, sometimes it is useful to run an acceptance test in isolation for troubleshooting purposes:<br /> <br /> * Identify the test you want to run. Eg: user-URS-UCSB-SDSU-SDSU<br /> * Move to the ./comps directory and execute that test's XML workflow with run_bbp_2G.py. Using the above example:<br /> &lt;pre&gt;<br /> $ ./run_bbp_2G.py -x ../ref_data/accept_inputs/user-URS-UCSB-SDSU-SDSU.xml<br /> &lt;/pre&gt;<br /> <br /> Since you are running the test outside of AcceptTest.py, you will not see a PASS/FAIL message once the simulation completes. However, you can review the contents of the ./outdata/&lt;SIMID&gt; directory to verify that the correct seismograms and response spectra tables were produced.<br /> <br /> == Manaully Setting Random Number Generator Seed Values ==<br /> <br /> Several of the platform codebases employ random number generators to produce SRFs and seismograms. These random number generators are generally seeded with an initial value (typically an integer) which are hard-coded in the platform. Advanced users may desire to change these seed values.<br /> <br /> Changing the seeds for seismogram synthesis varies depending on which codebase you want to use:<br /> <br /> * URS: Edit ./comps/hfsims_cfg.py, Line 43 &quot;self.RAND_NUM&quot;<br /> * UCSB: Edit ./src/ucsb/Syn1DSCEC/syn1D_LAH.f, Line 183 &quot;iseed&quot;, and recompile with &quot;make&quot;<br /> * SDSU:<br /> ** User event: Edit ./bbp_2g_gf/sdsu/scattering_generic.dat (seed values annotated in file)<br /> ** Validation event: Edit ./bbp_2g_gf/sdsu/&lt;event&gt;/scattering.dat</div> Patrices https://strike.scec.org/scecwiki/index.php?title=Broadband_User_Guide_v11.2.3&diff=5057 Broadband User Guide v11.2.3 2012-05-08T22:05:06Z <p>Patrices: </p> <hr /> <div>'''Version 11.2.3.'''<br /> <br /> If you find errors in this document or sections to be unclear, please either fix them yourself or contact software@scec.org.<br /> <br /> = Installing the Second-Generation Broadband Platform =<br /> Installing the Broadband Platform involves obtaining a copy of the code and building the required executables. You can either download the platform from the Broadband web site ([http://www.scec.org/research/broadband http://www.scec.org/research/broadband]) or check the code out of SCEC's Subversion repository. Most users should download the platform.<br /> <br /> == System Dependencies ==<br /> The current version of the Broadband Platform is designed to run on standard 64-bit Linux machines. Testing has been performed on SCEC's development servers running Fedora Core 10 (kernel version 2.6.27.41-170.2.117.fc10.x86_64). In this guide we outline how to install the platform into your own account on a Linux computer using the simplest approach.<br /> <br /> == Software Dependencies ==<br /> The Broadband Platform has certain software dependencies.<br /> <br /> Required:<br /> <br /> *Python v2.7 with<br /> **PyGTK<br /> **Matplotlib<br /> **Numpy<br /> **Pyproj<br /> <br /> *Intel compilers (64-bit) v12.0.4<br /> *GNU compilers (gcc, gfortran) v4.5.1<br /> *GNU Fortran 77 v3.4.6<br /> *GMT (Generic Mapping Toolkit)<br /> *ImageMagick<br /> <br /> == Setting Up Your Account ==<br /> For simplicity of installation, we recommend users use a bash shell for the Broadband Platform account. It is possible to get the platform running using other shell's, but we will focus on a bash shell installation. The user environment is a common source of problems since certain environment variables must be defined for the platform to work correctly.<br /> <br /> To check your account, make sure you can run basic commands like ''ls'' and ''cd'' before proceeding.<br /> <br /> == Downloading the Platform ==<br /> &lt;nowiki&gt;Download 4 files from the Broadband website, the code (bbp_dist_&lt;version&gt;.tgz), the data (bbp_data_&lt;version&gt;.tgz), and their checksum files (bbp_dist_&lt;version&gt;.tgz.md5 and bbp_data_&lt;version&gt;.tgz.md5). &lt;/nowiki&gt;The code file is about 100 MB, the data file about 3 GB. After you've downloaded the files to your local Linux system, the next step is to calculate the checksums yourself and compare them to the checksums you downloaded.<br /> <br /> First, verify that the ''md5sum'' command is in your path:<br /> <br /> $&gt; which md5sum<br /> <br /> You should get something like /usr/bin/md5sum. If you see the message 'no md5sum in...', contact your Linux system administrator and ask to have md5sum added to your path.<br /> <br /> Once you can run the ''md5sum'' command, run:<br /> <br /> $&gt; md5sum -c bbp_dist_&lt;version&gt;.tgz.md5<br /> $&gt; md5sum -c bbp_data_&lt;version&gt;.tgz.md5<br /> <br /> You should get the messages<br /> bbp_dist_&lt;version&gt;.tgz.md5: OK<br /> bbp_data_&lt;version&gt;.tgz.md5: OK<br /> <br /> If you get FAILED instead, re-download the tgz files and try again. When it passes, that means the files were downloaded without error.<br /> <br /> Once both files have passed the checksum test, untar the files.<br /> <br /> $&gt; tar xzvf bbp_dist_&lt;version&gt;.tgz file<br /> $&gt; tar xzvf bbp_data_&lt;version&gt;.tgz file<br /> <br /> If multiple users are planning to use the platform on the same system, you only need one copy of the data files per machine. Each user will still need his or her own copy of the code files.<br /> <br /> Alternatively, if you would like access to the latest version of the platform and get frequent but less thoroughly tested improvements, you can check out the platform from SCEC's Subversion repository. Only advanced users should take this approach, outlined in detail in the [[#Advanced Users| Advanced Users section]].<br /> <br /> == User Account Setup ==<br /> <br /> The Broadband platform installation is divided into two parts (1) input Green Functions (GF) data directory (9.3Gb), and (2) BBP home directory (366Mb). <br /> <br /> First, the Green's function libraries are larger, but they are static. The broadband platform reads the data files, but does not change them. <br /> <br /> Second, the remainder of the broadband platform is organized in the BBP home directory. The BBP home directory has a specific directory structure that includes the source code for the scientific programs, the python scripts that link the scientific programs, simulation input directory, temporary and log file directories, and the output data directory where all the platform results are written.<br /> <br /> The BBP home directory will increase in size as you run the platform, because both output data and output log files are written to the home directory. Running the acceptance tests will produce nearly ( 10Gb) of input data (5.2Gb), output data (500Mb), temporary files (2.7Gb), and output log files (250Mb). Once these tests have passed much of this data can be removed. However, the BBP home directory should have at least 10Gb of disk space to insure the acceptance tests can be run when a particular broadband platform software distribution is first installed on a system.<br /> <br /> == Data Directory ==<br /> Input data files called Greens Functions are distributed with the platform. These files are generated using specific velocity structures, so they are often considered region specific. We have GF for three regions including near Loma Prieta, near Landers, and near Northridge.<br /> <br /> The data directory is static, and the data directories are read-only. A single copy can be installed in a shared disk, which can then be shared by multiple users.<br /> <br /> == Setting Environment Variables ==<br /> The BBP source codes and scripts are organized under the broadband platform home directory. The broadband platform home directory is specified in a couple of places during Broadband Platform installation. <br /> <br /> Internal to the Broadband platform software, all broadband platform files (except the Greens Function data files) are in sub-directories of the BBP home directory.<br /> <br /> == BBP Environment Variable ==<br /> We recommend setting both an alias and a environment variable to the BBP home directory. This will help avoid typing it many times.<br /> <br /> If you're running a Bash shell, add the following line to your .bash_profile with your favorite text editor:<br /> <br /> export BBP=/home/scec-00/kumar/bbp_2g<br /> <br /> If you're running a C-shell, add the following line to your .cshrc with your favorite text editor:<br /> <br /> setenv BBP /home/scec-00/kumar/bbp_2g<br /> <br /> * PYTHONPATH<br /> After you've obtained a copy of the project, you'll need to make sure the comps directory is on Python's path so Python can find all the project modules. If you're running a Bash shell, add the following line to your .bash_profile with your favorite text editor:<br /> <br /> export PYTHONPATH=$BBP/comps:$PYTHONPATH<br /> <br /> If you're running a C-shell, add the following line to your .cshrc with your favorite text editor:<br /> <br /> setenv PYTHONPATH $BBP/comps:$PYTHONPATH<br /> <br /> * PATH<br /> In order to successfully compile the project, you'll need to make sure the required compilers directories are in your PATH variable. Broadband requires Intel 64-bit compilers, icc and ifort and GNU Compilers, gcc, g77 and f77 to compile the scientific code.<br /> <br /> If you are planning to run Broadband on SCEC Development servers, make sure you have the following directories in your PATH:<br /> <br /> For Bash Shell (in .bash_profile)<br /> <br /> export PATH=/usr/usc/intel/composerxe-2011.4.191/bin/intel64:/usr/usc/intel/composerxe-2011.4.191/mpirt/bin/intel64:$PATH<br /> <br /> For C-shell (in .cshrc)<br /> <br /> setenv PATH /usr/usc/intel/composerxe-2011.4.191/bin/intel64:/usr/usc/intel/composerxe-2011.4.191/mpirt/bin/intel64:$PATH<br /> <br /> When running elements of the platform over ssh, be sure to enable ssh forwarding (with the -X or -Y options).<br /> <br /> After modifying your login script above, log out and log back into the machine so the changes are reflected in your environment.<br /> <br /> == Edit Install_cfg.py with Installation Directory Paths ==<br /> <br /> You need to tell the platform where it's installed by editing a single python file called &quot;install_cfg.py&quot;. Edit the file bbp_2g/comps/install_cfg.py with your favorite text editor, and edit the lines:<br /> <br /> self.A_INSTALL_ROOT = &lt;bbp_2g directory&gt;<br /> self.A_GF_DIR = &lt;bbp_2g_gf directory&gt;<br /> <br /> as one example:<br /> <br /> self.A_INSTALL_ROOT = /home/scec-00/kumar/bbp_2g<br /> self.A_GF_DIR = /home/scec-00/kumar/bbp_2g_gf<br /> <br /> with the paths on your system to the bbp_2g directory (the source) and the bbp_2g_gf directory (the data) that you unzipped. For example, it could be /home/scottcal/broadband_platform/bbp_2g and /home/scottcal/broadband_platform/bbp_2g_gf.<br /> <br /> Here is some information about these two directories that may be useful as you decide how, and where, to install these two parts of the Broadband Platform on your computer disk system. The data files, and therefore the &lt;bbp_2g_gf directory&gt; are nearly 3GB, but they are static and will not be modified and will not grow in size during use of the platform. The source directory is small to begin. However, this directory will increase as the platform is used, since the results produced by the platform will be stored here.<br /> <br /> == Directory Structure ==<br /> The platform consists of two top-level directories, bbp_2g and bbp_2g_gf. bbp_2g contains the source code, executables, scripts, tests, input, working, and output directories. bbp_2g_gf contains the Green's Functions, input files for the validation events, and other required input files for the various code bases. Note that indata, logs, outdata, tmpdata, and xml are created when the platform is first run, so they will be missing when you first install the platform.<br /> <br /> bbp_2g has the following directories:<br /> *checksums: Contains checksums for bbp_2g_gf files<br /> *comps: The Python scripts to run the platform<br /> *docs: Documentation for the platform<br /> *etc: Miscellaneous utility scripts<br /> *examples: Contains example input files<br /> *indata: An internal directory, used to stage input files<br /> *logs: Contains logs from BBP runs<br /> *outdata: Contains output files from a run<br /> *ref_data: Contains reference files for BBP tests<br /> *start: Put input files for an interactive run here<br /> *src: Source code for BBP modules<br /> *tests: Contains unit and acceptance tests<br /> *tmpdata: An internal directory, used during a run<br /> *xml: Contains XML files which describe simulations and can be used as input<br /> <br /> bbp_2g_gf has the following directories:<br /> *compare: Contains observed seismograms for validation events<br /> *plot: Data files for GMT plots<br /> *sdsu, ucsb, urs: Contains Green's functions, velocity files, and other required inputs for the codebases.<br /> <br /> In general, you will be interacting with the start directory for input files, comps to run the platform, tests to test the platform, and outdata to examine data products.<br /> <br /> === Adding aliases ===<br /> <br /> You may find it helpful to add aliases, so you can quickly and easily move to different broadband directories with a single command. We recommend creating aliases for the home, start, and outdata directories.<br /> <br /> If you are using the Bash shell, you can create aliases by adding the following lines to ~/.bash_profile:<br /> <br /> alias bbp= 'cd &lt;path to bbp_2g directory&gt;'<br /> alias start='cd &lt;path to bbp_2g directory&gt;/start'<br /> alias outdata='cd &lt;path to bbp_2g directory&gt;/outdata'<br /> <br /> If you're using a C shell, edit your ~/.cshrc and add:<br /> <br /> alias bbp cd &lt;path to bbp_2g directory&gt;<br /> alias start cd &lt;path to bbp_2g directory&gt;/start<br /> alias outdata cd &lt;path to bbp_2g directory&gt;/outdata<br /> <br /> Log out and log back in. You'll notice that now you can type the alias command as a shortcut to change directories:<br /> <br /> $&gt; pwd<br /> /home/scec-00/scottcal<br /> $&gt; start<br /> $&gt; pwd<br /> /home/scec-00/scottcal/bband/bbp_2g/start<br /> <br /> This can be a useful way to navigate around the broadband platform directories.<br /> <br /> == Building the Platform ==<br /> Once you have checked out the code, you need to build it. By default, every executable is compiled using the compiler recommended by the code developer. However, if you have limited compiler options or are building the codes on an untested system, you may need to specify non-standard alternative compilers, as described below.<br /> <br /> Before you can build the platform, you need to make sure that the Intel compilers are in your path. This is done automatically on broadband.usc.edu, but on other systems you can check by typing:<br /> <br /> $&gt;which icc<br /> <br /> If you get the message &quot;no icc in ...&quot;, then you'll need to add the Intel compilers to your path. Once the Intel compilers are in your path, you can make the code by cd-ing to the bbp_2g/src directory and typing make:<br /> <br /> $&gt; cd src<br /> $&gt; make<br /> <br /> It takes a minute or two to build the code. You may encounter build warnings; these are fine. However, if you get any build errors, this is a problem and should be investigated.<br /> <br /> By default, every executable is compiled using the compiler recommended by the code developer. Depending on the system, some compilers may not be available to you. You can override the C and Fortran compilers used by editing<br /> <br /> src/makefile<br /> <br /> Uncomment USER_C and set FC and CC to the compilers you wish. For example:<br /> <br /> Before:<br /> <br /> #USER_C=1<br /> FC=f77<br /> CC=gcc<br /> <br /> After (an example, you may choose different compilers):<br /> <br /> USER_C=1<br /> FC=gfortran<br /> CC=gcc<br /> <br /> Note that not all compiler combinations have been thoroughly tested. You may encounter build errors with untested compiler combinations. If you encounter any errors while building the platform, consult the Troubleshooting section at the end of this user guide for know issues and their solutions.<br /> <br /> Once the platform has been successfully built, you can move on to running the tests to verify that all components are working correctly.<br /> <br /> == Advanced Users ==<br /> Alternatively, if you would like access to the latest version of the platform, to get frequent but less thoroughly tested improvements, you can check out the platform from SCEC's Subversion version control repository on source.usc.edu. Only advanced users should follow this approach. If you are unsure, you should download the code as outlined in [[#Downloading the Platform|Downloading the Platform]] and skip this section.<br /> <br /> You may need to request access from the SCEC system administrator, John Yu ([mailto:johnyu@usc.edu johnyu@usc.edu]). Make sure you have subversion in your path before beginning.<br /> <br /> Once you have access, you'll need to decide if you want a stable tagged version, or the latest version in the repository. For a stable version, open a terminal window on the system of your choice and type:<br /> <br /> $&gt; svn checkout https://source.usc.edu/svn/broadband/tags/&lt;stable version&gt; bbp_2g<br /> <br /> For the latest version, type:<br /> <br /> $&gt; svn checkout https://source.usc.edu/svn/broadband/trunk bbp_2g<br /> <br /> This will check out the project to your local machine. It contains the source code, tests, and some example files. You also need to obtain a copy of the Broadband Platform data files, containing the Green's tensors. They are too large to be stored in version control. You can obtain a copy from SCEC software distribution server. If you are working on SCEC development server, you might be able to create a symbolic link to data folder. Please contact [[#User_Support|User Support]] to get a location of the data folder on the SCEC development server. If you are not working on SCEC development server, or don't have an SCEC Linux login account, you can get a archive (.tgz) file of the Green's functions from the same download site you obtained this guide.<br /> <br /> If you know where a read-accessible installation of the green functions data directories you can create a link to that location. This can save disk space in some cases.<br /> <br /> ln -s /home/scec-00/scottcal/bband/bbp_2g_gf &lt;path to your gf directory&gt;<br /> <br /> Periodically you should check for updates to the code. To do so, go to your bbp_2g directory and type<br /> <br /> $&gt; svn update<br /> <br /> This will pull down any code updates that have been made in the repository. After you update, make the code again (detailed in [[#Building the Platform|Building the Platform]]) so that any code changes are captured in the executables.<br /> <br /> == Running the Broadband Platform ==<br /> We recommend users initiate all Broadband Platform runs from the &quot;start&quot; directory. The start directory is a collection point for input files for a particular simulation.<br /> <br /> Assuming the user is starting at BBP home directory, the user should move to the start directory and then run the Checksum, Unit and Acceptance tests to confirm the Broadband Platform software installation is operating as expected.<br /> <br /> $&gt; cd start<br /> <br /> == Running Checksum, Unit, and Acceptance Tests ==<br /> The broadband platform contains three kinds of tests. The checksum tests verify that the data files were copied correctly and you have all the files that are expected. Unit tests run each module using a set of input files, and compare the results against known outputs. They verify that each module has been built and is working correctly. Acceptance tests verify that the modules are working correctly together. They test the platform end-to-end using different combinations with known inputs and compare the results. All the possible module combinations for both user-defined and validation events are tested as checks against integration errors.<br /> <br /> Begin with the checksum tests. Once they past, run the unit tests and finally the acceptance tests.<br /> <br /> == Running Checksum Tests ==<br /> To run the checksum tests, change to the checksums directory and run md5sum_check.py.<br /> <br /> From the BBP home directory:<br /> <br /> $&gt; cd checksums<br /> $&gt; ./md5sum_check.py<br /> <br /> It takes about 5 minutes to compute the checksums. If a checksum disagrees, that means that the contents of the datafile were not what was expected. Try reinstalling the data files and try again. If you continue to get a checksum error, contact support.<br /> <br /> Once the checksums agree, move on to the unit tests.<br /> <br /> == Running Unit Tests ==<br /> To run the unit tests, change to the tests directory and run UnitTests.py.<br /> <br /> From the BBP home directory:<br /> <br /> $&gt; cd tests<br /> $&gt; ./UnitTests.py<br /> <br /> The unit tests take about 15 minutes to run. When they're complete, the console will either print &quot;OK&quot; or how many tests failed. If a test has failed, first check that you have built the executables.You can rerun just the specific test that failed (test_&lt;module&gt;.py). If the test is still failing, also verify that you have the ref_data directory, since it contains the input and reference files. If you're looking for more information about the failure, you can consult the Unit Tests log file in bbp_2g/logs/unit_test.log . If you can't determine the reason for the failure, contact support.<br /> <br /> Once the unit tests all pass, proceed to the acceptance tests. If there are any failure or errors while running the unit tests, consult the Troubleshooting section at the end of this user guide for know issues and their solutions.<br /> <br /> == Running Acceptance Tests ==<br /> Make sure the unit tests pass before moving on to the acceptance tests. To run the acceptance tests, change to the tests directory (if you're not there already) and run AcceptTests.py. <br /> The acceptance tests take a long time to run, around 20 hours<br /> <br /> From the BBP home directory:<br /> <br /> $&gt; cd tests<br /> $&gt; ./AcceptTests.py &amp;&gt; accept.out &amp;<br /> <br /> Since the tests take so long to run (twenty hours), you should run them as a background process, and redirect their output to a log file, as shown in the command above.<br /> <br /> You can check the progress by tailing the log file.<br /> <br /> $&gt; tail accept.out<br /> <br /> When all the acceptance tests are completed, the AcceptTests.py script will either print &quot;OK&quot; or how many tests failed. <br /> <br /> Acceptance test failures indicate that the modules are not integrated correctly. Like with the unit tests, verify that you have the ref_data directory. If a certain acceptance test fails, you can get more information by consulting the acceptance test logs in bbp_2g/logs/acceptance_tests_logs/&lt;test that failed&gt;.log . If you can't determine the reason for the failure, contact [[support]].<br /> <br /> Since the acceptance tests can take a long time to run, you may wish to resume where you left off. This feature is supported automatically. If you do not wish to resume, delete the resume file in ref_data/accept_inputs/resume.txt. If there are any failure or errors while running the acceptance tests, consult the Troubleshooting section at the end of this user guide for know issues and their solutions.<br /> <br /> = Types of Broadband Platform Simulations =<br /> <br /> The platform supports two kinds of simulations, validation events and user-defined events. Validation simulations are performed using a historical event, and are directly compared to observed seismograms using goodness-of-fit. User-defined events are run using a rupture description provided by the user which may not necessarily be a historical earthquake.<br /> <br /> When you run a simulation, the platform assigns an ID to it. This ID can be used to track the simulation and locate the output data products.<br /> <br /> To supply input files to the platform, put them in the start directory. Extensions are important - the platform recognizes station lists (.stl), SRF files (.srf), and simple source descriptions (.src). If there are multiple files of a type, the platform will prompt the user to select one.<br /> <br /> To perform a simulation, a user selects between different required and optional modules. Below we present a summary of the various modules.<br /> <br /> = Modules =<br /> The broadband platform consists of a series of modules. There are two main types of modules, science modules and utility modules. Science modules are those for which the platform has multiple implementations, provided by different coding research groups. Utility modules only have 1 implementation. A schematic of the available modules and their flow relationships is shown below:<br /> <br /> == Science Modules ==<br /> All simulations must include a low-frequency, high-frequency, and site response science module. Simulations may include an optional rupture generation science module. Users may select between the following different implementations of each of these modules:<br /> <br /> Rupture generation:URS, UCSB<br /> <br /> Low-frequency:URS, UCSB<br /> <br /> High-frequency:URS, UCSB, SDSU<br /> <br /> Site response:URS, UCSB, SDSU<br /> <br /> == Utility Modules ==<br /> A spectral response utility module is automatically run after the site response module. Additionally, users may select an optional goodness-of-fit utility module to run at the conclusion of the simulation. In the case of a user-defined event, users select a historical event or previously run simulation to use as the comparison for goodness-of-fit.<br /> <br /> = Platform Directory =<br /> <br /> A broadband platform distribution is organized in a specific directory structure that separates the input data sets, the python scripts, the simulation configuration files, log files, and output data files.<br /> <br /> When running Broadband Platform simulations, standard procedure is to place the simulation input files in the start directory and invoke the Broadband platform scripts from there.<br /> <br /> From the BBP home directory:<br /> <br /> $&gt; cd start<br /> $&gt; run_bbp_2G.py<br /> <br /> Simulation output results will be written into the bbp_home/output<br /> <br /> = Validation Simulations =<br /> To run a validation simulation, go to the comps directory and run run_bbp_2G.py. The platform will ask you a series of questions. Answer 'y' to &quot;Do you want to perform a validation run?&quot;<br /> <br /> From the BBP home directory:<br /> <br /> $&gt; cd start<br /> $&gt; run_bbp_2G.py<br /> Welcome to the SCEC Broadband Platform.<br /> Please select the modules you want to run.<br /> Do you want to perform a validation run (y/n)? y<br /> Do you want to validate with:<br /> Northridge (1)<br /> Loma Prieta (2)<br /> Landers (3)<br /> ?<br /> ...<br /> <br /> No input files are required by the user. However, you may wish to run with a reduced station list to speed up the computations. You can put your own station list into the start directory (the format is described in [[#Station File List|section 5.3]]). Note that any stations which do not have observed seismograms will not be included in the automatically generated goodness-of-fit comparison.<br /> <br /> In addition to the low-frequency modules which compute seismograms using 1D Green's Tensors, validation events can also be run using precomputed 3D seismograms to supply the low-frequency.<br /> <br /> = User-defined Simulations =<br /> To run a user-defined simulation, two input files are required, a rupture description and a station list. The rupture description can either be in SRF format or a simplified source description (the format is described in [[#Simple source description|section 5.1]]). To run a user-defined simulation, run run_bbp_2G.py.<br /> <br /> From the BBP home directory:<br /> <br /> $&gt; cd start<br /> $&gt; run_bbp_2G.py<br /> Welcome to the SCEC Broadband Platform.<br /> Please select the modules you want to run.<br /> Do you want to perform a validation run (y/n)? y<br /> Do you want to run a rupture generator (y/n)? <br /> ...<br /> <br /> You may then choose if you want to run a rupture generator. This is necessary if you're supplying a simple rupture description. If you're supplying an SRF file, you can skip this. Next you can select from different module implementations. Finally, you have the option to run goodness-of-fit against either observed seismograms or another simulation.<br /> <br /> ...<br /> Do you want to run goodness of fit (y/n)? y<br /> What reference files would you like to compare to? Enter a simulation ID or a scenario name: &lt;comparison&gt;<br /> Enter a label to use for the comparison seismograms: &lt;label&gt;<br /> <br /> The label will be used in GoF plots to distinguish one set of results from the other.<br /> <br /> The user-defined events must be within one of the regions supported by the platform - Southern California, Northern California, or the Mojave. The platform will automatically select a region based on the event hypocenter. If the event falls outside of these regions, you'll get an error.<br /> <br /> = Logging =<br /> During the run, log files will be produced in logs/&lt;simulation ID&gt;/&lt;simulation ID&gt;.&lt;module name&gt;.log. If the platform fails, this is a good place to look to determine the error. Additionally, any fatal errors will be recorded in fatal_error.log.<br /> <br /> Metadata capturing all the executable calls is located in tmpdata/&lt;simulation ID&gt;/metadata.txt for careful tracing of exactly what was called. Both the log files and metadata can be useful if troubleshooting an issue.<br /> <br /> = Data Products =<br /> The platform produces a variety of data products. &lt;nowiki&gt;All data products are located in outdata/&lt;simulation ID&gt;. &lt;/nowiki&gt;On most Linux systems, you can show images using display:<br /> <br /> $&gt; display &lt;PNG file&gt;<br /> <br /> Make sure you have X11 forwarding enabled.<br /> <br /> == Station map ==<br /> To help visualize the stations in relationship to the fault, the platform produces a PNG file displaying station locations with red circles and the fault plane with a black line, on an image of California. You can find this file in outdata/&lt;simulation ID&gt;/station_map.png.<br /> <br /> == Seismograms ==<br /> When running the platform, you have the option to output velocity and acceleration seismograms, for each station. Plots of these files can be found in outdata/&lt;simulation ID&gt;/&lt;simulation ID&gt;.&lt;station&gt;_&lt;velocity or acceleration&gt;_seis.png.<br /> <br /> The raw seismogram data is available in outdata/&lt;simulation ID&gt;/&lt;simulation ID&gt;.&lt;station&gt;.vel.bbp (velocity) and outdata/&lt;simulation ID&gt;.&lt;station&gt;.acc.bbp (acceleration). Its format is described in [[#BBP seismograms|section 5.4]].<br /> <br /> To compare seismogram data, you can run comps/plotit.py with two seismograms. It will plot them both for comparison. From the comps directory, run:<br /> <br /> $&gt; plotit.py &lt;path to seismogram 1&gt; &lt;path to seismogram 2&gt;<br /> <br /> == Response spectra ==<br /> The respect code, run at the end of each simulation, calculates the response spectra for each station. The raw respect data is located at<br /> <br /> From the BBP home directory:<br /> <br /> outdata/&lt;simulation ID&gt;/&lt;simulation ID&gt;.&lt;station&gt;.rsp<br /> <br /> in the format described in [[#Response spectra|section 5.5]].<br /> <br /> == Goodness-of-fit ==<br /> If you run goodness-of-fit, several additional data products are produced. The goodness-of-fit comparison is performed by comparing the response spectra of a set of calculated seismograms to seismograms from another simulation or observed seismograms. For each station involved in the comparison, a plot comparing the response spectra can be found at outdata/&lt;simulation ID&gt;/&lt;comparison label&gt;_&lt;simulation ID&gt;_&lt;station&gt;_rsp.png. A plot showing the seismograms on top and bottom can be found at outdata/&lt;comparison label&gt;_&lt;simulation ID&gt;_&lt;station&gt;_overlay.png. The goodness-of-fit plot can be found at gof-&lt;comparison label&gt;-&lt;simulation ID&gt;_r0-&lt;cutoff distance&gt;.png.<br /> <br /> Note that at least 3 stations must be run for goodness-of-fit to be valid. If fewer than 3 stations are run, no goodness of fit calculation will be performed.<br /> <br /> == Rupture files ==<br /> When a user-defined event is simulated, the user has the option to run a rupture generator. This generator produces an SRF file, found in outdata/&lt;simulation ID&gt;/*.srf. This file can be put in the start directory and used in future runs. Additionally, the platform produces a plot of the cumulative slip on the fault surface, outdata/&lt;simulation ID&gt;/&lt;SRF prefix&gt;.png.<br /> <br /> = Platform Modes =<br /> The platform can be run in multiple modes. The default is interactive mode, in which the user is prompted to answer a series of questions. Once all the information has been gathered, the run begins.<br /> <br /> For a large number of runs, or if the user is repeating a specific run, this can be tedious. The platform provides two other ways to describe a run, with an option file or an XML description.<br /> <br /> An option file provides responses to all the questions that the platform poses. The format is described in [[#Option File|section 5.6]], but it's basically a text file, 1 entry per line, with support for comments. It can be fed to the platform using the -o option.<br /> <br /> The platform will also accept XML files containing a full description of a run. The schema for these files is given in [[#XML workflow description schema|section 5.7]]. These files are also produced by the platform after every simulation, and placed in xml/&lt;simulation ID&gt;.xml. So if you want to rerun a simulation, you can point the platform to the XML file from that simulation using the -x option. Note that a new simulation ID will be assigned to the run, so there is no risk of overwriting previous simulation results.<br /> <br /> = Available Options =<br /> To get a list of the current available options, run run_bbp_2G.py with the -h flag.<br /> <br /> $&gt; run_bbp_2G.py -h<br /> Usage: run_bbp_2G.py [options]<br /> Options:<br /> -h, --help Show this help message and exit<br /> -x XML_FILE, --xml-file=XML_FILE Run using XML description of workflow<br /> -s SIM_ID, --simID=SIM_ID Force a simID<br /> -o OPTFILE, --option-file=OPTFILE File containing responses to interactive platform prompts<br /> -v, --version Broadband platform version<br /> -c, --compact Compact output results. Remove temporary files for simulations that complete successfully.<br /> -g, --generate-xml Generates the XML description but does not run the platform<br /> -l LOG_FILE, --log=LOG_FILE Store all output in a file<br /> <br /> = Cleanup =<br /> After a while, you may find that your indata, tmpdata, outdata, and logs directories are getting cluttered with files from past runs. If you wish to delete these old files, you can use the clean_directories.sh script in the etc directory.<br /> <br /> From the BBP home directory:<br /> <br /> $&gt; cd etc<br /> $&gt; ./clean_directories &lt;days&gt;<br /> <br /> Any simulation ID directories in the indata, tmpdata, outdata, and logs directories which were last accessed &lt;days&gt; days or longer ago will be deleted. If you have a few directories you want to keep, either copy them somewhere else, or copy them to a directory name that's not all digits and they won't be deleted.<br /> <br /> = Examples =<br /> Below are some examples that you can try using the sample files in the examples directory. Make sure all the tests pass before you try this. You should be in the comps directory when you start these examples:<br /> <br /> From the BBP home directory:<br /> <br /> $&gt; cd comps<br /> <br /> == Sample Validation Run ==<br /> You don't need to move any files for this. Notice that 3D seismograms are a low-frequency option, since you're running a validation event.<br /> <br /> From the BBP home directory:<br /> <br /> $&gt; cd start<br /> $&gt; run_bbp_2G.py <br /> Welcome to the SCEC Broadband Platform.<br /> Please select the modules you want to run.<br /> Do you want to perform a validation run (y/n)? y<br /> Do you want to validate with:<br /> Northridge (1)<br /> Loma Prieta (2)<br /> Landers (3)<br /> ?1<br /> Do you want to<br /> run all validation stations (1)<br /> select a station list (2)<br /> ?1<br /> Choose a source of low frequency seismograms:<br /> URS module (1)<br /> URS 3D seismograms (2)<br /> UCSB module (3)<br /> SDSU module (4)<br /> SDSU 3D seismograms (5)<br /> ?2<br /> Choose a high frequency module:<br /> URS (1)<br /> UCSB (2)<br /> SDSU (3)<br /> ?1<br /> Choose a site response module:<br /> URS (1)<br /> UCSB (2)<br /> SDSU (3)<br /> ?1<br /> Do you want to plot velocity seismograms (y/n)? y<br /> Do you want to plot acceleration seismograms (y/n)? y<br /> <br /> This simulation takes about 10 minutes. Once it's complete the platform will tell you:<br /> <br /> You can find results in &lt;path to bbp_2g install&gt;/outdata/&lt;simulation ID&gt; .<br /> <br /> In that directory you will find:<br /> <br /> *Velocity seismograms (&lt;simulation ID&gt;.&lt;station&gt;.bbp)<br /> *Acceleration seismograms (&lt;simulation ID&gt;.&lt;station&gt;.acc.bbp)<br /> *Plots of velocity seismograms (&lt;simulation ID&gt;.&lt;station&gt;_velocity_seis.png)<br /> *Plots of acceleration seismograms (&lt;simulation ID&gt;.&lt;station&gt;_acceleration_seis.png)<br /> *Response spectra files (&lt;simulation ID&gt;.&lt;station&gt;.rsp)<br /> *Plots comparing simulated and observed seismograms (Northridge_&lt;simulation ID&gt;_&lt;station&gt;_overlay.png)<br /> *Plots comparing simulated and observed response spectra (Northridge_&lt;simulation ID&gt;_&lt;station&gt;_rsp.png)<br /> *Overall goodness-of-fit plots (gof-Northridge-&lt;simulation ID&gt;_r0-25.png)<br /> <br /> == Sample Validation run, custom stations ==<br /> If the validation runs aren't performed with 3D low-frequency, it can take a long time, up to 10 minutes per station. Sometimes you might want to run with a reduced station list so the simulation will run faster.<br /> <br /> Copy the files in example/valid_custom_stations into the start directory. Take a look at the format of the station file:<br /> <br /> $&gt; more valid_test_stat.stl <br /> #Required: lon, lat, station name, distance to fault plane, Vs30<br /> #Optional: low freq corner, high freq corner<br /> #Unused: station information<br /> #lon lat stationdist Vs30 LF corner HF corner station information<br /> -118.6417 34.5640 cast 20.47 450 0.120 23.0 CSMIP peer.berkeley.edu/nga<br /> -118.4180 34.0628 lacn 22.82 278 0.140 23.0 CSMIP peer.berkeley.edu/nga<br /> -118.8811 34.2886 moor 24.16 405 0.160 23.0 CSMIP peer.berkeley.edu/nga<br /> <br /> Now, run the platform, using a station list:<br /> <br /> From the BBP Home directory<br /> <br /> $&gt; cd start<br /> $&gt; run_bbp_2G.py <br /> Welcome to the SCEC Broadband Platform.<br /> Please select the modules you want to run.<br /> Do you want to perform a validation run (y/n)? y<br /> Do you want to validate with:<br /> Northridge (1)<br /> Loma Prieta (2)<br /> Landers (3)<br /> ?1<br /> Do you want to<br /> run all validation stations (1)<br /> select a station list (2)<br /> ?2<br /> <br /> If you have multiple station list files in your start directory, you may see the following prompt asking you to select one. If you only have one, the platform will select it automatically.<br /> <br /> Found multiple BBP station list files in the start directory. Please select one:<br /> nr_one_stat.stl (1)<br /> valid_test_stat.stl (2)<br /> ?2<br /> Choose a source of low frequency seismograms:<br /> URS module (1)<br /> URS 3D seismograms (2)<br /> UCSB module (3)<br /> SDSU module (4)<br /> SDSU 3D seismograms (5)<br /> ?3<br /> Choose a high frequency module:<br /> URS (1)<br /> UCSB (2)<br /> SDSU (3)<br /> ?2<br /> Choose a site response module:<br /> URS (1)<br /> UCSB (2)<br /> SDSU (3)<br /> ?2<br /> Do you want to plot velocity seismograms (y/n)? y<br /> Do you want to plot acceleration seismograms (y/n)? y<br /> <br /> Again, when the run completes in about 15 minutes you can find results in the output directory. You'll notice far fewer files, as only 3 stations were run instead of 133. The goodness-of-fit plots won't look very good - more stations are really needed to get an accurate plot.<br /> <br /> == Sample User-defined run with source description ==<br /> Next let's try running a user-defined event. Copy examples/user_rup_gen/nr_one_stat.stl and examples/user_rup_gen/user_eq.src to the start directory. user_eq.src is a simple source description. Its format is outlined in [[#XML workflow description schema|section 5.1]]. Since this is a user-defined event, precomputed 3D seismograms aren't a valid option.<br /> <br /> $&gt; run_bbp_2G.py <br /> Welcome to the SCEC Broadband Platform.<br /> Please select the modules you want to run.<br /> Do you want to perform a validation run (y/n)? n<br /> Do you want to run a rupture generator (y/n)? y<br /> Rupture generators:<br /> URS (1)<br /> UCSB (2)<br /> ?1<br /> Using region: Southern California<br /> Choose a low frequency module:<br /> URS (1)<br /> UCSB (2)<br /> ?2<br /> Found multiple BBP station list files in the start directory. Please select one:<br /> nr_one_stat.stl (1)<br /> valid_test_stat.stl (2)<br /> ?1<br /> Choose a high frequency module:<br /> URS (1)<br /> UCSB (2)<br /> SDSU (3)<br /> ?2<br /> Choose a site response module:<br /> URS (1)<br /> UCSB (2)<br /> SDSU (3)<br /> ?1<br /> Do you want to plot velocity seismograms (y/n)? y<br /> Do you want to plot acceleration seismograms (y/n)? y<br /> Do you want to run goodness of fit (y/n)? n<br /> <br /> Since this run only includes one station, it will run in about 5 minutes. In the output directory you'll notice there are no goodness-of-fit or files, since we didn't run goodness-of-fit. However, there is also a map file (station_map.png), showing the fault plane and the stations, and a plot of the rupture slip (user_eq.png). The SRF generated by the rupture generator is in user_eq.srf; this file could be used in future runs. The filenames of the rupture slip plot and SRF are taken from the rupture description filename.<br /> <br /> == Sample User-defined run with SRF file and goodness-of-fit ==<br /> Finally, try a run with an SRF file and run goodness-of-fit on the results. Copy in examples/user_no_rup_gen/ucsb_modSRF_0.srf and examples/user_no_rup_gen/nr_three_stat.stl<br /> <br /> $&gt; run_bbp_2G.py <br /> Welcome to the SCEC Broadband Platform.<br /> Please select the modules you want to run.<br /> Do you want to perform a validation run (y/n)? n<br /> Do you want to run a rupture generator (y/n)? n<br /> Using region: Southern California<br /> Choose a low frequency module:<br /> URS (1)<br /> UCSB (2)<br /> ?1<br /> Found multiple BBP station list files in the start directory. Please select one:<br /> nr_one_stat.stl (1)<br /> valid_test_stat.stl (2)<br /> nr_three_stat.stl (3)<br /> ?3<br /> Choose a high frequency module:<br /> URS (1)<br /> UCSB (2)<br /> SDSU (3)<br /> ?3<br /> Choose a site response module:<br /> URS (1)<br /> UCSB (2)<br /> SDSU (3)<br /> ?1<br /> Do you want to plot velocity seismograms (y/n)? y<br /> Do you want to plot acceleration seismograms (y/n)? y<br /> Do you want to run goodness of fit (y/n)? y<br /> What reference files would you like to compare to? Enter a simulation ID or a scenario name: Northridge<br /> Enter a label to use for the comparison seismograms: nr<br /> <br /> The reference files can either be a scenario event or a simulation ID previously run. The label is just for the figures when comparisons are plotted.<br /> <br /> This run will take about 15 minutes, and the results can be found in the appropriate outdir. Again, the goodness of fit measures will look poor due to the few stations involved in the comparison. If you had fewer than 3 stations, no goodness-of-fit plots would be produced. However, response spectra comparison plots will still be generated.<br /> <br /> = File Formats =<br /> This section offers descriptions of various file formats in the broadband platform.<br /> <br /> == Simple source description ==<br /> This is the format for the simple source description. It is not whitespace sensitive. The filename must end in .src for the platform to identify it as a source description.<br /> <br /> MAGNITUDE = &lt;magnitude&gt;<br /> FAULT_LENGTH = &lt;length of fault&gt;<br /> DLEN = &lt;DX, along length&gt;<br /> FAULT_WIDTH = &lt;down-dip fault width&gt;<br /> DWID = &lt;DY, along width&gt;<br /> DEPTH_TO_TOP = &lt;depth of fault below surface&gt;<br /> STRIKE = &lt;nowiki&gt;&lt;strike&gt;&lt;/nowiki&gt;<br /> RAKE = &lt;rake&gt;<br /> DIP = &lt;dip&gt;<br /> LAT_TOP_CENTER = &lt;latitude of top center point in fault plane&gt;<br /> LON_TOP_CENTER = &lt;longitude of top center point in fault plane&gt;<br /> HYPO_ALONG_STK = &lt;along strike location of hypocenter (0.0 = middle)&gt;<br /> HYPO_DOWN_DIP = &lt;down dip location of hypocenter (0.0 = top)&gt;<br /> DT = &lt;nowiki&gt;&lt;dt&gt;&lt;/nowiki&gt;<br /> SEED = &lt;random seed used in calculations&gt;<br /> CORNER_FREQ = &lt;corner frequency to use&gt;<br /> <br /> == SRF rupture description ==<br /> Details of the Standard Rupture Format (SRF) are given in more detail in the accompanying document. The general fault surface is represented by a distribution of point sources, and it can support one or more planes. The platform produces SRFs as output from rupture generators, but a user can also supply an SRF file as input for user-defined simulations. SRF filenames must end with the suffix .srf for the platform to correctly identify them.<br /> <br /> == Station File List ==<br /> The user may specify a list of stations, matching the following format:<br /> <br /> #optional<br /> %comment<br /> # lines<br /> &lt;nowiki&gt;&lt;lon&gt; &lt;lat&gt; &lt;stat name&gt; &lt;distance to fault trace&gt; &lt;Vs30&gt; &lt;LF corner&gt; &lt;HF corner&gt; &lt;stat info&gt;&lt;/nowiki&gt;<br /> ...<br /> <br /> The station list filename needs to end in .stl for the platform to recognize it as a station list.<br /> <br /> == BBP seismograms ==<br /> All intermediate and output seismograms are produced in a 4-column text format, whether velocity or acceleration.<br /> <br /> # optional<br /> % comment<br /> # lines<br /> &lt;nowiki&gt;&lt;timestamp&gt; &lt;North/South&gt; &lt;East/West&gt; &lt;Up/Down&gt;&lt;/nowiki&gt;<br /> ...<br /> <br /> Time is in seconds and motion is in cm/s (velocity) or cm/s/s (acceleration) unless otherwise specified in the header. Velocity filenames end in .vel.bbp; accelerations in .acc.bbp.<br /> <br /> == Response spectra ==<br /> The response spectra file is in 4-column text format.<br /> <br /> # optional<br /> % comment<br /> # lines<br /> &lt;nowiki&gt;&lt;period (sec)&gt; &lt;North/South&gt; &lt;East/West&gt; &lt;Up/Down&gt;&lt;/nowiki&gt;<br /> ...<br /> <br /> The platform samples response spectra at 112 periods, 0.01-20 sec and outputs pseudo spectral acceleration in units of g.<br /> <br /> == Option File ==<br /> Option files contain responses to the prompts in the platform. You can use them with the -o option to run_bbp_2G.py. The responses have to match the prompts exactly. For example, if you craft an option file assuming there is only one station list in the start directory (and therefore the user isn't prompted to select one) but then it is run with multiple station lists in the start directory, this will cause the run to abort. Option files are recommended to perform a series of runs with different inputs or different modules. If you have a run you perform regularly, it's better practice to run the platform with the -g option and the option file to produce an XML description, which are more complete descriptions of the workflow.<br /> <br /> #optional comments<br /> %using either symbol<br /> n #comments<br /> y % can go<br /> 1 # here<br /> ...<br /> <br /> Use with:<br /> <br /> $&gt; run_bbp_2G.py -o &lt;option file&gt;<br /> <br /> == XML workflow description schema ==<br /> Each time the platform is invoked, an XML file is produced describing the workflow, obeying the following schema:<br /> <br /> &lt;nowiki&gt;&lt;xs:schema xmlns:xs=&quot;http://www.w3.org/2001/XMLSchema&quot;&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:element name= &quot;BBP_Run_Specification&quot; minOccurs= &quot;1&quot; maxOccurs= &quot;1&quot;&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:attribute name=&quot;version&quot; type = &quot;xs:string&quot; use = &quot;required&quot; /&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:complexType&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:sequence&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:element name= &quot;Validation_Run&quot; minOccurs= &quot;0&quot; maxOccurs = &quot;1&quot;&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:attribute name= &quot;event&quot; type= &quot;xs:string&quot; use= &quot;required&quot; /&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:attribute name= &quot;input_station_file&quot; type = &quot;xs:string&quot; /&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:attribute name= &quot;subset&quot; type = &quot;xs:boolean&quot; use = &quot;required&quot; /&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;/xs:element&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:element name= &quot;BBP_Modules&quot;&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:complexType&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:sequence&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:element name = &quot;BBP_Module&quot; maxOccurs = &quot;unbounded&quot; &gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:complexType&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:sequence&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:element name= &quot;name&quot; type=&quot;xs:string&quot; /&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:element name= &quot;staged_files&quot; &gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:complexType&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:sequence&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:element name=&quot;file&quot; type=&quot;xs:string&quot; maxOccurs= &quot;unbounded&quot;/&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;/xs:sequence&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;/xs:complexType&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;/xs:element&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:element name= &quot;arguments&quot; &gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:complexType&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:sequence&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:element name=&quot;argument&quot; type=&quot;xs:string&quot; maxOccurs=&quot;unbounded&quot;&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:attribute name= &quot;type&quot; type= &quot;xs:string&quot; user= &quot;required&quot; /&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;/xs:element&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;/xs:sequence&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;/xs:complexType&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;/xs:element&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;/xs:sequence&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;/xs:complexType&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;/xs:element&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;/xs:sequence&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;/xs:complexType&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;/xs:element&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;/xs:sequence&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;/xs:complexType&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;/xs:element&gt;&lt;/nowiki&gt;<br /> <br /> These files are difficult to construct by hand, but can be generated using the -g flag when running run_bbp_2G.py.<br /> <br /> = User Support =<br /> If you run into bugs with the platform, you can open a trouble ticket at the [http://northridge.usc.edu/trac/broadband Broadband Trac site].<br /> <br /> Check to see if there has already been a ticket opened for the bug. If you are unable to get the platform to run, you can get direct user support by emailing [mailto:software@intensity.usc.edu software@intensity.usc.edu].<br /> <br /> = Appendix A: Possible Module Permutations =<br /> == Validation Events ==<br /> <br /> {| class=&quot;wikitable&quot; | border=&quot;1&quot;<br /> | Permutation #<br /> | Low-frequency module<br /> | High-frequency module<br /> | Site response<br /> <br /> |-<br /> | &lt;center&gt;1&lt;/center&gt;<br /> | &lt;center&gt;URS 1D&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;2&lt;/center&gt;<br /> | &lt;center&gt;URS 1D&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;3&lt;/center&gt;<br /> | &lt;center&gt;URS 1D&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;4&lt;/center&gt;<br /> | &lt;center&gt;URS 1D&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;5&lt;/center&gt;<br /> | &lt;center&gt;URS 1D&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;6&lt;/center&gt;<br /> | &lt;center&gt;URS 1D&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;7&lt;/center&gt;<br /> | &lt;center&gt;URS 1D&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;8&lt;/center&gt;<br /> | &lt;center&gt;URS 1D&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;9&lt;/center&gt;<br /> | &lt;center&gt;URS 1D&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;10&lt;/center&gt;<br /> | &lt;center&gt;URS 3D precomputed&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;11&lt;/center&gt;<br /> | &lt;center&gt;URS 3D precomputed&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;12&lt;/center&gt;<br /> | &lt;center&gt;URS 3D precomputed&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;13&lt;/center&gt;<br /> | &lt;center&gt;URS 3D precomputed&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;14&lt;/center&gt;<br /> | &lt;center&gt;URS 3D precomputed&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;15&lt;/center&gt;<br /> | &lt;center&gt;URS 3D precomputed&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;16&lt;/center&gt;<br /> | &lt;center&gt;URS 3D precomputed&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;17&lt;/center&gt;<br /> | &lt;center&gt;URS 3D precomputed&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;18&lt;/center&gt;<br /> | &lt;center&gt;URS 3D precomputed&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;19&lt;/center&gt;<br /> | &lt;center&gt;UCSB 1D&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;20&lt;/center&gt;<br /> | &lt;center&gt;UCSB 1D&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;21&lt;/center&gt;<br /> | &lt;center&gt;UCSB 1D&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;22&lt;/center&gt;<br /> | &lt;center&gt;UCSB 1D&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;23&lt;/center&gt;<br /> | &lt;center&gt;UCSB 1D&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;24&lt;/center&gt;<br /> | &lt;center&gt;UCSB 1D&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;25&lt;/center&gt;<br /> | &lt;center&gt;UCSB 1D&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;26&lt;/center&gt;<br /> | &lt;center&gt;UCSB 1D&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;27&lt;/center&gt;<br /> | &lt;center&gt;UCSB 1D&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;28&lt;/center&gt;<br /> | &lt;center&gt;SDSU 1D&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;29&lt;/center&gt;<br /> | &lt;center&gt;SDSU 1D&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;30&lt;/center&gt;<br /> | &lt;center&gt;SDSU 1D&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;31&lt;/center&gt;<br /> | &lt;center&gt;SDSU 1D&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;32&lt;/center&gt;<br /> | &lt;center&gt;SDSU 1D&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;33&lt;/center&gt;<br /> | &lt;center&gt;SDSU 1D&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;34&lt;/center&gt;<br /> | &lt;center&gt;SDSU 1D&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;35&lt;/center&gt;<br /> | &lt;center&gt;SDSU 1D&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;36&lt;/center&gt;<br /> | &lt;center&gt;SDSU 1D&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;37&lt;/center&gt;<br /> | &lt;center&gt;SDSU 3D precomputed&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;38&lt;/center&gt;<br /> | &lt;center&gt;SDSU 3D precomputed&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;39&lt;/center&gt;<br /> | &lt;center&gt;SDSU 3D precomputed&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;40&lt;/center&gt;<br /> | &lt;center&gt;SDSU 3D precomputed&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;41&lt;/center&gt;<br /> | &lt;center&gt;SDSU 3D precomputed&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;42&lt;/center&gt;<br /> | &lt;center&gt;SDSU 3D precomputed&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;43&lt;/center&gt;<br /> | &lt;center&gt;SDSU 3D precomputed&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;44&lt;/center&gt;<br /> | &lt;center&gt;SDSU 3D precomputed&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;45&lt;/center&gt;<br /> | &lt;center&gt;SDSU 3D precomputed&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> |}<br /> <br /> ==User-Defined Events==<br /> <br /> {| class=&quot;wikitable&quot; | border=&quot;1&quot;<br /> | Permutation #<br /> | Rupture generator<br /> | Low-frequency<br /> | High-frequency<br /> | Site response<br /> <br /> |-<br /> | &lt;center&gt;1&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;2&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;3&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;4&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;5&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;6&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;7&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;8&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;9&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;10&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;11&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;12&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;13&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;14&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;15&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;16&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;17&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;18&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;19&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;20&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;21&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;22&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;23&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;24&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;25&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;26&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;27&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;28&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;29&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;30&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;31&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;32&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;33&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;34&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;35&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;36&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;37&lt;/center&gt;<br /> | &lt;center&gt;User-supplied SRF&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;38&lt;/center&gt;<br /> | &lt;center&gt;User-supplied SRF&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;39&lt;/center&gt;<br /> | &lt;center&gt;User-supplied SRF&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;40&lt;/center&gt;<br /> | &lt;center&gt;User-supplied SRF&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;41&lt;/center&gt;<br /> | &lt;center&gt;User-supplied SRF&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;42&lt;/center&gt;<br /> | &lt;center&gt;User-supplied SRF&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;43&lt;/center&gt;<br /> | &lt;center&gt;User-supplied SRF&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;44&lt;/center&gt;<br /> | &lt;center&gt;User-supplied SRF&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;45&lt;/center&gt;<br /> | &lt;center&gt;User-supplied SRF&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;46&lt;/center&gt;<br /> | &lt;center&gt;User-supplied SRF&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;47&lt;/center&gt;<br /> | &lt;center&gt;User-supplied SRF&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;48&lt;/center&gt;<br /> | &lt;center&gt;User-supplied SRF&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;49&lt;/center&gt;<br /> | &lt;center&gt;User-supplied SRF&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;50&lt;/center&gt;<br /> | &lt;center&gt;User-supplied SRF&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;51&lt;/center&gt;<br /> | &lt;center&gt;User-supplied SRF&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;52&lt;/center&gt;<br /> | &lt;center&gt;User-supplied SRF&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;53&lt;/center&gt;<br /> | &lt;center&gt;User-supplied SRF&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;54&lt;/center&gt;<br /> | &lt;center&gt;User-supplied SRF&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> |}<br /> <br /> = Appendix B: Troubleshooting =<br /> If you experience trouble building the platform or successfully running test and simulations, try the following solutions.<br /> <br /> == Build Errors ==<br /> <br /> The instruction for installing Broadband Platform are listed in Section 1: &quot;Installing the Second-Generation Broadband Platform&quot; of the User guide. If after following all steps listed in this section of the user guide the build fails, check if the failure is listed in this section and try the solution to fix the issue you are facing.<br /> <br /> === 64-bit Intel Compiler Issue ===<br /> If you try to compile with:<br /> &lt;pre&gt;<br /> % cd bbp_2g/src<br /> % make<br /> &lt;/pre&gt; <br /> <br /> and you get:<br /> &lt;pre&gt;<br /> ... <br /> make[2]: Entering directory `.../bbp_2g/src/ucsb/getInFile'<br /> icc -o getfaultGlobal getfaultGlobal.c<br /> ld: cannot find -lgcc_s_32<br /> make[2]: *** [getfaultGlobal] Error 1<br /> make[2]: Leaving directory `.../bbp_2g/src/ucsb/getInFile'<br /> make[1]: *** [all] Error 2<br /> make[1]: Leaving directory `.../bbp_2g/src/ucsb'<br /> make: *** [all] Error 2<br /> &lt;/pre&gt;<br /> <br /> '''Cause:''' The Broadband Platform requires Intel 64-bit compilers to build successfully. In this case the 32-bit Intel compilers are being invoked as they are being picked up from the PATH environment variable. The error is due to a missing GNU-GCC 32-bit compatibility pack that has not been installed on your system. This is not required when 64-bit Intel compilers are used.<br /> <br /> '''Solution:''' Ensure that the path Intel 64-bit compilers are listed in you PATH variable and being picked up by running 'which icc' and 'which ifort'. If you are trying to build the platform on SCEC development servers like Intensity, verify your path variable has:<br /> &lt;pre&gt;<br /> PATH=...:/usr/usc/intel/composerxe-2011.4.191/mpirt/bin/intel64:/usr/usc/intel/composerxe-2011.4.191/bin/intel64<br /> &lt;/pre&gt;<br /> <br /> === 32-bit Platform Issue ===<br /> <br /> On trying to build the platform, the build fails with the following message:<br /> &lt;pre&gt;<br /> $ make all<br /> cd urs; make -f makefile FC=gfortran CC=icc USER_C=1;<br /> make[1]: Entering directory `.../bbp_2g/src/urs'<br /> mkdir -p bin;<br /> cd getpar/src; make -f Makefile CC=icc FC=gfortran USER_C=1;<br /> make[2]: Entering directory `.../bbp_2g/src/urs/getpar/src'<br /> icc -O3 -DENVIRONMENT -c -o defpar.o defpar.c<br /> icc -O3 -DENVIRONMENT -c -o getpar.o getpar.c<br /> icc -O3 -DENVIRONMENT -c -o getarg.o getarg.c<br /> getarg.c(112): warning #303: explicit type is missing (&quot;int&quot; assumed)<br /> register i;<br /> ^ <br /> icc -O3 -DENVIRONMENT -c -o getlocation.o getlocation.c<br /> getlocation.c(9): warning #147: declaration is incompatible with &quot;__ssize_t={int} getline(char **restrict, size_t={unsigned int} *restrict, FILE *restrict)&quot; (declared at line 671 of &quot;/usr/include/stdio.h&quot;)<br /> static int getline(FILE *fd, char *line)<br /> <br /> ...<br /> ...<br /> ...<br /> <br /> make[2]: Entering directory `.../bbp_2g/src/sdsu/srcV1.4'<br /> icc -w -Wall -c ray3DJHfor.c<br /> gfortran module_bbtoolbox.f90 module_interface.f90 main_bbtoolbox.f90 coda.f90 composition.f90 convolution.f90 fourier.f90 error.f90 geometry.f90 interpolation.f90 io.f90 random.f90 scattering.f90 source.f90 ray3DJHfor.o -o BBtoolbox.exe<br /> ray3DJHfor.o: In function `raytracing_':<br /> ray3DJHfor.c:(.text+0x8cf): undefined reference to `__libm_sse2_log'<br /> ray3DJHfor.c:(.text+0x96b): undefined reference to `__libm_sse2_asin'<br /> ray3DJHfor.c:(.text+0x9cd): undefined reference to `__libm_sse2_asin'<br /> ray3DJHfor.c:(.text+0xa00): undefined reference to `__libm_sse2_tan'<br /> ray3DJHfor.c:(.text+0xa3d): undefined reference to `__libm_sse2_tan'<br /> ray3DJHfor.c:(.text+0xa52): undefined reference to `__libm_sse2_log'<br /> collect2: ld returned 1 exit status<br /> make[2]: *** [BBtoolbox.exe] Error 1<br /> make[2]: Leaving directory `.../bbp_2g/src/sdsu/srcV1.4'<br /> make[1]: *** [all] Error 2<br /> make[1]: Leaving directory `.../bbp_2g/src/sdsu'<br /> make: *** [all] Error 2<br /> &lt;/pre&gt;<br /> <br /> '''Cause:''' In this case the user tried to build Broadband on a 32-bit platform. Broadband code was designed to be run on 64-bit platform. Any attempt to build Broadband on a 32-bit platform will result in numerous warnings and the build will fail with error messages similar to ones listed above.<br /> <br /> '''Solution:''' Try building Broadband on a 64-bit platform will the all the dependencies listed in Section 1.1: &quot;System Dependencies&quot; and Section 1.2: &quot;Software Dependencies&quot;<br /> <br /> == Unit/Acceptance Test Failures and Errors ==<br /> <br /> Unit and Acceptance tests are provided to verify the Broadband platform and it's supporting modules built by the user are functioning as designed. Under certain circumstances, some of these test might fail. While some of these failure might indicate serious problems that will have to be addressed before the platform can used, it is acceptable to ignore some of the failures. This section lists some failures and their solutions.<br /> <br /> === ERROR: test_syn1d (test_syn1d.Test_syn1D) ===<br /> The Unit test for Syn1d module fails with the following message:<br /> &lt;pre&gt;<br /> ERROR: test_syn1d (test_syn1d.Test_syn1D)<br /> ----------------------------------------------------------------------<br /> Traceback (most recent call last):<br /> File &quot;.../bbp_2g/tests/test_syn1d.py&quot;, line 62, in test_syn1d<br /> synObj.run()<br /> File &quot;.../bbp_2g/comps/syn1D.py&quot;, line 236, in run<br /> shutil.copy2(a_tmpfile, expected_file)<br /> File &quot;/usr/lib/python2.6/shutil.py&quot;, line 99, in copy2<br /> copyfile(src, dst)<br /> File &quot;/usr/lib/python2.6/shutil.py&quot;, line 52, in copyfile<br /> fsrc = open(src, 'rb')<br /> IOError: [Errno 2] No such file or directory: '.../bbp_2g/tmpdata/3310632/s01.3comp'<br /> &lt;/pre&gt;<br /> <br /> '''Cause:''' Syn1d module requires the Green's Function file to run and the path to this file might be incorrect in 'bbp_2g_gf/ucsb/GreenBank/Northridge/GreenBank.inf' file.<br /> <br /> '''Solution:''' This issue can be fixed by correcting the paths listed in the GreenBank.inf files in the Green's Function directory. Here are step by step instructions to fix this issue:<br /> <br /> 1. Locate your Greens Functions directory: 'bbp_2g_gf'<br /> 2. Navigate to bbp_2g_gf/ucsb/GreenBank/Northridge folder.<br /> 3. Open Green_Bank.inf files with a text editor.<br /> 4. Locate the text &quot;The name of file to store Green Bank&quot;<br /> 5. Note the location of the Green Bank file under the line found in step 4, similar to &quot;/home/scec-00/scottcal/bband/bbp_2g_gf/ucsb/GreenBank/Northridge/Green_1d.soil&quot;.<br /> 6. Replace the path found in Step 5 with just the file name, in the case of Northridge it is &quot;Green_1d.soil&quot;<br /> 7. Save and close the Green_Bank.inf.<br /> 8. Navigate to bbp_2g_gf/ucsb/GreenBank/LomaPrieta folder and repeat steps 3-7. The name of the Green Bank file for LomaPrieta is &quot;Green_1d.LoPr&quot;.<br /> 9. Navigate to bbp_2g_gf/ucsb/GreenBank/Landers folder and repeat steps 3-7. The name of the Green Bank file for Landers is &quot;Green1D.Landers&quot;<br /> <br /> === ERROR: test_gensrf (test_genslip.Test_Genslip) ===<br /> The Unit test for Genslip module fails with the following message:<br /> &lt;pre&gt;<br /> ======================================================================<br /> ERROR: test_gensrf (test_genslip.Test_Genslip)<br /> ----------------------------------------------------------------------<br /> Traceback (most recent call last):<br /> File &quot;.../bbp_2g/tests/test_genslip.py&quot;, line 51, in test_gensrf<br /> gen.run()<br /> File &quot;.../bbp_2g/comps/genslip.py&quot;, line 153, in run<br /> ps.run()<br /> File &quot;.../bbp_2g/comps/plot_srf.py&quot;, line 52, in run<br /> shutil.copy2(&quot;%s/%s.ps.png&quot; % (a_tmpdir, self.r_srffile[0:self.r_srffile.find(&quot;.srf&quot;)]), &quot;%s/%s.png&quot; % (a_outdir, self.r_srffile[0:self.r_srffile.find(&quot;.srf&quot;)]))<br /> File &quot;/usr/lib/python2.6/shutil.py&quot;, line 99, in copy2<br /> copyfile(src, dst)<br /> File &quot;/usr/lib/python2.6/shutil.py&quot;, line 52, in copyfile<br /> fsrc = open(src, 'rb')<br /> IOError: [Errno 2] No such file or directory: '.../bbp_2g/tmpdata/3309008/3309008_test_eq.ps.png'<br /> &lt;/pre&gt;<br /> <br /> '''Cause:''' The Genslip module calls the Plot_SRF module to the plot the SRF file. Plot_SRF uses C-shell code to locate and use GMT package to plot the SRF file. This shell code might fail on some flavors of Linux with a message like &quot;Newline in variable name&quot; in the Plot_SRF log file.<br /> <br /> '''Solution:''' This issue can be fixed by editing the plot_SRF.csh file. Here are step by step instructions to fix this issue:<br /> <br /> 1. Locate shell script file: bbp_2g/src/plot/plot_SRF.csh<br /> 2. Open the file in your preferred text editor<br /> 3. Locate the line 'set FIND_GMT = $?'<br /> 4. Replace the line found in step 3 with 'set FIND_GMT = $status'<br /> 5. Locate the section of code that starts with the statement &quot;# FIND MAX. SLIP&quot;<br /> 6. Replace the following line in section found in step 5:<br /> &lt;pre&gt;<br /> set SMAX = `$XYZCODE calc_xy=$CALC_XY type=&quot;${TYPE}&quot; nseg=-1 &lt; $SLIPFILE.srf | \<br /> gawk -v m=$SMAX '{if($3&gt;m)m=$3;}END{printf &quot;%.0f\n&quot;,m;}'`<br /> <br /> with (collapse the statement to a single line by removing '\' at the end of first part of the statement):<br /> <br /> set SMAX = `$XYZCODE calc_xy=$CALC_XY type=&quot;${TYPE}&quot; nseg=-1 &lt; $SLIPFILE.srf | gawk -v m=$SMAX '{if($3&gt;m)m=$3;}END{printf &quot;%.0f\n&quot;,m;}'`<br /> &lt;/pre&gt;<br /> 7. Save the file and exit<br /> <br /> === ERROR: test_ucgen (test_ucrmg.Test_UCrmg) ===<br /> The Unit test for Ucrmg module fails with the following message:<br /> &lt;pre&gt;<br /> ======================================================================<br /> ERROR: test_ucgen (test_ucrmg.Test_UCrmg)<br /> ----------------------------------------------------------------------<br /> Traceback (most recent call last):<br /> File &quot;.../bbp_2g/tests/test_ucrmg.py&quot;, line 59, in test_ucgen<br /> ucObj.run()<br /> File &quot;.../bbp_2g/comps/ucrmg.py&quot;, line 161, in run<br /> ps.run()<br /> File &quot;.../bbp_2g/comps/plot_srf.py&quot;, line 52, in run<br /> shutil.copy2(&quot;%s/%s.ps.png&quot; % (a_tmpdir, self.r_srffile[0:self.r_srffile.find(&quot;.srf&quot;)]), &quot;%s/%s.png&quot; % (a_outdir, self.r_srffile[0:self.r_srffile.find(&quot;.srf&quot;)]))<br /> File &quot;/usr/lib/python2.6/shutil.py&quot;, line 99, in copy2<br /> copyfile(src, dst)<br /> File &quot;/usr/lib/python2.6/shutil.py&quot;, line 52, in copyfile<br /> fsrc = open(src, 'rb')<br /> IOError: [Errno 2] No such file or directory: '.../bbp_2g/tmpdata/3309831/test_ucsb.ps.png'<br /> &lt;/pre&gt;<br /> <br /> '''Cause:''' The Ucrmg module calls the Plot_SRF module to the plot the SRF file. Plot_SRF uses C-shell code to locate and use GMT package to plot the SRF file. This shell code might fail on some flavors of Linux with a message like &quot;Newline in variable name&quot; in the Plot_SRF log file.<br /> <br /> '''Solution:''' This issue can be fixed by editing the plot_SRF.csh file. The steps to fix this issue are listed under the solution for &quot;ERROR: test_gensrf (test_genslip.Test_Genslip)&quot; above.<br /> <br /> === FAIL: test_site_amp (test_uc_site.Test_UC_Site) ===<br /> <br /> The unit test for UC-Site module might fail with the following message:<br /> &lt;pre&gt;<br /> ======================================================================<br /> FAIL: test_site_amp (test_uc_site.Test_UC_Site)<br /> ----------------------------------------------------------------------<br /> Traceback (most recent call last):<br /> File &quot;.../bbp_2g/tests/test_uc_site.py&quot;, line 92, in test_site_amp<br /> self.failIf(cmp_bbp.cmp_bbp(a_ref_file_no_header, test_file_no_header, tolerance=0.035)!=0,errmsg)<br /> AssertionError: Output file .../bbp_2g/tmpdata/3310633/s04.3comp does not match reference file .../bbp_2g/ref_data/ucsb/s04.site.3comp<br /> &lt;/pre&gt;<br /> <br /> '''Cause:''' The synthetic seismogram generated by the UC-Site module on the user system differs from the reference result included in the Broadband release.<br /> <br /> '''Solution:''' The stochastic nature of the high frequency simulations is considered, and a constant random seed as input for our tests. This is the same constant random seed used to generate the reference results included in the release. This ensures that the time-series generated with unit tests agree with reference results. However, the high frequency codes are more sensitive to changes in compilers and machines due to the algorithm, so small differences that cause the test to fail are generally acceptable. The user is however encouraged to plot the two time-series and visually inspect them to verify they look similar. We are trying to come up with a better comparison for these tests.<br /> <br /> = Appendix C: Technical Notes =<br /> <br /> == Running Individual Acceptance Tests ==<br /> <br /> The acceptance test script ./tests/AcceptTest.py attempts to run all of the defined tests when executed. However, sometimes it is useful to run an acceptance test in isolation for troubleshooting purposes:<br /> <br /> * Identify the test you want to run. Eg: user-URS-UCSB-SDSU-SDSU<br /> * Move to the ./comps directory and execute that test's XML workflow with run_bbp_2G.py. Using the above example:<br /> &lt;pre&gt;<br /> $ ./run_bbp_2G.py -x ../ref_data/accept_inputs/user-URS-UCSB-SDSU-SDSU.xml<br /> &lt;/pre&gt;<br /> <br /> Since you are running the test outside of AcceptTest.py, you will not see a PASS/FAIL message once the simulation completes. However, you can review the contents of the ./outdata/&lt;SIMID&gt; directory to verify that the correct seismograms and response spectra tables were produced.<br /> <br /> == Manaully Setting Random Number Generator Seed Values ==<br /> <br /> Several of the platform codebases employ random number generators to produce SRFs and seismograms. These random number generators are generally seeded with an initial value (typically an integer) which are hard-coded in the platform. Advanced users may desire to change these seed values.<br /> <br /> Changing the seeds for seismogram synthesis varies depending on which codebase you want to use:<br /> <br /> * URS: Edit ./comps/hfsims_cfg.py, Line 43 &quot;self.RAND_NUM&quot;<br /> * UCSB: Edit ./src/ucsb/Syn1DSCEC/syn1D_LAH.f, Line 183 &quot;iseed&quot;, and recompile with &quot;make&quot;<br /> * SDSU:<br /> ** User event: Edit ./bbp_2g_gf/sdsu/scattering_generic.dat (seed values annotated in file)<br /> ** Validation event: Edit ./bbp_2g_gf/sdsu/&lt;event&gt;/scattering.dat</div> Patrices https://strike.scec.org/scecwiki/index.php?title=Broadband_User_Guide_v11.2.3&diff=5056 Broadband User Guide v11.2.3 2012-05-08T22:02:44Z <p>Patrices: </p> <hr /> <div>'''Version 11.2.3.'''<br /> <br /> If you find errors in this document or sections to be unclear, please either fix them yourself or contact software@scec.org.<br /> <br /> = Installing the Second-Generation Broadband Platform =<br /> Installing the Broadband Platform involves obtaining a copy of the code and building the required executables. You can either download the platform from the Broadband web site ([http://www.scec.org/research/broadband http://www.scec.org/research/broadband]) or check the code out of SCEC's Subversion repository. Most users should download the platform.<br /> <br /> == System Dependencies ==<br /> The current version of the Broadband Platform is designed to run on standard 64-bit Linux machines. Testing has been performed on SCEC's development servers running Fedora Core 10 (kernel version 2.6.27.41-170.2.117.fc10.x86_64). In this guide we outline how to install the platform into your own account on a Linux computer using the simplest approach.<br /> <br /> == Software Dependencies ==<br /> The Broadband Platform has certain software dependencies.<br /> <br /> Required:<br /> <br /> *Python v2.7 with<br /> **PyGTK<br /> **Matplotlib<br /> **Numpy<br /> **Pyproj<br /> <br /> *Intel compilers (64-bit) v12.0.4<br /> *GNU compilers (gcc, gfortran) v4.5.1<br /> *GNU Fortran 77 v3.4.6<br /> *GMT (Generic Mapping Toolkit)<br /> *ImageMagick<br /> <br /> == Setting Up Your Account ==<br /> For simplicity of installation, we recommend users use a bash shell for the Broadband Platform account. It is possible to get the platform running using other shell's, but we will focus on a bash shell installation. The user environment is a common source of problems since certain environment variables must be defined for the platform to work correctly.<br /> <br /> To check your account, make sure you can run basic commands like ''ls'' and ''cd'' before proceeding.<br /> <br /> == Downloading the Platform ==<br /> &lt;nowiki&gt;Download 4 files from the Broadband website, the code (bbp_dist_&lt;version&gt;.tgz), the data (bbp_data_&lt;version&gt;.tgz), and their checksum files (bbp_dist_&lt;version&gt;.tgz.md5 and bbp_data_&lt;version&gt;.tgz.md5). &lt;/nowiki&gt;The code file is about 100 MB, the data file about 3 GB. After you've downloaded the files to your local Linux system, the next step is to calculate the checksums yourself and compare them to the checksums you downloaded.<br /> <br /> First, verify that the ''md5sum'' command is in your path:<br /> <br /> $&gt; which md5sum<br /> <br /> You should get something like /usr/bin/md5sum. If you see the message 'no md5sum in...', contact your Linux system administrator and ask to have md5sum added to your path.<br /> <br /> Once you can run the ''md5sum'' command, run:<br /> <br /> $&gt; md5sum -c bbp_dist_&lt;version&gt;.tgz.md5<br /> $&gt; md5sum -c bbp_data_&lt;version&gt;.tgz.md5<br /> <br /> You should get the messages<br /> bbp_dist_&lt;version&gt;.tgz.md5: OK<br /> bbp_data_&lt;version&gt;.tgz.md5: OK<br /> <br /> If you get FAILED instead, re-download the tgz files and try again. When it passes, that means the files were downloaded without error.<br /> <br /> Once both files have passed the checksum test, untar the files.<br /> <br /> $&gt; tar xzvf bbp_dist_&lt;version&gt;.tgz file<br /> $&gt; tar xzvf bbp_data_&lt;version&gt;.tgz file<br /> <br /> If multiple users are planning to use the platform on the same system, you only need one copy of the data files per machine. Each user will still need his or her own copy of the code files.<br /> <br /> Alternatively, if you would like access to the latest version of the platform and get frequent but less thoroughly tested improvements, you can check out the platform from SCEC's Subversion repository. Only advanced users should take this approach, outlined in detail in the [[#Advanced Users| Advanced Users section]].<br /> <br /> == User Account Setup ==<br /> <br /> The Broadband platform installation is divided into two parts (1) input Green Functions (GF) data directory (9.3Gb), and (2) BBP home directory (366Mb). <br /> <br /> First, the Green's function libraries are larger, but they are static. The broadband platform reads the data files, but does not change them. <br /> <br /> Second, the remainder of the broadband platform is organized in the BBP home directory. The BBP home directory has a specific directory structure that includes the source code for the scientific programs, the python scripts that link the scientific programs, simulation input directory, temporary and log file directories, and the output data directory where all the platform results are written.<br /> <br /> The BBP home directory will increase in size as you run the platform, because both output data and output log files are written to the home directory. Running the acceptance tests will produce nearly ( 10Gb) of input data (5.2Gb), output data (500Mb), temporary files (2.7Gb), and output log files (250Mb). Once these tests have passed much of this data can be removed. However, the BBP home directory should have at least 10Gb of disk space to insure the acceptance tests can be run when a particular broadband platform software distribution is first installed on a system.<br /> <br /> == Data Directory ==<br /> Input data files called Greens Functions are distributed with the platform. These files are generated using specific velocity structures, so they are often considered region specific. We have GF for three regions including near Loma Prieta, near Landers, and near Northridge.<br /> <br /> The data directory is static, and the data directories are read-only. A single copy can be installed in a shared disk, which can then be shared by multiple users.<br /> <br /> == Setting Environment Variables ==<br /> The BBP source codes and scripts are organized under the broadband platform home directory. The broadband platform home directory is specified in a couple of places during Broadband Platform installation. <br /> <br /> Internal to the Broadband platform software, all broadband platform files (except the Greens Function data files) are in sub-directories of the BBP home directory.<br /> <br /> == BBP Environment Variable ==<br /> We recommend setting both an alias and a environment variable to the BBP home directory. This will help avoid typing it many times.<br /> <br /> If you're running a Bash shell, add the following line to your .bash_profile with your favorite text editor:<br /> <br /> export BBP=/home/scec-00/kumar/bbp_2g<br /> <br /> If you're running a C-shell, add the following line to your .cshrc with your favorite text editor:<br /> <br /> setenv BBP /home/scec-00/kumar/bbp_2g<br /> <br /> * PYTHONPATH<br /> After you've obtained a copy of the project, you'll need to make sure the comps directory is on Python's path so Python can find all the project modules. If you're running a Bash shell, add the following line to your .bash_profile with your favorite text editor:<br /> <br /> export PYTHONPATH=$BBP/comps:$PYTHONPATH<br /> <br /> If you're running a C-shell, add the following line to your .cshrc with your favorite text editor:<br /> <br /> setenv PYTHONPATH $BBP/comps:$PYTHONPATH<br /> <br /> * PATH<br /> In order to successfully compile the project, you'll need to make sure the required compilers directories are in your PATH variable. Broadband requires Intel 64-bit compilers, icc and ifort and GNU Compilers, gcc, g77 and f77 to compile the scientific code.<br /> <br /> If you are planning to run Broadband on SCEC Development servers, make sure you have the following directories in your PATH:<br /> <br /> For Bash Shell (in .bash_profile)<br /> <br /> export PATH=/usr/usc/intel/composerxe-2011.4.191/bin/intel64:/usr/usc/intel/composerxe-2011.4.191/mpirt/bin/intel64:$PATH<br /> <br /> For C-shell (in .cshrc)<br /> <br /> setenv PATH /usr/usc/intel/composerxe-2011.4.191/bin/intel64:/usr/usc/intel/composerxe-2011.4.191/mpirt/bin/intel64:$PATH<br /> <br /> When running elements of the platform over ssh, be sure to enable ssh forwarding (with the -X or -Y options).<br /> <br /> After modifying your login script above, log out and log back into the machine so the changes are reflected in your environment.<br /> <br /> == Edit Install_cfg.py with Installation Directory Paths ==<br /> <br /> You need to tell the platform where it's installed by editing a single python file called &quot;install_cfg.py&quot;. Edit the file bbp_2g/comps/install_cfg.py with your favorite text editor, and edit the lines:<br /> <br /> self.A_INSTALL_ROOT = &lt;bbp_2g directory&gt;<br /> self.A_GF_DIR = &lt;bbp_2g_gf directory&gt;<br /> <br /> as one example:<br /> <br /> self.A_INSTALL_ROOT = /home/scec-00/kumar/bbp_2g<br /> self.A_GF_DIR = /home/scec-00/kumar/bbp_2g_gf<br /> <br /> with the paths on your system to the bbp_2g directory (the source) and the bbp_2g_gf directory (the data) that you unzipped. For example, it could be /home/scottcal/broadband_platform/bbp_2g and /home/scottcal/broadband_platform/bbp_2g_gf.<br /> <br /> Here is some information about these two directories that may be useful as you decide how, and where, to install these two parts of the Broadband Platform on your computer disk system. The data files, and therefore the &lt;bbp_2g_gf directory&gt; are nearly 3GB, but they are static and will not be modified and will not grow in size during use of the platform. The source directory is small to begin. However, this directory will increase as the platform is used, since the results produced by the platform will be stored here.<br /> <br /> == Directory Structure ==<br /> The platform consists of two top-level directories, bbp_2g and bbp_2g_gf. bbp_2g contains the source code, executables, scripts, tests, input, working, and output directories. bbp_2g_gf contains the Green's Functions, input files for the validation events, and other required input files for the various code bases. Note that indata, logs, outdata, tmpdata, and xml are created when the platform is first run, so they will be missing when you first install the platform.<br /> <br /> bbp_2g has the following directories:<br /> *checksums: Contains checksums for bbp_2g_gf files<br /> *comps: The Python scripts to run the platform<br /> *docs: Documentation for the platform<br /> *etc: Miscellaneous utility scripts<br /> *examples: Contains example input files<br /> *indata: An internal directory, used to stage input files<br /> *logs: Contains logs from BBP runs<br /> *outdata: Contains output files from a run<br /> *ref_data: Contains reference files for BBP tests<br /> *start: Put input files for an interactive run here<br /> *src: Source code for BBP modules<br /> *tests: Contains unit and acceptance tests<br /> *tmpdata: An internal directory, used during a run<br /> *xml: Contains XML files which describe simulations and can be used as input<br /> <br /> bbp_2g_gf has the following directories:<br /> *compare: Contains observed seismograms for validation events<br /> *plot: Data files for GMT plots<br /> *sdsu, ucsb, urs: Contains Green's functions, velocity files, and other required inputs for the codebases.<br /> <br /> In general, you will be interacting with the start directory for input files, comps to run the platform, tests to test the platform, and outdata to examine data products.<br /> <br /> === Adding aliases ===<br /> <br /> You may find it helpful to add aliases, so you can quickly and easily move to different broadband directories with a single command. We recommend creating aliases for the home, start, and outdata directories.<br /> <br /> If you are using the Bash shell, you can create aliases by adding the following lines to ~/.bash_profile:<br /> <br /> alias bbp= 'cd &lt;path to bbp_2g directory&gt;'<br /> alias start='cd &lt;path to bbp_2g directory&gt;/start'<br /> alias outdata='cd &lt;path to bbp_2g directory&gt;/outdata'<br /> <br /> If you're using a C shell, edit your ~/.cshrc and add:<br /> <br /> alias bbp cd &lt;path to bbp_2g directory&gt;<br /> alias start cd &lt;path to bbp_2g directory&gt;/start<br /> alias outdata cd &lt;path to bbp_2g directory&gt;/outdata<br /> <br /> Log out and log back in. You'll notice that now you can type the alias command as a shortcut to change directories:<br /> <br /> $&gt; pwd<br /> /home/scec-00/scottcal<br /> $&gt; start<br /> $&gt; pwd<br /> /home/scec-00/scottcal/bband/bbp_2g/start<br /> <br /> This can be a useful way to navigate around the broadband platform directories.<br /> <br /> == Building the Platform ==<br /> Once you have checked out the code, you need to build it. By default, every executable is compiled using the compiler recommended by the code developer. However, if you have limited compiler options or are building the codes on an untested system, you may need to specify non-standard alternative compilers, as described below.<br /> <br /> Before you can build the platform, you need to make sure that the Intel compilers are in your path. This is done automatically on broadband.usc.edu, but on other systems you can check by typing:<br /> <br /> $&gt;which icc<br /> <br /> If you get the message &quot;no icc in ...&quot;, then you'll need to add the Intel compilers to your path. Once the Intel compilers are in your path, you can make the code by cd-ing to the bbp_2g/src directory and typing make:<br /> <br /> $&gt; cd src<br /> $&gt; make<br /> <br /> It takes a minute or two to build the code. You may encounter build warnings; these are fine. However, if you get any build errors, this is a problem and should be investigated.<br /> <br /> By default, every executable is compiled using the compiler recommended by the code developer. Depending on the system, some compilers may not be available to you. You can override the C and Fortran compilers used by editing<br /> <br /> src/makefile<br /> <br /> Uncomment USER_C and set FC and CC to the compilers you wish. For example:<br /> <br /> Before:<br /> <br /> #USER_C=1<br /> FC=f77<br /> CC=gcc<br /> <br /> After (an example, you may choose different compilers):<br /> <br /> USER_C=1<br /> FC=gfortran<br /> CC=gcc<br /> <br /> Note that not all compiler combinations have been thoroughly tested. You may encounter build errors with untested compiler combinations. If you encounter any errors while building the platform, consult the Troubleshooting section at the end of this user guide for know issues and their solutions.<br /> <br /> Once the platform has been successfully built, you can move on to running the tests to verify that all components are working correctly.<br /> <br /> == Advanced Users ==<br /> Alternatively, if you would like access to the latest version of the platform, to get frequent but less thoroughly tested improvements, you can check out the platform from SCEC's Subversion version control repository on source.usc.edu. Only advanced users should follow this approach. If you are unsure, you should download the code as outlined in [[#Downloading the Platform|Downloading the Platform]] and skip this section.<br /> <br /> You may need to request access from the SCEC system administrator, John Yu ([mailto:johnyu@usc.edu johnyu@usc.edu]). Make sure you have subversion in your path before beginning.<br /> <br /> Once you have access, you'll need to decide if you want a stable tagged version, or the latest version in the repository. For a stable version, open a terminal window on the system of your choice and type:<br /> <br /> $&gt; svn checkout https://source.usc.edu/svn/broadband/tags/&lt;stable version&gt; bbp_2g<br /> <br /> For the latest version, type:<br /> <br /> $&gt; svn checkout https://source.usc.edu/svn/broadband/trunk bbp_2g<br /> <br /> This will check out the project to your local machine. It contains the source code, tests, and some example files. You also need to obtain a copy of the Broadband Platform data files, containing the Green's tensors. They are too large to be stored in version control. You can obtain a copy from SCEC software distribution server. If you are working on SCEC development server, you might be able to create a symbolic link to data folder. Please contact [[#User_Support|User Support]] to get a location of the data folder on the SCEC development server. If you are not working on SCEC development server, or don't have an SCEC Linux login account, you can get a archive (.tgz) file of the Green's functions from the same download site you obtained this guide.<br /> <br /> If you know where a read-accessible installation of the green functions data directories you can create a link to that location. This can save disk space in some cases.<br /> <br /> ln -s /home/scec-00/scottcal/bband/bbp_2g_gf &lt;path to your gf directory&gt;<br /> <br /> Periodically you should check for updates to the code. To do so, go to your bbp_2g directory and type<br /> <br /> $&gt; svn update<br /> <br /> This will pull down any code updates that have been made in the repository. After you update, make the code again (detailed in [[#Building the Platform|Building the Platform]]) so that any code changes are captured in the executables.<br /> <br /> == Running the Broadband Platform ==<br /> We recommend users initiate all Broadband Platform runs from the &quot;start&quot; directory. The start directory is a collection point for input files for a particular simulation.<br /> <br /> Assuming the user is starting at BBP home directory, the user should move to the start directory and then run the Checksum, Unit and Acceptance tests to confirm the Broadband Platform software installation is operating as expected.<br /> <br /> $&gt; cd start<br /> <br /> == Running Checksum, Unit, and Acceptance Tests ==<br /> The broadband platform contains three kinds of tests. The checksum tests verify that the data files were copied correctly and you have all the files that are expected. Unit tests run each module using a set of input files, and compare the results against known outputs. They verify that each module has been built and is working correctly. Acceptance tests verify that the modules are working correctly together. They test the platform end-to-end using different combinations with known inputs and compare the results. All the possible module combinations for both user-defined and validation events are tested as checks against integration errors.<br /> <br /> Begin with the checksum tests. Once they past, run the unit tests and finally the acceptance tests.<br /> <br /> == Running Checksum Tests ==<br /> To run the checksum tests, change to the checksums directory and run md5sum_check.py.<br /> <br /> From the BBP home directory:<br /> <br /> $&gt; cd checksums<br /> $&gt; ./md5sum_check.py<br /> <br /> It takes about 5 minutes to compute the checksums. If a checksum disagrees, that means that the contents of the datafile were not what was expected. Try reinstalling the data files and try again. If you continue to get a checksum error, contact support.<br /> <br /> Once the checksums agree, move on to the unit tests.<br /> <br /> == Running Unit Tests ==<br /> To run the unit tests, change to the tests directory and run UnitTests.py.<br /> <br /> From the BBP home directory:<br /> <br /> $&gt; cd tests<br /> $&gt; ./UnitTests.py<br /> <br /> The unit tests take about 15 minutes to run. When they're complete, the console will either print &quot;OK&quot; or how many tests failed. If a test has failed, first check that you have built the executables.You can rerun just the specific test that failed (test_&lt;module&gt;.py). If the test is still failing, also verify that you have the ref_data directory, since it contains the input and reference files. If you're looking for more information about the failure, you can consult the Unit Tests log file in bbp_2g/logs/unit_test.log . If you can't determine the reason for the failure, contact support.<br /> <br /> Once the unit tests all pass, proceed to the acceptance tests. If there are any failure or errors while running the unit tests, consult the Troubleshooting section at the end of this user guide for know issues and their solutions.<br /> <br /> == Running Acceptance Tests ==<br /> Make sure the unit tests pass before moving on to the acceptance tests. To run the acceptance tests, change to the tests directory (if you're not there already) and run AcceptTests.py. <br /> The acceptance tests take a long time to run, around 20 hours<br /> <br /> From the BBP home directory:<br /> <br /> $&gt; cd tests<br /> $&gt; ./AcceptTests.py &amp;&gt; accept.out &amp;<br /> <br /> Since the tests take so long to run (twenty hours), you should run them as a background process, and redirect their output to a log file, as shown in the command above.<br /> <br /> You can check the progress by tailing the log file.<br /> <br /> $&gt; tail accept.out<br /> <br /> When all the acceptance tests are completed, the AcceptTests.py script will either print &quot;OK&quot; or how many tests failed. <br /> <br /> Acceptance test failures indicate that the modules are not integrated correctly. Like with the unit tests, verify that you have the ref_data directory. If a certain acceptance test fails, you can get more information by consulting the acceptance test logs in bbp_2g/logs/acceptance_tests_logs/&lt;test that failed&gt;.log . If you can't determine the reason for the failure, contact [[support]].<br /> <br /> Since the acceptance tests can take a long time to run, you may wish to resume where you left off. This feature is supported automatically. If you do not wish to resume, delete the resume file in ref_data/accept_inputs/resume.txt. If there are any failure or errors while running the acceptance tests, consult the Troubleshooting section at the end of this user guide for know issues and their solutions.<br /> <br /> = Types of Broadband Platform Simulations =<br /> <br /> The platform supports two kinds of simulations, validation events and user-defined events. Validation simulations are performed using a historical event, and are directly compared to observed seismograms using goodness-of-fit. User-defined events are run using a rupture description provided by the user which may not necessarily be a historical earthquake.<br /> <br /> When you run a simulation, the platform assigns an ID to it. This ID can be used to track the simulation and locate the output data products.<br /> <br /> To supply input files to the platform, put them in the start directory. Extensions are important - the platform recognizes station lists (.stl), SRF files (.srf), and simple source descriptions (.src). If there are multiple files of a type, the platform will prompt the user to select one.<br /> <br /> To perform a simulation, a user selects between different required and optional modules. Below we present a summary of the various modules.<br /> <br /> = Modules =<br /> The broadband platform consists of a series of modules. There are two main types of modules, science modules and utility modules. Science modules are those for which the platform has multiple implementations, provided by different coding research groups. Utility modules only have 1 implementation. A schematic of the available modules and their flow relationships is shown below:<br /> <br /> = Science Modules =<br /> All simulations must include a low-frequency, high-frequency, and site response science module. Simulations may include an optional rupture generation science module. Users may select between the following different implementations of each of these modules:<br /> <br /> Rupture generation:URS, UCSB<br /> <br /> Low-frequency:URS, UCSB<br /> <br /> High-frequency:URS, UCSB, SDSU<br /> <br /> Site response:URS, UCSB, SDSU<br /> <br /> = Utility Modules =<br /> A spectral response utility module is automatically run after the site response module. Additionally, users may select an optional goodness-of-fit utility module to run at the conclusion of the simulation. In the case of a user-defined event, users select a historical event or previously run simulation to use as the comparison for goodness-of-fit.<br /> <br /> = Platform Directory =<br /> <br /> A broadband platform distribution is organized in a specific directory structure that separates the input data sets, the python scripts, the simulation configuration files, log files, and output data files.<br /> <br /> When running Broadband Platform simulations, standard procedure is to place the simulation input files in the start directory and invoke the Broadband platform scripts from there.<br /> <br /> From the BBP home directory:<br /> <br /> $&gt; cd start<br /> $&gt; run_bbp_2G.py<br /> <br /> Simulation output results will be written into the bbp_home/output<br /> <br /> = Validation Simulations =<br /> To run a validation simulation, go to the comps directory and run run_bbp_2G.py. The platform will ask you a series of questions. Answer 'y' to &quot;Do you want to perform a validation run?&quot;<br /> <br /> From the BBP home directory:<br /> <br /> $&gt; cd start<br /> $&gt; run_bbp_2G.py<br /> Welcome to the SCEC Broadband Platform.<br /> Please select the modules you want to run.<br /> Do you want to perform a validation run (y/n)? y<br /> Do you want to validate with:<br /> Northridge (1)<br /> Loma Prieta (2)<br /> Landers (3)<br /> ?<br /> ...<br /> <br /> No input files are required by the user. However, you may wish to run with a reduced station list to speed up the computations. You can put your own station list into the start directory (the format is described in [[#Station File List|section 5.3]]). Note that any stations which do not have observed seismograms will not be included in the automatically generated goodness-of-fit comparison.<br /> <br /> In addition to the low-frequency modules which compute seismograms using 1D Green's Tensors, validation events can also be run using precomputed 3D seismograms to supply the low-frequency.<br /> <br /> = User-defined Simulations =<br /> To run a user-defined simulation, two input files are required, a rupture description and a station list. The rupture description can either be in SRF format or a simplified source description (the format is described in [[#Simple source description|section 5.1]]). To run a user-defined simulation, run run_bbp_2G.py.<br /> <br /> From the BBP home directory:<br /> <br /> $&gt; cd start<br /> $&gt; run_bbp_2G.py<br /> Welcome to the SCEC Broadband Platform.<br /> Please select the modules you want to run.<br /> Do you want to perform a validation run (y/n)? y<br /> Do you want to run a rupture generator (y/n)? <br /> ...<br /> <br /> You may then choose if you want to run a rupture generator. This is necessary if you're supplying a simple rupture description. If you're supplying an SRF file, you can skip this. Next you can select from different module implementations. Finally, you have the option to run goodness-of-fit against either observed seismograms or another simulation.<br /> <br /> ...<br /> Do you want to run goodness of fit (y/n)? y<br /> What reference files would you like to compare to? Enter a simulation ID or a scenario name: &lt;comparison&gt;<br /> Enter a label to use for the comparison seismograms: &lt;label&gt;<br /> <br /> The label will be used in GoF plots to distinguish one set of results from the other.<br /> <br /> The user-defined events must be within one of the regions supported by the platform - Southern California, Northern California, or the Mojave. The platform will automatically select a region based on the event hypocenter. If the event falls outside of these regions, you'll get an error.<br /> <br /> = Logging =<br /> During the run, log files will be produced in logs/&lt;simulation ID&gt;/&lt;simulation ID&gt;.&lt;module name&gt;.log. If the platform fails, this is a good place to look to determine the error. Additionally, any fatal errors will be recorded in fatal_error.log.<br /> <br /> Metadata capturing all the executable calls is located in tmpdata/&lt;simulation ID&gt;/metadata.txt for careful tracing of exactly what was called. Both the log files and metadata can be useful if troubleshooting an issue.<br /> <br /> = Data Products =<br /> The platform produces a variety of data products. &lt;nowiki&gt;All data products are located in outdata/&lt;simulation ID&gt;. &lt;/nowiki&gt;On most Linux systems, you can show images using display:<br /> <br /> $&gt; display &lt;PNG file&gt;<br /> <br /> Make sure you have X11 forwarding enabled.<br /> <br /> == Station map ==<br /> To help visualize the stations in relationship to the fault, the platform produces a PNG file displaying station locations with red circles and the fault plane with a black line, on an image of California. You can find this file in outdata/&lt;simulation ID&gt;/station_map.png.<br /> <br /> == Seismograms ==<br /> When running the platform, you have the option to output velocity and acceleration seismograms, for each station. Plots of these files can be found in outdata/&lt;simulation ID&gt;/&lt;simulation ID&gt;.&lt;station&gt;_&lt;velocity or acceleration&gt;_seis.png.<br /> <br /> The raw seismogram data is available in outdata/&lt;simulation ID&gt;/&lt;simulation ID&gt;.&lt;station&gt;.vel.bbp (velocity) and outdata/&lt;simulation ID&gt;.&lt;station&gt;.acc.bbp (acceleration). Its format is described in [[#BBP seismograms|section 5.4]].<br /> <br /> To compare seismogram data, you can run comps/plotit.py with two seismograms. It will plot them both for comparison. From the comps directory, run:<br /> <br /> $&gt; plotit.py &lt;path to seismogram 1&gt; &lt;path to seismogram 2&gt;<br /> <br /> == Response spectra ==<br /> The respect code, run at the end of each simulation, calculates the response spectra for each station. The raw respect data is located at<br /> <br /> From the BBP home directory:<br /> <br /> outdata/&lt;simulation ID&gt;/&lt;simulation ID&gt;.&lt;station&gt;.rsp<br /> <br /> in the format described in [[#Response spectra|section 5.5]].<br /> <br /> == Goodness-of-fit ==<br /> If you run goodness-of-fit, several additional data products are produced. The goodness-of-fit comparison is performed by comparing the response spectra of a set of calculated seismograms to seismograms from another simulation or observed seismograms. For each station involved in the comparison, a plot comparing the response spectra can be found at outdata/&lt;simulation ID&gt;/&lt;comparison label&gt;_&lt;simulation ID&gt;_&lt;station&gt;_rsp.png. A plot showing the seismograms on top and bottom can be found at outdata/&lt;comparison label&gt;_&lt;simulation ID&gt;_&lt;station&gt;_overlay.png. The goodness-of-fit plot can be found at gof-&lt;comparison label&gt;-&lt;simulation ID&gt;_r0-&lt;cutoff distance&gt;.png.<br /> <br /> Note that at least 3 stations must be run for goodness-of-fit to be valid. If fewer than 3 stations are run, no goodness of fit calculation will be performed.<br /> <br /> == Rupture files ==<br /> When a user-defined event is simulated, the user has the option to run a rupture generator. This generator produces an SRF file, found in outdata/&lt;simulation ID&gt;/*.srf. This file can be put in the start directory and used in future runs. Additionally, the platform produces a plot of the cumulative slip on the fault surface, outdata/&lt;simulation ID&gt;/&lt;SRF prefix&gt;.png.<br /> <br /> = Platform Modes =<br /> The platform can be run in multiple modes. The default is interactive mode, in which the user is prompted to answer a series of questions. Once all the information has been gathered, the run begins.<br /> <br /> For a large number of runs, or if the user is repeating a specific run, this can be tedious. The platform provides two other ways to describe a run, with an option file or an XML description.<br /> <br /> An option file provides responses to all the questions that the platform poses. The format is described in [[#Option File|section 5.6]], but it's basically a text file, 1 entry per line, with support for comments. It can be fed to the platform using the -o option.<br /> <br /> The platform will also accept XML files containing a full description of a run. The schema for these files is given in [[#XML workflow description schema|section 5.7]]. These files are also produced by the platform after every simulation, and placed in xml/&lt;simulation ID&gt;.xml. So if you want to rerun a simulation, you can point the platform to the XML file from that simulation using the -x option. Note that a new simulation ID will be assigned to the run, so there is no risk of overwriting previous simulation results.<br /> <br /> = Available Options =<br /> To get a list of the current available options, run run_bbp_2G.py with the -h flag.<br /> <br /> $&gt; run_bbp_2G.py -h<br /> Usage: run_bbp_2G.py [options]<br /> Options:<br /> -h, --help Show this help message and exit<br /> -x XML_FILE, --xml-file=XML_FILE Run using XML description of workflow<br /> -s SIM_ID, --simID=SIM_ID Force a simID<br /> -o OPTFILE, --option-file=OPTFILE File containing responses to interactive platform prompts<br /> -v, --version Broadband platform version<br /> -c, --compact Compact output results. Remove temporary files for simulations that complete successfully.<br /> -g, --generate-xml Generates the XML description but does not run the platform<br /> -l LOG_FILE, --log=LOG_FILE Store all output in a file<br /> <br /> = Cleanup =<br /> After a while, you may find that your indata, tmpdata, outdata, and logs directories are getting cluttered with files from past runs. If you wish to delete these old files, you can use the clean_directories.sh script in the etc directory.<br /> <br /> From the BBP home directory:<br /> <br /> $&gt; cd etc<br /> $&gt; ./clean_directories &lt;days&gt;<br /> <br /> Any simulation ID directories in the indata, tmpdata, outdata, and logs directories which were last accessed &lt;days&gt; days or longer ago will be deleted. If you have a few directories you want to keep, either copy them somewhere else, or copy them to a directory name that's not all digits and they won't be deleted.<br /> <br /> = Examples =<br /> Below are some examples that you can try using the sample files in the examples directory. Make sure all the tests pass before you try this. You should be in the comps directory when you start these examples:<br /> <br /> From the BBP home directory:<br /> <br /> $&gt; cd comps<br /> <br /> == Sample Validation Run ==<br /> You don't need to move any files for this. Notice that 3D seismograms are a low-frequency option, since you're running a validation event.<br /> <br /> From the BBP home directory:<br /> <br /> $&gt; cd start<br /> $&gt; run_bbp_2G.py <br /> Welcome to the SCEC Broadband Platform.<br /> Please select the modules you want to run.<br /> Do you want to perform a validation run (y/n)? y<br /> Do you want to validate with:<br /> Northridge (1)<br /> Loma Prieta (2)<br /> Landers (3)<br /> ?1<br /> Do you want to<br /> run all validation stations (1)<br /> select a station list (2)<br /> ?1<br /> Choose a source of low frequency seismograms:<br /> URS module (1)<br /> URS 3D seismograms (2)<br /> UCSB module (3)<br /> SDSU module (4)<br /> SDSU 3D seismograms (5)<br /> ?2<br /> Choose a high frequency module:<br /> URS (1)<br /> UCSB (2)<br /> SDSU (3)<br /> ?1<br /> Choose a site response module:<br /> URS (1)<br /> UCSB (2)<br /> SDSU (3)<br /> ?1<br /> Do you want to plot velocity seismograms (y/n)? y<br /> Do you want to plot acceleration seismograms (y/n)? y<br /> <br /> This simulation takes about 10 minutes. Once it's complete the platform will tell you:<br /> <br /> You can find results in &lt;path to bbp_2g install&gt;/outdata/&lt;simulation ID&gt; .<br /> <br /> In that directory you will find:<br /> <br /> *Velocity seismograms (&lt;simulation ID&gt;.&lt;station&gt;.bbp)<br /> *Acceleration seismograms (&lt;simulation ID&gt;.&lt;station&gt;.acc.bbp)<br /> *Plots of velocity seismograms (&lt;simulation ID&gt;.&lt;station&gt;_velocity_seis.png)<br /> *Plots of acceleration seismograms (&lt;simulation ID&gt;.&lt;station&gt;_acceleration_seis.png)<br /> *Response spectra files (&lt;simulation ID&gt;.&lt;station&gt;.rsp)<br /> *Plots comparing simulated and observed seismograms (Northridge_&lt;simulation ID&gt;_&lt;station&gt;_overlay.png)<br /> *Plots comparing simulated and observed response spectra (Northridge_&lt;simulation ID&gt;_&lt;station&gt;_rsp.png)<br /> *Overall goodness-of-fit plots (gof-Northridge-&lt;simulation ID&gt;_r0-25.png)<br /> <br /> == Sample Validation run, custom stations ==<br /> If the validation runs aren't performed with 3D low-frequency, it can take a long time, up to 10 minutes per station. Sometimes you might want to run with a reduced station list so the simulation will run faster.<br /> <br /> Copy the files in example/valid_custom_stations into the start directory. Take a look at the format of the station file:<br /> <br /> $&gt; more valid_test_stat.stl <br /> #Required: lon, lat, station name, distance to fault plane, Vs30<br /> #Optional: low freq corner, high freq corner<br /> #Unused: station information<br /> #lon lat stationdist Vs30 LF corner HF corner station information<br /> -118.6417 34.5640 cast 20.47 450 0.120 23.0 CSMIP peer.berkeley.edu/nga<br /> -118.4180 34.0628 lacn 22.82 278 0.140 23.0 CSMIP peer.berkeley.edu/nga<br /> -118.8811 34.2886 moor 24.16 405 0.160 23.0 CSMIP peer.berkeley.edu/nga<br /> <br /> Now, run the platform, using a station list:<br /> <br /> From the BBP Home directory<br /> <br /> $&gt; cd start<br /> $&gt; run_bbp_2G.py <br /> Welcome to the SCEC Broadband Platform.<br /> Please select the modules you want to run.<br /> Do you want to perform a validation run (y/n)? y<br /> Do you want to validate with:<br /> Northridge (1)<br /> Loma Prieta (2)<br /> Landers (3)<br /> ?1<br /> Do you want to<br /> run all validation stations (1)<br /> select a station list (2)<br /> ?2<br /> <br /> If you have multiple station list files in your start directory, you may see the following prompt asking you to select one. If you only have one, the platform will select it automatically.<br /> <br /> Found multiple BBP station list files in the start directory. Please select one:<br /> nr_one_stat.stl (1)<br /> valid_test_stat.stl (2)<br /> ?2<br /> Choose a source of low frequency seismograms:<br /> URS module (1)<br /> URS 3D seismograms (2)<br /> UCSB module (3)<br /> SDSU module (4)<br /> SDSU 3D seismograms (5)<br /> ?3<br /> Choose a high frequency module:<br /> URS (1)<br /> UCSB (2)<br /> SDSU (3)<br /> ?2<br /> Choose a site response module:<br /> URS (1)<br /> UCSB (2)<br /> SDSU (3)<br /> ?2<br /> Do you want to plot velocity seismograms (y/n)? y<br /> Do you want to plot acceleration seismograms (y/n)? y<br /> <br /> Again, when the run completes in about 15 minutes you can find results in the output directory. You'll notice far fewer files, as only 3 stations were run instead of 133. The goodness-of-fit plots won't look very good - more stations are really needed to get an accurate plot.<br /> <br /> == Sample User-defined run with source description ==<br /> Next let's try running a user-defined event. Copy examples/user_rup_gen/nr_one_stat.stl and examples/user_rup_gen/user_eq.src to the start directory. user_eq.src is a simple source description. Its format is outlined in [[#XML workflow description schema|section 5.1]]. Since this is a user-defined event, precomputed 3D seismograms aren't a valid option.<br /> <br /> $&gt; run_bbp_2G.py <br /> Welcome to the SCEC Broadband Platform.<br /> Please select the modules you want to run.<br /> Do you want to perform a validation run (y/n)? n<br /> Do you want to run a rupture generator (y/n)? y<br /> Rupture generators:<br /> URS (1)<br /> UCSB (2)<br /> ?1<br /> Using region: Southern California<br /> Choose a low frequency module:<br /> URS (1)<br /> UCSB (2)<br /> ?2<br /> Found multiple BBP station list files in the start directory. Please select one:<br /> nr_one_stat.stl (1)<br /> valid_test_stat.stl (2)<br /> ?1<br /> Choose a high frequency module:<br /> URS (1)<br /> UCSB (2)<br /> SDSU (3)<br /> ?2<br /> Choose a site response module:<br /> URS (1)<br /> UCSB (2)<br /> SDSU (3)<br /> ?1<br /> Do you want to plot velocity seismograms (y/n)? y<br /> Do you want to plot acceleration seismograms (y/n)? y<br /> Do you want to run goodness of fit (y/n)? n<br /> <br /> Since this run only includes one station, it will run in about 5 minutes. In the output directory you'll notice there are no goodness-of-fit or files, since we didn't run goodness-of-fit. However, there is also a map file (station_map.png), showing the fault plane and the stations, and a plot of the rupture slip (user_eq.png). The SRF generated by the rupture generator is in user_eq.srf; this file could be used in future runs. The filenames of the rupture slip plot and SRF are taken from the rupture description filename.<br /> <br /> == Sample User-defined run with SRF file and goodness-of-fit ==<br /> Finally, try a run with an SRF file and run goodness-of-fit on the results. Copy in examples/user_no_rup_gen/ucsb_modSRF_0.srf and examples/user_no_rup_gen/nr_three_stat.stl<br /> <br /> $&gt; run_bbp_2G.py <br /> Welcome to the SCEC Broadband Platform.<br /> Please select the modules you want to run.<br /> Do you want to perform a validation run (y/n)? n<br /> Do you want to run a rupture generator (y/n)? n<br /> Using region: Southern California<br /> Choose a low frequency module:<br /> URS (1)<br /> UCSB (2)<br /> ?1<br /> Found multiple BBP station list files in the start directory. Please select one:<br /> nr_one_stat.stl (1)<br /> valid_test_stat.stl (2)<br /> nr_three_stat.stl (3)<br /> ?3<br /> Choose a high frequency module:<br /> URS (1)<br /> UCSB (2)<br /> SDSU (3)<br /> ?3<br /> Choose a site response module:<br /> URS (1)<br /> UCSB (2)<br /> SDSU (3)<br /> ?1<br /> Do you want to plot velocity seismograms (y/n)? y<br /> Do you want to plot acceleration seismograms (y/n)? y<br /> Do you want to run goodness of fit (y/n)? y<br /> What reference files would you like to compare to? Enter a simulation ID or a scenario name: Northridge<br /> Enter a label to use for the comparison seismograms: nr<br /> <br /> The reference files can either be a scenario event or a simulation ID previously run. The label is just for the figures when comparisons are plotted.<br /> <br /> This run will take about 15 minutes, and the results can be found in the appropriate outdir. Again, the goodness of fit measures will look poor due to the few stations involved in the comparison. If you had fewer than 3 stations, no goodness-of-fit plots would be produced. However, response spectra comparison plots will still be generated.<br /> <br /> = File Formats =<br /> This section offers descriptions of various file formats in the broadband platform.<br /> <br /> == Simple source description ==<br /> This is the format for the simple source description. It is not whitespace sensitive. The filename must end in .src for the platform to identify it as a source description.<br /> <br /> MAGNITUDE = &lt;magnitude&gt;<br /> FAULT_LENGTH = &lt;length of fault&gt;<br /> DLEN = &lt;DX, along length&gt;<br /> FAULT_WIDTH = &lt;down-dip fault width&gt;<br /> DWID = &lt;DY, along width&gt;<br /> DEPTH_TO_TOP = &lt;depth of fault below surface&gt;<br /> STRIKE = &lt;nowiki&gt;&lt;strike&gt;&lt;/nowiki&gt;<br /> RAKE = &lt;rake&gt;<br /> DIP = &lt;dip&gt;<br /> LAT_TOP_CENTER = &lt;latitude of top center point in fault plane&gt;<br /> LON_TOP_CENTER = &lt;longitude of top center point in fault plane&gt;<br /> HYPO_ALONG_STK = &lt;along strike location of hypocenter (0.0 = middle)&gt;<br /> HYPO_DOWN_DIP = &lt;down dip location of hypocenter (0.0 = top)&gt;<br /> DT = &lt;nowiki&gt;&lt;dt&gt;&lt;/nowiki&gt;<br /> SEED = &lt;random seed used in calculations&gt;<br /> CORNER_FREQ = &lt;corner frequency to use&gt;<br /> <br /> == SRF rupture description ==<br /> Details of the Standard Rupture Format (SRF) are given in more detail in the accompanying document. The general fault surface is represented by a distribution of point sources, and it can support one or more planes. The platform produces SRFs as output from rupture generators, but a user can also supply an SRF file as input for user-defined simulations. SRF filenames must end with the suffix .srf for the platform to correctly identify them.<br /> <br /> == Station File List ==<br /> The user may specify a list of stations, matching the following format:<br /> <br /> #optional<br /> %comment<br /> # lines<br /> &lt;nowiki&gt;&lt;lon&gt; &lt;lat&gt; &lt;stat name&gt; &lt;distance to fault trace&gt; &lt;Vs30&gt; &lt;LF corner&gt; &lt;HF corner&gt; &lt;stat info&gt;&lt;/nowiki&gt;<br /> ...<br /> <br /> The station list filename needs to end in .stl for the platform to recognize it as a station list.<br /> <br /> == BBP seismograms ==<br /> All intermediate and output seismograms are produced in a 4-column text format, whether velocity or acceleration.<br /> <br /> # optional<br /> % comment<br /> # lines<br /> &lt;nowiki&gt;&lt;timestamp&gt; &lt;North/South&gt; &lt;East/West&gt; &lt;Up/Down&gt;&lt;/nowiki&gt;<br /> ...<br /> <br /> Time is in seconds and motion is in cm/s (velocity) or cm/s/s (acceleration) unless otherwise specified in the header. Velocity filenames end in .vel.bbp; accelerations in .acc.bbp.<br /> <br /> == Response spectra ==<br /> The response spectra file is in 4-column text format.<br /> <br /> # optional<br /> % comment<br /> # lines<br /> &lt;nowiki&gt;&lt;period (sec)&gt; &lt;North/South&gt; &lt;East/West&gt; &lt;Up/Down&gt;&lt;/nowiki&gt;<br /> ...<br /> <br /> The platform samples response spectra at 112 periods, 0.01-20 sec and outputs pseudo spectral acceleration in units of g.<br /> <br /> == Option File ==<br /> Option files contain responses to the prompts in the platform. You can use them with the -o option to run_bbp_2G.py. The responses have to match the prompts exactly. For example, if you craft an option file assuming there is only one station list in the start directory (and therefore the user isn't prompted to select one) but then it is run with multiple station lists in the start directory, this will cause the run to abort. Option files are recommended to perform a series of runs with different inputs or different modules. If you have a run you perform regularly, it's better practice to run the platform with the -g option and the option file to produce an XML description, which are more complete descriptions of the workflow.<br /> <br /> #optional comments<br /> %using either symbol<br /> n #comments<br /> y % can go<br /> 1 # here<br /> ...<br /> <br /> Use with:<br /> <br /> $&gt; run_bbp_2G.py -o &lt;option file&gt;<br /> <br /> == XML workflow description schema ==<br /> Each time the platform is invoked, an XML file is produced describing the workflow, obeying the following schema:<br /> <br /> &lt;nowiki&gt;&lt;xs:schema xmlns:xs=&quot;http://www.w3.org/2001/XMLSchema&quot;&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:element name= &quot;BBP_Run_Specification&quot; minOccurs= &quot;1&quot; maxOccurs= &quot;1&quot;&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:attribute name=&quot;version&quot; type = &quot;xs:string&quot; use = &quot;required&quot; /&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:complexType&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:sequence&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:element name= &quot;Validation_Run&quot; minOccurs= &quot;0&quot; maxOccurs = &quot;1&quot;&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:attribute name= &quot;event&quot; type= &quot;xs:string&quot; use= &quot;required&quot; /&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:attribute name= &quot;input_station_file&quot; type = &quot;xs:string&quot; /&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:attribute name= &quot;subset&quot; type = &quot;xs:boolean&quot; use = &quot;required&quot; /&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;/xs:element&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:element name= &quot;BBP_Modules&quot;&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:complexType&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:sequence&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:element name = &quot;BBP_Module&quot; maxOccurs = &quot;unbounded&quot; &gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:complexType&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:sequence&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:element name= &quot;name&quot; type=&quot;xs:string&quot; /&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:element name= &quot;staged_files&quot; &gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:complexType&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:sequence&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:element name=&quot;file&quot; type=&quot;xs:string&quot; maxOccurs= &quot;unbounded&quot;/&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;/xs:sequence&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;/xs:complexType&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;/xs:element&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:element name= &quot;arguments&quot; &gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:complexType&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:sequence&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:element name=&quot;argument&quot; type=&quot;xs:string&quot; maxOccurs=&quot;unbounded&quot;&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:attribute name= &quot;type&quot; type= &quot;xs:string&quot; user= &quot;required&quot; /&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;/xs:element&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;/xs:sequence&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;/xs:complexType&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;/xs:element&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;/xs:sequence&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;/xs:complexType&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;/xs:element&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;/xs:sequence&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;/xs:complexType&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;/xs:element&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;/xs:sequence&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;/xs:complexType&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;/xs:element&gt;&lt;/nowiki&gt;<br /> <br /> These files are difficult to construct by hand, but can be generated using the -g flag when running run_bbp_2G.py.<br /> <br /> = User Support =<br /> If you run into bugs with the platform, you can open a trouble ticket at the [http://northridge.usc.edu/trac/broadband Broadband Trac site].<br /> <br /> Check to see if there has already been a ticket opened for the bug. If you are unable to get the platform to run, you can get direct user support by emailing [mailto:software@intensity.usc.edu software@intensity.usc.edu].<br /> <br /> = Appendix A: Possible Module Permutations =<br /> == Validation Events ==<br /> <br /> {| class=&quot;wikitable&quot; | border=&quot;1&quot;<br /> | Permutation #<br /> | Low-frequency module<br /> | High-frequency module<br /> | Site response<br /> <br /> |-<br /> | &lt;center&gt;1&lt;/center&gt;<br /> | &lt;center&gt;URS 1D&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;2&lt;/center&gt;<br /> | &lt;center&gt;URS 1D&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;3&lt;/center&gt;<br /> | &lt;center&gt;URS 1D&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;4&lt;/center&gt;<br /> | &lt;center&gt;URS 1D&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;5&lt;/center&gt;<br /> | &lt;center&gt;URS 1D&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;6&lt;/center&gt;<br /> | &lt;center&gt;URS 1D&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;7&lt;/center&gt;<br /> | &lt;center&gt;URS 1D&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;8&lt;/center&gt;<br /> | &lt;center&gt;URS 1D&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;9&lt;/center&gt;<br /> | &lt;center&gt;URS 1D&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;10&lt;/center&gt;<br /> | &lt;center&gt;URS 3D precomputed&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;11&lt;/center&gt;<br /> | &lt;center&gt;URS 3D precomputed&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;12&lt;/center&gt;<br /> | &lt;center&gt;URS 3D precomputed&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;13&lt;/center&gt;<br /> | &lt;center&gt;URS 3D precomputed&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;14&lt;/center&gt;<br /> | &lt;center&gt;URS 3D precomputed&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;15&lt;/center&gt;<br /> | &lt;center&gt;URS 3D precomputed&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;16&lt;/center&gt;<br /> | &lt;center&gt;URS 3D precomputed&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;17&lt;/center&gt;<br /> | &lt;center&gt;URS 3D precomputed&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;18&lt;/center&gt;<br /> | &lt;center&gt;URS 3D precomputed&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;19&lt;/center&gt;<br /> | &lt;center&gt;UCSB 1D&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;20&lt;/center&gt;<br /> | &lt;center&gt;UCSB 1D&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;21&lt;/center&gt;<br /> | &lt;center&gt;UCSB 1D&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;22&lt;/center&gt;<br /> | &lt;center&gt;UCSB 1D&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;23&lt;/center&gt;<br /> | &lt;center&gt;UCSB 1D&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;24&lt;/center&gt;<br /> | &lt;center&gt;UCSB 1D&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;25&lt;/center&gt;<br /> | &lt;center&gt;UCSB 1D&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;26&lt;/center&gt;<br /> | &lt;center&gt;UCSB 1D&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;27&lt;/center&gt;<br /> | &lt;center&gt;UCSB 1D&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;28&lt;/center&gt;<br /> | &lt;center&gt;SDSU 1D&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;29&lt;/center&gt;<br /> | &lt;center&gt;SDSU 1D&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;30&lt;/center&gt;<br /> | &lt;center&gt;SDSU 1D&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;31&lt;/center&gt;<br /> | &lt;center&gt;SDSU 1D&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;32&lt;/center&gt;<br /> | &lt;center&gt;SDSU 1D&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;33&lt;/center&gt;<br /> | &lt;center&gt;SDSU 1D&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;34&lt;/center&gt;<br /> | &lt;center&gt;SDSU 1D&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;35&lt;/center&gt;<br /> | &lt;center&gt;SDSU 1D&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;36&lt;/center&gt;<br /> | &lt;center&gt;SDSU 1D&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;37&lt;/center&gt;<br /> | &lt;center&gt;SDSU 3D precomputed&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;38&lt;/center&gt;<br /> | &lt;center&gt;SDSU 3D precomputed&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;39&lt;/center&gt;<br /> | &lt;center&gt;SDSU 3D precomputed&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;40&lt;/center&gt;<br /> | &lt;center&gt;SDSU 3D precomputed&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;41&lt;/center&gt;<br /> | &lt;center&gt;SDSU 3D precomputed&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;42&lt;/center&gt;<br /> | &lt;center&gt;SDSU 3D precomputed&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;43&lt;/center&gt;<br /> | &lt;center&gt;SDSU 3D precomputed&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;44&lt;/center&gt;<br /> | &lt;center&gt;SDSU 3D precomputed&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;45&lt;/center&gt;<br /> | &lt;center&gt;SDSU 3D precomputed&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> |}<br /> <br /> ==User-Defined Events==<br /> <br /> {| class=&quot;wikitable&quot; | border=&quot;1&quot;<br /> | Permutation #<br /> | Rupture generator<br /> | Low-frequency<br /> | High-frequency<br /> | Site response<br /> <br /> |-<br /> | &lt;center&gt;1&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;2&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;3&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;4&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;5&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;6&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;7&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;8&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;9&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;10&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;11&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;12&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;13&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;14&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;15&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;16&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;17&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;18&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;19&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;20&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;21&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;22&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;23&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;24&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;25&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;26&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;27&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;28&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;29&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;30&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;31&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;32&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;33&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;34&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;35&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;36&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;37&lt;/center&gt;<br /> | &lt;center&gt;User-supplied SRF&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;38&lt;/center&gt;<br /> | &lt;center&gt;User-supplied SRF&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;39&lt;/center&gt;<br /> | &lt;center&gt;User-supplied SRF&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;40&lt;/center&gt;<br /> | &lt;center&gt;User-supplied SRF&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;41&lt;/center&gt;<br /> | &lt;center&gt;User-supplied SRF&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;42&lt;/center&gt;<br /> | &lt;center&gt;User-supplied SRF&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;43&lt;/center&gt;<br /> | &lt;center&gt;User-supplied SRF&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;44&lt;/center&gt;<br /> | &lt;center&gt;User-supplied SRF&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;45&lt;/center&gt;<br /> | &lt;center&gt;User-supplied SRF&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;46&lt;/center&gt;<br /> | &lt;center&gt;User-supplied SRF&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;47&lt;/center&gt;<br /> | &lt;center&gt;User-supplied SRF&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;48&lt;/center&gt;<br /> | &lt;center&gt;User-supplied SRF&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;49&lt;/center&gt;<br /> | &lt;center&gt;User-supplied SRF&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;50&lt;/center&gt;<br /> | &lt;center&gt;User-supplied SRF&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;51&lt;/center&gt;<br /> | &lt;center&gt;User-supplied SRF&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;52&lt;/center&gt;<br /> | &lt;center&gt;User-supplied SRF&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;53&lt;/center&gt;<br /> | &lt;center&gt;User-supplied SRF&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;54&lt;/center&gt;<br /> | &lt;center&gt;User-supplied SRF&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> |}<br /> <br /> = Appendix B: Troubleshooting =<br /> If you experience trouble building the platform or successfully running test and simulations, try the following solutions.<br /> <br /> == Build Errors ==<br /> <br /> The instruction for installing Broadband Platform are listed in Section 1: &quot;Installing the Second-Generation Broadband Platform&quot; of the User guide. If after following all steps listed in this section of the user guide the build fails, check if the failure is listed in this section and try the solution to fix the issue you are facing.<br /> <br /> === 64-bit Intel Compiler Issue ===<br /> If you try to compile with:<br /> &lt;pre&gt;<br /> % cd bbp_2g/src<br /> % make<br /> &lt;/pre&gt; <br /> <br /> and you get:<br /> &lt;pre&gt;<br /> ... <br /> make[2]: Entering directory `.../bbp_2g/src/ucsb/getInFile'<br /> icc -o getfaultGlobal getfaultGlobal.c<br /> ld: cannot find -lgcc_s_32<br /> make[2]: *** [getfaultGlobal] Error 1<br /> make[2]: Leaving directory `.../bbp_2g/src/ucsb/getInFile'<br /> make[1]: *** [all] Error 2<br /> make[1]: Leaving directory `.../bbp_2g/src/ucsb'<br /> make: *** [all] Error 2<br /> &lt;/pre&gt;<br /> <br /> '''Cause:''' The Broadband Platform requires Intel 64-bit compilers to build successfully. In this case the 32-bit Intel compilers are being invoked as they are being picked up from the PATH environment variable. The error is due to a missing GNU-GCC 32-bit compatibility pack that has not been installed on your system. This is not required when 64-bit Intel compilers are used.<br /> <br /> '''Solution:''' Ensure that the path Intel 64-bit compilers are listed in you PATH variable and being picked up by running 'which icc' and 'which ifort'. If you are trying to build the platform on SCEC development servers like Intensity, verify your path variable has:<br /> &lt;pre&gt;<br /> PATH=...:/usr/usc/intel/composerxe-2011.4.191/mpirt/bin/intel64:/usr/usc/intel/composerxe-2011.4.191/bin/intel64<br /> &lt;/pre&gt;<br /> <br /> === 32-bit Platform Issue ===<br /> <br /> On trying to build the platform, the build fails with the following message:<br /> &lt;pre&gt;<br /> $ make all<br /> cd urs; make -f makefile FC=gfortran CC=icc USER_C=1;<br /> make[1]: Entering directory `.../bbp_2g/src/urs'<br /> mkdir -p bin;<br /> cd getpar/src; make -f Makefile CC=icc FC=gfortran USER_C=1;<br /> make[2]: Entering directory `.../bbp_2g/src/urs/getpar/src'<br /> icc -O3 -DENVIRONMENT -c -o defpar.o defpar.c<br /> icc -O3 -DENVIRONMENT -c -o getpar.o getpar.c<br /> icc -O3 -DENVIRONMENT -c -o getarg.o getarg.c<br /> getarg.c(112): warning #303: explicit type is missing (&quot;int&quot; assumed)<br /> register i;<br /> ^ <br /> icc -O3 -DENVIRONMENT -c -o getlocation.o getlocation.c<br /> getlocation.c(9): warning #147: declaration is incompatible with &quot;__ssize_t={int} getline(char **restrict, size_t={unsigned int} *restrict, FILE *restrict)&quot; (declared at line 671 of &quot;/usr/include/stdio.h&quot;)<br /> static int getline(FILE *fd, char *line)<br /> <br /> ...<br /> ...<br /> ...<br /> <br /> make[2]: Entering directory `.../bbp_2g/src/sdsu/srcV1.4'<br /> icc -w -Wall -c ray3DJHfor.c<br /> gfortran module_bbtoolbox.f90 module_interface.f90 main_bbtoolbox.f90 coda.f90 composition.f90 convolution.f90 fourier.f90 error.f90 geometry.f90 interpolation.f90 io.f90 random.f90 scattering.f90 source.f90 ray3DJHfor.o -o BBtoolbox.exe<br /> ray3DJHfor.o: In function `raytracing_':<br /> ray3DJHfor.c:(.text+0x8cf): undefined reference to `__libm_sse2_log'<br /> ray3DJHfor.c:(.text+0x96b): undefined reference to `__libm_sse2_asin'<br /> ray3DJHfor.c:(.text+0x9cd): undefined reference to `__libm_sse2_asin'<br /> ray3DJHfor.c:(.text+0xa00): undefined reference to `__libm_sse2_tan'<br /> ray3DJHfor.c:(.text+0xa3d): undefined reference to `__libm_sse2_tan'<br /> ray3DJHfor.c:(.text+0xa52): undefined reference to `__libm_sse2_log'<br /> collect2: ld returned 1 exit status<br /> make[2]: *** [BBtoolbox.exe] Error 1<br /> make[2]: Leaving directory `.../bbp_2g/src/sdsu/srcV1.4'<br /> make[1]: *** [all] Error 2<br /> make[1]: Leaving directory `.../bbp_2g/src/sdsu'<br /> make: *** [all] Error 2<br /> &lt;/pre&gt;<br /> <br /> '''Cause:''' In this case the user tried to build Broadband on a 32-bit platform. Broadband code was designed to be run on 64-bit platform. Any attempt to build Broadband on a 32-bit platform will result in numerous warnings and the build will fail with error messages similar to ones listed above.<br /> <br /> '''Solution:''' Try building Broadband on a 64-bit platform will the all the dependencies listed in Section 1.1: &quot;System Dependencies&quot; and Section 1.2: &quot;Software Dependencies&quot;<br /> <br /> == Unit/Acceptance Test Failures and Errors ==<br /> <br /> Unit and Acceptance tests are provided to verify the Broadband platform and it's supporting modules built by the user are functioning as designed. Under certain circumstances, some of these test might fail. While some of these failure might indicate serious problems that will have to be addressed before the platform can used, it is acceptable to ignore some of the failures. This section lists some failures and their solutions.<br /> <br /> === ERROR: test_syn1d (test_syn1d.Test_syn1D) ===<br /> The Unit test for Syn1d module fails with the following message:<br /> &lt;pre&gt;<br /> ERROR: test_syn1d (test_syn1d.Test_syn1D)<br /> ----------------------------------------------------------------------<br /> Traceback (most recent call last):<br /> File &quot;.../bbp_2g/tests/test_syn1d.py&quot;, line 62, in test_syn1d<br /> synObj.run()<br /> File &quot;.../bbp_2g/comps/syn1D.py&quot;, line 236, in run<br /> shutil.copy2(a_tmpfile, expected_file)<br /> File &quot;/usr/lib/python2.6/shutil.py&quot;, line 99, in copy2<br /> copyfile(src, dst)<br /> File &quot;/usr/lib/python2.6/shutil.py&quot;, line 52, in copyfile<br /> fsrc = open(src, 'rb')<br /> IOError: [Errno 2] No such file or directory: '.../bbp_2g/tmpdata/3310632/s01.3comp'<br /> &lt;/pre&gt;<br /> <br /> '''Cause:''' Syn1d module requires the Green's Function file to run and the path to this file might be incorrect in 'bbp_2g_gf/ucsb/GreenBank/Northridge/GreenBank.inf' file.<br /> <br /> '''Solution:''' This issue can be fixed by correcting the paths listed in the GreenBank.inf files in the Green's Function directory. Here are step by step instructions to fix this issue:<br /> <br /> 1. Locate your Greens Functions directory: 'bbp_2g_gf'<br /> 2. Navigate to bbp_2g_gf/ucsb/GreenBank/Northridge folder.<br /> 3. Open Green_Bank.inf files with a text editor.<br /> 4. Locate the text &quot;The name of file to store Green Bank&quot;<br /> 5. Note the location of the Green Bank file under the line found in step 4, similar to &quot;/home/scec-00/scottcal/bband/bbp_2g_gf/ucsb/GreenBank/Northridge/Green_1d.soil&quot;.<br /> 6. Replace the path found in Step 5 with just the file name, in the case of Northridge it is &quot;Green_1d.soil&quot;<br /> 7. Save and close the Green_Bank.inf.<br /> 8. Navigate to bbp_2g_gf/ucsb/GreenBank/LomaPrieta folder and repeat steps 3-7. The name of the Green Bank file for LomaPrieta is &quot;Green_1d.LoPr&quot;.<br /> 9. Navigate to bbp_2g_gf/ucsb/GreenBank/Landers folder and repeat steps 3-7. The name of the Green Bank file for Landers is &quot;Green1D.Landers&quot;<br /> <br /> === ERROR: test_gensrf (test_genslip.Test_Genslip) ===<br /> The Unit test for Genslip module fails with the following message:<br /> &lt;pre&gt;<br /> ======================================================================<br /> ERROR: test_gensrf (test_genslip.Test_Genslip)<br /> ----------------------------------------------------------------------<br /> Traceback (most recent call last):<br /> File &quot;.../bbp_2g/tests/test_genslip.py&quot;, line 51, in test_gensrf<br /> gen.run()<br /> File &quot;.../bbp_2g/comps/genslip.py&quot;, line 153, in run<br /> ps.run()<br /> File &quot;.../bbp_2g/comps/plot_srf.py&quot;, line 52, in run<br /> shutil.copy2(&quot;%s/%s.ps.png&quot; % (a_tmpdir, self.r_srffile[0:self.r_srffile.find(&quot;.srf&quot;)]), &quot;%s/%s.png&quot; % (a_outdir, self.r_srffile[0:self.r_srffile.find(&quot;.srf&quot;)]))<br /> File &quot;/usr/lib/python2.6/shutil.py&quot;, line 99, in copy2<br /> copyfile(src, dst)<br /> File &quot;/usr/lib/python2.6/shutil.py&quot;, line 52, in copyfile<br /> fsrc = open(src, 'rb')<br /> IOError: [Errno 2] No such file or directory: '.../bbp_2g/tmpdata/3309008/3309008_test_eq.ps.png'<br /> &lt;/pre&gt;<br /> <br /> '''Cause:''' The Genslip module calls the Plot_SRF module to the plot the SRF file. Plot_SRF uses C-shell code to locate and use GMT package to plot the SRF file. This shell code might fail on some flavors of Linux with a message like &quot;Newline in variable name&quot; in the Plot_SRF log file.<br /> <br /> '''Solution:''' This issue can be fixed by editing the plot_SRF.csh file. Here are step by step instructions to fix this issue:<br /> <br /> 1. Locate shell script file: bbp_2g/src/plot/plot_SRF.csh<br /> 2. Open the file in your preferred text editor<br /> 3. Locate the line 'set FIND_GMT = $?'<br /> 4. Replace the line found in step 3 with 'set FIND_GMT = $status'<br /> 5. Locate the section of code that starts with the statement &quot;# FIND MAX. SLIP&quot;<br /> 6. Replace the following line in section found in step 5:<br /> &lt;pre&gt;<br /> set SMAX = `$XYZCODE calc_xy=$CALC_XY type=&quot;${TYPE}&quot; nseg=-1 &lt; $SLIPFILE.srf | \<br /> gawk -v m=$SMAX '{if($3&gt;m)m=$3;}END{printf &quot;%.0f\n&quot;,m;}'`<br /> <br /> with (collapse the statement to a single line by removing '\' at the end of first part of the statement):<br /> <br /> set SMAX = `$XYZCODE calc_xy=$CALC_XY type=&quot;${TYPE}&quot; nseg=-1 &lt; $SLIPFILE.srf | gawk -v m=$SMAX '{if($3&gt;m)m=$3;}END{printf &quot;%.0f\n&quot;,m;}'`<br /> &lt;/pre&gt;<br /> 7. Save the file and exit<br /> <br /> === ERROR: test_ucgen (test_ucrmg.Test_UCrmg) ===<br /> The Unit test for Ucrmg module fails with the following message:<br /> &lt;pre&gt;<br /> ======================================================================<br /> ERROR: test_ucgen (test_ucrmg.Test_UCrmg)<br /> ----------------------------------------------------------------------<br /> Traceback (most recent call last):<br /> File &quot;.../bbp_2g/tests/test_ucrmg.py&quot;, line 59, in test_ucgen<br /> ucObj.run()<br /> File &quot;.../bbp_2g/comps/ucrmg.py&quot;, line 161, in run<br /> ps.run()<br /> File &quot;.../bbp_2g/comps/plot_srf.py&quot;, line 52, in run<br /> shutil.copy2(&quot;%s/%s.ps.png&quot; % (a_tmpdir, self.r_srffile[0:self.r_srffile.find(&quot;.srf&quot;)]), &quot;%s/%s.png&quot; % (a_outdir, self.r_srffile[0:self.r_srffile.find(&quot;.srf&quot;)]))<br /> File &quot;/usr/lib/python2.6/shutil.py&quot;, line 99, in copy2<br /> copyfile(src, dst)<br /> File &quot;/usr/lib/python2.6/shutil.py&quot;, line 52, in copyfile<br /> fsrc = open(src, 'rb')<br /> IOError: [Errno 2] No such file or directory: '.../bbp_2g/tmpdata/3309831/test_ucsb.ps.png'<br /> &lt;/pre&gt;<br /> <br /> '''Cause:''' The Ucrmg module calls the Plot_SRF module to the plot the SRF file. Plot_SRF uses C-shell code to locate and use GMT package to plot the SRF file. This shell code might fail on some flavors of Linux with a message like &quot;Newline in variable name&quot; in the Plot_SRF log file.<br /> <br /> '''Solution:''' This issue can be fixed by editing the plot_SRF.csh file. The steps to fix this issue are listed under the solution for &quot;ERROR: test_gensrf (test_genslip.Test_Genslip)&quot; above.<br /> <br /> === FAIL: test_site_amp (test_uc_site.Test_UC_Site) ===<br /> <br /> The unit test for UC-Site module might fail with the following message:<br /> &lt;pre&gt;<br /> ======================================================================<br /> FAIL: test_site_amp (test_uc_site.Test_UC_Site)<br /> ----------------------------------------------------------------------<br /> Traceback (most recent call last):<br /> File &quot;.../bbp_2g/tests/test_uc_site.py&quot;, line 92, in test_site_amp<br /> self.failIf(cmp_bbp.cmp_bbp(a_ref_file_no_header, test_file_no_header, tolerance=0.035)!=0,errmsg)<br /> AssertionError: Output file .../bbp_2g/tmpdata/3310633/s04.3comp does not match reference file .../bbp_2g/ref_data/ucsb/s04.site.3comp<br /> &lt;/pre&gt;<br /> <br /> '''Cause:''' The synthetic seismogram generated by the UC-Site module on the user system differs from the reference result included in the Broadband release.<br /> <br /> '''Solution:''' The stochastic nature of the high frequency simulations is considered, and a constant random seed as input for our tests. This is the same constant random seed used to generate the reference results included in the release. This ensures that the time-series generated with unit tests agree with reference results. However, the high frequency codes are more sensitive to changes in compilers and machines due to the algorithm, so small differences that cause the test to fail are generally acceptable. The user is however encouraged to plot the two time-series and visually inspect them to verify they look similar. We are trying to come up with a better comparison for these tests.<br /> <br /> = Appendix C: Technical Notes =<br /> <br /> == Running Individual Acceptance Tests ==<br /> <br /> The acceptance test script ./tests/AcceptTest.py attempts to run all of the defined tests when executed. However, sometimes it is useful to run an acceptance test in isolation for troubleshooting purposes:<br /> <br /> * Identify the test you want to run. Eg: user-URS-UCSB-SDSU-SDSU<br /> * Move to the ./comps directory and execute that test's XML workflow with run_bbp_2G.py. Using the above example:<br /> &lt;pre&gt;<br /> $ ./run_bbp_2G.py -x ../ref_data/accept_inputs/user-URS-UCSB-SDSU-SDSU.xml<br /> &lt;/pre&gt;<br /> <br /> Since you are running the test outside of AcceptTest.py, you will not see a PASS/FAIL message once the simulation completes. However, you can review the contents of the ./outdata/&lt;SIMID&gt; directory to verify that the correct seismograms and response spectra tables were produced.<br /> <br /> == Manaully Setting Random Number Generator Seed Values ==<br /> <br /> Several of the platform codebases employ random number generators to produce SRFs and seismograms. These random number generators are generally seeded with an initial value (typically an integer) which are hard-coded in the platform. Advanced users may desire to change these seed values.<br /> <br /> Changing the seeds for seismogram synthesis varies depending on which codebase you want to use:<br /> <br /> * URS: Edit ./comps/hfsims_cfg.py, Line 43 &quot;self.RAND_NUM&quot;<br /> * UCSB: Edit ./src/ucsb/Syn1DSCEC/syn1D_LAH.f, Line 183 &quot;iseed&quot;, and recompile with &quot;make&quot;<br /> * SDSU:<br /> ** User event: Edit ./bbp_2g_gf/sdsu/scattering_generic.dat (seed values annotated in file)<br /> ** Validation event: Edit ./bbp_2g_gf/sdsu/&lt;event&gt;/scattering.dat</div> Patrices https://strike.scec.org/scecwiki/index.php?title=Broadband_User_Guide_v11.2.3&diff=5055 Broadband User Guide v11.2.3 2012-05-08T21:55:24Z <p>Patrices: </p> <hr /> <div>'''Version 11.2.3.'''<br /> <br /> If you find errors in this document or sections to be unclear, please either fix them yourself or contact software@scec.org.<br /> <br /> = Installing the Second-Generation Broadband Platform =<br /> Installing the Broadband Platform involves obtaining a copy of the code and building the required executables. You can either download the platform from the Broadband web site ([http://www.scec.org/research/broadband http://www.scec.org/research/broadband]) or check the code out of SCEC's Subversion repository. Most users should download the platform.<br /> <br /> = System Dependencies =<br /> The current version of the Broadband Platform is designed to run on standard 64-bit Linux machines. Testing has been performed on SCEC's development servers running Fedora Core 10 (kernel version 2.6.27.41-170.2.117.fc10.x86_64). In this guide we outline how to install the platform into your own account on a Linux computer using the simplest approach.<br /> <br /> = Software Dependencies =<br /> The Broadband Platform has certain software dependencies.<br /> <br /> Required:<br /> <br /> *Python v2.7 with<br /> **PyGTK<br /> **Matplotlib<br /> **Numpy<br /> **Pyproj<br /> <br /> *Intel compilers (64-bit) v12.0.4<br /> *GNU compilers (gcc, gfortran) v4.5.1<br /> *GNU Fortran 77 v3.4.6<br /> *GMT (Generic Mapping Toolkit)<br /> *ImageMagick<br /> <br /> = Setting Up Your Account =<br /> For simplicity of installation, we recommend users use a bash shell for the Broadband Platform account. It is possible to get the platform running using other shell's, but we will focus on a bash shell installation. The user environment is a common source of problems since certain environment variables must be defined for the platform to work correctly.<br /> <br /> To check your account, make sure you can run basic commands like ''ls'' and ''cd'' before proceeding.<br /> <br /> = Downloading the Platform =<br /> &lt;nowiki&gt;Download 4 files from the Broadband website, the code (bbp_dist_&lt;version&gt;.tgz), the data (bbp_data_&lt;version&gt;.tgz), and their checksum files (bbp_dist_&lt;version&gt;.tgz.md5 and bbp_data_&lt;version&gt;.tgz.md5). &lt;/nowiki&gt;The code file is about 100 MB, the data file about 3 GB. After you've downloaded the files to your local Linux system, the next step is to calculate the checksums yourself and compare them to the checksums you downloaded.<br /> <br /> First, verify that the ''md5sum'' command is in your path:<br /> <br /> $&gt; which md5sum<br /> <br /> You should get something like /usr/bin/md5sum. If you see the message 'no md5sum in...', contact your Linux system administrator and ask to have md5sum added to your path.<br /> <br /> Once you can run the ''md5sum'' command, run:<br /> <br /> $&gt; md5sum -c bbp_dist_&lt;version&gt;.tgz.md5<br /> $&gt; md5sum -c bbp_data_&lt;version&gt;.tgz.md5<br /> <br /> You should get the messages<br /> bbp_dist_&lt;version&gt;.tgz.md5: OK<br /> bbp_data_&lt;version&gt;.tgz.md5: OK<br /> <br /> If you get FAILED instead, re-download the tgz files and try again. When it passes, that means the files were downloaded without error.<br /> <br /> Once both files have passed the checksum test, untar the files.<br /> <br /> $&gt; tar xzvf bbp_dist_&lt;version&gt;.tgz file<br /> $&gt; tar xzvf bbp_data_&lt;version&gt;.tgz file<br /> <br /> If multiple users are planning to use the platform on the same system, you only need one copy of the data files per machine. Each user will still need his or her own copy of the code files.<br /> <br /> Alternatively, if you would like access to the latest version of the platform and get frequent but less thoroughly tested improvements, you can check out the platform from SCEC's Subversion repository. Only advanced users should take this approach, outlined in detail in the [[#Advanced Users| Advanced Users section]].<br /> <br /> = User Account Setup =<br /> <br /> The Broadband platform installation is divided into two parts (1) input Green Functions (GF) data directory (9.3Gb), and (2) BBP home directory (366Mb). <br /> <br /> First, the Green's function libraries are larger, but they are static. The broadband platform reads the data files, but does not change them. <br /> <br /> Second, the remainder of the broadband platform is organized in the BBP home directory. The BBP home directory has a specific directory structure that includes the source code for the scientific programs, the python scripts that link the scientific programs, simulation input directory, temporary and log file directories, and the output data directory where all the platform results are written.<br /> <br /> The BBP home directory will increase in size as you run the platform, because both output data and output log files are written to the home directory. Running the acceptance tests will produce nearly ( 10Gb) of input data (5.2Gb), output data (500Mb), temporary files (2.7Gb), and output log files (250Mb). Once these tests have passed much of this data can be removed. However, the BBP home directory should have at least 10Gb of disk space to insure the acceptance tests can be run when a particular broadband platform software distribution is first installed on a system.<br /> <br /> = Data Directory =<br /> Input data files called Greens Functions are distributed with the platform. These files are generated using specific velocity structures, so they are often considered region specific. We have GF for three regions including near Loma Prieta, near Landers, and near Northridge.<br /> <br /> The data directory is static, and the data directories are read-only. A single copy can be installed in a shared disk, which can then be shared by multiple users.<br /> <br /> = Setting Environment Variables =<br /> The BBP source codes and scripts are organized under the broadband platform home directory. The broadband platform home directory is specified in a couple of places during Broadband Platform installation. <br /> <br /> Internal to the Broadband platform software, all broadband platform files (except the Greens Function data files) are in sub-directories of the BBP home directory.<br /> <br /> = BBP Environment Variable =<br /> We recommend setting both an alias and a environment variable to the BBP home directory. This will help avoid typing it many times.<br /> <br /> If you're running a Bash shell, add the following line to your .bash_profile with your favorite text editor:<br /> <br /> export BBP=/home/scec-00/kumar/bbp_2g<br /> <br /> If you're running a C-shell, add the following line to your .cshrc with your favorite text editor:<br /> <br /> setenv BBP /home/scec-00/kumar/bbp_2g<br /> <br /> * PYTHONPATH<br /> After you've obtained a copy of the project, you'll need to make sure the comps directory is on Python's path so Python can find all the project modules. If you're running a Bash shell, add the following line to your .bash_profile with your favorite text editor:<br /> <br /> export PYTHONPATH=$BBP/comps:$PYTHONPATH<br /> <br /> If you're running a C-shell, add the following line to your .cshrc with your favorite text editor:<br /> <br /> setenv PYTHONPATH $BBP/comps:$PYTHONPATH<br /> <br /> * PATH<br /> In order to successfully compile the project, you'll need to make sure the required compilers directories are in your PATH variable. Broadband requires Intel 64-bit compilers, icc and ifort and GNU Compilers, gcc, g77 and f77 to compile the scientific code.<br /> <br /> If you are planning to run Broadband on SCEC Development servers, make sure you have the following directories in your PATH:<br /> <br /> For Bash Shell (in .bash_profile)<br /> <br /> export PATH=/usr/usc/intel/composerxe-2011.4.191/bin/intel64:/usr/usc/intel/composerxe-2011.4.191/mpirt/bin/intel64:$PATH<br /> <br /> For C-shell (in .cshrc)<br /> <br /> setenv PATH /usr/usc/intel/composerxe-2011.4.191/bin/intel64:/usr/usc/intel/composerxe-2011.4.191/mpirt/bin/intel64:$PATH<br /> <br /> When running elements of the platform over ssh, be sure to enable ssh forwarding (with the -X or -Y options).<br /> <br /> After modifying your login script above, log out and log back into the machine so the changes are reflected in your environment.<br /> <br /> = Edit Install_cfg.py with Installation Directory Paths =<br /> <br /> You need to tell the platform where it's installed by editing a single python file called &quot;install_cfg.py&quot;. Edit the file bbp_2g/comps/install_cfg.py with your favorite text editor, and edit the lines:<br /> <br /> self.A_INSTALL_ROOT = &lt;bbp_2g directory&gt;<br /> self.A_GF_DIR = &lt;bbp_2g_gf directory&gt;<br /> <br /> as one example:<br /> <br /> self.A_INSTALL_ROOT = /home/scec-00/kumar/bbp_2g<br /> self.A_GF_DIR = /home/scec-00/kumar/bbp_2g_gf<br /> <br /> with the paths on your system to the bbp_2g directory (the source) and the bbp_2g_gf directory (the data) that you unzipped. For example, it could be /home/scottcal/broadband_platform/bbp_2g and /home/scottcal/broadband_platform/bbp_2g_gf.<br /> <br /> Here is some information about these two directories that may be useful as you decide how, and where, to install these two parts of the Broadband Platform on your computer disk system. The data files, and therefore the &lt;bbp_2g_gf directory&gt; are nearly 3GB, but they are static and will not be modified and will not grow in size during use of the platform. The source directory is small to begin. However, this directory will increase as the platform is used, since the results produced by the platform will be stored here.<br /> <br /> = Directory Structure =<br /> The platform consists of two top-level directories, bbp_2g and bbp_2g_gf. bbp_2g contains the source code, executables, scripts, tests, input, working, and output directories. bbp_2g_gf contains the Green's Functions, input files for the validation events, and other required input files for the various code bases. Note that indata, logs, outdata, tmpdata, and xml are created when the platform is first run, so they will be missing when you first install the platform.<br /> <br /> bbp_2g has the following directories:<br /> *checksums: Contains checksums for bbp_2g_gf files<br /> *comps: The Python scripts to run the platform<br /> *docs: Documentation for the platform<br /> *etc: Miscellaneous utility scripts<br /> *examples: Contains example input files<br /> *indata: An internal directory, used to stage input files<br /> *logs: Contains logs from BBP runs<br /> *outdata: Contains output files from a run<br /> *ref_data: Contains reference files for BBP tests<br /> *start: Put input files for an interactive run here<br /> *src: Source code for BBP modules<br /> *tests: Contains unit and acceptance tests<br /> *tmpdata: An internal directory, used during a run<br /> *xml: Contains XML files which describe simulations and can be used as input<br /> <br /> bbp_2g_gf has the following directories:<br /> *compare: Contains observed seismograms for validation events<br /> *plot: Data files for GMT plots<br /> *sdsu, ucsb, urs: Contains Green's functions, velocity files, and other required inputs for the codebases.<br /> <br /> In general, you will be interacting with the start directory for input files, comps to run the platform, tests to test the platform, and outdata to examine data products.<br /> <br /> == Adding aliases ==<br /> <br /> You may find it helpful to add aliases, so you can quickly and easily move to different broadband directories with a single command. We recommend creating aliases for the home, start, and outdata directories.<br /> <br /> If you are using the Bash shell, you can create aliases by adding the following lines to ~/.bash_profile:<br /> <br /> alias bbp= 'cd &lt;path to bbp_2g directory&gt;'<br /> alias start='cd &lt;path to bbp_2g directory&gt;/start'<br /> alias outdata='cd &lt;path to bbp_2g directory&gt;/outdata'<br /> <br /> If you're using a C shell, edit your ~/.cshrc and add:<br /> <br /> alias bbp cd &lt;path to bbp_2g directory&gt;<br /> alias start cd &lt;path to bbp_2g directory&gt;/start<br /> alias outdata cd &lt;path to bbp_2g directory&gt;/outdata<br /> <br /> Log out and log back in. You'll notice that now you can type the alias command as a shortcut to change directories:<br /> <br /> $&gt; pwd<br /> /home/scec-00/scottcal<br /> $&gt; start<br /> $&gt; pwd<br /> /home/scec-00/scottcal/bband/bbp_2g/start<br /> <br /> This can be a useful way to navigate around the broadband platform directories.<br /> <br /> = Building the Platform =<br /> Once you have checked out the code, you need to build it. By default, every executable is compiled using the compiler recommended by the code developer. However, if you have limited compiler options or are building the codes on an untested system, you may need to specify non-standard alternative compilers, as described below.<br /> <br /> Before you can build the platform, you need to make sure that the Intel compilers are in your path. This is done automatically on broadband.usc.edu, but on other systems you can check by typing:<br /> <br /> $&gt;which icc<br /> <br /> If you get the message &quot;no icc in ...&quot;, then you'll need to add the Intel compilers to your path. Once the Intel compilers are in your path, you can make the code by cd-ing to the bbp_2g/src directory and typing make:<br /> <br /> $&gt; cd src<br /> $&gt; make<br /> <br /> It takes a minute or two to build the code. You may encounter build warnings; these are fine. However, if you get any build errors, this is a problem and should be investigated.<br /> <br /> By default, every executable is compiled using the compiler recommended by the code developer. Depending on the system, some compilers may not be available to you. You can override the C and Fortran compilers used by editing<br /> <br /> src/makefile<br /> <br /> Uncomment USER_C and set FC and CC to the compilers you wish. For example:<br /> <br /> Before:<br /> <br /> #USER_C=1<br /> FC=f77<br /> CC=gcc<br /> <br /> After (an example, you may choose different compilers):<br /> <br /> USER_C=1<br /> FC=gfortran<br /> CC=gcc<br /> <br /> Note that not all compiler combinations have been thoroughly tested. You may encounter build errors with untested compiler combinations. If you encounter any errors while building the platform, consult the Troubleshooting section at the end of this user guide for know issues and their solutions.<br /> <br /> Once the platform has been successfully built, you can move on to running the tests to verify that all components are working correctly.<br /> <br /> = Advanced Users =<br /> Alternatively, if you would like access to the latest version of the platform, to get frequent but less thoroughly tested improvements, you can check out the platform from SCEC's Subversion version control repository on source.usc.edu. Only advanced users should follow this approach. If you are unsure, you should download the code as outlined in [[#Downloading the Platform|Downloading the Platform]] and skip this section.<br /> <br /> You may need to request access from the SCEC system administrator, John Yu ([mailto:johnyu@usc.edu johnyu@usc.edu]). Make sure you have subversion in your path before beginning.<br /> <br /> Once you have access, you'll need to decide if you want a stable tagged version, or the latest version in the repository. For a stable version, open a terminal window on the system of your choice and type:<br /> <br /> $&gt; svn checkout https://source.usc.edu/svn/broadband/tags/&lt;stable version&gt; bbp_2g<br /> <br /> For the latest version, type:<br /> <br /> $&gt; svn checkout https://source.usc.edu/svn/broadband/trunk bbp_2g<br /> <br /> This will check out the project to your local machine. It contains the source code, tests, and some example files. You also need to obtain a copy of the Broadband Platform data files, containing the Green's tensors. They are too large to be stored in version control. You can obtain a copy from SCEC software distribution server. If you are working on SCEC development server, you might be able to create a symbolic link to data folder. Please contact [[#User_Support|User Support]] to get a location of the data folder on the SCEC development server. If you are not working on SCEC development server, or don't have an SCEC Linux login account, you can get a archive (.tgz) file of the Green's functions from the same download site you obtained this guide.<br /> <br /> If you know where a read-accessible installation of the green functions data directories you can create a link to that location. This can save disk space in some cases.<br /> <br /> ln -s /home/scec-00/scottcal/bband/bbp_2g_gf &lt;path to your gf directory&gt;<br /> <br /> Periodically you should check for updates to the code. To do so, go to your bbp_2g directory and type<br /> <br /> $&gt; svn update<br /> <br /> This will pull down any code updates that have been made in the repository. After you update, make the code again (detailed in [[#Building the Platform|Building the Platform]]) so that any code changes are captured in the executables.<br /> <br /> = Running the Broadband Platform =<br /> We recommend users initiate all Broadband Platform runs from the &quot;start&quot; directory. The start directory is a collection point for input files for a particular simulation.<br /> <br /> Assuming the user is starting at BBP home directory, the user should move to the start directory and then run the Checksum, Unit and Acceptance tests to confirm the Broadband Platform software installation is operating as expected.<br /> <br /> $&gt; cd start<br /> <br /> = Running Checksum, Unit, and Acceptance Tests =<br /> The broadband platform contains three kinds of tests. The checksum tests verify that the data files were copied correctly and you have all the files that are expected. Unit tests run each module using a set of input files, and compare the results against known outputs. They verify that each module has been built and is working correctly. Acceptance tests verify that the modules are working correctly together. They test the platform end-to-end using different combinations with known inputs and compare the results. All the possible module combinations for both user-defined and validation events are tested as checks against integration errors.<br /> <br /> Begin with the checksum tests. Once they past, run the unit tests and finally the acceptance tests.<br /> <br /> = Running Checksum Tests =<br /> To run the checksum tests, change to the checksums directory and run md5sum_check.py.<br /> <br /> From the BBP home directory:<br /> <br /> $&gt; cd checksums<br /> $&gt; ./md5sum_check.py<br /> <br /> It takes about 5 minutes to compute the checksums. If a checksum disagrees, that means that the contents of the datafile were not what was expected. Try reinstalling the data files and try again. If you continue to get a checksum error, contact support.<br /> <br /> Once the checksums agree, move on to the unit tests.<br /> <br /> = Running Unit Tests =<br /> To run the unit tests, change to the tests directory and run UnitTests.py.<br /> <br /> From the BBP home directory:<br /> <br /> $&gt; cd tests<br /> $&gt; ./UnitTests.py<br /> <br /> The unit tests take about 15 minutes to run. When they're complete, the console will either print &quot;OK&quot; or how many tests failed. If a test has failed, first check that you have built the executables.You can rerun just the specific test that failed (test_&lt;module&gt;.py). If the test is still failing, also verify that you have the ref_data directory, since it contains the input and reference files. If you're looking for more information about the failure, you can consult the Unit Tests log file in bbp_2g/logs/unit_test.log . If you can't determine the reason for the failure, contact support.<br /> <br /> Once the unit tests all pass, proceed to the acceptance tests. If there are any failure or errors while running the unit tests, consult the Troubleshooting section at the end of this user guide for know issues and their solutions.<br /> <br /> = Running Acceptance Tests =<br /> Make sure the unit tests pass before moving on to the acceptance tests. To run the acceptance tests, change to the tests directory (if you're not there already) and run AcceptTests.py. <br /> The acceptance tests take a long time to run, around 20 hours<br /> <br /> From the BBP home directory:<br /> <br /> $&gt; cd tests<br /> $&gt; ./AcceptTests.py &amp;&gt; accept.out &amp;<br /> <br /> Since the tests take so long to run (twenty hours), you should run them as a background process, and redirect their output to a log file, as shown in the command above.<br /> <br /> You can check the progress by tailing the log file.<br /> <br /> $&gt; tail accept.out<br /> <br /> When all the acceptance tests are completed, the AcceptTests.py script will either print &quot;OK&quot; or how many tests failed. <br /> <br /> Acceptance test failures indicate that the modules are not integrated correctly. Like with the unit tests, verify that you have the ref_data directory. If a certain acceptance test fails, you can get more information by consulting the acceptance test logs in bbp_2g/logs/acceptance_tests_logs/&lt;test that failed&gt;.log . If you can't determine the reason for the failure, contact [[support]].<br /> <br /> Since the acceptance tests can take a long time to run, you may wish to resume where you left off. This feature is supported automatically. If you do not wish to resume, delete the resume file in ref_data/accept_inputs/resume.txt. If there are any failure or errors while running the acceptance tests, consult the Troubleshooting section at the end of this user guide for know issues and their solutions.<br /> <br /> = Types of Broadband Platform Simulations =<br /> <br /> The platform supports two kinds of simulations, validation events and user-defined events. Validation simulations are performed using a historical event, and are directly compared to observed seismograms using goodness-of-fit. User-defined events are run using a rupture description provided by the user which may not necessarily be a historical earthquake.<br /> <br /> When you run a simulation, the platform assigns an ID to it. This ID can be used to track the simulation and locate the output data products.<br /> <br /> To supply input files to the platform, put them in the start directory. Extensions are important - the platform recognizes station lists (.stl), SRF files (.srf), and simple source descriptions (.src). If there are multiple files of a type, the platform will prompt the user to select one.<br /> <br /> To perform a simulation, a user selects between different required and optional modules. Below we present a summary of the various modules.<br /> <br /> = Modules =<br /> The broadband platform consists of a series of modules. There are two main types of modules, science modules and utility modules. Science modules are those for which the platform has multiple implementations, provided by different coding research groups. Utility modules only have 1 implementation. A schematic of the available modules and their flow relationships is shown below:<br /> <br /> = Science Modules =<br /> All simulations must include a low-frequency, high-frequency, and site response science module. Simulations may include an optional rupture generation science module. Users may select between the following different implementations of each of these modules:<br /> <br /> Rupture generation:URS, UCSB<br /> <br /> Low-frequency:URS, UCSB<br /> <br /> High-frequency:URS, UCSB, SDSU<br /> <br /> Site response:URS, UCSB, SDSU<br /> <br /> = Utility Modules =<br /> A spectral response utility module is automatically run after the site response module. Additionally, users may select an optional goodness-of-fit utility module to run at the conclusion of the simulation. In the case of a user-defined event, users select a historical event or previously run simulation to use as the comparison for goodness-of-fit.<br /> <br /> = Platform Directory =<br /> <br /> A broadband platform distribution is organized in a specific directory structure that separates the input data sets, the python scripts, the simulation configuration files, log files, and output data files.<br /> <br /> When running Broadband Platform simulations, standard procedure is to place the simulation input files in the start directory and invoke the Broadband platform scripts from there.<br /> <br /> From the BBP home directory:<br /> <br /> $&gt; cd start<br /> $&gt; run_bbp_2G.py<br /> <br /> Simulation output results will be written into the bbp_home/output<br /> <br /> = Validation Simulations =<br /> To run a validation simulation, go to the comps directory and run run_bbp_2G.py. The platform will ask you a series of questions. Answer 'y' to &quot;Do you want to perform a validation run?&quot;<br /> <br /> From the BBP home directory:<br /> <br /> $&gt; cd start<br /> $&gt; run_bbp_2G.py<br /> Welcome to the SCEC Broadband Platform.<br /> Please select the modules you want to run.<br /> Do you want to perform a validation run (y/n)? y<br /> Do you want to validate with:<br /> Northridge (1)<br /> Loma Prieta (2)<br /> Landers (3)<br /> ?<br /> ...<br /> <br /> No input files are required by the user. However, you may wish to run with a reduced station list to speed up the computations. You can put your own station list into the start directory (the format is described in [[#Station File List|section 5.3]]). Note that any stations which do not have observed seismograms will not be included in the automatically generated goodness-of-fit comparison.<br /> <br /> In addition to the low-frequency modules which compute seismograms using 1D Green's Tensors, validation events can also be run using precomputed 3D seismograms to supply the low-frequency.<br /> <br /> = User-defined Simulations =<br /> To run a user-defined simulation, two input files are required, a rupture description and a station list. The rupture description can either be in SRF format or a simplified source description (the format is described in [[#Simple source description|section 5.1]]). To run a user-defined simulation, run run_bbp_2G.py.<br /> <br /> From the BBP home directory:<br /> <br /> $&gt; cd start<br /> $&gt; run_bbp_2G.py<br /> Welcome to the SCEC Broadband Platform.<br /> Please select the modules you want to run.<br /> Do you want to perform a validation run (y/n)? y<br /> Do you want to run a rupture generator (y/n)? <br /> ...<br /> <br /> You may then choose if you want to run a rupture generator. This is necessary if you're supplying a simple rupture description. If you're supplying an SRF file, you can skip this. Next you can select from different module implementations. Finally, you have the option to run goodness-of-fit against either observed seismograms or another simulation.<br /> <br /> ...<br /> Do you want to run goodness of fit (y/n)? y<br /> What reference files would you like to compare to? Enter a simulation ID or a scenario name: &lt;comparison&gt;<br /> Enter a label to use for the comparison seismograms: &lt;label&gt;<br /> <br /> The label will be used in GoF plots to distinguish one set of results from the other.<br /> <br /> The user-defined events must be within one of the regions supported by the platform - Southern California, Northern California, or the Mojave. The platform will automatically select a region based on the event hypocenter. If the event falls outside of these regions, you'll get an error.<br /> <br /> = Logging =<br /> During the run, log files will be produced in logs/&lt;simulation ID&gt;/&lt;simulation ID&gt;.&lt;module name&gt;.log. If the platform fails, this is a good place to look to determine the error. Additionally, any fatal errors will be recorded in fatal_error.log.<br /> <br /> Metadata capturing all the executable calls is located in tmpdata/&lt;simulation ID&gt;/metadata.txt for careful tracing of exactly what was called. Both the log files and metadata can be useful if troubleshooting an issue.<br /> <br /> = Data Products =<br /> The platform produces a variety of data products. &lt;nowiki&gt;All data products are located in outdata/&lt;simulation ID&gt;. &lt;/nowiki&gt;On most Linux systems, you can show images using display:<br /> <br /> $&gt; display &lt;PNG file&gt;<br /> <br /> Make sure you have X11 forwarding enabled.<br /> <br /> == Station map ==<br /> To help visualize the stations in relationship to the fault, the platform produces a PNG file displaying station locations with red circles and the fault plane with a black line, on an image of California. You can find this file in outdata/&lt;simulation ID&gt;/station_map.png.<br /> <br /> == Seismograms ==<br /> When running the platform, you have the option to output velocity and acceleration seismograms, for each station. Plots of these files can be found in outdata/&lt;simulation ID&gt;/&lt;simulation ID&gt;.&lt;station&gt;_&lt;velocity or acceleration&gt;_seis.png.<br /> <br /> The raw seismogram data is available in outdata/&lt;simulation ID&gt;/&lt;simulation ID&gt;.&lt;station&gt;.vel.bbp (velocity) and outdata/&lt;simulation ID&gt;.&lt;station&gt;.acc.bbp (acceleration). Its format is described in [[#BBP seismograms|section 5.4]].<br /> <br /> To compare seismogram data, you can run comps/plotit.py with two seismograms. It will plot them both for comparison. From the comps directory, run:<br /> <br /> $&gt; plotit.py &lt;path to seismogram 1&gt; &lt;path to seismogram 2&gt;<br /> <br /> == Response spectra ==<br /> The respect code, run at the end of each simulation, calculates the response spectra for each station. The raw respect data is located at<br /> <br /> From the BBP home directory:<br /> <br /> outdata/&lt;simulation ID&gt;/&lt;simulation ID&gt;.&lt;station&gt;.rsp<br /> <br /> in the format described in [[#Response spectra|section 5.5]].<br /> <br /> == Goodness-of-fit ==<br /> If you run goodness-of-fit, several additional data products are produced. The goodness-of-fit comparison is performed by comparing the response spectra of a set of calculated seismograms to seismograms from another simulation or observed seismograms. For each station involved in the comparison, a plot comparing the response spectra can be found at outdata/&lt;simulation ID&gt;/&lt;comparison label&gt;_&lt;simulation ID&gt;_&lt;station&gt;_rsp.png. A plot showing the seismograms on top and bottom can be found at outdata/&lt;comparison label&gt;_&lt;simulation ID&gt;_&lt;station&gt;_overlay.png. The goodness-of-fit plot can be found at gof-&lt;comparison label&gt;-&lt;simulation ID&gt;_r0-&lt;cutoff distance&gt;.png.<br /> <br /> Note that at least 3 stations must be run for goodness-of-fit to be valid. If fewer than 3 stations are run, no goodness of fit calculation will be performed.<br /> <br /> == Rupture files ==<br /> When a user-defined event is simulated, the user has the option to run a rupture generator. This generator produces an SRF file, found in outdata/&lt;simulation ID&gt;/*.srf. This file can be put in the start directory and used in future runs. Additionally, the platform produces a plot of the cumulative slip on the fault surface, outdata/&lt;simulation ID&gt;/&lt;SRF prefix&gt;.png.<br /> <br /> = Platform Modes =<br /> The platform can be run in multiple modes. The default is interactive mode, in which the user is prompted to answer a series of questions. Once all the information has been gathered, the run begins.<br /> <br /> For a large number of runs, or if the user is repeating a specific run, this can be tedious. The platform provides two other ways to describe a run, with an option file or an XML description.<br /> <br /> An option file provides responses to all the questions that the platform poses. The format is described in [[#Option File|section 5.6]], but it's basically a text file, 1 entry per line, with support for comments. It can be fed to the platform using the -o option.<br /> <br /> The platform will also accept XML files containing a full description of a run. The schema for these files is given in [[#XML workflow description schema|section 5.7]]. These files are also produced by the platform after every simulation, and placed in xml/&lt;simulation ID&gt;.xml. So if you want to rerun a simulation, you can point the platform to the XML file from that simulation using the -x option. Note that a new simulation ID will be assigned to the run, so there is no risk of overwriting previous simulation results.<br /> <br /> = Available Options =<br /> To get a list of the current available options, run run_bbp_2G.py with the -h flag.<br /> <br /> $&gt; run_bbp_2G.py -h<br /> Usage: run_bbp_2G.py [options]<br /> Options:<br /> -h, --help Show this help message and exit<br /> -x XML_FILE, --xml-file=XML_FILE Run using XML description of workflow<br /> -s SIM_ID, --simID=SIM_ID Force a simID<br /> -o OPTFILE, --option-file=OPTFILE File containing responses to interactive platform prompts<br /> -v, --version Broadband platform version<br /> -c, --compact Compact output results. Remove temporary files for simulations that complete successfully.<br /> -g, --generate-xml Generates the XML description but does not run the platform<br /> -l LOG_FILE, --log=LOG_FILE Store all output in a file<br /> <br /> = Cleanup =<br /> After a while, you may find that your indata, tmpdata, outdata, and logs directories are getting cluttered with files from past runs. If you wish to delete these old files, you can use the clean_directories.sh script in the etc directory.<br /> <br /> From the BBP home directory:<br /> <br /> $&gt; cd etc<br /> $&gt; ./clean_directories &lt;days&gt;<br /> <br /> Any simulation ID directories in the indata, tmpdata, outdata, and logs directories which were last accessed &lt;days&gt; days or longer ago will be deleted. If you have a few directories you want to keep, either copy them somewhere else, or copy them to a directory name that's not all digits and they won't be deleted.<br /> <br /> = Examples =<br /> Below are some examples that you can try using the sample files in the examples directory. Make sure all the tests pass before you try this. You should be in the comps directory when you start these examples:<br /> <br /> From the BBP home directory:<br /> <br /> $&gt; cd comps<br /> <br /> == Sample Validation Run ==<br /> You don't need to move any files for this. Notice that 3D seismograms are a low-frequency option, since you're running a validation event.<br /> <br /> From the BBP home directory:<br /> <br /> $&gt; cd start<br /> $&gt; run_bbp_2G.py <br /> Welcome to the SCEC Broadband Platform.<br /> Please select the modules you want to run.<br /> Do you want to perform a validation run (y/n)? y<br /> Do you want to validate with:<br /> Northridge (1)<br /> Loma Prieta (2)<br /> Landers (3)<br /> ?1<br /> Do you want to<br /> run all validation stations (1)<br /> select a station list (2)<br /> ?1<br /> Choose a source of low frequency seismograms:<br /> URS module (1)<br /> URS 3D seismograms (2)<br /> UCSB module (3)<br /> SDSU module (4)<br /> SDSU 3D seismograms (5)<br /> ?2<br /> Choose a high frequency module:<br /> URS (1)<br /> UCSB (2)<br /> SDSU (3)<br /> ?1<br /> Choose a site response module:<br /> URS (1)<br /> UCSB (2)<br /> SDSU (3)<br /> ?1<br /> Do you want to plot velocity seismograms (y/n)? y<br /> Do you want to plot acceleration seismograms (y/n)? y<br /> <br /> This simulation takes about 10 minutes. Once it's complete the platform will tell you:<br /> <br /> You can find results in &lt;path to bbp_2g install&gt;/outdata/&lt;simulation ID&gt; .<br /> <br /> In that directory you will find:<br /> <br /> *Velocity seismograms (&lt;simulation ID&gt;.&lt;station&gt;.bbp)<br /> *Acceleration seismograms (&lt;simulation ID&gt;.&lt;station&gt;.acc.bbp)<br /> *Plots of velocity seismograms (&lt;simulation ID&gt;.&lt;station&gt;_velocity_seis.png)<br /> *Plots of acceleration seismograms (&lt;simulation ID&gt;.&lt;station&gt;_acceleration_seis.png)<br /> *Response spectra files (&lt;simulation ID&gt;.&lt;station&gt;.rsp)<br /> *Plots comparing simulated and observed seismograms (Northridge_&lt;simulation ID&gt;_&lt;station&gt;_overlay.png)<br /> *Plots comparing simulated and observed response spectra (Northridge_&lt;simulation ID&gt;_&lt;station&gt;_rsp.png)<br /> *Overall goodness-of-fit plots (gof-Northridge-&lt;simulation ID&gt;_r0-25.png)<br /> <br /> == Sample Validation run, custom stations ==<br /> If the validation runs aren't performed with 3D low-frequency, it can take a long time, up to 10 minutes per station. Sometimes you might want to run with a reduced station list so the simulation will run faster.<br /> <br /> Copy the files in example/valid_custom_stations into the start directory. Take a look at the format of the station file:<br /> <br /> $&gt; more valid_test_stat.stl <br /> #Required: lon, lat, station name, distance to fault plane, Vs30<br /> #Optional: low freq corner, high freq corner<br /> #Unused: station information<br /> #lon lat stationdist Vs30 LF corner HF corner station information<br /> -118.6417 34.5640 cast 20.47 450 0.120 23.0 CSMIP peer.berkeley.edu/nga<br /> -118.4180 34.0628 lacn 22.82 278 0.140 23.0 CSMIP peer.berkeley.edu/nga<br /> -118.8811 34.2886 moor 24.16 405 0.160 23.0 CSMIP peer.berkeley.edu/nga<br /> <br /> Now, run the platform, using a station list:<br /> <br /> From the BBP Home directory<br /> <br /> $&gt; cd start<br /> $&gt; run_bbp_2G.py <br /> Welcome to the SCEC Broadband Platform.<br /> Please select the modules you want to run.<br /> Do you want to perform a validation run (y/n)? y<br /> Do you want to validate with:<br /> Northridge (1)<br /> Loma Prieta (2)<br /> Landers (3)<br /> ?1<br /> Do you want to<br /> run all validation stations (1)<br /> select a station list (2)<br /> ?2<br /> <br /> If you have multiple station list files in your start directory, you may see the following prompt asking you to select one. If you only have one, the platform will select it automatically.<br /> <br /> Found multiple BBP station list files in the start directory. Please select one:<br /> nr_one_stat.stl (1)<br /> valid_test_stat.stl (2)<br /> ?2<br /> Choose a source of low frequency seismograms:<br /> URS module (1)<br /> URS 3D seismograms (2)<br /> UCSB module (3)<br /> SDSU module (4)<br /> SDSU 3D seismograms (5)<br /> ?3<br /> Choose a high frequency module:<br /> URS (1)<br /> UCSB (2)<br /> SDSU (3)<br /> ?2<br /> Choose a site response module:<br /> URS (1)<br /> UCSB (2)<br /> SDSU (3)<br /> ?2<br /> Do you want to plot velocity seismograms (y/n)? y<br /> Do you want to plot acceleration seismograms (y/n)? y<br /> <br /> Again, when the run completes in about 15 minutes you can find results in the output directory. You'll notice far fewer files, as only 3 stations were run instead of 133. The goodness-of-fit plots won't look very good - more stations are really needed to get an accurate plot.<br /> <br /> == Sample User-defined run with source description ==<br /> Next let's try running a user-defined event. Copy examples/user_rup_gen/nr_one_stat.stl and examples/user_rup_gen/user_eq.src to the start directory. user_eq.src is a simple source description. Its format is outlined in [[#XML workflow description schema|section 5.1]]. Since this is a user-defined event, precomputed 3D seismograms aren't a valid option.<br /> <br /> $&gt; run_bbp_2G.py <br /> Welcome to the SCEC Broadband Platform.<br /> Please select the modules you want to run.<br /> Do you want to perform a validation run (y/n)? n<br /> Do you want to run a rupture generator (y/n)? y<br /> Rupture generators:<br /> URS (1)<br /> UCSB (2)<br /> ?1<br /> Using region: Southern California<br /> Choose a low frequency module:<br /> URS (1)<br /> UCSB (2)<br /> ?2<br /> Found multiple BBP station list files in the start directory. Please select one:<br /> nr_one_stat.stl (1)<br /> valid_test_stat.stl (2)<br /> ?1<br /> Choose a high frequency module:<br /> URS (1)<br /> UCSB (2)<br /> SDSU (3)<br /> ?2<br /> Choose a site response module:<br /> URS (1)<br /> UCSB (2)<br /> SDSU (3)<br /> ?1<br /> Do you want to plot velocity seismograms (y/n)? y<br /> Do you want to plot acceleration seismograms (y/n)? y<br /> Do you want to run goodness of fit (y/n)? n<br /> <br /> Since this run only includes one station, it will run in about 5 minutes. In the output directory you'll notice there are no goodness-of-fit or files, since we didn't run goodness-of-fit. However, there is also a map file (station_map.png), showing the fault plane and the stations, and a plot of the rupture slip (user_eq.png). The SRF generated by the rupture generator is in user_eq.srf; this file could be used in future runs. The filenames of the rupture slip plot and SRF are taken from the rupture description filename.<br /> <br /> == Sample User-defined run with SRF file and goodness-of-fit ==<br /> Finally, try a run with an SRF file and run goodness-of-fit on the results. Copy in examples/user_no_rup_gen/ucsb_modSRF_0.srf and examples/user_no_rup_gen/nr_three_stat.stl<br /> <br /> $&gt; run_bbp_2G.py <br /> Welcome to the SCEC Broadband Platform.<br /> Please select the modules you want to run.<br /> Do you want to perform a validation run (y/n)? n<br /> Do you want to run a rupture generator (y/n)? n<br /> Using region: Southern California<br /> Choose a low frequency module:<br /> URS (1)<br /> UCSB (2)<br /> ?1<br /> Found multiple BBP station list files in the start directory. Please select one:<br /> nr_one_stat.stl (1)<br /> valid_test_stat.stl (2)<br /> nr_three_stat.stl (3)<br /> ?3<br /> Choose a high frequency module:<br /> URS (1)<br /> UCSB (2)<br /> SDSU (3)<br /> ?3<br /> Choose a site response module:<br /> URS (1)<br /> UCSB (2)<br /> SDSU (3)<br /> ?1<br /> Do you want to plot velocity seismograms (y/n)? y<br /> Do you want to plot acceleration seismograms (y/n)? y<br /> Do you want to run goodness of fit (y/n)? y<br /> What reference files would you like to compare to? Enter a simulation ID or a scenario name: Northridge<br /> Enter a label to use for the comparison seismograms: nr<br /> <br /> The reference files can either be a scenario event or a simulation ID previously run. The label is just for the figures when comparisons are plotted.<br /> <br /> This run will take about 15 minutes, and the results can be found in the appropriate outdir. Again, the goodness of fit measures will look poor due to the few stations involved in the comparison. If you had fewer than 3 stations, no goodness-of-fit plots would be produced. However, response spectra comparison plots will still be generated.<br /> <br /> = File Formats =<br /> This section offers descriptions of various file formats in the broadband platform.<br /> <br /> == Simple source description ==<br /> This is the format for the simple source description. It is not whitespace sensitive. The filename must end in .src for the platform to identify it as a source description.<br /> <br /> MAGNITUDE = &lt;magnitude&gt;<br /> FAULT_LENGTH = &lt;length of fault&gt;<br /> DLEN = &lt;DX, along length&gt;<br /> FAULT_WIDTH = &lt;down-dip fault width&gt;<br /> DWID = &lt;DY, along width&gt;<br /> DEPTH_TO_TOP = &lt;depth of fault below surface&gt;<br /> STRIKE = &lt;nowiki&gt;&lt;strike&gt;&lt;/nowiki&gt;<br /> RAKE = &lt;rake&gt;<br /> DIP = &lt;dip&gt;<br /> LAT_TOP_CENTER = &lt;latitude of top center point in fault plane&gt;<br /> LON_TOP_CENTER = &lt;longitude of top center point in fault plane&gt;<br /> HYPO_ALONG_STK = &lt;along strike location of hypocenter (0.0 = middle)&gt;<br /> HYPO_DOWN_DIP = &lt;down dip location of hypocenter (0.0 = top)&gt;<br /> DT = &lt;nowiki&gt;&lt;dt&gt;&lt;/nowiki&gt;<br /> SEED = &lt;random seed used in calculations&gt;<br /> CORNER_FREQ = &lt;corner frequency to use&gt;<br /> <br /> == SRF rupture description ==<br /> Details of the Standard Rupture Format (SRF) are given in more detail in the accompanying document. The general fault surface is represented by a distribution of point sources, and it can support one or more planes. The platform produces SRFs as output from rupture generators, but a user can also supply an SRF file as input for user-defined simulations. SRF filenames must end with the suffix .srf for the platform to correctly identify them.<br /> <br /> == Station File List ==<br /> The user may specify a list of stations, matching the following format:<br /> <br /> #optional<br /> %comment<br /> # lines<br /> &lt;nowiki&gt;&lt;lon&gt; &lt;lat&gt; &lt;stat name&gt; &lt;distance to fault trace&gt; &lt;Vs30&gt; &lt;LF corner&gt; &lt;HF corner&gt; &lt;stat info&gt;&lt;/nowiki&gt;<br /> ...<br /> <br /> The station list filename needs to end in .stl for the platform to recognize it as a station list.<br /> <br /> == BBP seismograms ==<br /> All intermediate and output seismograms are produced in a 4-column text format, whether velocity or acceleration.<br /> <br /> # optional<br /> % comment<br /> # lines<br /> &lt;nowiki&gt;&lt;timestamp&gt; &lt;North/South&gt; &lt;East/West&gt; &lt;Up/Down&gt;&lt;/nowiki&gt;<br /> ...<br /> <br /> Time is in seconds and motion is in cm/s (velocity) or cm/s/s (acceleration) unless otherwise specified in the header. Velocity filenames end in .vel.bbp; accelerations in .acc.bbp.<br /> <br /> == Response spectra ==<br /> The response spectra file is in 4-column text format.<br /> <br /> # optional<br /> % comment<br /> # lines<br /> &lt;nowiki&gt;&lt;period (sec)&gt; &lt;North/South&gt; &lt;East/West&gt; &lt;Up/Down&gt;&lt;/nowiki&gt;<br /> ...<br /> <br /> The platform samples response spectra at 112 periods, 0.01-20 sec and outputs pseudo spectral acceleration in units of g.<br /> <br /> == Option File ==<br /> Option files contain responses to the prompts in the platform. You can use them with the -o option to run_bbp_2G.py. The responses have to match the prompts exactly. For example, if you craft an option file assuming there is only one station list in the start directory (and therefore the user isn't prompted to select one) but then it is run with multiple station lists in the start directory, this will cause the run to abort. Option files are recommended to perform a series of runs with different inputs or different modules. If you have a run you perform regularly, it's better practice to run the platform with the -g option and the option file to produce an XML description, which are more complete descriptions of the workflow.<br /> <br /> #optional comments<br /> %using either symbol<br /> n #comments<br /> y % can go<br /> 1 # here<br /> ...<br /> <br /> Use with:<br /> <br /> $&gt; run_bbp_2G.py -o &lt;option file&gt;<br /> <br /> == XML workflow description schema ==<br /> Each time the platform is invoked, an XML file is produced describing the workflow, obeying the following schema:<br /> <br /> &lt;nowiki&gt;&lt;xs:schema xmlns:xs=&quot;http://www.w3.org/2001/XMLSchema&quot;&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:element name= &quot;BBP_Run_Specification&quot; minOccurs= &quot;1&quot; maxOccurs= &quot;1&quot;&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:attribute name=&quot;version&quot; type = &quot;xs:string&quot; use = &quot;required&quot; /&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:complexType&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:sequence&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:element name= &quot;Validation_Run&quot; minOccurs= &quot;0&quot; maxOccurs = &quot;1&quot;&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:attribute name= &quot;event&quot; type= &quot;xs:string&quot; use= &quot;required&quot; /&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:attribute name= &quot;input_station_file&quot; type = &quot;xs:string&quot; /&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:attribute name= &quot;subset&quot; type = &quot;xs:boolean&quot; use = &quot;required&quot; /&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;/xs:element&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:element name= &quot;BBP_Modules&quot;&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:complexType&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:sequence&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:element name = &quot;BBP_Module&quot; maxOccurs = &quot;unbounded&quot; &gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:complexType&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:sequence&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:element name= &quot;name&quot; type=&quot;xs:string&quot; /&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:element name= &quot;staged_files&quot; &gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:complexType&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:sequence&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:element name=&quot;file&quot; type=&quot;xs:string&quot; maxOccurs= &quot;unbounded&quot;/&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;/xs:sequence&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;/xs:complexType&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;/xs:element&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:element name= &quot;arguments&quot; &gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:complexType&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:sequence&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:element name=&quot;argument&quot; type=&quot;xs:string&quot; maxOccurs=&quot;unbounded&quot;&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:attribute name= &quot;type&quot; type= &quot;xs:string&quot; user= &quot;required&quot; /&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;/xs:element&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;/xs:sequence&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;/xs:complexType&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;/xs:element&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;/xs:sequence&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;/xs:complexType&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;/xs:element&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;/xs:sequence&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;/xs:complexType&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;/xs:element&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;/xs:sequence&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;/xs:complexType&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;/xs:element&gt;&lt;/nowiki&gt;<br /> <br /> These files are difficult to construct by hand, but can be generated using the -g flag when running run_bbp_2G.py.<br /> <br /> = User Support =<br /> If you run into bugs with the platform, you can open a trouble ticket at the [http://northridge.usc.edu/trac/broadband Broadband Trac site].<br /> <br /> Check to see if there has already been a ticket opened for the bug. If you are unable to get the platform to run, you can get direct user support by emailing [mailto:software@intensity.usc.edu software@intensity.usc.edu].<br /> <br /> = Appendix A: Possible Module Permutations =<br /> == Validation Events ==<br /> <br /> {| class=&quot;wikitable&quot; | border=&quot;1&quot;<br /> | Permutation #<br /> | Low-frequency module<br /> | High-frequency module<br /> | Site response<br /> <br /> |-<br /> | &lt;center&gt;1&lt;/center&gt;<br /> | &lt;center&gt;URS 1D&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;2&lt;/center&gt;<br /> | &lt;center&gt;URS 1D&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;3&lt;/center&gt;<br /> | &lt;center&gt;URS 1D&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;4&lt;/center&gt;<br /> | &lt;center&gt;URS 1D&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;5&lt;/center&gt;<br /> | &lt;center&gt;URS 1D&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;6&lt;/center&gt;<br /> | &lt;center&gt;URS 1D&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;7&lt;/center&gt;<br /> | &lt;center&gt;URS 1D&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;8&lt;/center&gt;<br /> | &lt;center&gt;URS 1D&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;9&lt;/center&gt;<br /> | &lt;center&gt;URS 1D&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;10&lt;/center&gt;<br /> | &lt;center&gt;URS 3D precomputed&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;11&lt;/center&gt;<br /> | &lt;center&gt;URS 3D precomputed&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;12&lt;/center&gt;<br /> | &lt;center&gt;URS 3D precomputed&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;13&lt;/center&gt;<br /> | &lt;center&gt;URS 3D precomputed&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;14&lt;/center&gt;<br /> | &lt;center&gt;URS 3D precomputed&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;15&lt;/center&gt;<br /> | &lt;center&gt;URS 3D precomputed&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;16&lt;/center&gt;<br /> | &lt;center&gt;URS 3D precomputed&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;17&lt;/center&gt;<br /> | &lt;center&gt;URS 3D precomputed&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;18&lt;/center&gt;<br /> | &lt;center&gt;URS 3D precomputed&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;19&lt;/center&gt;<br /> | &lt;center&gt;UCSB 1D&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;20&lt;/center&gt;<br /> | &lt;center&gt;UCSB 1D&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;21&lt;/center&gt;<br /> | &lt;center&gt;UCSB 1D&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;22&lt;/center&gt;<br /> | &lt;center&gt;UCSB 1D&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;23&lt;/center&gt;<br /> | &lt;center&gt;UCSB 1D&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;24&lt;/center&gt;<br /> | &lt;center&gt;UCSB 1D&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;25&lt;/center&gt;<br /> | &lt;center&gt;UCSB 1D&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;26&lt;/center&gt;<br /> | &lt;center&gt;UCSB 1D&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;27&lt;/center&gt;<br /> | &lt;center&gt;UCSB 1D&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;28&lt;/center&gt;<br /> | &lt;center&gt;SDSU 1D&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;29&lt;/center&gt;<br /> | &lt;center&gt;SDSU 1D&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;30&lt;/center&gt;<br /> | &lt;center&gt;SDSU 1D&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;31&lt;/center&gt;<br /> | &lt;center&gt;SDSU 1D&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;32&lt;/center&gt;<br /> | &lt;center&gt;SDSU 1D&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;33&lt;/center&gt;<br /> | &lt;center&gt;SDSU 1D&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;34&lt;/center&gt;<br /> | &lt;center&gt;SDSU 1D&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;35&lt;/center&gt;<br /> | &lt;center&gt;SDSU 1D&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;36&lt;/center&gt;<br /> | &lt;center&gt;SDSU 1D&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;37&lt;/center&gt;<br /> | &lt;center&gt;SDSU 3D precomputed&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;38&lt;/center&gt;<br /> | &lt;center&gt;SDSU 3D precomputed&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;39&lt;/center&gt;<br /> | &lt;center&gt;SDSU 3D precomputed&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;40&lt;/center&gt;<br /> | &lt;center&gt;SDSU 3D precomputed&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;41&lt;/center&gt;<br /> | &lt;center&gt;SDSU 3D precomputed&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;42&lt;/center&gt;<br /> | &lt;center&gt;SDSU 3D precomputed&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;43&lt;/center&gt;<br /> | &lt;center&gt;SDSU 3D precomputed&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;44&lt;/center&gt;<br /> | &lt;center&gt;SDSU 3D precomputed&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;45&lt;/center&gt;<br /> | &lt;center&gt;SDSU 3D precomputed&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> |}<br /> <br /> ==User-Defined Events==<br /> <br /> {| class=&quot;wikitable&quot; | border=&quot;1&quot;<br /> | Permutation #<br /> | Rupture generator<br /> | Low-frequency<br /> | High-frequency<br /> | Site response<br /> <br /> |-<br /> | &lt;center&gt;1&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;2&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;3&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;4&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;5&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;6&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;7&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;8&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;9&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;10&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;11&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;12&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;13&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;14&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;15&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;16&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;17&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;18&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;19&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;20&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;21&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;22&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;23&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;24&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;25&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;26&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;27&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;28&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;29&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;30&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;31&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;32&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;33&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;34&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;35&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;36&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;37&lt;/center&gt;<br /> | &lt;center&gt;User-supplied SRF&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;38&lt;/center&gt;<br /> | &lt;center&gt;User-supplied SRF&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;39&lt;/center&gt;<br /> | &lt;center&gt;User-supplied SRF&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;40&lt;/center&gt;<br /> | &lt;center&gt;User-supplied SRF&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;41&lt;/center&gt;<br /> | &lt;center&gt;User-supplied SRF&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;42&lt;/center&gt;<br /> | &lt;center&gt;User-supplied SRF&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;43&lt;/center&gt;<br /> | &lt;center&gt;User-supplied SRF&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;44&lt;/center&gt;<br /> | &lt;center&gt;User-supplied SRF&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;45&lt;/center&gt;<br /> | &lt;center&gt;User-supplied SRF&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;46&lt;/center&gt;<br /> | &lt;center&gt;User-supplied SRF&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;47&lt;/center&gt;<br /> | &lt;center&gt;User-supplied SRF&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;48&lt;/center&gt;<br /> | &lt;center&gt;User-supplied SRF&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;49&lt;/center&gt;<br /> | &lt;center&gt;User-supplied SRF&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;50&lt;/center&gt;<br /> | &lt;center&gt;User-supplied SRF&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;51&lt;/center&gt;<br /> | &lt;center&gt;User-supplied SRF&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;52&lt;/center&gt;<br /> | &lt;center&gt;User-supplied SRF&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;53&lt;/center&gt;<br /> | &lt;center&gt;User-supplied SRF&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;54&lt;/center&gt;<br /> | &lt;center&gt;User-supplied SRF&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> |}<br /> <br /> = Appendix B: Troubleshooting =<br /> If you experience trouble building the platform or successfully running test and simulations, try the following solutions.<br /> <br /> == Build Errors ==<br /> <br /> The instruction for installing Broadband Platform are listed in Section 1: &quot;Installing the Second-Generation Broadband Platform&quot; of the User guide. If after following all steps listed in this section of the user guide the build fails, check if the failure is listed in this section and try the solution to fix the issue you are facing.<br /> <br /> === 64-bit Intel Compiler Issue ===<br /> If you try to compile with:<br /> &lt;pre&gt;<br /> % cd bbp_2g/src<br /> % make<br /> &lt;/pre&gt; <br /> <br /> and you get:<br /> &lt;pre&gt;<br /> ... <br /> make[2]: Entering directory `.../bbp_2g/src/ucsb/getInFile'<br /> icc -o getfaultGlobal getfaultGlobal.c<br /> ld: cannot find -lgcc_s_32<br /> make[2]: *** [getfaultGlobal] Error 1<br /> make[2]: Leaving directory `.../bbp_2g/src/ucsb/getInFile'<br /> make[1]: *** [all] Error 2<br /> make[1]: Leaving directory `.../bbp_2g/src/ucsb'<br /> make: *** [all] Error 2<br /> &lt;/pre&gt;<br /> <br /> '''Cause:''' The Broadband Platform requires Intel 64-bit compilers to build successfully. In this case the 32-bit Intel compilers are being invoked as they are being picked up from the PATH environment variable. The error is due to a missing GNU-GCC 32-bit compatibility pack that has not been installed on your system. This is not required when 64-bit Intel compilers are used.<br /> <br /> '''Solution:''' Ensure that the path Intel 64-bit compilers are listed in you PATH variable and being picked up by running 'which icc' and 'which ifort'. If you are trying to build the platform on SCEC development servers like Intensity, verify your path variable has:<br /> &lt;pre&gt;<br /> PATH=...:/usr/usc/intel/composerxe-2011.4.191/mpirt/bin/intel64:/usr/usc/intel/composerxe-2011.4.191/bin/intel64<br /> &lt;/pre&gt;<br /> <br /> === 32-bit Platform Issue ===<br /> <br /> On trying to build the platform, the build fails with the following message:<br /> &lt;pre&gt;<br /> $ make all<br /> cd urs; make -f makefile FC=gfortran CC=icc USER_C=1;<br /> make[1]: Entering directory `.../bbp_2g/src/urs'<br /> mkdir -p bin;<br /> cd getpar/src; make -f Makefile CC=icc FC=gfortran USER_C=1;<br /> make[2]: Entering directory `.../bbp_2g/src/urs/getpar/src'<br /> icc -O3 -DENVIRONMENT -c -o defpar.o defpar.c<br /> icc -O3 -DENVIRONMENT -c -o getpar.o getpar.c<br /> icc -O3 -DENVIRONMENT -c -o getarg.o getarg.c<br /> getarg.c(112): warning #303: explicit type is missing (&quot;int&quot; assumed)<br /> register i;<br /> ^ <br /> icc -O3 -DENVIRONMENT -c -o getlocation.o getlocation.c<br /> getlocation.c(9): warning #147: declaration is incompatible with &quot;__ssize_t={int} getline(char **restrict, size_t={unsigned int} *restrict, FILE *restrict)&quot; (declared at line 671 of &quot;/usr/include/stdio.h&quot;)<br /> static int getline(FILE *fd, char *line)<br /> <br /> ...<br /> ...<br /> ...<br /> <br /> make[2]: Entering directory `.../bbp_2g/src/sdsu/srcV1.4'<br /> icc -w -Wall -c ray3DJHfor.c<br /> gfortran module_bbtoolbox.f90 module_interface.f90 main_bbtoolbox.f90 coda.f90 composition.f90 convolution.f90 fourier.f90 error.f90 geometry.f90 interpolation.f90 io.f90 random.f90 scattering.f90 source.f90 ray3DJHfor.o -o BBtoolbox.exe<br /> ray3DJHfor.o: In function `raytracing_':<br /> ray3DJHfor.c:(.text+0x8cf): undefined reference to `__libm_sse2_log'<br /> ray3DJHfor.c:(.text+0x96b): undefined reference to `__libm_sse2_asin'<br /> ray3DJHfor.c:(.text+0x9cd): undefined reference to `__libm_sse2_asin'<br /> ray3DJHfor.c:(.text+0xa00): undefined reference to `__libm_sse2_tan'<br /> ray3DJHfor.c:(.text+0xa3d): undefined reference to `__libm_sse2_tan'<br /> ray3DJHfor.c:(.text+0xa52): undefined reference to `__libm_sse2_log'<br /> collect2: ld returned 1 exit status<br /> make[2]: *** [BBtoolbox.exe] Error 1<br /> make[2]: Leaving directory `.../bbp_2g/src/sdsu/srcV1.4'<br /> make[1]: *** [all] Error 2<br /> make[1]: Leaving directory `.../bbp_2g/src/sdsu'<br /> make: *** [all] Error 2<br /> &lt;/pre&gt;<br /> <br /> '''Cause:''' In this case the user tried to build Broadband on a 32-bit platform. Broadband code was designed to be run on 64-bit platform. Any attempt to build Broadband on a 32-bit platform will result in numerous warnings and the build will fail with error messages similar to ones listed above.<br /> <br /> '''Solution:''' Try building Broadband on a 64-bit platform will the all the dependencies listed in Section 1.1: &quot;System Dependencies&quot; and Section 1.2: &quot;Software Dependencies&quot;<br /> <br /> == Unit/Acceptance Test Failures and Errors ==<br /> <br /> Unit and Acceptance tests are provided to verify the Broadband platform and it's supporting modules built by the user are functioning as designed. Under certain circumstances, some of these test might fail. While some of these failure might indicate serious problems that will have to be addressed before the platform can used, it is acceptable to ignore some of the failures. This section lists some failures and their solutions.<br /> <br /> === ERROR: test_syn1d (test_syn1d.Test_syn1D) ===<br /> The Unit test for Syn1d module fails with the following message:<br /> &lt;pre&gt;<br /> ERROR: test_syn1d (test_syn1d.Test_syn1D)<br /> ----------------------------------------------------------------------<br /> Traceback (most recent call last):<br /> File &quot;.../bbp_2g/tests/test_syn1d.py&quot;, line 62, in test_syn1d<br /> synObj.run()<br /> File &quot;.../bbp_2g/comps/syn1D.py&quot;, line 236, in run<br /> shutil.copy2(a_tmpfile, expected_file)<br /> File &quot;/usr/lib/python2.6/shutil.py&quot;, line 99, in copy2<br /> copyfile(src, dst)<br /> File &quot;/usr/lib/python2.6/shutil.py&quot;, line 52, in copyfile<br /> fsrc = open(src, 'rb')<br /> IOError: [Errno 2] No such file or directory: '.../bbp_2g/tmpdata/3310632/s01.3comp'<br /> &lt;/pre&gt;<br /> <br /> '''Cause:''' Syn1d module requires the Green's Function file to run and the path to this file might be incorrect in 'bbp_2g_gf/ucsb/GreenBank/Northridge/GreenBank.inf' file.<br /> <br /> '''Solution:''' This issue can be fixed by correcting the paths listed in the GreenBank.inf files in the Green's Function directory. Here are step by step instructions to fix this issue:<br /> <br /> 1. Locate your Greens Functions directory: 'bbp_2g_gf'<br /> 2. Navigate to bbp_2g_gf/ucsb/GreenBank/Northridge folder.<br /> 3. Open Green_Bank.inf files with a text editor.<br /> 4. Locate the text &quot;The name of file to store Green Bank&quot;<br /> 5. Note the location of the Green Bank file under the line found in step 4, similar to &quot;/home/scec-00/scottcal/bband/bbp_2g_gf/ucsb/GreenBank/Northridge/Green_1d.soil&quot;.<br /> 6. Replace the path found in Step 5 with just the file name, in the case of Northridge it is &quot;Green_1d.soil&quot;<br /> 7. Save and close the Green_Bank.inf.<br /> 8. Navigate to bbp_2g_gf/ucsb/GreenBank/LomaPrieta folder and repeat steps 3-7. The name of the Green Bank file for LomaPrieta is &quot;Green_1d.LoPr&quot;.<br /> 9. Navigate to bbp_2g_gf/ucsb/GreenBank/Landers folder and repeat steps 3-7. The name of the Green Bank file for Landers is &quot;Green1D.Landers&quot;<br /> <br /> === ERROR: test_gensrf (test_genslip.Test_Genslip) ===<br /> The Unit test for Genslip module fails with the following message:<br /> &lt;pre&gt;<br /> ======================================================================<br /> ERROR: test_gensrf (test_genslip.Test_Genslip)<br /> ----------------------------------------------------------------------<br /> Traceback (most recent call last):<br /> File &quot;.../bbp_2g/tests/test_genslip.py&quot;, line 51, in test_gensrf<br /> gen.run()<br /> File &quot;.../bbp_2g/comps/genslip.py&quot;, line 153, in run<br /> ps.run()<br /> File &quot;.../bbp_2g/comps/plot_srf.py&quot;, line 52, in run<br /> shutil.copy2(&quot;%s/%s.ps.png&quot; % (a_tmpdir, self.r_srffile[0:self.r_srffile.find(&quot;.srf&quot;)]), &quot;%s/%s.png&quot; % (a_outdir, self.r_srffile[0:self.r_srffile.find(&quot;.srf&quot;)]))<br /> File &quot;/usr/lib/python2.6/shutil.py&quot;, line 99, in copy2<br /> copyfile(src, dst)<br /> File &quot;/usr/lib/python2.6/shutil.py&quot;, line 52, in copyfile<br /> fsrc = open(src, 'rb')<br /> IOError: [Errno 2] No such file or directory: '.../bbp_2g/tmpdata/3309008/3309008_test_eq.ps.png'<br /> &lt;/pre&gt;<br /> <br /> '''Cause:''' The Genslip module calls the Plot_SRF module to the plot the SRF file. Plot_SRF uses C-shell code to locate and use GMT package to plot the SRF file. This shell code might fail on some flavors of Linux with a message like &quot;Newline in variable name&quot; in the Plot_SRF log file.<br /> <br /> '''Solution:''' This issue can be fixed by editing the plot_SRF.csh file. Here are step by step instructions to fix this issue:<br /> <br /> 1. Locate shell script file: bbp_2g/src/plot/plot_SRF.csh<br /> 2. Open the file in your preferred text editor<br /> 3. Locate the line 'set FIND_GMT = $?'<br /> 4. Replace the line found in step 3 with 'set FIND_GMT = $status'<br /> 5. Locate the section of code that starts with the statement &quot;# FIND MAX. SLIP&quot;<br /> 6. Replace the following line in section found in step 5:<br /> &lt;pre&gt;<br /> set SMAX = `$XYZCODE calc_xy=$CALC_XY type=&quot;${TYPE}&quot; nseg=-1 &lt; $SLIPFILE.srf | \<br /> gawk -v m=$SMAX '{if($3&gt;m)m=$3;}END{printf &quot;%.0f\n&quot;,m;}'`<br /> <br /> with (collapse the statement to a single line by removing '\' at the end of first part of the statement):<br /> <br /> set SMAX = `$XYZCODE calc_xy=$CALC_XY type=&quot;${TYPE}&quot; nseg=-1 &lt; $SLIPFILE.srf | gawk -v m=$SMAX '{if($3&gt;m)m=$3;}END{printf &quot;%.0f\n&quot;,m;}'`<br /> &lt;/pre&gt;<br /> 7. Save the file and exit<br /> <br /> === ERROR: test_ucgen (test_ucrmg.Test_UCrmg) ===<br /> The Unit test for Ucrmg module fails with the following message:<br /> &lt;pre&gt;<br /> ======================================================================<br /> ERROR: test_ucgen (test_ucrmg.Test_UCrmg)<br /> ----------------------------------------------------------------------<br /> Traceback (most recent call last):<br /> File &quot;.../bbp_2g/tests/test_ucrmg.py&quot;, line 59, in test_ucgen<br /> ucObj.run()<br /> File &quot;.../bbp_2g/comps/ucrmg.py&quot;, line 161, in run<br /> ps.run()<br /> File &quot;.../bbp_2g/comps/plot_srf.py&quot;, line 52, in run<br /> shutil.copy2(&quot;%s/%s.ps.png&quot; % (a_tmpdir, self.r_srffile[0:self.r_srffile.find(&quot;.srf&quot;)]), &quot;%s/%s.png&quot; % (a_outdir, self.r_srffile[0:self.r_srffile.find(&quot;.srf&quot;)]))<br /> File &quot;/usr/lib/python2.6/shutil.py&quot;, line 99, in copy2<br /> copyfile(src, dst)<br /> File &quot;/usr/lib/python2.6/shutil.py&quot;, line 52, in copyfile<br /> fsrc = open(src, 'rb')<br /> IOError: [Errno 2] No such file or directory: '.../bbp_2g/tmpdata/3309831/test_ucsb.ps.png'<br /> &lt;/pre&gt;<br /> <br /> '''Cause:''' The Ucrmg module calls the Plot_SRF module to the plot the SRF file. Plot_SRF uses C-shell code to locate and use GMT package to plot the SRF file. This shell code might fail on some flavors of Linux with a message like &quot;Newline in variable name&quot; in the Plot_SRF log file.<br /> <br /> '''Solution:''' This issue can be fixed by editing the plot_SRF.csh file. The steps to fix this issue are listed under the solution for &quot;ERROR: test_gensrf (test_genslip.Test_Genslip)&quot; above.<br /> <br /> === FAIL: test_site_amp (test_uc_site.Test_UC_Site) ===<br /> <br /> The unit test for UC-Site module might fail with the following message:<br /> &lt;pre&gt;<br /> ======================================================================<br /> FAIL: test_site_amp (test_uc_site.Test_UC_Site)<br /> ----------------------------------------------------------------------<br /> Traceback (most recent call last):<br /> File &quot;.../bbp_2g/tests/test_uc_site.py&quot;, line 92, in test_site_amp<br /> self.failIf(cmp_bbp.cmp_bbp(a_ref_file_no_header, test_file_no_header, tolerance=0.035)!=0,errmsg)<br /> AssertionError: Output file .../bbp_2g/tmpdata/3310633/s04.3comp does not match reference file .../bbp_2g/ref_data/ucsb/s04.site.3comp<br /> &lt;/pre&gt;<br /> <br /> '''Cause:''' The synthetic seismogram generated by the UC-Site module on the user system differs from the reference result included in the Broadband release.<br /> <br /> '''Solution:''' The stochastic nature of the high frequency simulations is considered, and a constant random seed as input for our tests. This is the same constant random seed used to generate the reference results included in the release. This ensures that the time-series generated with unit tests agree with reference results. However, the high frequency codes are more sensitive to changes in compilers and machines due to the algorithm, so small differences that cause the test to fail are generally acceptable. The user is however encouraged to plot the two time-series and visually inspect them to verify they look similar. We are trying to come up with a better comparison for these tests.<br /> <br /> = Appendix C: Technical Notes =<br /> <br /> == Running Individual Acceptance Tests ==<br /> <br /> The acceptance test script ./tests/AcceptTest.py attempts to run all of the defined tests when executed. However, sometimes it is useful to run an acceptance test in isolation for troubleshooting purposes:<br /> <br /> * Identify the test you want to run. Eg: user-URS-UCSB-SDSU-SDSU<br /> * Move to the ./comps directory and execute that test's XML workflow with run_bbp_2G.py. Using the above example:<br /> &lt;pre&gt;<br /> $ ./run_bbp_2G.py -x ../ref_data/accept_inputs/user-URS-UCSB-SDSU-SDSU.xml<br /> &lt;/pre&gt;<br /> <br /> Since you are running the test outside of AcceptTest.py, you will not see a PASS/FAIL message once the simulation completes. However, you can review the contents of the ./outdata/&lt;SIMID&gt; directory to verify that the correct seismograms and response spectra tables were produced.<br /> <br /> == Manaully Setting Random Number Generator Seed Values ==<br /> <br /> Several of the platform codebases employ random number generators to produce SRFs and seismograms. These random number generators are generally seeded with an initial value (typically an integer) which are hard-coded in the platform. Advanced users may desire to change these seed values.<br /> <br /> Changing the seeds for seismogram synthesis varies depending on which codebase you want to use:<br /> <br /> * URS: Edit ./comps/hfsims_cfg.py, Line 43 &quot;self.RAND_NUM&quot;<br /> * UCSB: Edit ./src/ucsb/Syn1DSCEC/syn1D_LAH.f, Line 183 &quot;iseed&quot;, and recompile with &quot;make&quot;<br /> * SDSU:<br /> ** User event: Edit ./bbp_2g_gf/sdsu/scattering_generic.dat (seed values annotated in file)<br /> ** Validation event: Edit ./bbp_2g_gf/sdsu/&lt;event&gt;/scattering.dat</div> Patrices https://strike.scec.org/scecwiki/index.php?title=Broadband_User_Guide_v11.2.3&diff=5054 Broadband User Guide v11.2.3 2012-05-08T21:38:52Z <p>Patrices: </p> <hr /> <div>'''Version 11.2.3.'''<br /> <br /> If you find errors in this document or sections to be unclear, please either fix them yourself or contact software@scec.org.<br /> <br /> == Installing the Second-Generation Broadband Platform ==<br /> Installing the Broadband Platform involves obtaining a copy of the code and building the required executables. You can either download the platform from the Broadband web site ([http://www.scec.org/research/broadband http://www.scec.org/research/broadband]) or check the code out of SCEC's Subversion repository. Most users should download the platform.<br /> <br /> == System Dependencies ==<br /> The current version of the Broadband Platform is designed to run on standard 64-bit Linux machines. Testing has been performed on SCEC's development servers running Fedora Core 10 (kernel version 2.6.27.41-170.2.117.fc10.x86_64). In this guide we outline how to install the platform into your own account on a Linux computer using the simplest approach.<br /> <br /> == Software Dependencies ==<br /> The Broadband Platform has certain software dependencies.<br /> <br /> Required:<br /> <br /> *Python v2.7 with<br /> **PyGTK<br /> **Matplotlib<br /> **Numpy<br /> **Pyproj<br /> <br /> *Intel compilers (64-bit) v12.0.4<br /> *GNU compilers (gcc, gfortran) v4.5.1<br /> *GNU Fortran 77 v3.4.6<br /> *GMT (Generic Mapping Toolkit)<br /> *ImageMagick<br /> <br /> == Setting Up Your Account ==<br /> For simplicity of installation, we recommend users use a bash shell for the Broadband Platform account. It is possible to get the platform running using other shell's, but we will focus on a bash shell installation. The user environment is a common source of problems since certain environment variables must be defined for the platform to work correctly.<br /> <br /> To check your account, make sure you can run basic commands like ''ls'' and ''cd'' before proceeding.<br /> <br /> == Downloading the Platform ==<br /> &lt;nowiki&gt;Download 4 files from the Broadband website, the code (bbp_dist_&lt;version&gt;.tgz), the data (bbp_data_&lt;version&gt;.tgz), and their checksum files (bbp_dist_&lt;version&gt;.tgz.md5 and bbp_data_&lt;version&gt;.tgz.md5). &lt;/nowiki&gt;The code file is about 100 MB, the data file about 3 GB. After you've downloaded the files to your local Linux system, the next step is to calculate the checksums yourself and compare them to the checksums you downloaded.<br /> <br /> First, verify that the ''md5sum'' command is in your path:<br /> <br /> $&gt; which md5sum<br /> <br /> You should get something like /usr/bin/md5sum. If you see the message 'no md5sum in...', contact your Linux system administrator and ask to have md5sum added to your path.<br /> <br /> Once you can run the ''md5sum'' command, run:<br /> <br /> $&gt; md5sum -c bbp_dist_&lt;version&gt;.tgz.md5<br /> $&gt; md5sum -c bbp_data_&lt;version&gt;.tgz.md5<br /> <br /> You should get the messages<br /> bbp_dist_&lt;version&gt;.tgz.md5: OK<br /> bbp_data_&lt;version&gt;.tgz.md5: OK<br /> <br /> If you get FAILED instead, re-download the tgz files and try again. When it passes, that means the files were downloaded without error.<br /> <br /> Once both files have passed the checksum test, untar the files.<br /> <br /> $&gt; tar xzvf bbp_dist_&lt;version&gt;.tgz file<br /> $&gt; tar xzvf bbp_data_&lt;version&gt;.tgz file<br /> <br /> If multiple users are planning to use the platform on the same system, you only need one copy of the data files per machine. Each user will still need his or her own copy of the code files.<br /> <br /> Alternatively, if you would like access to the latest version of the platform and get frequent but less thoroughly tested improvements, you can check out the platform from SCEC's Subversion repository. Only advanced users should take this approach, outlined in detail in the [[#Advanced Users| Advanced Users section]].<br /> <br /> == User Account Setup ==<br /> <br /> The Broadband platform installation is divided into two parts (1) input Green Functions (GF) data directory (9.3Gb), and (2) BBP home directory (366Mb). <br /> <br /> First, the Green's function libraries are larger, but they are static. The broadband platform reads the data files, but does not change them. <br /> <br /> Second, the remainder of the broadband platform is organized in the BBP home directory. The BBP home directory has a specific directory structure that includes the source code for the scientific programs, the python scripts that link the scientific programs, simulation input directory, temporary and log file directories, and the output data directory where all the platform results are written.<br /> <br /> The BBP home directory will increase in size as you run the platform, because both output data and output log files are written to the home directory. Running the acceptance tests will produce nearly ( 10Gb) of input data (5.2Gb), output data (500Mb), temporary files (2.7Gb), and output log files (250Mb). Once these tests have passed much of this data can be removed. However, the BBP home directory should have at least 10Gb of disk space to insure the acceptance tests can be run when a particular broadband platform software distribution is first installed on a system.<br /> <br /> == Data Directory ==<br /> Input data files called Greens Functions are distributed with the platform. These files are generated using specific velocity structures, so they are often considered region specific. We have GF for three regions including near Loma Prieta, near Landers, and near Northridge.<br /> <br /> The data directory is static, and the data directories are read-only. A single copy can be installed in a shared disk, which can then be shared by multiple users.<br /> <br /> == Setting Environment Variables ==<br /> The BBP source codes and scripts are organized under the broadband platform home directory. The broadband platform home directory is specified in a couple of places during Broadband Platform installation. <br /> <br /> Internal to the Broadband platform software, all broadband platform files (except the Greens Function data files) are in sub-directories of the BBP home directory.<br /> <br /> == BBP Environment Variable ==<br /> We recommend setting both an alias and a environment variable to the BBP home directory. This will help avoid typing it many times.<br /> <br /> If you're running a Bash shell, add the following line to your .bash_profile with your favorite text editor:<br /> <br /> export BBP=/home/scec-00/kumar/bbp_2g<br /> <br /> If you're running a C-shell, add the following line to your .cshrc with your favorite text editor:<br /> <br /> setenv BBP /home/scec-00/kumar/bbp_2g<br /> <br /> * PYTHONPATH<br /> After you've obtained a copy of the project, you'll need to make sure the comps directory is on Python's path so Python can find all the project modules. If you're running a Bash shell, add the following line to your .bash_profile with your favorite text editor:<br /> <br /> export PYTHONPATH=$BBP/comps:$PYTHONPATH<br /> <br /> If you're running a C-shell, add the following line to your .cshrc with your favorite text editor:<br /> <br /> setenv PYTHONPATH $BBP/comps:$PYTHONPATH<br /> <br /> * PATH<br /> In order to successfully compile the project, you'll need to make sure the required compilers directories are in your PATH variable. Broadband requires Intel 64-bit compilers, icc and ifort and GNU Compilers, gcc, g77 and f77 to compile the scientific code.<br /> <br /> If you are planning to run Broadband on SCEC Development servers, make sure you have the following directories in your PATH:<br /> <br /> For Bash Shell (in .bash_profile)<br /> <br /> export PATH=/usr/usc/intel/composerxe-2011.4.191/bin/intel64:/usr/usc/intel/composerxe-2011.4.191/mpirt/bin/intel64:$PATH<br /> <br /> For C-shell (in .cshrc)<br /> <br /> setenv PATH /usr/usc/intel/composerxe-2011.4.191/bin/intel64:/usr/usc/intel/composerxe-2011.4.191/mpirt/bin/intel64:$PATH<br /> <br /> When running elements of the platform over ssh, be sure to enable ssh forwarding (with the -X or -Y options).<br /> <br /> After modifying your login script above, log out and log back into the machine so the changes are reflected in your environment.<br /> <br /> == Edit Install_cfg.py with Installation Directory Paths ==<br /> <br /> You need to tell the platform where it's installed by editing a single python file called &quot;install_cfg.py&quot;. Edit the file bbp_2g/comps/install_cfg.py with your favorite text editor, and edit the lines:<br /> <br /> self.A_INSTALL_ROOT = &lt;bbp_2g directory&gt;<br /> self.A_GF_DIR = &lt;bbp_2g_gf directory&gt;<br /> <br /> as one example:<br /> <br /> self.A_INSTALL_ROOT = /home/scec-00/kumar/bbp_2g<br /> self.A_GF_DIR = /home/scec-00/kumar/bbp_2g_gf<br /> <br /> with the paths on your system to the bbp_2g directory (the source) and the bbp_2g_gf directory (the data) that you unzipped. For example, it could be /home/scottcal/broadband_platform/bbp_2g and /home/scottcal/broadband_platform/bbp_2g_gf.<br /> <br /> Here is some information about these two directories that may be useful as you decide how, and where, to install these two parts of the Broadband Platform on your computer disk system. The data files, and therefore the &lt;bbp_2g_gf directory&gt; are nearly 3GB, but they are static and will not be modified and will not grow in size during use of the platform. The source directory is small to begin. However, this directory will increase as the platform is used, since the results produced by the platform will be stored here.<br /> <br /> == Directory Structure ==<br /> The platform consists of two top-level directories, bbp_2g and bbp_2g_gf. bbp_2g contains the source code, executables, scripts, tests, input, working, and output directories. bbp_2g_gf contains the Green's Functions, input files for the validation events, and other required input files for the various code bases. Note that indata, logs, outdata, tmpdata, and xml are created when the platform is first run, so they will be missing when you first install the platform.<br /> <br /> bbp_2g has the following directories:<br /> *checksums: Contains checksums for bbp_2g_gf files<br /> *comps: The Python scripts to run the platform<br /> *docs: Documentation for the platform<br /> *etc: Miscellaneous utility scripts<br /> *examples: Contains example input files<br /> *indata: An internal directory, used to stage input files<br /> *logs: Contains logs from BBP runs<br /> *outdata: Contains output files from a run<br /> *ref_data: Contains reference files for BBP tests<br /> *start: Put input files for an interactive run here<br /> *src: Source code for BBP modules<br /> *tests: Contains unit and acceptance tests<br /> *tmpdata: An internal directory, used during a run<br /> *xml: Contains XML files which describe simulations and can be used as input<br /> <br /> bbp_2g_gf has the following directories:<br /> *compare: Contains observed seismograms for validation events<br /> *plot: Data files for GMT plots<br /> *sdsu, ucsb, urs: Contains Green's functions, velocity files, and other required inputs for the codebases.<br /> <br /> In general, you will be interacting with the start directory for input files, comps to run the platform, tests to test the platform, and outdata to examine data products.<br /> <br /> === Adding aliases ===<br /> <br /> You may find it helpful to add aliases, so you can quickly and easily move to different broadband directories with a single command. We recommend creating aliases for the home, start, and outdata directories.<br /> <br /> If you are using the Bash shell, you can create aliases by adding the following lines to ~/.bash_profile:<br /> <br /> alias bbp= 'cd &lt;path to bbp_2g directory&gt;'<br /> alias start='cd &lt;path to bbp_2g directory&gt;/start'<br /> alias outdata='cd &lt;path to bbp_2g directory&gt;/outdata'<br /> <br /> If you're using a C shell, edit your ~/.cshrc and add:<br /> <br /> alias bbp cd &lt;path to bbp_2g directory&gt;<br /> alias start cd &lt;path to bbp_2g directory&gt;/start<br /> alias outdata cd &lt;path to bbp_2g directory&gt;/outdata<br /> <br /> Log out and log back in. You'll notice that now you can type the alias command as a shortcut to change directories:<br /> <br /> $&gt; pwd<br /> /home/scec-00/scottcal<br /> $&gt; start<br /> $&gt; pwd<br /> /home/scec-00/scottcal/bband/bbp_2g/start<br /> <br /> This can be a useful way to navigate around the broadband platform directories.<br /> <br /> == Building the Platform ==<br /> Once you have checked out the code, you need to build it. By default, every executable is compiled using the compiler recommended by the code developer. However, if you have limited compiler options or are building the codes on an untested system, you may need to specify non-standard alternative compilers, as described below.<br /> <br /> Before you can build the platform, you need to make sure that the Intel compilers are in your path. This is done automatically on broadband.usc.edu, but on other systems you can check by typing:<br /> <br /> $&gt;which icc<br /> <br /> If you get the message &quot;no icc in ...&quot;, then you'll need to add the Intel compilers to your path. Once the Intel compilers are in your path, you can make the code by cd-ing to the bbp_2g/src directory and typing make:<br /> <br /> $&gt; cd src<br /> $&gt; make<br /> <br /> It takes a minute or two to build the code. You may encounter build warnings; these are fine. However, if you get any build errors, this is a problem and should be investigated.<br /> <br /> By default, every executable is compiled using the compiler recommended by the code developer. Depending on the system, some compilers may not be available to you. You can override the C and Fortran compilers used by editing<br /> <br /> src/makefile<br /> <br /> Uncomment USER_C and set FC and CC to the compilers you wish. For example:<br /> <br /> Before:<br /> <br /> #USER_C=1<br /> FC=f77<br /> CC=gcc<br /> <br /> After (an example, you may choose different compilers):<br /> <br /> USER_C=1<br /> FC=gfortran<br /> CC=gcc<br /> <br /> Note that not all compiler combinations have been thoroughly tested. You may encounter build errors with untested compiler combinations. If you encounter any errors while building the platform, consult the Troubleshooting section at the end of this user guide for know issues and their solutions.<br /> <br /> Once the platform has been successfully built, you can move on to running the tests to verify that all components are working correctly.<br /> <br /> == Advanced Users ==<br /> Alternatively, if you would like access to the latest version of the platform, to get frequent but less thoroughly tested improvements, you can check out the platform from SCEC's Subversion version control repository on source.usc.edu. Only advanced users should follow this approach. If you are unsure, you should download the code as outlined in [[#Downloading the Platform|Downloading the Platform]] and skip this section.<br /> <br /> You may need to request access from the SCEC system administrator, John Yu ([mailto:johnyu@usc.edu johnyu@usc.edu]). Make sure you have subversion in your path before beginning.<br /> <br /> Once you have access, you'll need to decide if you want a stable tagged version, or the latest version in the repository. For a stable version, open a terminal window on the system of your choice and type:<br /> <br /> $&gt; svn checkout https://source.usc.edu/svn/broadband/tags/&lt;stable version&gt; bbp_2g<br /> <br /> For the latest version, type:<br /> <br /> $&gt; svn checkout https://source.usc.edu/svn/broadband/trunk bbp_2g<br /> <br /> This will check out the project to your local machine. It contains the source code, tests, and some example files. You also need to obtain a copy of the Broadband Platform data files, containing the Green's tensors. They are too large to be stored in version control. You can obtain a copy from SCEC software distribution server. If you are working on SCEC development server, you might be able to create a symbolic link to data folder. Please contact [[#User_Support|User Support]] to get a location of the data folder on the SCEC development server. If you are not working on SCEC development server, or don't have an SCEC Linux login account, you can get a archive (.tgz) file of the Green's functions from the same download site you obtained this guide.<br /> <br /> If you know where a read-accessible installation of the green functions data directories you can create a link to that location. This can save disk space in some cases.<br /> <br /> ln -s /home/scec-00/scottcal/bband/bbp_2g_gf &lt;path to your gf directory&gt;<br /> <br /> Periodically you should check for updates to the code. To do so, go to your bbp_2g directory and type<br /> <br /> $&gt; svn update<br /> <br /> This will pull down any code updates that have been made in the repository. After you update, make the code again (detailed in [[#Building the Platform|Building the Platform]]) so that any code changes are captured in the executables.<br /> <br /> == Running the Broadband Platform ==<br /> We recommend users initiate all Broadband Platform runs from the &quot;start&quot; directory. The start directory is a collection point for input files for a particular simulation.<br /> <br /> Assuming the user is starting at BBP home directory, the user should move to the start directory and then run the Checksum, Unit and Acceptance tests to confirm the Broadband Platform software installation is operating as expected.<br /> <br /> $&gt; cd start<br /> <br /> == Running Checksum, Unit, and Acceptance Tests ==<br /> The broadband platform contains three kinds of tests. The checksum tests verify that the data files were copied correctly and you have all the files that are expected. Unit tests run each module using a set of input files, and compare the results against known outputs. They verify that each module has been built and is working correctly. Acceptance tests verify that the modules are working correctly together. They test the platform end-to-end using different combinations with known inputs and compare the results. All the possible module combinations for both user-defined and validation events are tested as checks against integration errors.<br /> <br /> Begin with the checksum tests. Once they past, run the unit tests and finally the acceptance tests.<br /> <br /> == Running Checksum Tests ==<br /> To run the checksum tests, change to the checksums directory and run md5sum_check.py.<br /> <br /> From the BBP home directory:<br /> <br /> $&gt; cd checksums<br /> $&gt; ./md5sum_check.py<br /> <br /> It takes about 5 minutes to compute the checksums. If a checksum disagrees, that means that the contents of the datafile were not what was expected. Try reinstalling the data files and try again. If you continue to get a checksum error, contact support.<br /> <br /> Once the checksums agree, move on to the unit tests.<br /> <br /> == Running Unit Tests ==<br /> To run the unit tests, change to the tests directory and run UnitTests.py.<br /> <br /> From the BBP home directory:<br /> <br /> $&gt; cd tests<br /> $&gt; ./UnitTests.py<br /> <br /> The unit tests take about 15 minutes to run. When they're complete, the console will either print &quot;OK&quot; or how many tests failed. If a test has failed, first check that you have built the executables.You can rerun just the specific test that failed (test_&lt;module&gt;.py). If the test is still failing, also verify that you have the ref_data directory, since it contains the input and reference files. If you're looking for more information about the failure, you can consult the Unit Tests log file in bbp_2g/logs/unit_test.log . If you can't determine the reason for the failure, contact support.<br /> <br /> Once the unit tests all pass, proceed to the acceptance tests. If there are any failure or errors while running the unit tests, consult the Troubleshooting section at the end of this user guide for know issues and their solutions.<br /> <br /> == Running Acceptance Tests ==<br /> Make sure the unit tests pass before moving on to the acceptance tests. To run the acceptance tests, change to the tests directory (if you're not there already) and run AcceptTests.py. <br /> The acceptance tests take a long time to run, around 20 hours<br /> <br /> From the BBP home directory:<br /> <br /> $&gt; cd tests<br /> $&gt; ./AcceptTests.py &amp;&gt; accept.out &amp;<br /> <br /> Since the tests take so long to run (twenty hours), you should run them as a background process, and redirect their output to a log file, as shown in the command above.<br /> <br /> You can check the progress by tailing the log file.<br /> <br /> $&gt; tail accept.out<br /> <br /> When all the acceptance tests are completed, the AcceptTests.py script will either print &quot;OK&quot; or how many tests failed. <br /> <br /> Acceptance test failures indicate that the modules are not integrated correctly. Like with the unit tests, verify that you have the ref_data directory. If a certain acceptance test fails, you can get more information by consulting the acceptance test logs in bbp_2g/logs/acceptance_tests_logs/&lt;test that failed&gt;.log . If you can't determine the reason for the failure, contact [[support]].<br /> <br /> Since the acceptance tests can take a long time to run, you may wish to resume where you left off. This feature is supported automatically. If you do not wish to resume, delete the resume file in ref_data/accept_inputs/resume.txt. If there are any failure or errors while running the acceptance tests, consult the Troubleshooting section at the end of this user guide for know issues and their solutions.<br /> <br /> == Types of Broadband Platform Simulations == <br /> <br /> The platform supports two kinds of simulations, validation events and user-defined events. Validation simulations are performed using a historical event, and are directly compared to observed seismograms using goodness-of-fit. User-defined events are run using a rupture description provided by the user which may not necessarily be a historical earthquake.<br /> <br /> When you run a simulation, the platform assigns an ID to it. This ID can be used to track the simulation and locate the output data products.<br /> <br /> To supply input files to the platform, put them in the start directory. Extensions are important - the platform recognizes station lists (.stl), SRF files (.srf), and simple source descriptions (.src). If there are multiple files of a type, the platform will prompt the user to select one.<br /> <br /> To perform a simulation, a user selects between different required and optional modules. Below we present a summary of the various modules.<br /> <br /> == Modules ==<br /> The broadband platform consists of a series of modules. There are two main types of modules, science modules and utility modules. Science modules are those for which the platform has multiple implementations, provided by different coding research groups. Utility modules only have 1 implementation. A schematic of the available modules and their flow relationships is shown below:<br /> <br /> == Science Modules ==<br /> All simulations must include a low-frequency, high-frequency, and site response science module. Simulations may include an optional rupture generation science module. Users may select between the following different implementations of each of these modules:<br /> <br /> Rupture generation:URS, UCSB<br /> <br /> Low-frequency:URS, UCSB<br /> <br /> High-frequency:URS, UCSB, SDSU<br /> <br /> Site response:URS, UCSB, SDSU<br /> <br /> == Utility Modules ==<br /> A spectral response utility module is automatically run after the site response module. Additionally, users may select an optional goodness-of-fit utility module to run at the conclusion of the simulation. In the case of a user-defined event, users select a historical event or previously run simulation to use as the comparison for goodness-of-fit.<br /> <br /> == Platform Directory ==<br /> <br /> A broadband platform distribution is organized in a specific directory structure that separates the input data sets, the python scripts, the simulation configuration files, log files, and output data files.<br /> <br /> When running Broadband Platform simulations, standard procedure is to place the simulation input files in the start directory and invoke the Broadband platform scripts from there.<br /> <br /> From the BBP home directory:<br /> <br /> $&gt; cd start<br /> $&gt; run_bbp_2G.py<br /> <br /> Simulation output results will be written into the bbp_home/output<br /> <br /> == Validation Simulations ==<br /> To run a validation simulation, go to the comps directory and run run_bbp_2G.py. The platform will ask you a series of questions. Answer 'y' to &quot;Do you want to perform a validation run?&quot;<br /> <br /> From the BBP home directory:<br /> <br /> $&gt; cd start<br /> $&gt; run_bbp_2G.py<br /> Welcome to the SCEC Broadband Platform.<br /> Please select the modules you want to run.<br /> Do you want to perform a validation run (y/n)? y<br /> Do you want to validate with:<br /> Northridge (1)<br /> Loma Prieta (2)<br /> Landers (3)<br /> ?<br /> ...<br /> <br /> No input files are required by the user. However, you may wish to run with a reduced station list to speed up the computations. You can put your own station list into the start directory (the format is described in [[#Station File List|section 5.3]]). Note that any stations which do not have observed seismograms will not be included in the automatically generated goodness-of-fit comparison.<br /> <br /> In addition to the low-frequency modules which compute seismograms using 1D Green's Tensors, validation events can also be run using precomputed 3D seismograms to supply the low-frequency.<br /> <br /> == User-defined Simulations ==<br /> To run a user-defined simulation, two input files are required, a rupture description and a station list. The rupture description can either be in SRF format or a simplified source description (the format is described in [[#Simple source description|section 5.1]]). To run a user-defined simulation, run run_bbp_2G.py.<br /> <br /> From the BBP home directory:<br /> <br /> $&gt; cd start<br /> $&gt; run_bbp_2G.py<br /> Welcome to the SCEC Broadband Platform.<br /> Please select the modules you want to run.<br /> Do you want to perform a validation run (y/n)? y<br /> Do you want to run a rupture generator (y/n)? <br /> ...<br /> <br /> You may then choose if you want to run a rupture generator. This is necessary if you're supplying a simple rupture description. If you're supplying an SRF file, you can skip this. Next you can select from different module implementations. Finally, you have the option to run goodness-of-fit against either observed seismograms or another simulation.<br /> <br /> ...<br /> Do you want to run goodness of fit (y/n)? y<br /> What reference files would you like to compare to? Enter a simulation ID or a scenario name: &lt;comparison&gt;<br /> Enter a label to use for the comparison seismograms: &lt;label&gt;<br /> <br /> The label will be used in GoF plots to distinguish one set of results from the other.<br /> <br /> The user-defined events must be within one of the regions supported by the platform - Southern California, Northern California, or the Mojave. The platform will automatically select a region based on the event hypocenter. If the event falls outside of these regions, you'll get an error.<br /> <br /> == Logging ==<br /> During the run, log files will be produced in logs/&lt;simulation ID&gt;/&lt;simulation ID&gt;.&lt;module name&gt;.log. If the platform fails, this is a good place to look to determine the error. Additionally, any fatal errors will be recorded in fatal_error.log.<br /> <br /> Metadata capturing all the executable calls is located in tmpdata/&lt;simulation ID&gt;/metadata.txt for careful tracing of exactly what was called. Both the log files and metadata can be useful if troubleshooting an issue.<br /> <br /> == Data Products ==<br /> The platform produces a variety of data products. &lt;nowiki&gt;All data products are located in outdata/&lt;simulation ID&gt;. &lt;/nowiki&gt;On most Linux systems, you can show images using display:<br /> <br /> $&gt; display &lt;PNG file&gt;<br /> <br /> Make sure you have X11 forwarding enabled.<br /> <br /> === Station map ===<br /> To help visualize the stations in relationship to the fault, the platform produces a PNG file displaying station locations with red circles and the fault plane with a black line, on an image of California. You can find this file in outdata/&lt;simulation ID&gt;/station_map.png.<br /> <br /> === Seismograms ===<br /> When running the platform, you have the option to output velocity and acceleration seismograms, for each station. Plots of these files can be found in outdata/&lt;simulation ID&gt;/&lt;simulation ID&gt;.&lt;station&gt;_&lt;velocity or acceleration&gt;_seis.png.<br /> <br /> The raw seismogram data is available in outdata/&lt;simulation ID&gt;/&lt;simulation ID&gt;.&lt;station&gt;.vel.bbp (velocity) and outdata/&lt;simulation ID&gt;.&lt;station&gt;.acc.bbp (acceleration). Its format is described in [[#BBP seismograms|section 5.4]].<br /> <br /> To compare seismogram data, you can run comps/plotit.py with two seismograms. It will plot them both for comparison. From the comps directory, run:<br /> <br /> $&gt; plotit.py &lt;path to seismogram 1&gt; &lt;path to seismogram 2&gt;<br /> <br /> === Response spectra ===<br /> The respect code, run at the end of each simulation, calculates the response spectra for each station. The raw respect data is located at<br /> <br /> From the BBP home directory:<br /> <br /> outdata/&lt;simulation ID&gt;/&lt;simulation ID&gt;.&lt;station&gt;.rsp<br /> <br /> in the format described in [[#Response spectra|section 5.5]].<br /> <br /> === Goodness-of-fit ===<br /> If you run goodness-of-fit, several additional data products are produced. The goodness-of-fit comparison is performed by comparing the response spectra of a set of calculated seismograms to seismograms from another simulation or observed seismograms. For each station involved in the comparison, a plot comparing the response spectra can be found at outdata/&lt;simulation ID&gt;/&lt;comparison label&gt;_&lt;simulation ID&gt;_&lt;station&gt;_rsp.png. A plot showing the seismograms on top and bottom can be found at outdata/&lt;comparison label&gt;_&lt;simulation ID&gt;_&lt;station&gt;_overlay.png. The goodness-of-fit plot can be found at gof-&lt;comparison label&gt;-&lt;simulation ID&gt;_r0-&lt;cutoff distance&gt;.png.<br /> <br /> Note that at least 3 stations must be run for goodness-of-fit to be valid. If fewer than 3 stations are run, no goodness of fit calculation will be performed.<br /> <br /> === Rupture files ===<br /> When a user-defined event is simulated, the user has the option to run a rupture generator. This generator produces an SRF file, found in outdata/&lt;simulation ID&gt;/*.srf. This file can be put in the start directory and used in future runs. Additionally, the platform produces a plot of the cumulative slip on the fault surface, outdata/&lt;simulation ID&gt;/&lt;SRF prefix&gt;.png.<br /> <br /> == Platform Modes ==<br /> The platform can be run in multiple modes. The default is interactive mode, in which the user is prompted to answer a series of questions. Once all the information has been gathered, the run begins.<br /> <br /> For a large number of runs, or if the user is repeating a specific run, this can be tedious. The platform provides two other ways to describe a run, with an option file or an XML description.<br /> <br /> An option file provides responses to all the questions that the platform poses. The format is described in [[#Option File|section 5.6]], but it's basically a text file, 1 entry per line, with support for comments. It can be fed to the platform using the -o option.<br /> <br /> The platform will also accept XML files containing a full description of a run. The schema for these files is given in [[#XML workflow description schema|section 5.7]]. These files are also produced by the platform after every simulation, and placed in xml/&lt;simulation ID&gt;.xml. So if you want to rerun a simulation, you can point the platform to the XML file from that simulation using the -x option. Note that a new simulation ID will be assigned to the run, so there is no risk of overwriting previous simulation results.<br /> <br /> == Available Options ==<br /> To get a list of the current available options, run run_bbp_2G.py with the -h flag.<br /> <br /> $&gt; run_bbp_2G.py -h<br /> Usage: run_bbp_2G.py [options]<br /> Options:<br /> -h, --help Show this help message and exit<br /> -x XML_FILE, --xml-file=XML_FILE Run using XML description of workflow<br /> -s SIM_ID, --simID=SIM_ID Force a simID<br /> -o OPTFILE, --option-file=OPTFILE File containing responses to interactive platform prompts<br /> -v, --version Broadband platform version<br /> -c, --compact Compact output results. Remove temporary files for simulations that complete successfully.<br /> -g, --generate-xml Generates the XML description but does not run the platform<br /> -l LOG_FILE, --log=LOG_FILE Store all output in a file<br /> <br /> == Cleanup ==<br /> After a while, you may find that your indata, tmpdata, outdata, and logs directories are getting cluttered with files from past runs. If you wish to delete these old files, you can use the clean_directories.sh script in the etc directory.<br /> <br /> From the BBP home directory:<br /> <br /> $&gt; cd etc<br /> $&gt; ./clean_directories &lt;days&gt;<br /> <br /> Any simulation ID directories in the indata, tmpdata, outdata, and logs directories which were last accessed &lt;days&gt; days or longer ago will be deleted. If you have a few directories you want to keep, either copy them somewhere else, or copy them to a directory name that's not all digits and they won't be deleted.<br /> <br /> == Examples ==<br /> Below are some examples that you can try using the sample files in the examples directory. Make sure all the tests pass before you try this. You should be in the comps directory when you start these examples:<br /> <br /> From the BBP home directory:<br /> <br /> $&gt; cd comps<br /> <br /> === Sample Validation Run ===<br /> You don't need to move any files for this. Notice that 3D seismograms are a low-frequency option, since you're running a validation event.<br /> <br /> From the BBP home directory:<br /> <br /> $&gt; cd start<br /> $&gt; run_bbp_2G.py <br /> Welcome to the SCEC Broadband Platform.<br /> Please select the modules you want to run.<br /> Do you want to perform a validation run (y/n)? y<br /> Do you want to validate with:<br /> Northridge (1)<br /> Loma Prieta (2)<br /> Landers (3)<br /> ?1<br /> Do you want to<br /> run all validation stations (1)<br /> select a station list (2)<br /> ?1<br /> Choose a source of low frequency seismograms:<br /> URS module (1)<br /> URS 3D seismograms (2)<br /> UCSB module (3)<br /> SDSU module (4)<br /> SDSU 3D seismograms (5)<br /> ?2<br /> Choose a high frequency module:<br /> URS (1)<br /> UCSB (2)<br /> SDSU (3)<br /> ?1<br /> Choose a site response module:<br /> URS (1)<br /> UCSB (2)<br /> SDSU (3)<br /> ?1<br /> Do you want to plot velocity seismograms (y/n)? y<br /> Do you want to plot acceleration seismograms (y/n)? y<br /> <br /> This simulation takes about 10 minutes. Once it's complete the platform will tell you:<br /> <br /> You can find results in &lt;path to bbp_2g install&gt;/outdata/&lt;simulation ID&gt; .<br /> <br /> In that directory you will find:<br /> <br /> *Velocity seismograms (&lt;simulation ID&gt;.&lt;station&gt;.bbp)<br /> *Acceleration seismograms (&lt;simulation ID&gt;.&lt;station&gt;.acc.bbp)<br /> *Plots of velocity seismograms (&lt;simulation ID&gt;.&lt;station&gt;_velocity_seis.png)<br /> *Plots of acceleration seismograms (&lt;simulation ID&gt;.&lt;station&gt;_acceleration_seis.png)<br /> *Response spectra files (&lt;simulation ID&gt;.&lt;station&gt;.rsp)<br /> *Plots comparing simulated and observed seismograms (Northridge_&lt;simulation ID&gt;_&lt;station&gt;_overlay.png)<br /> *Plots comparing simulated and observed response spectra (Northridge_&lt;simulation ID&gt;_&lt;station&gt;_rsp.png)<br /> *Overall goodness-of-fit plots (gof-Northridge-&lt;simulation ID&gt;_r0-25.png)<br /> <br /> === Sample Validation run, custom stations ===<br /> If the validation runs aren't performed with 3D low-frequency, it can take a long time, up to 10 minutes per station. Sometimes you might want to run with a reduced station list so the simulation will run faster.<br /> <br /> Copy the files in example/valid_custom_stations into the start directory. Take a look at the format of the station file:<br /> <br /> $&gt; more valid_test_stat.stl <br /> #Required: lon, lat, station name, distance to fault plane, Vs30<br /> #Optional: low freq corner, high freq corner<br /> #Unused: station information<br /> #lon lat stationdist Vs30 LF corner HF corner station information<br /> -118.6417 34.5640 cast 20.47 450 0.120 23.0 CSMIP peer.berkeley.edu/nga<br /> -118.4180 34.0628 lacn 22.82 278 0.140 23.0 CSMIP peer.berkeley.edu/nga<br /> -118.8811 34.2886 moor 24.16 405 0.160 23.0 CSMIP peer.berkeley.edu/nga<br /> <br /> Now, run the platform, using a station list:<br /> <br /> From the BBP Home directory<br /> <br /> $&gt; cd start<br /> $&gt; run_bbp_2G.py <br /> Welcome to the SCEC Broadband Platform.<br /> Please select the modules you want to run.<br /> Do you want to perform a validation run (y/n)? y<br /> Do you want to validate with:<br /> Northridge (1)<br /> Loma Prieta (2)<br /> Landers (3)<br /> ?1<br /> Do you want to<br /> run all validation stations (1)<br /> select a station list (2)<br /> ?2<br /> <br /> If you have multiple station list files in your start directory, you may see the following prompt asking you to select one. If you only have one, the platform will select it automatically.<br /> <br /> Found multiple BBP station list files in the start directory. Please select one:<br /> nr_one_stat.stl (1)<br /> valid_test_stat.stl (2)<br /> ?2<br /> Choose a source of low frequency seismograms:<br /> URS module (1)<br /> URS 3D seismograms (2)<br /> UCSB module (3)<br /> SDSU module (4)<br /> SDSU 3D seismograms (5)<br /> ?3<br /> Choose a high frequency module:<br /> URS (1)<br /> UCSB (2)<br /> SDSU (3)<br /> ?2<br /> Choose a site response module:<br /> URS (1)<br /> UCSB (2)<br /> SDSU (3)<br /> ?2<br /> Do you want to plot velocity seismograms (y/n)? y<br /> Do you want to plot acceleration seismograms (y/n)? y<br /> <br /> Again, when the run completes in about 15 minutes you can find results in the output directory. You'll notice far fewer files, as only 3 stations were run instead of 133. The goodness-of-fit plots won't look very good - more stations are really needed to get an accurate plot.<br /> <br /> === Sample User-defined run with source description ===<br /> Next let's try running a user-defined event. Copy examples/user_rup_gen/nr_one_stat.stl and examples/user_rup_gen/user_eq.src to the start directory. user_eq.src is a simple source description. Its format is outlined in [[#XML workflow description schema|section 5.1]]. Since this is a user-defined event, precomputed 3D seismograms aren't a valid option.<br /> <br /> $&gt; run_bbp_2G.py <br /> Welcome to the SCEC Broadband Platform.<br /> Please select the modules you want to run.<br /> Do you want to perform a validation run (y/n)? n<br /> Do you want to run a rupture generator (y/n)? y<br /> Rupture generators:<br /> URS (1)<br /> UCSB (2)<br /> ?1<br /> Using region: Southern California<br /> Choose a low frequency module:<br /> URS (1)<br /> UCSB (2)<br /> ?2<br /> Found multiple BBP station list files in the start directory. Please select one:<br /> nr_one_stat.stl (1)<br /> valid_test_stat.stl (2)<br /> ?1<br /> Choose a high frequency module:<br /> URS (1)<br /> UCSB (2)<br /> SDSU (3)<br /> ?2<br /> Choose a site response module:<br /> URS (1)<br /> UCSB (2)<br /> SDSU (3)<br /> ?1<br /> Do you want to plot velocity seismograms (y/n)? y<br /> Do you want to plot acceleration seismograms (y/n)? y<br /> Do you want to run goodness of fit (y/n)? n<br /> <br /> Since this run only includes one station, it will run in about 5 minutes. In the output directory you'll notice there are no goodness-of-fit or files, since we didn't run goodness-of-fit. However, there is also a map file (station_map.png), showing the fault plane and the stations, and a plot of the rupture slip (user_eq.png). The SRF generated by the rupture generator is in user_eq.srf; this file could be used in future runs. The filenames of the rupture slip plot and SRF are taken from the rupture description filename.<br /> <br /> === Sample User-defined run with SRF file and goodness-of-fit ===<br /> Finally, try a run with an SRF file and run goodness-of-fit on the results. Copy in examples/user_no_rup_gen/ucsb_modSRF_0.srf and examples/user_no_rup_gen/nr_three_stat.stl<br /> <br /> $&gt; run_bbp_2G.py <br /> Welcome to the SCEC Broadband Platform.<br /> Please select the modules you want to run.<br /> Do you want to perform a validation run (y/n)? n<br /> Do you want to run a rupture generator (y/n)? n<br /> Using region: Southern California<br /> Choose a low frequency module:<br /> URS (1)<br /> UCSB (2)<br /> ?1<br /> Found multiple BBP station list files in the start directory. Please select one:<br /> nr_one_stat.stl (1)<br /> valid_test_stat.stl (2)<br /> nr_three_stat.stl (3)<br /> ?3<br /> Choose a high frequency module:<br /> URS (1)<br /> UCSB (2)<br /> SDSU (3)<br /> ?3<br /> Choose a site response module:<br /> URS (1)<br /> UCSB (2)<br /> SDSU (3)<br /> ?1<br /> Do you want to plot velocity seismograms (y/n)? y<br /> Do you want to plot acceleration seismograms (y/n)? y<br /> Do you want to run goodness of fit (y/n)? y<br /> What reference files would you like to compare to? Enter a simulation ID or a scenario name: Northridge<br /> Enter a label to use for the comparison seismograms: nr<br /> <br /> The reference files can either be a scenario event or a simulation ID previously run. The label is just for the figures when comparisons are plotted.<br /> <br /> This run will take about 15 minutes, and the results can be found in the appropriate outdir. Again, the goodness of fit measures will look poor due to the few stations involved in the comparison. If you had fewer than 3 stations, no goodness-of-fit plots would be produced. However, response spectra comparison plots will still be generated.<br /> <br /> == File Formats ==<br /> This section offers descriptions of various file formats in the broadband platform.<br /> <br /> === Simple source description ===<br /> This is the format for the simple source description. It is not whitespace sensitive. The filename must end in .src for the platform to identify it as a source description.<br /> <br /> MAGNITUDE = &lt;magnitude&gt;<br /> FAULT_LENGTH = &lt;length of fault&gt;<br /> DLEN = &lt;DX, along length&gt;<br /> FAULT_WIDTH = &lt;down-dip fault width&gt;<br /> DWID = &lt;DY, along width&gt;<br /> DEPTH_TO_TOP = &lt;depth of fault below surface&gt;<br /> STRIKE = &lt;nowiki&gt;&lt;strike&gt;&lt;/nowiki&gt;<br /> RAKE = &lt;rake&gt;<br /> DIP = &lt;dip&gt;<br /> LAT_TOP_CENTER = &lt;latitude of top center point in fault plane&gt;<br /> LON_TOP_CENTER = &lt;longitude of top center point in fault plane&gt;<br /> HYPO_ALONG_STK = &lt;along strike location of hypocenter (0.0 = middle)&gt;<br /> HYPO_DOWN_DIP = &lt;down dip location of hypocenter (0.0 = top)&gt;<br /> DT = &lt;nowiki&gt;&lt;dt&gt;&lt;/nowiki&gt;<br /> SEED = &lt;random seed used in calculations&gt;<br /> CORNER_FREQ = &lt;corner frequency to use&gt;<br /> <br /> === SRF rupture description ===<br /> Details of the Standard Rupture Format (SRF) are given in more detail in the accompanying document. The general fault surface is represented by a distribution of point sources, and it can support one or more planes. The platform produces SRFs as output from rupture generators, but a user can also supply an SRF file as input for user-defined simulations. SRF filenames must end with the suffix .srf for the platform to correctly identify them.<br /> <br /> === Station File List ===<br /> The user may specify a list of stations, matching the following format:<br /> <br /> #optional<br /> %comment<br /> # lines<br /> &lt;nowiki&gt;&lt;lon&gt; &lt;lat&gt; &lt;stat name&gt; &lt;distance to fault trace&gt; &lt;Vs30&gt; &lt;LF corner&gt; &lt;HF corner&gt; &lt;stat info&gt;&lt;/nowiki&gt;<br /> ...<br /> <br /> The station list filename needs to end in .stl for the platform to recognize it as a station list.<br /> <br /> === BBP seismograms ===<br /> All intermediate and output seismograms are produced in a 4-column text format, whether velocity or acceleration.<br /> <br /> # optional<br /> % comment<br /> # lines<br /> &lt;nowiki&gt;&lt;timestamp&gt; &lt;North/South&gt; &lt;East/West&gt; &lt;Up/Down&gt;&lt;/nowiki&gt;<br /> ...<br /> <br /> Time is in seconds and motion is in cm/s (velocity) or cm/s/s (acceleration) unless otherwise specified in the header. Velocity filenames end in .vel.bbp; accelerations in .acc.bbp.<br /> <br /> === Response spectra ===<br /> The response spectra file is in 4-column text format.<br /> <br /> # optional<br /> % comment<br /> # lines<br /> &lt;nowiki&gt;&lt;period (sec)&gt; &lt;North/South&gt; &lt;East/West&gt; &lt;Up/Down&gt;&lt;/nowiki&gt;<br /> ...<br /> <br /> The platform samples response spectra at 112 periods, 0.01-20 sec and outputs pseudo spectral acceleration in units of g.<br /> <br /> === Option File ===<br /> Option files contain responses to the prompts in the platform. You can use them with the -o option to run_bbp_2G.py. The responses have to match the prompts exactly. For example, if you craft an option file assuming there is only one station list in the start directory (and therefore the user isn't prompted to select one) but then it is run with multiple station lists in the start directory, this will cause the run to abort. Option files are recommended to perform a series of runs with different inputs or different modules. If you have a run you perform regularly, it's better practice to run the platform with the -g option and the option file to produce an XML description, which are more complete descriptions of the workflow.<br /> <br /> #optional comments<br /> %using either symbol<br /> n #comments<br /> y % can go<br /> 1 # here<br /> ...<br /> <br /> Use with:<br /> <br /> $&gt; run_bbp_2G.py -o &lt;option file&gt;<br /> <br /> === XML workflow description schema ===<br /> Each time the platform is invoked, an XML file is produced describing the workflow, obeying the following schema:<br /> <br /> &lt;nowiki&gt;&lt;xs:schema xmlns:xs=&quot;http://www.w3.org/2001/XMLSchema&quot;&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:element name= &quot;BBP_Run_Specification&quot; minOccurs= &quot;1&quot; maxOccurs= &quot;1&quot;&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:attribute name=&quot;version&quot; type = &quot;xs:string&quot; use = &quot;required&quot; /&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:complexType&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:sequence&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:element name= &quot;Validation_Run&quot; minOccurs= &quot;0&quot; maxOccurs = &quot;1&quot;&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:attribute name= &quot;event&quot; type= &quot;xs:string&quot; use= &quot;required&quot; /&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:attribute name= &quot;input_station_file&quot; type = &quot;xs:string&quot; /&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:attribute name= &quot;subset&quot; type = &quot;xs:boolean&quot; use = &quot;required&quot; /&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;/xs:element&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:element name= &quot;BBP_Modules&quot;&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:complexType&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:sequence&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:element name = &quot;BBP_Module&quot; maxOccurs = &quot;unbounded&quot; &gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:complexType&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:sequence&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:element name= &quot;name&quot; type=&quot;xs:string&quot; /&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:element name= &quot;staged_files&quot; &gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:complexType&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:sequence&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:element name=&quot;file&quot; type=&quot;xs:string&quot; maxOccurs= &quot;unbounded&quot;/&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;/xs:sequence&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;/xs:complexType&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;/xs:element&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:element name= &quot;arguments&quot; &gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:complexType&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:sequence&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:element name=&quot;argument&quot; type=&quot;xs:string&quot; maxOccurs=&quot;unbounded&quot;&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:attribute name= &quot;type&quot; type= &quot;xs:string&quot; user= &quot;required&quot; /&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;/xs:element&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;/xs:sequence&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;/xs:complexType&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;/xs:element&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;/xs:sequence&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;/xs:complexType&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;/xs:element&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;/xs:sequence&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;/xs:complexType&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;/xs:element&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;/xs:sequence&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;/xs:complexType&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;/xs:element&gt;&lt;/nowiki&gt;<br /> <br /> These files are difficult to construct by hand, but can be generated using the -g flag when running run_bbp_2G.py.<br /> <br /> == User Support ==<br /> If you run into bugs with the platform, you can open a trouble ticket at the [http://northridge.usc.edu/trac/broadband Broadband Trac site].<br /> <br /> Check to see if there has already been a ticket opened for the bug. If you are unable to get the platform to run, you can get direct user support by emailing [mailto:software@intensity.usc.edu software@intensity.usc.edu].<br /> <br /> == Appendix A: Possible Module Permutations ==<br /> === Validation Events ===<br /> <br /> {| class=&quot;wikitable&quot; | border=&quot;1&quot;<br /> | Permutation #<br /> | Low-frequency module<br /> | High-frequency module<br /> | Site response<br /> <br /> |-<br /> | &lt;center&gt;1&lt;/center&gt;<br /> | &lt;center&gt;URS 1D&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;2&lt;/center&gt;<br /> | &lt;center&gt;URS 1D&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;3&lt;/center&gt;<br /> | &lt;center&gt;URS 1D&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;4&lt;/center&gt;<br /> | &lt;center&gt;URS 1D&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;5&lt;/center&gt;<br /> | &lt;center&gt;URS 1D&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;6&lt;/center&gt;<br /> | &lt;center&gt;URS 1D&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;7&lt;/center&gt;<br /> | &lt;center&gt;URS 1D&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;8&lt;/center&gt;<br /> | &lt;center&gt;URS 1D&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;9&lt;/center&gt;<br /> | &lt;center&gt;URS 1D&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;10&lt;/center&gt;<br /> | &lt;center&gt;URS 3D precomputed&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;11&lt;/center&gt;<br /> | &lt;center&gt;URS 3D precomputed&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;12&lt;/center&gt;<br /> | &lt;center&gt;URS 3D precomputed&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;13&lt;/center&gt;<br /> | &lt;center&gt;URS 3D precomputed&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;14&lt;/center&gt;<br /> | &lt;center&gt;URS 3D precomputed&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;15&lt;/center&gt;<br /> | &lt;center&gt;URS 3D precomputed&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;16&lt;/center&gt;<br /> | &lt;center&gt;URS 3D precomputed&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;17&lt;/center&gt;<br /> | &lt;center&gt;URS 3D precomputed&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;18&lt;/center&gt;<br /> | &lt;center&gt;URS 3D precomputed&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;19&lt;/center&gt;<br /> | &lt;center&gt;UCSB 1D&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;20&lt;/center&gt;<br /> | &lt;center&gt;UCSB 1D&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;21&lt;/center&gt;<br /> | &lt;center&gt;UCSB 1D&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;22&lt;/center&gt;<br /> | &lt;center&gt;UCSB 1D&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;23&lt;/center&gt;<br /> | &lt;center&gt;UCSB 1D&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;24&lt;/center&gt;<br /> | &lt;center&gt;UCSB 1D&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;25&lt;/center&gt;<br /> | &lt;center&gt;UCSB 1D&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;26&lt;/center&gt;<br /> | &lt;center&gt;UCSB 1D&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;27&lt;/center&gt;<br /> | &lt;center&gt;UCSB 1D&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;28&lt;/center&gt;<br /> | &lt;center&gt;SDSU 1D&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;29&lt;/center&gt;<br /> | &lt;center&gt;SDSU 1D&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;30&lt;/center&gt;<br /> | &lt;center&gt;SDSU 1D&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;31&lt;/center&gt;<br /> | &lt;center&gt;SDSU 1D&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;32&lt;/center&gt;<br /> | &lt;center&gt;SDSU 1D&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;33&lt;/center&gt;<br /> | &lt;center&gt;SDSU 1D&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;34&lt;/center&gt;<br /> | &lt;center&gt;SDSU 1D&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;35&lt;/center&gt;<br /> | &lt;center&gt;SDSU 1D&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;36&lt;/center&gt;<br /> | &lt;center&gt;SDSU 1D&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;37&lt;/center&gt;<br /> | &lt;center&gt;SDSU 3D precomputed&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;38&lt;/center&gt;<br /> | &lt;center&gt;SDSU 3D precomputed&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;39&lt;/center&gt;<br /> | &lt;center&gt;SDSU 3D precomputed&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;40&lt;/center&gt;<br /> | &lt;center&gt;SDSU 3D precomputed&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;41&lt;/center&gt;<br /> | &lt;center&gt;SDSU 3D precomputed&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;42&lt;/center&gt;<br /> | &lt;center&gt;SDSU 3D precomputed&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;43&lt;/center&gt;<br /> | &lt;center&gt;SDSU 3D precomputed&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;44&lt;/center&gt;<br /> | &lt;center&gt;SDSU 3D precomputed&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;45&lt;/center&gt;<br /> | &lt;center&gt;SDSU 3D precomputed&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> |}<br /> <br /> ===User-Defined Events===<br /> <br /> {| class=&quot;wikitable&quot; | border=&quot;1&quot;<br /> | Permutation #<br /> | Rupture generator<br /> | Low-frequency<br /> | High-frequency<br /> | Site response<br /> <br /> |-<br /> | &lt;center&gt;1&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;2&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;3&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;4&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;5&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;6&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;7&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;8&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;9&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;10&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;11&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;12&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;13&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;14&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;15&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;16&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;17&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;18&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;19&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;20&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;21&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;22&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;23&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;24&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;25&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;26&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;27&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;28&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;29&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;30&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;31&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;32&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;33&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;34&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;35&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;36&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;37&lt;/center&gt;<br /> | &lt;center&gt;User-supplied SRF&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;38&lt;/center&gt;<br /> | &lt;center&gt;User-supplied SRF&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;39&lt;/center&gt;<br /> | &lt;center&gt;User-supplied SRF&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;40&lt;/center&gt;<br /> | &lt;center&gt;User-supplied SRF&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;41&lt;/center&gt;<br /> | &lt;center&gt;User-supplied SRF&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;42&lt;/center&gt;<br /> | &lt;center&gt;User-supplied SRF&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;43&lt;/center&gt;<br /> | &lt;center&gt;User-supplied SRF&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;44&lt;/center&gt;<br /> | &lt;center&gt;User-supplied SRF&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;45&lt;/center&gt;<br /> | &lt;center&gt;User-supplied SRF&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;46&lt;/center&gt;<br /> | &lt;center&gt;User-supplied SRF&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;47&lt;/center&gt;<br /> | &lt;center&gt;User-supplied SRF&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;48&lt;/center&gt;<br /> | &lt;center&gt;User-supplied SRF&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;49&lt;/center&gt;<br /> | &lt;center&gt;User-supplied SRF&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;50&lt;/center&gt;<br /> | &lt;center&gt;User-supplied SRF&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;51&lt;/center&gt;<br /> | &lt;center&gt;User-supplied SRF&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;52&lt;/center&gt;<br /> | &lt;center&gt;User-supplied SRF&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;53&lt;/center&gt;<br /> | &lt;center&gt;User-supplied SRF&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;54&lt;/center&gt;<br /> | &lt;center&gt;User-supplied SRF&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> |}<br /> <br /> == Appendix B: Troubleshooting ==<br /> If you experience trouble building the platform or successfully running test and simulations, try the following solutions.<br /> <br /> === Build Errors ===<br /> <br /> The instruction for installing Broadband Platform are listed in Section 1: &quot;Installing the Second-Generation Broadband Platform&quot; of the User guide. If after following all steps listed in this section of the user guide the build fails, check if the failure is listed in this section and try the solution to fix the issue you are facing.<br /> <br /> ==== 64-bit Intel Compiler Issue ====<br /> If you try to compile with:<br /> &lt;pre&gt;<br /> % cd bbp_2g/src<br /> % make<br /> &lt;/pre&gt; <br /> <br /> and you get:<br /> &lt;pre&gt;<br /> ... <br /> make[2]: Entering directory `.../bbp_2g/src/ucsb/getInFile'<br /> icc -o getfaultGlobal getfaultGlobal.c<br /> ld: cannot find -lgcc_s_32<br /> make[2]: *** [getfaultGlobal] Error 1<br /> make[2]: Leaving directory `.../bbp_2g/src/ucsb/getInFile'<br /> make[1]: *** [all] Error 2<br /> make[1]: Leaving directory `.../bbp_2g/src/ucsb'<br /> make: *** [all] Error 2<br /> &lt;/pre&gt;<br /> <br /> '''Cause:''' The Broadband Platform requires Intel 64-bit compilers to build successfully. In this case the 32-bit Intel compilers are being invoked as they are being picked up from the PATH environment variable. The error is due to a missing GNU-GCC 32-bit compatibility pack that has not been installed on your system. This is not required when 64-bit Intel compilers are used.<br /> <br /> '''Solution:''' Ensure that the path Intel 64-bit compilers are listed in you PATH variable and being picked up by running 'which icc' and 'which ifort'. If you are trying to build the platform on SCEC development servers like Intensity, verify your path variable has:<br /> &lt;pre&gt;<br /> PATH=...:/usr/usc/intel/composerxe-2011.4.191/mpirt/bin/intel64:/usr/usc/intel/composerxe-2011.4.191/bin/intel64<br /> &lt;/pre&gt;<br /> <br /> ==== 32-bit Platform Issue ====<br /> <br /> On trying to build the platform, the build fails with the following message:<br /> &lt;pre&gt;<br /> $ make all<br /> cd urs; make -f makefile FC=gfortran CC=icc USER_C=1;<br /> make[1]: Entering directory `.../bbp_2g/src/urs'<br /> mkdir -p bin;<br /> cd getpar/src; make -f Makefile CC=icc FC=gfortran USER_C=1;<br /> make[2]: Entering directory `.../bbp_2g/src/urs/getpar/src'<br /> icc -O3 -DENVIRONMENT -c -o defpar.o defpar.c<br /> icc -O3 -DENVIRONMENT -c -o getpar.o getpar.c<br /> icc -O3 -DENVIRONMENT -c -o getarg.o getarg.c<br /> getarg.c(112): warning #303: explicit type is missing (&quot;int&quot; assumed)<br /> register i;<br /> ^ <br /> icc -O3 -DENVIRONMENT -c -o getlocation.o getlocation.c<br /> getlocation.c(9): warning #147: declaration is incompatible with &quot;__ssize_t={int} getline(char **restrict, size_t={unsigned int} *restrict, FILE *restrict)&quot; (declared at line 671 of &quot;/usr/include/stdio.h&quot;)<br /> static int getline(FILE *fd, char *line)<br /> <br /> ...<br /> ...<br /> ...<br /> <br /> make[2]: Entering directory `.../bbp_2g/src/sdsu/srcV1.4'<br /> icc -w -Wall -c ray3DJHfor.c<br /> gfortran module_bbtoolbox.f90 module_interface.f90 main_bbtoolbox.f90 coda.f90 composition.f90 convolution.f90 fourier.f90 error.f90 geometry.f90 interpolation.f90 io.f90 random.f90 scattering.f90 source.f90 ray3DJHfor.o -o BBtoolbox.exe<br /> ray3DJHfor.o: In function `raytracing_':<br /> ray3DJHfor.c:(.text+0x8cf): undefined reference to `__libm_sse2_log'<br /> ray3DJHfor.c:(.text+0x96b): undefined reference to `__libm_sse2_asin'<br /> ray3DJHfor.c:(.text+0x9cd): undefined reference to `__libm_sse2_asin'<br /> ray3DJHfor.c:(.text+0xa00): undefined reference to `__libm_sse2_tan'<br /> ray3DJHfor.c:(.text+0xa3d): undefined reference to `__libm_sse2_tan'<br /> ray3DJHfor.c:(.text+0xa52): undefined reference to `__libm_sse2_log'<br /> collect2: ld returned 1 exit status<br /> make[2]: *** [BBtoolbox.exe] Error 1<br /> make[2]: Leaving directory `.../bbp_2g/src/sdsu/srcV1.4'<br /> make[1]: *** [all] Error 2<br /> make[1]: Leaving directory `.../bbp_2g/src/sdsu'<br /> make: *** [all] Error 2<br /> &lt;/pre&gt;<br /> <br /> '''Cause:''' In this case the user tried to build Broadband on a 32-bit platform. Broadband code was designed to be run on 64-bit platform. Any attempt to build Broadband on a 32-bit platform will result in numerous warnings and the build will fail with error messages similar to ones listed above.<br /> <br /> '''Solution:''' Try building Broadband on a 64-bit platform will the all the dependencies listed in Section 1.1: &quot;System Dependencies&quot; and Section 1.2: &quot;Software Dependencies&quot;<br /> <br /> === Unit/Acceptance Test Failures and Errors ===<br /> <br /> Unit and Acceptance tests are provided to verify the Broadband platform and it's supporting modules built by the user are functioning as designed. Under certain circumstances, some of these test might fail. While some of these failure might indicate serious problems that will have to be addressed before the platform can used, it is acceptable to ignore some of the failures. This section lists some failures and their solutions.<br /> <br /> ==== ERROR: test_syn1d (test_syn1d.Test_syn1D) ====<br /> The Unit test for Syn1d module fails with the following message:<br /> &lt;pre&gt;<br /> ERROR: test_syn1d (test_syn1d.Test_syn1D)<br /> ----------------------------------------------------------------------<br /> Traceback (most recent call last):<br /> File &quot;.../bbp_2g/tests/test_syn1d.py&quot;, line 62, in test_syn1d<br /> synObj.run()<br /> File &quot;.../bbp_2g/comps/syn1D.py&quot;, line 236, in run<br /> shutil.copy2(a_tmpfile, expected_file)<br /> File &quot;/usr/lib/python2.6/shutil.py&quot;, line 99, in copy2<br /> copyfile(src, dst)<br /> File &quot;/usr/lib/python2.6/shutil.py&quot;, line 52, in copyfile<br /> fsrc = open(src, 'rb')<br /> IOError: [Errno 2] No such file or directory: '.../bbp_2g/tmpdata/3310632/s01.3comp'<br /> &lt;/pre&gt;<br /> <br /> '''Cause:''' Syn1d module requires the Green's Function file to run and the path to this file might be incorrect in 'bbp_2g_gf/ucsb/GreenBank/Northridge/GreenBank.inf' file.<br /> <br /> '''Solution:''' This issue can be fixed by correcting the paths listed in the GreenBank.inf files in the Green's Function directory. Here are step by step instructions to fix this issue:<br /> <br /> 1. Locate your Greens Functions directory: 'bbp_2g_gf'<br /> 2. Navigate to bbp_2g_gf/ucsb/GreenBank/Northridge folder.<br /> 3. Open Green_Bank.inf files with a text editor.<br /> 4. Locate the text &quot;The name of file to store Green Bank&quot;<br /> 5. Note the location of the Green Bank file under the line found in step 4, similar to &quot;/home/scec-00/scottcal/bband/bbp_2g_gf/ucsb/GreenBank/Northridge/Green_1d.soil&quot;.<br /> 6. Replace the path found in Step 5 with just the file name, in the case of Northridge it is &quot;Green_1d.soil&quot;<br /> 7. Save and close the Green_Bank.inf.<br /> 8. Navigate to bbp_2g_gf/ucsb/GreenBank/LomaPrieta folder and repeat steps 3-7. The name of the Green Bank file for LomaPrieta is &quot;Green_1d.LoPr&quot;.<br /> 9. Navigate to bbp_2g_gf/ucsb/GreenBank/Landers folder and repeat steps 3-7. The name of the Green Bank file for Landers is &quot;Green1D.Landers&quot;<br /> <br /> ==== ERROR: test_gensrf (test_genslip.Test_Genslip) ====<br /> The Unit test for Genslip module fails with the following message:<br /> &lt;pre&gt;<br /> ======================================================================<br /> ERROR: test_gensrf (test_genslip.Test_Genslip)<br /> ----------------------------------------------------------------------<br /> Traceback (most recent call last):<br /> File &quot;.../bbp_2g/tests/test_genslip.py&quot;, line 51, in test_gensrf<br /> gen.run()<br /> File &quot;.../bbp_2g/comps/genslip.py&quot;, line 153, in run<br /> ps.run()<br /> File &quot;.../bbp_2g/comps/plot_srf.py&quot;, line 52, in run<br /> shutil.copy2(&quot;%s/%s.ps.png&quot; % (a_tmpdir, self.r_srffile[0:self.r_srffile.find(&quot;.srf&quot;)]), &quot;%s/%s.png&quot; % (a_outdir, self.r_srffile[0:self.r_srffile.find(&quot;.srf&quot;)]))<br /> File &quot;/usr/lib/python2.6/shutil.py&quot;, line 99, in copy2<br /> copyfile(src, dst)<br /> File &quot;/usr/lib/python2.6/shutil.py&quot;, line 52, in copyfile<br /> fsrc = open(src, 'rb')<br /> IOError: [Errno 2] No such file or directory: '.../bbp_2g/tmpdata/3309008/3309008_test_eq.ps.png'<br /> &lt;/pre&gt;<br /> <br /> '''Cause:''' The Genslip module calls the Plot_SRF module to the plot the SRF file. Plot_SRF uses C-shell code to locate and use GMT package to plot the SRF file. This shell code might fail on some flavors of Linux with a message like &quot;Newline in variable name&quot; in the Plot_SRF log file.<br /> <br /> '''Solution:''' This issue can be fixed by editing the plot_SRF.csh file. Here are step by step instructions to fix this issue:<br /> <br /> 1. Locate shell script file: bbp_2g/src/plot/plot_SRF.csh<br /> 2. Open the file in your preferred text editor<br /> 3. Locate the line 'set FIND_GMT = $?'<br /> 4. Replace the line found in step 3 with 'set FIND_GMT = $status'<br /> 5. Locate the section of code that starts with the statement &quot;# FIND MAX. SLIP&quot;<br /> 6. Replace the following line in section found in step 5:<br /> &lt;pre&gt;<br /> set SMAX = `$XYZCODE calc_xy=$CALC_XY type=&quot;${TYPE}&quot; nseg=-1 &lt; $SLIPFILE.srf | \<br /> gawk -v m=$SMAX '{if($3&gt;m)m=$3;}END{printf &quot;%.0f\n&quot;,m;}'`<br /> <br /> with (collapse the statement to a single line by removing '\' at the end of first part of the statement):<br /> <br /> set SMAX = `$XYZCODE calc_xy=$CALC_XY type=&quot;${TYPE}&quot; nseg=-1 &lt; $SLIPFILE.srf | gawk -v m=$SMAX '{if($3&gt;m)m=$3;}END{printf &quot;%.0f\n&quot;,m;}'`<br /> &lt;/pre&gt;<br /> 7. Save the file and exit<br /> <br /> ==== ERROR: test_ucgen (test_ucrmg.Test_UCrmg) ====<br /> The Unit test for Ucrmg module fails with the following message:<br /> &lt;pre&gt;<br /> ======================================================================<br /> ERROR: test_ucgen (test_ucrmg.Test_UCrmg)<br /> ----------------------------------------------------------------------<br /> Traceback (most recent call last):<br /> File &quot;.../bbp_2g/tests/test_ucrmg.py&quot;, line 59, in test_ucgen<br /> ucObj.run()<br /> File &quot;.../bbp_2g/comps/ucrmg.py&quot;, line 161, in run<br /> ps.run()<br /> File &quot;.../bbp_2g/comps/plot_srf.py&quot;, line 52, in run<br /> shutil.copy2(&quot;%s/%s.ps.png&quot; % (a_tmpdir, self.r_srffile[0:self.r_srffile.find(&quot;.srf&quot;)]), &quot;%s/%s.png&quot; % (a_outdir, self.r_srffile[0:self.r_srffile.find(&quot;.srf&quot;)]))<br /> File &quot;/usr/lib/python2.6/shutil.py&quot;, line 99, in copy2<br /> copyfile(src, dst)<br /> File &quot;/usr/lib/python2.6/shutil.py&quot;, line 52, in copyfile<br /> fsrc = open(src, 'rb')<br /> IOError: [Errno 2] No such file or directory: '.../bbp_2g/tmpdata/3309831/test_ucsb.ps.png'<br /> &lt;/pre&gt;<br /> <br /> '''Cause:''' The Ucrmg module calls the Plot_SRF module to the plot the SRF file. Plot_SRF uses C-shell code to locate and use GMT package to plot the SRF file. This shell code might fail on some flavors of Linux with a message like &quot;Newline in variable name&quot; in the Plot_SRF log file.<br /> <br /> '''Solution:''' This issue can be fixed by editing the plot_SRF.csh file. The steps to fix this issue are listed under the solution for &quot;ERROR: test_gensrf (test_genslip.Test_Genslip)&quot; above.<br /> <br /> ==== FAIL: test_site_amp (test_uc_site.Test_UC_Site) ====<br /> <br /> The unit test for UC-Site module might fail with the following message:<br /> &lt;pre&gt;<br /> ======================================================================<br /> FAIL: test_site_amp (test_uc_site.Test_UC_Site)<br /> ----------------------------------------------------------------------<br /> Traceback (most recent call last):<br /> File &quot;.../bbp_2g/tests/test_uc_site.py&quot;, line 92, in test_site_amp<br /> self.failIf(cmp_bbp.cmp_bbp(a_ref_file_no_header, test_file_no_header, tolerance=0.035)!=0,errmsg)<br /> AssertionError: Output file .../bbp_2g/tmpdata/3310633/s04.3comp does not match reference file .../bbp_2g/ref_data/ucsb/s04.site.3comp<br /> &lt;/pre&gt;<br /> <br /> '''Cause:''' The synthetic seismogram generated by the UC-Site module on the user system differs from the reference result included in the Broadband release.<br /> <br /> '''Solution:''' The stochastic nature of the high frequency simulations is considered, and a constant random seed as input for our tests. This is the same constant random seed used to generate the reference results included in the release. This ensures that the time-series generated with unit tests agree with reference results. However, the high frequency codes are more sensitive to changes in compilers and machines due to the algorithm, so small differences that cause the test to fail are generally acceptable. The user is however encouraged to plot the two time-series and visually inspect them to verify they look similar. We are trying to come up with a better comparison for these tests.<br /> <br /> == Appendix C: Technical Notes ==<br /> <br /> === Running Individual Acceptance Tests ===<br /> <br /> The acceptance test script ./tests/AcceptTest.py attempts to run all of the defined tests when executed. However, sometimes it is useful to run an acceptance test in isolation for troubleshooting purposes:<br /> <br /> * Identify the test you want to run. Eg: user-URS-UCSB-SDSU-SDSU<br /> * Move to the ./comps directory and execute that test's XML workflow with run_bbp_2G.py. Using the above example:<br /> &lt;pre&gt;<br /> $ ./run_bbp_2G.py -x ../ref_data/accept_inputs/user-URS-UCSB-SDSU-SDSU.xml<br /> &lt;/pre&gt;<br /> <br /> Since you are running the test outside of AcceptTest.py, you will not see a PASS/FAIL message once the simulation completes. However, you can review the contents of the ./outdata/&lt;SIMID&gt; directory to verify that the correct seismograms and response spectra tables were produced.<br /> <br /> === Manaully Setting Random Number Generator Seed Values ===<br /> <br /> Several of the platform codebases employ random number generators to produce SRFs and seismograms. These random number generators are generally seeded with an initial value (typically an integer) which are hard-coded in the platform. Advanced users may desire to change these seed values.<br /> <br /> Changing the seeds for seismogram synthesis varies depending on which codebase you want to use:<br /> <br /> * URS: Edit ./comps/hfsims_cfg.py, Line 43 &quot;self.RAND_NUM&quot;<br /> * UCSB: Edit ./src/ucsb/Syn1DSCEC/syn1D_LAH.f, Line 183 &quot;iseed&quot;, and recompile with &quot;make&quot;<br /> * SDSU:<br /> ** User event: Edit ./bbp_2g_gf/sdsu/scattering_generic.dat (seed values annotated in file)<br /> ** Validation event: Edit ./bbp_2g_gf/sdsu/&lt;event&gt;/scattering.dat</div> Patrices https://strike.scec.org/scecwiki/index.php?title=Broadband_User_Guide_v11.2.3&diff=5053 Broadband User Guide v11.2.3 2012-05-08T21:37:18Z <p>Patrices: </p> <hr /> <div>'''Version 11.2.3.'''<br /> <br /> If you find errors in this document or sections to be unclear, please either fix them yourself or contact software@scec.org.<br /> <br /> == Installing the Second-Generation Broadband Platform ==<br /> Installing the Broadband Platform involves obtaining a copy of the code and building the required executables. You can either download the platform from the Broadband web site ([http://www.scec.org/research/broadband http://www.scec.org/research/broadband]) or check the code out of SCEC's Subversion repository. Most users should download the platform.<br /> <br /> == System Dependencies ==<br /> The current version of the Broadband Platform is designed to run on standard 64-bit Linux machines. Testing has been performed on SCEC's development servers running Fedora Core 10 (kernel version 2.6.27.41-170.2.117.fc10.x86_64). In this guide we outline how to install the platform into your own account on a Linux computer using the simplest approach.<br /> <br /> == Software Dependencies ==<br /> The Broadband Platform has certain software dependencies.<br /> <br /> Required:<br /> <br /> *Python v2.7 with<br /> **PyGTK<br /> **Matplotlib<br /> **Numpy<br /> **Pyproj<br /> <br /> *Intel compilers (64-bit) v12.0.4<br /> *GNU compilers (gcc, gfortran) v4.5.1<br /> *GNU Fortran 77 v3.4.6<br /> *GMT (Generic Mapping Toolkit)<br /> *ImageMagick<br /> <br /> == Setting Up Your Account ==<br /> For simplicity of installation, we recommend users use a bash shell for the Broadband Platform account. It is possible to get the platform running using other shell's, but we will focus on a bash shell installation. The user environment is a common source of problems since certain environment variables must be defined for the platform to work correctly.<br /> <br /> To check your account, make sure you can run basic commands like ''ls'' and ''cd'' before proceeding.<br /> <br /> == Downloading the Platform ==<br /> &lt;nowiki&gt;Download 4 files from the Broadband website, the code (bbp_dist_&lt;version&gt;.tgz), the data (bbp_data_&lt;version&gt;.tgz), and their checksum files (bbp_dist_&lt;version&gt;.tgz.md5 and bbp_data_&lt;version&gt;.tgz.md5). &lt;/nowiki&gt;The code file is about 100 MB, the data file about 3 GB. After you've downloaded the files to your local Linux system, the next step is to calculate the checksums yourself and compare them to the checksums you downloaded.<br /> <br /> First, verify that the ''md5sum'' command is in your path:<br /> <br /> $&gt; which md5sum<br /> <br /> You should get something like /usr/bin/md5sum. If you see the message 'no md5sum in...', contact your Linux system administrator and ask to have md5sum added to your path.<br /> <br /> Once you can run the ''md5sum'' command, run:<br /> <br /> $&gt; md5sum -c bbp_dist_&lt;version&gt;.tgz.md5<br /> $&gt; md5sum -c bbp_data_&lt;version&gt;.tgz.md5<br /> <br /> You should get the messages<br /> bbp_dist_&lt;version&gt;.tgz.md5: OK<br /> bbp_data_&lt;version&gt;.tgz.md5: OK<br /> <br /> If you get FAILED instead, re-download the tgz files and try again. When it passes, that means the files were downloaded without error.<br /> <br /> Once both files have passed the checksum test, untar the files.<br /> <br /> $&gt; tar xzvf bbp_dist_&lt;version&gt;.tgz file<br /> $&gt; tar xzvf bbp_data_&lt;version&gt;.tgz file<br /> <br /> If multiple users are planning to use the platform on the same system, you only need one copy of the data files per machine. Each user will still need his or her own copy of the code files.<br /> <br /> Alternatively, if you would like access to the latest version of the platform and get frequent but less thoroughly tested improvements, you can check out the platform from SCEC's Subversion repository. Only advanced users should take this approach, outlined in detail in the [[#Advanced Users| Advanced Users section]].<br /> <br /> == User Account Setup ==<br /> <br /> The Broadband platform installation is divided into two parts (1) input Green Functions (GF) data directory (9.3Gb), and (2) BBP home directory (366Mb). <br /> <br /> First, the Green's function libraries are larger, but they are static. The broadband platform reads the data files, but does not change them. <br /> <br /> Second, the remainder of the broadband platform is organized in the BBP home directory. The BBP home directory has a specific directory structure that includes the source code for the scientific programs, the python scripts that link the scientific programs, simulation input directory, temporary and log file directories, and the output data directory where all the platform results are written.<br /> <br /> The BBP home directory will increase in size as you run the platform, because both output data and output log files are written to the home directory. Running the acceptance tests will produce nearly ( 10Gb) of input data (5.2Gb), output data (500Mb), temporary files (2.7Gb), and output log files (250Mb). Once these tests have passed much of this data can be removed. However, the BBP home directory should have at least 10Gb of disk space to insure the acceptance tests can be run when a particular broadband platform software distribution is first installed on a system.<br /> <br /> == Data Directory ==<br /> Input data files called Greens Functions are distributed with the platform. These files are generated using specific velocity structures, so they are often considered region specific. We have GF for three regions including near Loma Prieta, near Landers, and near Northridge.<br /> <br /> The data directory is static, and the data directories are read-only. A single copy can be installed in a shared disk, which can then be shared by multiple users.<br /> <br /> == Setting Environment Variables ==<br /> The BBP source codes and scripts are organized under the broadband platform home directory. The broadband platform home directory is specified in a couple of places during Broadband Platform installation. <br /> <br /> Internal to the Broadband platform software, all broadband platform files (except the Greens Function data files) are in sub-directories of the BBP home directory.<br /> <br /> == BBP Environment Variable ==<br /> We recommend setting both an alias and a environment variable to the BBP home directory. This will help avoid typing it many times.<br /> <br /> If you're running a Bash shell, add the following line to your .bash_profile with your favorite text editor:<br /> <br /> export BBP=/home/scec-00/kumar/bbp_2g<br /> <br /> If you're running a C-shell, add the following line to your .cshrc with your favorite text editor:<br /> <br /> setenv BBP /home/scec-00/kumar/bbp_2g<br /> <br /> * PYTHONPATH<br /> After you've obtained a copy of the project, you'll need to make sure the comps directory is on Python's path so Python can find all the project modules. If you're running a Bash shell, add the following line to your .bash_profile with your favorite text editor:<br /> <br /> export PYTHONPATH=$BBP/comps:$PYTHONPATH<br /> <br /> If you're running a C-shell, add the following line to your .cshrc with your favorite text editor:<br /> <br /> setenv PYTHONPATH $BBP/comps:$PYTHONPATH<br /> <br /> * PATH<br /> In order to successfully compile the project, you'll need to make sure the required compilers directories are in your PATH variable. Broadband requires Intel 64-bit compilers, icc and ifort and GNU Compilers, gcc, g77 and f77 to compile the scientific code.<br /> <br /> If you are planning to run Broadband on SCEC Development servers, make sure you have the following directories in your PATH:<br /> <br /> For Bash Shell (in .bash_profile)<br /> <br /> export PATH=/usr/usc/intel/composerxe-2011.4.191/bin/intel64:/usr/usc/intel/composerxe-2011.4.191/mpirt/bin/intel64:$PATH<br /> <br /> For C-shell (in .cshrc)<br /> <br /> setenv PATH /usr/usc/intel/composerxe-2011.4.191/bin/intel64:/usr/usc/intel/composerxe-2011.4.191/mpirt/bin/intel64:$PATH<br /> <br /> When running elements of the platform over ssh, be sure to enable ssh forwarding (with the -X or -Y options).<br /> <br /> After modifying your login script above, log out and log back into the machine so the changes are reflected in your environment.<br /> <br /> == Edit Install_cfg.py with Installation Directory Paths ==<br /> <br /> You need to tell the platform where it's installed by editing a single python file called &quot;install_cfg.py&quot;. Edit the file bbp_2g/comps/install_cfg.py with your favorite text editor, and edit the lines:<br /> <br /> self.A_INSTALL_ROOT = &lt;bbp_2g directory&gt;<br /> self.A_GF_DIR = &lt;bbp_2g_gf directory&gt;<br /> <br /> as one example:<br /> <br /> self.A_INSTALL_ROOT = /home/scec-00/kumar/bbp_2g<br /> self.A_GF_DIR = /home/scec-00/kumar/bbp_2g_gf<br /> <br /> with the paths on your system to the bbp_2g directory (the source) and the bbp_2g_gf directory (the data) that you unzipped. For example, it could be /home/scottcal/broadband_platform/bbp_2g and /home/scottcal/broadband_platform/bbp_2g_gf.<br /> <br /> Here is some information about these two directories that may be useful as you decide how, and where, to install these two parts of the Broadband Platform on your computer disk system. The data files, and therefore the &lt;bbp_2g_gf directory&gt; are nearly 3GB, but they are static and will not be modified and will not grow in size during use of the platform. The source directory is small to begin. However, this directory will increase as the platform is used, since the results produced by the platform will be stored here.<br /> <br /> == Directory Structure ==<br /> The platform consists of two top-level directories, bbp_2g and bbp_2g_gf. bbp_2g contains the source code, executables, scripts, tests, input, working, and output directories. bbp_2g_gf contains the Green's Functions, input files for the validation events, and other required input files for the various code bases. Note that indata, logs, outdata, tmpdata, and xml are created when the platform is first run, so they will be missing when you first install the platform.<br /> <br /> bbp_2g has the following directories:<br /> *checksums: Contains checksums for bbp_2g_gf files<br /> *comps: The Python scripts to run the platform<br /> *docs: Documentation for the platform<br /> *etc: Miscellaneous utility scripts<br /> *examples: Contains example input files<br /> *indata: An internal directory, used to stage input files<br /> *logs: Contains logs from BBP runs<br /> *outdata: Contains output files from a run<br /> *ref_data: Contains reference files for BBP tests<br /> *start: Put input files for an interactive run here<br /> *src: Source code for BBP modules<br /> *tests: Contains unit and acceptance tests<br /> *tmpdata: An internal directory, used during a run<br /> *xml: Contains XML files which describe simulations and can be used as input<br /> <br /> bbp_2g_gf has the following directories:<br /> *compare: Contains observed seismograms for validation events<br /> *plot: Data files for GMT plots<br /> *sdsu, ucsb, urs: Contains Green's functions, velocity files, and other required inputs for the codebases.<br /> <br /> In general, you will be interacting with the start directory for input files, comps to run the platform, tests to test the platform, and outdata to examine data products.<br /> <br /> === Adding aliases ===<br /> <br /> You may find it helpful to add aliases, so you can quickly and easily move to different broadband directories with a single command. We recommend creating aliases for the home, start, and outdata directories.<br /> <br /> If you are using the Bash shell, you can create aliases by adding the following lines to ~/.bash_profile:<br /> <br /> alias bbp= 'cd &lt;path to bbp_2g directory&gt;'<br /> alias start='cd &lt;path to bbp_2g directory&gt;/start'<br /> alias outdata='cd &lt;path to bbp_2g directory&gt;/outdata'<br /> <br /> If you're using a C shell, edit your ~/.cshrc and add:<br /> <br /> alias bbp cd &lt;path to bbp_2g directory&gt;<br /> alias start cd &lt;path to bbp_2g directory&gt;/start<br /> alias outdata cd &lt;path to bbp_2g directory&gt;/outdata<br /> <br /> Log out and log back in. You'll notice that now you can type the alias command as a shortcut to change directories:<br /> <br /> $&gt; pwd<br /> /home/scec-00/scottcal<br /> $&gt; start<br /> $&gt; pwd<br /> /home/scec-00/scottcal/bband/bbp_2g/start<br /> <br /> This can be a useful way to navigate around the broadband platform directories.<br /> <br /> == Building the Platform ==<br /> Once you have checked out the code, you need to build it. By default, every executable is compiled using the compiler recommended by the code developer. However, if you have limited compiler options or are building the codes on an untested system, you may need to specify non-standard alternative compilers, as described below.<br /> <br /> Before you can build the platform, you need to make sure that the Intel compilers are in your path. This is done automatically on broadband.usc.edu, but on other systems you can check by typing:<br /> <br /> $&gt;which icc<br /> <br /> If you get the message &quot;no icc in ...&quot;, then you'll need to add the Intel compilers to your path. Once the Intel compilers are in your path, you can make the code by cd-ing to the bbp_2g/src directory and typing make:<br /> <br /> $&gt; cd src<br /> $&gt; make<br /> <br /> It takes a minute or two to build the code. You may encounter build warnings; these are fine. However, if you get any build errors, this is a problem and should be investigated.<br /> <br /> By default, every executable is compiled using the compiler recommended by the code developer. Depending on the system, some compilers may not be available to you. You can override the C and Fortran compilers used by editing<br /> <br /> src/makefile<br /> <br /> Uncomment USER_C and set FC and CC to the compilers you wish. For example:<br /> <br /> Before:<br /> <br /> #USER_C=1<br /> FC=f77<br /> CC=gcc<br /> <br /> After (an example, you may choose different compilers):<br /> <br /> USER_C=1<br /> FC=gfortran<br /> CC=gcc<br /> <br /> Note that not all compiler combinations have been thoroughly tested. You may encounter build errors with untested compiler combinations. If you encounter any errors while building the platform, consult the Troubleshooting section at the end of this user guide for know issues and their solutions.<br /> <br /> Once the platform has been successfully built, you can move on to running the tests to verify that all components are working correctly.<br /> <br /> == Advanced Users ==<br /> Alternatively, if you would like access to the latest version of the platform, to get frequent but less thoroughly tested improvements, you can check out the platform from SCEC's Subversion version control repository on source.usc.edu. Only advanced users should follow this approach. If you are unsure, you should download the code as outlined in [[#Downloading the Platform|Downloading the Platform]] and skip this section.<br /> <br /> You may need to request access from the SCEC system administrator, John Yu ([mailto:johnyu@usc.edu johnyu@usc.edu]). Make sure you have subversion in your path before beginning.<br /> <br /> Once you have access, you'll need to decide if you want a stable tagged version, or the latest version in the repository. For a stable version, open a terminal window on the system of your choice and type:<br /> <br /> $&gt; svn checkout https://source.usc.edu/svn/broadband/tags/&lt;stable version&gt; bbp_2g<br /> <br /> For the latest version, type:<br /> <br /> $&gt; svn checkout https://source.usc.edu/svn/broadband/trunk bbp_2g<br /> <br /> This will check out the project to your local machine. It contains the source code, tests, and some example files. You also need to obtain a copy of the Broadband Platform data files, containing the Green's tensors. They are too large to be stored in version control. You can obtain a copy from SCEC software distribution server. If you are working on SCEC development server, you might be able to create a symbolic link to data folder. Please contact [[#User_Support|User Support]] to get a location of the data folder on the SCEC development server. If you are not working on SCEC development server, or don't have an SCEC Linux login account, you can get a archive (.tgz) file of the Green's functions from the same download site you obtained this guide.<br /> <br /> If you know where a read-accessible installation of the green functions data directories you can create a link to that location. This can save disk space in some cases.<br /> <br /> ln -s /home/scec-00/scottcal/bband/bbp_2g_gf &lt;path to your gf directory&gt;<br /> <br /> Periodically you should check for updates to the code. To do so, go to your bbp_2g directory and type<br /> <br /> $&gt; svn update<br /> <br /> This will pull down any code updates that have been made in the repository. After you update, make the code again (detailed in [[#Building the Platform|Building the Platform]]) so that any code changes are captured in the executables.<br /> <br /> == Running the Broadband Platform ==<br /> We recommend users initiate all Broadband Platform runs from the &quot;start&quot; directory. The start directory is a collection point for input files for a particular simulation.<br /> <br /> Assuming the user is starting at BBP home directory, the user should move to the start directory and then run the Checksum, Unit and Acceptance tests to confirm the Broadband Platform software installation is operating as expected.<br /> <br /> $&gt; cd start<br /> <br /> == Running Checksum, Unit, and Acceptance Tests ==<br /> The broadband platform contains three kinds of tests. The checksum tests verify that the data files were copied correctly and you have all the files that are expected. Unit tests run each module using a set of input files, and compare the results against known outputs. They verify that each module has been built and is working correctly. Acceptance tests verify that the modules are working correctly together. They test the platform end-to-end using different combinations with known inputs and compare the results. All the possible module combinations for both user-defined and validation events are tested as checks against integration errors.<br /> <br /> Begin with the checksum tests. Once they past, run the unit tests and finally the acceptance tests.<br /> <br /> == Running Checksum Tests ==<br /> To run the checksum tests, change to the checksums directory and run md5sum_check.py.<br /> <br /> From the BBP home directory:<br /> <br /> $&gt; cd checksums<br /> $&gt; ./md5sum_check.py<br /> <br /> It takes about 5 minutes to compute the checksums. If a checksum disagrees, that means that the contents of the datafile were not what was expected. Try reinstalling the data files and try again. If you continue to get a checksum error, contact support.<br /> <br /> Once the checksums agree, move on to the unit tests.<br /> <br /> == Running Unit Tests ==<br /> To run the unit tests, change to the tests directory and run UnitTests.py.<br /> <br /> From the BBP home directory:<br /> <br /> $&gt; cd tests<br /> $&gt; ./UnitTests.py<br /> <br /> The unit tests take about 15 minutes to run. When they're complete, the console will either print &quot;OK&quot; or how many tests failed. If a test has failed, first check that you have built the executables.You can rerun just the specific test that failed (test_&lt;module&gt;.py). If the test is still failing, also verify that you have the ref_data directory, since it contains the input and reference files. If you're looking for more information about the failure, you can consult the Unit Tests log file in bbp_2g/logs/unit_test.log . If you can't determine the reason for the failure, contact support.<br /> <br /> Once the unit tests all pass, proceed to the acceptance tests. If there are any failure or errors while running the unit tests, consult the Troubleshooting section at the end of this user guide for know issues and their solutions.<br /> <br /> == Running Acceptance Tests ==<br /> Make sure the unit tests pass before moving on to the acceptance tests. To run the acceptance tests, change to the tests directory (if you're not there already) and run AcceptTests.py. <br /> The acceptance tests take a long time to run, around 20 hours<br /> <br /> From the BBP home directory:<br /> <br /> $&gt; cd tests<br /> $&gt; ./AcceptTests.py &amp;&gt; accept.out &amp;<br /> <br /> Since the tests take so long to run (twenty hours), you should run them as a background process, and redirect their output to a log file, as shown in the command above.<br /> <br /> You can check the progress by tailing the log file.<br /> <br /> $&gt; tail accept.out<br /> <br /> When all the acceptance tests are completed, the AcceptTests.py script will either print &quot;OK&quot; or how many tests failed. <br /> <br /> Acceptance test failures indicate that the modules are not integrated correctly. Like with the unit tests, verify that you have the ref_data directory. If a certain acceptance test fails, you can get more information by consulting the acceptance test logs in bbp_2g/logs/acceptance_tests_logs/&lt;test that failed&gt;.log . If you can't determine the reason for the failure, contact [[support]].<br /> <br /> Since the acceptance tests can take a long time to run, you may wish to resume where you left off. This feature is supported automatically. If you do not wish to resume, delete the resume file in ref_data/accept_inputs/resume.txt. If there are any failure or errors while running the acceptance tests, consult the Troubleshooting section at the end of this user guide for know issues and their solutions.<br /> <br /> == Types of Broadband Platform Simulations == <br /> <br /> The platform supports two kinds of simulations, validation events and user-defined events. Validation simulations are performed using a historical event, and are directly compared to observed seismograms using goodness-of-fit. User-defined events are run using a rupture description provided by the user which may not necessarily be a historical earthquake.<br /> <br /> When you run a simulation, the platform assigns an ID to it. This ID can be used to track the simulation and locate the output data products.<br /> <br /> To supply input files to the platform, put them in the start directory. Extensions are important - the platform recognizes station lists (.stl), SRF files (.srf), and simple source descriptions (.src). If there are multiple files of a type, the platform will prompt the user to select one.<br /> <br /> To perform a simulation, a user selects between different required and optional modules. Below we present a summary of the various modules.<br /> <br /> == Modules ==<br /> The broadband platform consists of a series of modules. There are two main types of modules, science modules and utility modules. Science modules are those for which the platform has multiple implementations, provided by different coding research groups. Utility modules only have 1 implementation. A schematic of the available modules and their flow relationships is shown below:<br /> <br /> == Science Modules ==<br /> All simulations must include a low-frequency, high-frequency, and site response science module. Simulations may include an optional rupture generation science module. Users may select between the following different implementations of each of these modules:<br /> <br /> Rupture generation:URS, UCSB<br /> <br /> Low-frequency:URS, UCSB<br /> <br /> High-frequency:URS, UCSB, SDSU<br /> <br /> Site response:URS, UCSB, SDSU<br /> <br /> == Utility Modules ==<br /> A spectral response utility module is automatically run after the site response module. Additionally, users may select an optional goodness-of-fit utility module to run at the conclusion of the simulation. In the case of a user-defined event, users select a historical event or previously run simulation to use as the comparison for goodness-of-fit.<br /> <br /> == Platform Directory ==<br /> <br /> A broadband platform distribution is organized in a specific directory structure that separates the input data sets, the python scripts, the simulation configuration files, log files, and output data files.<br /> <br /> When running Broadband Platform simulations, standard procedure is to place the simulation input files in the start directory and invoke the Broadband platform scripts from there.<br /> <br /> From the BBP home directory:<br /> <br /> $&gt; cd start<br /> $&gt; run_bbp_2G.py<br /> <br /> Simulation output results will be written into the bbp_home/output<br /> <br /> == Validation Simulations ==<br /> To run a validation simulation, go to the comps directory and run run_bbp_2G.py. The platform will ask you a series of questions. Answer 'y' to &quot;Do you want to perform a validation run?&quot;<br /> <br /> From the BBP home directory:<br /> <br /> $&gt; cd start<br /> $&gt; run_bbp_2G.py<br /> Welcome to the SCEC Broadband Platform.<br /> Please select the modules you want to run.<br /> Do you want to perform a validation run (y/n)? y<br /> Do you want to validate with:<br /> Northridge (1)<br /> Loma Prieta (2)<br /> Landers (3)<br /> ?<br /> ...<br /> <br /> No input files are required by the user. However, you may wish to run with a reduced station list to speed up the computations. You can put your own station list into the start directory (the format is described in [[#Station File List|section 5.3]]). Note that any stations which do not have observed seismograms will not be included in the automatically generated goodness-of-fit comparison.<br /> <br /> In addition to the low-frequency modules which compute seismograms using 1D Green's Tensors, validation events can also be run using precomputed 3D seismograms to supply the low-frequency.<br /> <br /> == User-defined Simulations ==<br /> To run a user-defined simulation, two input files are required, a rupture description and a station list. The rupture description can either be in SRF format or a simplified source description (the format is described in [[#Simple source description|section 5.1]]). To run a user-defined simulation, run run_bbp_2G.py.<br /> <br /> From the BBP home directory:<br /> <br /> $&gt; cd start<br /> $&gt; run_bbp_2G.py<br /> Welcome to the SCEC Broadband Platform.<br /> Please select the modules you want to run.<br /> Do you want to perform a validation run (y/n)? y<br /> Do you want to run a rupture generator (y/n)? <br /> ...<br /> <br /> You may then choose if you want to run a rupture generator. This is necessary if you're supplying a simple rupture description. If you're supplying an SRF file, you can skip this. Next you can select from different module implementations. Finally, you have the option to run goodness-of-fit against either observed seismograms or another simulation.<br /> <br /> ...<br /> Do you want to run goodness of fit (y/n)? y<br /> What reference files would you like to compare to? Enter a simulation ID or a scenario name: &lt;comparison&gt;<br /> Enter a label to use for the comparison seismograms: &lt;label&gt;<br /> <br /> The label will be used in GoF plots to distinguish one set of results from the other.<br /> <br /> The user-defined events must be within one of the regions supported by the platform - Southern California, Northern California, or the Mojave. The platform will automatically select a region based on the event hypocenter. If the event falls outside of these regions, you'll get an error.<br /> <br /> == Logging ==<br /> During the run, log files will be produced in logs/&lt;simulation ID&gt;/&lt;simulation ID&gt;.&lt;module name&gt;.log. If the platform fails, this is a good place to look to determine the error. Additionally, any fatal errors will be recorded in fatal_error.log.<br /> <br /> Metadata capturing all the executable calls is located in tmpdata/&lt;simulation ID&gt;/metadata.txt for careful tracing of exactly what was called. Both the log files and metadata can be useful if troubleshooting an issue.<br /> <br /> == Data Products ==<br /> The platform produces a variety of data products. &lt;nowiki&gt;All data products are located in outdata/&lt;simulation ID&gt;. &lt;/nowiki&gt;On most Linux systems, you can show images using display:<br /> <br /> $&gt; display &lt;PNG file&gt;<br /> <br /> Make sure you have X11 forwarding enabled.<br /> <br /> === Station map ===<br /> To help visualize the stations in relationship to the fault, the platform produces a PNG file displaying station locations with red circles and the fault plane with a black line, on an image of California. You can find this file in outdata/&lt;simulation ID&gt;/station_map.png.<br /> <br /> === Seismograms ===<br /> When running the platform, you have the option to output velocity and acceleration seismograms, for each station. Plots of these files can be found in outdata/&lt;simulation ID&gt;/&lt;simulation ID&gt;.&lt;station&gt;_&lt;velocity or acceleration&gt;_seis.png.<br /> <br /> The raw seismogram data is available in outdata/&lt;simulation ID&gt;/&lt;simulation ID&gt;.&lt;station&gt;.vel.bbp (velocity) and outdata/&lt;simulation ID&gt;.&lt;station&gt;.acc.bbp (acceleration). Its format is described in [[#BBP seismograms|section 5.4]].<br /> <br /> To compare seismogram data, you can run comps/plotit.py with two seismograms. It will plot them both for comparison. From the comps directory, run:<br /> <br /> $&gt; plotit.py &lt;path to seismogram 1&gt; &lt;path to seismogram 2&gt;<br /> <br /> === Response spectra ===<br /> The respect code, run at the end of each simulation, calculates the response spectra for each station. The raw respect data is located at<br /> <br /> From the BBP home directory:<br /> <br /> outdata/&lt;simulation ID&gt;/&lt;simulation ID&gt;.&lt;station&gt;.rsp<br /> <br /> in the format described in [[#Response spectra|section 5.5]].<br /> <br /> === Goodness-of-fit ===<br /> If you run goodness-of-fit, several additional data products are produced. The goodness-of-fit comparison is performed by comparing the response spectra of a set of calculated seismograms to seismograms from another simulation or observed seismograms. For each station involved in the comparison, a plot comparing the response spectra can be found at outdata/&lt;simulation ID&gt;/&lt;comparison label&gt;_&lt;simulation ID&gt;_&lt;station&gt;_rsp.png. A plot showing the seismograms on top and bottom can be found at outdata/&lt;comparison label&gt;_&lt;simulation ID&gt;_&lt;station&gt;_overlay.png. The goodness-of-fit plot can be found at gof-&lt;comparison label&gt;-&lt;simulation ID&gt;_r0-&lt;cutoff distance&gt;.png.<br /> <br /> Note that at least 3 stations must be run for goodness-of-fit to be valid. If fewer than 3 stations are run, no goodness of fit calculation will be performed.<br /> <br /> === Rupture files ===<br /> When a user-defined event is simulated, the user has the option to run a rupture generator. This generator produces an SRF file, found in outdata/&lt;simulation ID&gt;/*.srf. This file can be put in the start directory and used in future runs. Additionally, the platform produces a plot of the cumulative slip on the fault surface, outdata/&lt;simulation ID&gt;/&lt;SRF prefix&gt;.png.<br /> <br /> == Platform Modes ==<br /> The platform can be run in multiple modes. The default is interactive mode, in which the user is prompted to answer a series of questions. Once all the information has been gathered, the run begins.<br /> <br /> For a large number of runs, or if the user is repeating a specific run, this can be tedious. The platform provides two other ways to describe a run, with an option file or an XML description.<br /> <br /> An option file provides responses to all the questions that the platform poses. The format is described in [[#Option File|section 5.6]], but it's basically a text file, 1 entry per line, with support for comments. It can be fed to the platform using the -o option.<br /> <br /> The platform will also accept XML files containing a full description of a run. The schema for these files is given in [[#XML workflow description schema|section 5.7]]. These files are also produced by the platform after every simulation, and placed in xml/&lt;simulation ID&gt;.xml. So if you want to rerun a simulation, you can point the platform to the XML file from that simulation using the -x option. Note that a new simulation ID will be assigned to the run, so there is no risk of overwriting previous simulation results.<br /> <br /> == Available Options ==<br /> To get a list of the current available options, run run_bbp_2G.py with the -h flag.<br /> <br /> $&gt; run_bbp_2G.py -h<br /> Usage: run_bbp_2G.py [options]<br /> Options:<br /> -h, --help Show this help message and exit<br /> -x XML_FILE, --xml-file=XML_FILE Run using XML description of workflow<br /> -s SIM_ID, --simID=SIM_ID Force a simID<br /> -o OPTFILE, --option-file=OPTFILE File containing responses to interactive platform prompts<br /> -v, --version Broadband platform version<br /> -c, --compact Compact output results. Remove temporary files for simulations that complete successfully.<br /> -g, --generate-xml Generates the XML description but does not run the platform<br /> -l LOG_FILE, --log=LOG_FILE Store all output in a file<br /> <br /> == Cleanup ==<br /> After a while, you may find that your indata, tmpdata, outdata, and logs directories are getting cluttered with files from past runs. If you wish to delete these old files, you can use the clean_directories.sh script in the etc directory.<br /> <br /> From the BBP home directory:<br /> <br /> $&gt; cd etc<br /> $&gt; ./clean_directories &lt;days&gt;<br /> <br /> Any simulation ID directories in the indata, tmpdata, outdata, and logs directories which were last accessed &lt;days&gt; days or longer ago will be deleted. If you have a few directories you want to keep, either copy them somewhere else, or copy them to a directory name that's not all digits and they won't be deleted.<br /> <br /> == Examples ==<br /> Below are some examples that you can try using the sample files in the examples directory. Make sure all the tests pass before you try this. You should be in the comps directory when you start these examples:<br /> <br /> From the BBP home directory:<br /> <br /> $&gt; cd comps<br /> <br /> == Sample Validation Run ==<br /> You don't need to move any files for this. Notice that 3D seismograms are a low-frequency option, since you're running a validation event.<br /> <br /> From the BBP home directory:<br /> <br /> $&gt; cd start<br /> $&gt; run_bbp_2G.py <br /> Welcome to the SCEC Broadband Platform.<br /> Please select the modules you want to run.<br /> Do you want to perform a validation run (y/n)? y<br /> Do you want to validate with:<br /> Northridge (1)<br /> Loma Prieta (2)<br /> Landers (3)<br /> ?1<br /> Do you want to<br /> run all validation stations (1)<br /> select a station list (2)<br /> ?1<br /> Choose a source of low frequency seismograms:<br /> URS module (1)<br /> URS 3D seismograms (2)<br /> UCSB module (3)<br /> SDSU module (4)<br /> SDSU 3D seismograms (5)<br /> ?2<br /> Choose a high frequency module:<br /> URS (1)<br /> UCSB (2)<br /> SDSU (3)<br /> ?1<br /> Choose a site response module:<br /> URS (1)<br /> UCSB (2)<br /> SDSU (3)<br /> ?1<br /> Do you want to plot velocity seismograms (y/n)? y<br /> Do you want to plot acceleration seismograms (y/n)? y<br /> <br /> This simulation takes about 10 minutes. Once it's complete the platform will tell you:<br /> <br /> You can find results in &lt;path to bbp_2g install&gt;/outdata/&lt;simulation ID&gt; .<br /> <br /> In that directory you will find:<br /> <br /> *Velocity seismograms (&lt;simulation ID&gt;.&lt;station&gt;.bbp)<br /> *Acceleration seismograms (&lt;simulation ID&gt;.&lt;station&gt;.acc.bbp)<br /> *Plots of velocity seismograms (&lt;simulation ID&gt;.&lt;station&gt;_velocity_seis.png)<br /> *Plots of acceleration seismograms (&lt;simulation ID&gt;.&lt;station&gt;_acceleration_seis.png)<br /> *Response spectra files (&lt;simulation ID&gt;.&lt;station&gt;.rsp)<br /> *Plots comparing simulated and observed seismograms (Northridge_&lt;simulation ID&gt;_&lt;station&gt;_overlay.png)<br /> *Plots comparing simulated and observed response spectra (Northridge_&lt;simulation ID&gt;_&lt;station&gt;_rsp.png)<br /> *Overall goodness-of-fit plots (gof-Northridge-&lt;simulation ID&gt;_r0-25.png)<br /> <br /> == Sample Validation run, custom stations ==<br /> If the validation runs aren't performed with 3D low-frequency, it can take a long time, up to 10 minutes per station. Sometimes you might want to run with a reduced station list so the simulation will run faster.<br /> <br /> Copy the files in example/valid_custom_stations into the start directory. Take a look at the format of the station file:<br /> <br /> $&gt; more valid_test_stat.stl <br /> #Required: lon, lat, station name, distance to fault plane, Vs30<br /> #Optional: low freq corner, high freq corner<br /> #Unused: station information<br /> #lon lat stationdist Vs30 LF corner HF corner station information<br /> -118.6417 34.5640 cast 20.47 450 0.120 23.0 CSMIP peer.berkeley.edu/nga<br /> -118.4180 34.0628 lacn 22.82 278 0.140 23.0 CSMIP peer.berkeley.edu/nga<br /> -118.8811 34.2886 moor 24.16 405 0.160 23.0 CSMIP peer.berkeley.edu/nga<br /> <br /> Now, run the platform, using a station list:<br /> <br /> From the BBP Home directory<br /> <br /> $&gt; cd start<br /> $&gt; run_bbp_2G.py <br /> Welcome to the SCEC Broadband Platform.<br /> Please select the modules you want to run.<br /> Do you want to perform a validation run (y/n)? y<br /> Do you want to validate with:<br /> Northridge (1)<br /> Loma Prieta (2)<br /> Landers (3)<br /> ?1<br /> Do you want to<br /> run all validation stations (1)<br /> select a station list (2)<br /> ?2<br /> <br /> If you have multiple station list files in your start directory, you may see the following prompt asking you to select one. If you only have one, the platform will select it automatically.<br /> <br /> Found multiple BBP station list files in the start directory. Please select one:<br /> nr_one_stat.stl (1)<br /> valid_test_stat.stl (2)<br /> ?2<br /> Choose a source of low frequency seismograms:<br /> URS module (1)<br /> URS 3D seismograms (2)<br /> UCSB module (3)<br /> SDSU module (4)<br /> SDSU 3D seismograms (5)<br /> ?3<br /> Choose a high frequency module:<br /> URS (1)<br /> UCSB (2)<br /> SDSU (3)<br /> ?2<br /> Choose a site response module:<br /> URS (1)<br /> UCSB (2)<br /> SDSU (3)<br /> ?2<br /> Do you want to plot velocity seismograms (y/n)? y<br /> Do you want to plot acceleration seismograms (y/n)? y<br /> <br /> Again, when the run completes in about 15 minutes you can find results in the output directory. You'll notice far fewer files, as only 3 stations were run instead of 133. The goodness-of-fit plots won't look very good - more stations are really needed to get an accurate plot.<br /> <br /> == Sample User-defined run with source description ==<br /> Next let's try running a user-defined event. Copy examples/user_rup_gen/nr_one_stat.stl and examples/user_rup_gen/user_eq.src to the start directory. user_eq.src is a simple source description. Its format is outlined in [[#XML workflow description schema|section 5.1]]. Since this is a user-defined event, precomputed 3D seismograms aren't a valid option.<br /> <br /> $&gt; run_bbp_2G.py <br /> Welcome to the SCEC Broadband Platform.<br /> Please select the modules you want to run.<br /> Do you want to perform a validation run (y/n)? n<br /> Do you want to run a rupture generator (y/n)? y<br /> Rupture generators:<br /> URS (1)<br /> UCSB (2)<br /> ?1<br /> Using region: Southern California<br /> Choose a low frequency module:<br /> URS (1)<br /> UCSB (2)<br /> ?2<br /> Found multiple BBP station list files in the start directory. Please select one:<br /> nr_one_stat.stl (1)<br /> valid_test_stat.stl (2)<br /> ?1<br /> Choose a high frequency module:<br /> URS (1)<br /> UCSB (2)<br /> SDSU (3)<br /> ?2<br /> Choose a site response module:<br /> URS (1)<br /> UCSB (2)<br /> SDSU (3)<br /> ?1<br /> Do you want to plot velocity seismograms (y/n)? y<br /> Do you want to plot acceleration seismograms (y/n)? y<br /> Do you want to run goodness of fit (y/n)? n<br /> <br /> Since this run only includes one station, it will run in about 5 minutes. In the output directory you'll notice there are no goodness-of-fit or files, since we didn't run goodness-of-fit. However, there is also a map file (station_map.png), showing the fault plane and the stations, and a plot of the rupture slip (user_eq.png). The SRF generated by the rupture generator is in user_eq.srf; this file could be used in future runs. The filenames of the rupture slip plot and SRF are taken from the rupture description filename.<br /> <br /> == Sample User-defined run with SRF file and goodness-of-fit ==<br /> Finally, try a run with an SRF file and run goodness-of-fit on the results. Copy in examples/user_no_rup_gen/ucsb_modSRF_0.srf and examples/user_no_rup_gen/nr_three_stat.stl<br /> <br /> $&gt; run_bbp_2G.py <br /> Welcome to the SCEC Broadband Platform.<br /> Please select the modules you want to run.<br /> Do you want to perform a validation run (y/n)? n<br /> Do you want to run a rupture generator (y/n)? n<br /> Using region: Southern California<br /> Choose a low frequency module:<br /> URS (1)<br /> UCSB (2)<br /> ?1<br /> Found multiple BBP station list files in the start directory. Please select one:<br /> nr_one_stat.stl (1)<br /> valid_test_stat.stl (2)<br /> nr_three_stat.stl (3)<br /> ?3<br /> Choose a high frequency module:<br /> URS (1)<br /> UCSB (2)<br /> SDSU (3)<br /> ?3<br /> Choose a site response module:<br /> URS (1)<br /> UCSB (2)<br /> SDSU (3)<br /> ?1<br /> Do you want to plot velocity seismograms (y/n)? y<br /> Do you want to plot acceleration seismograms (y/n)? y<br /> Do you want to run goodness of fit (y/n)? y<br /> What reference files would you like to compare to? Enter a simulation ID or a scenario name: Northridge<br /> Enter a label to use for the comparison seismograms: nr<br /> <br /> The reference files can either be a scenario event or a simulation ID previously run. The label is just for the figures when comparisons are plotted.<br /> <br /> This run will take about 15 minutes, and the results can be found in the appropriate outdir. Again, the goodness of fit measures will look poor due to the few stations involved in the comparison. If you had fewer than 3 stations, no goodness-of-fit plots would be produced. However, response spectra comparison plots will still be generated.<br /> <br /> == File Formats ==<br /> This section offers descriptions of various file formats in the broadband platform.<br /> <br /> == Simple source description ==<br /> This is the format for the simple source description. It is not whitespace sensitive. The filename must end in .src for the platform to identify it as a source description.<br /> <br /> MAGNITUDE = &lt;magnitude&gt;<br /> FAULT_LENGTH = &lt;length of fault&gt;<br /> DLEN = &lt;DX, along length&gt;<br /> FAULT_WIDTH = &lt;down-dip fault width&gt;<br /> DWID = &lt;DY, along width&gt;<br /> DEPTH_TO_TOP = &lt;depth of fault below surface&gt;<br /> STRIKE = &lt;nowiki&gt;&lt;strike&gt;&lt;/nowiki&gt;<br /> RAKE = &lt;rake&gt;<br /> DIP = &lt;dip&gt;<br /> LAT_TOP_CENTER = &lt;latitude of top center point in fault plane&gt;<br /> LON_TOP_CENTER = &lt;longitude of top center point in fault plane&gt;<br /> HYPO_ALONG_STK = &lt;along strike location of hypocenter (0.0 = middle)&gt;<br /> HYPO_DOWN_DIP = &lt;down dip location of hypocenter (0.0 = top)&gt;<br /> DT = &lt;nowiki&gt;&lt;dt&gt;&lt;/nowiki&gt;<br /> SEED = &lt;random seed used in calculations&gt;<br /> CORNER_FREQ = &lt;corner frequency to use&gt;<br /> <br /> == SRF rupture description ==<br /> Details of the Standard Rupture Format (SRF) are given in more detail in the accompanying document. The general fault surface is represented by a distribution of point sources, and it can support one or more planes. The platform produces SRFs as output from rupture generators, but a user can also supply an SRF file as input for user-defined simulations. SRF filenames must end with the suffix .srf for the platform to correctly identify them.<br /> <br /> == Station File List ==<br /> The user may specify a list of stations, matching the following format:<br /> <br /> #optional<br /> %comment<br /> # lines<br /> &lt;nowiki&gt;&lt;lon&gt; &lt;lat&gt; &lt;stat name&gt; &lt;distance to fault trace&gt; &lt;Vs30&gt; &lt;LF corner&gt; &lt;HF corner&gt; &lt;stat info&gt;&lt;/nowiki&gt;<br /> ...<br /> <br /> The station list filename needs to end in .stl for the platform to recognize it as a station list.<br /> <br /> == BBP seismograms ==<br /> All intermediate and output seismograms are produced in a 4-column text format, whether velocity or acceleration.<br /> <br /> # optional<br /> % comment<br /> # lines<br /> &lt;nowiki&gt;&lt;timestamp&gt; &lt;North/South&gt; &lt;East/West&gt; &lt;Up/Down&gt;&lt;/nowiki&gt;<br /> ...<br /> <br /> Time is in seconds and motion is in cm/s (velocity) or cm/s/s (acceleration) unless otherwise specified in the header. Velocity filenames end in .vel.bbp; accelerations in .acc.bbp.<br /> <br /> == Response spectra ==<br /> The response spectra file is in 4-column text format.<br /> <br /> # optional<br /> % comment<br /> # lines<br /> &lt;nowiki&gt;&lt;period (sec)&gt; &lt;North/South&gt; &lt;East/West&gt; &lt;Up/Down&gt;&lt;/nowiki&gt;<br /> ...<br /> <br /> The platform samples response spectra at 112 periods, 0.01-20 sec and outputs pseudo spectral acceleration in units of g.<br /> <br /> == Option File ==<br /> Option files contain responses to the prompts in the platform. You can use them with the -o option to run_bbp_2G.py. The responses have to match the prompts exactly. For example, if you craft an option file assuming there is only one station list in the start directory (and therefore the user isn't prompted to select one) but then it is run with multiple station lists in the start directory, this will cause the run to abort. Option files are recommended to perform a series of runs with different inputs or different modules. If you have a run you perform regularly, it's better practice to run the platform with the -g option and the option file to produce an XML description, which are more complete descriptions of the workflow.<br /> <br /> #optional comments<br /> %using either symbol<br /> n #comments<br /> y % can go<br /> 1 # here<br /> ...<br /> <br /> Use with:<br /> <br /> $&gt; run_bbp_2G.py -o &lt;option file&gt;<br /> <br /> == XML workflow description schema ==<br /> Each time the platform is invoked, an XML file is produced describing the workflow, obeying the following schema:<br /> <br /> &lt;nowiki&gt;&lt;xs:schema xmlns:xs=&quot;http://www.w3.org/2001/XMLSchema&quot;&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:element name= &quot;BBP_Run_Specification&quot; minOccurs= &quot;1&quot; maxOccurs= &quot;1&quot;&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:attribute name=&quot;version&quot; type = &quot;xs:string&quot; use = &quot;required&quot; /&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:complexType&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:sequence&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:element name= &quot;Validation_Run&quot; minOccurs= &quot;0&quot; maxOccurs = &quot;1&quot;&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:attribute name= &quot;event&quot; type= &quot;xs:string&quot; use= &quot;required&quot; /&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:attribute name= &quot;input_station_file&quot; type = &quot;xs:string&quot; /&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:attribute name= &quot;subset&quot; type = &quot;xs:boolean&quot; use = &quot;required&quot; /&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;/xs:element&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:element name= &quot;BBP_Modules&quot;&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:complexType&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:sequence&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:element name = &quot;BBP_Module&quot; maxOccurs = &quot;unbounded&quot; &gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:complexType&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:sequence&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:element name= &quot;name&quot; type=&quot;xs:string&quot; /&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:element name= &quot;staged_files&quot; &gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:complexType&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:sequence&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:element name=&quot;file&quot; type=&quot;xs:string&quot; maxOccurs= &quot;unbounded&quot;/&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;/xs:sequence&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;/xs:complexType&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;/xs:element&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:element name= &quot;arguments&quot; &gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:complexType&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:sequence&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:element name=&quot;argument&quot; type=&quot;xs:string&quot; maxOccurs=&quot;unbounded&quot;&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:attribute name= &quot;type&quot; type= &quot;xs:string&quot; user= &quot;required&quot; /&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;/xs:element&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;/xs:sequence&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;/xs:complexType&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;/xs:element&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;/xs:sequence&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;/xs:complexType&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;/xs:element&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;/xs:sequence&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;/xs:complexType&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;/xs:element&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;/xs:sequence&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;/xs:complexType&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;/xs:element&gt;&lt;/nowiki&gt;<br /> <br /> These files are difficult to construct by hand, but can be generated using the -g flag when running run_bbp_2G.py.<br /> <br /> == User Support ==<br /> If you run into bugs with the platform, you can open a trouble ticket at the [http://northridge.usc.edu/trac/broadband Broadband Trac site].<br /> <br /> Check to see if there has already been a ticket opened for the bug. If you are unable to get the platform to run, you can get direct user support by emailing [mailto:software@intensity.usc.edu software@intensity.usc.edu].<br /> <br /> == Appendix A: Possible Module Permutations ==<br /> === Validation Events ===<br /> <br /> {| class=&quot;wikitable&quot; | border=&quot;1&quot;<br /> | Permutation #<br /> | Low-frequency module<br /> | High-frequency module<br /> | Site response<br /> <br /> |-<br /> | &lt;center&gt;1&lt;/center&gt;<br /> | &lt;center&gt;URS 1D&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;2&lt;/center&gt;<br /> | &lt;center&gt;URS 1D&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;3&lt;/center&gt;<br /> | &lt;center&gt;URS 1D&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;4&lt;/center&gt;<br /> | &lt;center&gt;URS 1D&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;5&lt;/center&gt;<br /> | &lt;center&gt;URS 1D&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;6&lt;/center&gt;<br /> | &lt;center&gt;URS 1D&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;7&lt;/center&gt;<br /> | &lt;center&gt;URS 1D&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;8&lt;/center&gt;<br /> | &lt;center&gt;URS 1D&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;9&lt;/center&gt;<br /> | &lt;center&gt;URS 1D&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;10&lt;/center&gt;<br /> | &lt;center&gt;URS 3D precomputed&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;11&lt;/center&gt;<br /> | &lt;center&gt;URS 3D precomputed&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;12&lt;/center&gt;<br /> | &lt;center&gt;URS 3D precomputed&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;13&lt;/center&gt;<br /> | &lt;center&gt;URS 3D precomputed&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;14&lt;/center&gt;<br /> | &lt;center&gt;URS 3D precomputed&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;15&lt;/center&gt;<br /> | &lt;center&gt;URS 3D precomputed&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;16&lt;/center&gt;<br /> | &lt;center&gt;URS 3D precomputed&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;17&lt;/center&gt;<br /> | &lt;center&gt;URS 3D precomputed&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;18&lt;/center&gt;<br /> | &lt;center&gt;URS 3D precomputed&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;19&lt;/center&gt;<br /> | &lt;center&gt;UCSB 1D&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;20&lt;/center&gt;<br /> | &lt;center&gt;UCSB 1D&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;21&lt;/center&gt;<br /> | &lt;center&gt;UCSB 1D&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;22&lt;/center&gt;<br /> | &lt;center&gt;UCSB 1D&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;23&lt;/center&gt;<br /> | &lt;center&gt;UCSB 1D&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;24&lt;/center&gt;<br /> | &lt;center&gt;UCSB 1D&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;25&lt;/center&gt;<br /> | &lt;center&gt;UCSB 1D&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;26&lt;/center&gt;<br /> | &lt;center&gt;UCSB 1D&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;27&lt;/center&gt;<br /> | &lt;center&gt;UCSB 1D&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;28&lt;/center&gt;<br /> | &lt;center&gt;SDSU 1D&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;29&lt;/center&gt;<br /> | &lt;center&gt;SDSU 1D&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;30&lt;/center&gt;<br /> | &lt;center&gt;SDSU 1D&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;31&lt;/center&gt;<br /> | &lt;center&gt;SDSU 1D&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;32&lt;/center&gt;<br /> | &lt;center&gt;SDSU 1D&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;33&lt;/center&gt;<br /> | &lt;center&gt;SDSU 1D&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;34&lt;/center&gt;<br /> | &lt;center&gt;SDSU 1D&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;35&lt;/center&gt;<br /> | &lt;center&gt;SDSU 1D&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;36&lt;/center&gt;<br /> | &lt;center&gt;SDSU 1D&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;37&lt;/center&gt;<br /> | &lt;center&gt;SDSU 3D precomputed&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;38&lt;/center&gt;<br /> | &lt;center&gt;SDSU 3D precomputed&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;39&lt;/center&gt;<br /> | &lt;center&gt;SDSU 3D precomputed&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;40&lt;/center&gt;<br /> | &lt;center&gt;SDSU 3D precomputed&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;41&lt;/center&gt;<br /> | &lt;center&gt;SDSU 3D precomputed&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;42&lt;/center&gt;<br /> | &lt;center&gt;SDSU 3D precomputed&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;43&lt;/center&gt;<br /> | &lt;center&gt;SDSU 3D precomputed&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;44&lt;/center&gt;<br /> | &lt;center&gt;SDSU 3D precomputed&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;45&lt;/center&gt;<br /> | &lt;center&gt;SDSU 3D precomputed&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> |}<br /> <br /> ===User-Defined Events===<br /> <br /> {| class=&quot;wikitable&quot; | border=&quot;1&quot;<br /> | Permutation #<br /> | Rupture generator<br /> | Low-frequency<br /> | High-frequency<br /> | Site response<br /> <br /> |-<br /> | &lt;center&gt;1&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;2&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;3&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;4&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;5&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;6&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;7&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;8&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;9&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;10&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;11&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;12&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;13&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;14&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;15&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;16&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;17&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;18&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;19&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;20&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;21&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;22&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;23&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;24&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;25&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;26&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;27&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;28&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;29&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;30&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;31&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;32&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;33&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;34&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;35&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;36&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;37&lt;/center&gt;<br /> | &lt;center&gt;User-supplied SRF&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;38&lt;/center&gt;<br /> | &lt;center&gt;User-supplied SRF&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;39&lt;/center&gt;<br /> | &lt;center&gt;User-supplied SRF&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;40&lt;/center&gt;<br /> | &lt;center&gt;User-supplied SRF&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;41&lt;/center&gt;<br /> | &lt;center&gt;User-supplied SRF&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;42&lt;/center&gt;<br /> | &lt;center&gt;User-supplied SRF&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;43&lt;/center&gt;<br /> | &lt;center&gt;User-supplied SRF&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;44&lt;/center&gt;<br /> | &lt;center&gt;User-supplied SRF&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;45&lt;/center&gt;<br /> | &lt;center&gt;User-supplied SRF&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;46&lt;/center&gt;<br /> | &lt;center&gt;User-supplied SRF&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;47&lt;/center&gt;<br /> | &lt;center&gt;User-supplied SRF&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;48&lt;/center&gt;<br /> | &lt;center&gt;User-supplied SRF&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;49&lt;/center&gt;<br /> | &lt;center&gt;User-supplied SRF&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;50&lt;/center&gt;<br /> | &lt;center&gt;User-supplied SRF&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;51&lt;/center&gt;<br /> | &lt;center&gt;User-supplied SRF&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;52&lt;/center&gt;<br /> | &lt;center&gt;User-supplied SRF&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;53&lt;/center&gt;<br /> | &lt;center&gt;User-supplied SRF&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;54&lt;/center&gt;<br /> | &lt;center&gt;User-supplied SRF&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> |}<br /> <br /> == Appendix B: Troubleshooting ==<br /> If you experience trouble building the platform or successfully running test and simulations, try the following solutions.<br /> <br /> === Build Errors ===<br /> <br /> The instruction for installing Broadband Platform are listed in Section 1: &quot;Installing the Second-Generation Broadband Platform&quot; of the User guide. If after following all steps listed in this section of the user guide the build fails, check if the failure is listed in this section and try the solution to fix the issue you are facing.<br /> <br /> ==== 64-bit Intel Compiler Issue ====<br /> If you try to compile with:<br /> &lt;pre&gt;<br /> % cd bbp_2g/src<br /> % make<br /> &lt;/pre&gt; <br /> <br /> and you get:<br /> &lt;pre&gt;<br /> ... <br /> make[2]: Entering directory `.../bbp_2g/src/ucsb/getInFile'<br /> icc -o getfaultGlobal getfaultGlobal.c<br /> ld: cannot find -lgcc_s_32<br /> make[2]: *** [getfaultGlobal] Error 1<br /> make[2]: Leaving directory `.../bbp_2g/src/ucsb/getInFile'<br /> make[1]: *** [all] Error 2<br /> make[1]: Leaving directory `.../bbp_2g/src/ucsb'<br /> make: *** [all] Error 2<br /> &lt;/pre&gt;<br /> <br /> '''Cause:''' The Broadband Platform requires Intel 64-bit compilers to build successfully. In this case the 32-bit Intel compilers are being invoked as they are being picked up from the PATH environment variable. The error is due to a missing GNU-GCC 32-bit compatibility pack that has not been installed on your system. This is not required when 64-bit Intel compilers are used.<br /> <br /> '''Solution:''' Ensure that the path Intel 64-bit compilers are listed in you PATH variable and being picked up by running 'which icc' and 'which ifort'. If you are trying to build the platform on SCEC development servers like Intensity, verify your path variable has:<br /> &lt;pre&gt;<br /> PATH=...:/usr/usc/intel/composerxe-2011.4.191/mpirt/bin/intel64:/usr/usc/intel/composerxe-2011.4.191/bin/intel64<br /> &lt;/pre&gt;<br /> <br /> ==== 32-bit Platform Issue ====<br /> <br /> On trying to build the platform, the build fails with the following message:<br /> &lt;pre&gt;<br /> $ make all<br /> cd urs; make -f makefile FC=gfortran CC=icc USER_C=1;<br /> make[1]: Entering directory `.../bbp_2g/src/urs'<br /> mkdir -p bin;<br /> cd getpar/src; make -f Makefile CC=icc FC=gfortran USER_C=1;<br /> make[2]: Entering directory `.../bbp_2g/src/urs/getpar/src'<br /> icc -O3 -DENVIRONMENT -c -o defpar.o defpar.c<br /> icc -O3 -DENVIRONMENT -c -o getpar.o getpar.c<br /> icc -O3 -DENVIRONMENT -c -o getarg.o getarg.c<br /> getarg.c(112): warning #303: explicit type is missing (&quot;int&quot; assumed)<br /> register i;<br /> ^ <br /> icc -O3 -DENVIRONMENT -c -o getlocation.o getlocation.c<br /> getlocation.c(9): warning #147: declaration is incompatible with &quot;__ssize_t={int} getline(char **restrict, size_t={unsigned int} *restrict, FILE *restrict)&quot; (declared at line 671 of &quot;/usr/include/stdio.h&quot;)<br /> static int getline(FILE *fd, char *line)<br /> <br /> ...<br /> ...<br /> ...<br /> <br /> make[2]: Entering directory `.../bbp_2g/src/sdsu/srcV1.4'<br /> icc -w -Wall -c ray3DJHfor.c<br /> gfortran module_bbtoolbox.f90 module_interface.f90 main_bbtoolbox.f90 coda.f90 composition.f90 convolution.f90 fourier.f90 error.f90 geometry.f90 interpolation.f90 io.f90 random.f90 scattering.f90 source.f90 ray3DJHfor.o -o BBtoolbox.exe<br /> ray3DJHfor.o: In function `raytracing_':<br /> ray3DJHfor.c:(.text+0x8cf): undefined reference to `__libm_sse2_log'<br /> ray3DJHfor.c:(.text+0x96b): undefined reference to `__libm_sse2_asin'<br /> ray3DJHfor.c:(.text+0x9cd): undefined reference to `__libm_sse2_asin'<br /> ray3DJHfor.c:(.text+0xa00): undefined reference to `__libm_sse2_tan'<br /> ray3DJHfor.c:(.text+0xa3d): undefined reference to `__libm_sse2_tan'<br /> ray3DJHfor.c:(.text+0xa52): undefined reference to `__libm_sse2_log'<br /> collect2: ld returned 1 exit status<br /> make[2]: *** [BBtoolbox.exe] Error 1<br /> make[2]: Leaving directory `.../bbp_2g/src/sdsu/srcV1.4'<br /> make[1]: *** [all] Error 2<br /> make[1]: Leaving directory `.../bbp_2g/src/sdsu'<br /> make: *** [all] Error 2<br /> &lt;/pre&gt;<br /> <br /> '''Cause:''' In this case the user tried to build Broadband on a 32-bit platform. Broadband code was designed to be run on 64-bit platform. Any attempt to build Broadband on a 32-bit platform will result in numerous warnings and the build will fail with error messages similar to ones listed above.<br /> <br /> '''Solution:''' Try building Broadband on a 64-bit platform will the all the dependencies listed in Section 1.1: &quot;System Dependencies&quot; and Section 1.2: &quot;Software Dependencies&quot;<br /> <br /> === Unit/Acceptance Test Failures and Errors ===<br /> <br /> Unit and Acceptance tests are provided to verify the Broadband platform and it's supporting modules built by the user are functioning as designed. Under certain circumstances, some of these test might fail. While some of these failure might indicate serious problems that will have to be addressed before the platform can used, it is acceptable to ignore some of the failures. This section lists some failures and their solutions.<br /> <br /> ==== ERROR: test_syn1d (test_syn1d.Test_syn1D) ====<br /> The Unit test for Syn1d module fails with the following message:<br /> &lt;pre&gt;<br /> ERROR: test_syn1d (test_syn1d.Test_syn1D)<br /> ----------------------------------------------------------------------<br /> Traceback (most recent call last):<br /> File &quot;.../bbp_2g/tests/test_syn1d.py&quot;, line 62, in test_syn1d<br /> synObj.run()<br /> File &quot;.../bbp_2g/comps/syn1D.py&quot;, line 236, in run<br /> shutil.copy2(a_tmpfile, expected_file)<br /> File &quot;/usr/lib/python2.6/shutil.py&quot;, line 99, in copy2<br /> copyfile(src, dst)<br /> File &quot;/usr/lib/python2.6/shutil.py&quot;, line 52, in copyfile<br /> fsrc = open(src, 'rb')<br /> IOError: [Errno 2] No such file or directory: '.../bbp_2g/tmpdata/3310632/s01.3comp'<br /> &lt;/pre&gt;<br /> <br /> '''Cause:''' Syn1d module requires the Green's Function file to run and the path to this file might be incorrect in 'bbp_2g_gf/ucsb/GreenBank/Northridge/GreenBank.inf' file.<br /> <br /> '''Solution:''' This issue can be fixed by correcting the paths listed in the GreenBank.inf files in the Green's Function directory. Here are step by step instructions to fix this issue:<br /> <br /> 1. Locate your Greens Functions directory: 'bbp_2g_gf'<br /> 2. Navigate to bbp_2g_gf/ucsb/GreenBank/Northridge folder.<br /> 3. Open Green_Bank.inf files with a text editor.<br /> 4. Locate the text &quot;The name of file to store Green Bank&quot;<br /> 5. Note the location of the Green Bank file under the line found in step 4, similar to &quot;/home/scec-00/scottcal/bband/bbp_2g_gf/ucsb/GreenBank/Northridge/Green_1d.soil&quot;.<br /> 6. Replace the path found in Step 5 with just the file name, in the case of Northridge it is &quot;Green_1d.soil&quot;<br /> 7. Save and close the Green_Bank.inf.<br /> 8. Navigate to bbp_2g_gf/ucsb/GreenBank/LomaPrieta folder and repeat steps 3-7. The name of the Green Bank file for LomaPrieta is &quot;Green_1d.LoPr&quot;.<br /> 9. Navigate to bbp_2g_gf/ucsb/GreenBank/Landers folder and repeat steps 3-7. The name of the Green Bank file for Landers is &quot;Green1D.Landers&quot;<br /> <br /> ==== ERROR: test_gensrf (test_genslip.Test_Genslip) ====<br /> The Unit test for Genslip module fails with the following message:<br /> &lt;pre&gt;<br /> ======================================================================<br /> ERROR: test_gensrf (test_genslip.Test_Genslip)<br /> ----------------------------------------------------------------------<br /> Traceback (most recent call last):<br /> File &quot;.../bbp_2g/tests/test_genslip.py&quot;, line 51, in test_gensrf<br /> gen.run()<br /> File &quot;.../bbp_2g/comps/genslip.py&quot;, line 153, in run<br /> ps.run()<br /> File &quot;.../bbp_2g/comps/plot_srf.py&quot;, line 52, in run<br /> shutil.copy2(&quot;%s/%s.ps.png&quot; % (a_tmpdir, self.r_srffile[0:self.r_srffile.find(&quot;.srf&quot;)]), &quot;%s/%s.png&quot; % (a_outdir, self.r_srffile[0:self.r_srffile.find(&quot;.srf&quot;)]))<br /> File &quot;/usr/lib/python2.6/shutil.py&quot;, line 99, in copy2<br /> copyfile(src, dst)<br /> File &quot;/usr/lib/python2.6/shutil.py&quot;, line 52, in copyfile<br /> fsrc = open(src, 'rb')<br /> IOError: [Errno 2] No such file or directory: '.../bbp_2g/tmpdata/3309008/3309008_test_eq.ps.png'<br /> &lt;/pre&gt;<br /> <br /> '''Cause:''' The Genslip module calls the Plot_SRF module to the plot the SRF file. Plot_SRF uses C-shell code to locate and use GMT package to plot the SRF file. This shell code might fail on some flavors of Linux with a message like &quot;Newline in variable name&quot; in the Plot_SRF log file.<br /> <br /> '''Solution:''' This issue can be fixed by editing the plot_SRF.csh file. Here are step by step instructions to fix this issue:<br /> <br /> 1. Locate shell script file: bbp_2g/src/plot/plot_SRF.csh<br /> 2. Open the file in your preferred text editor<br /> 3. Locate the line 'set FIND_GMT = $?'<br /> 4. Replace the line found in step 3 with 'set FIND_GMT = $status'<br /> 5. Locate the section of code that starts with the statement &quot;# FIND MAX. SLIP&quot;<br /> 6. Replace the following line in section found in step 5:<br /> &lt;pre&gt;<br /> set SMAX = `$XYZCODE calc_xy=$CALC_XY type=&quot;${TYPE}&quot; nseg=-1 &lt; $SLIPFILE.srf | \<br /> gawk -v m=$SMAX '{if($3&gt;m)m=$3;}END{printf &quot;%.0f\n&quot;,m;}'`<br /> <br /> with (collapse the statement to a single line by removing '\' at the end of first part of the statement):<br /> <br /> set SMAX = `$XYZCODE calc_xy=$CALC_XY type=&quot;${TYPE}&quot; nseg=-1 &lt; $SLIPFILE.srf | gawk -v m=$SMAX '{if($3&gt;m)m=$3;}END{printf &quot;%.0f\n&quot;,m;}'`<br /> &lt;/pre&gt;<br /> 7. Save the file and exit<br /> <br /> ==== ERROR: test_ucgen (test_ucrmg.Test_UCrmg) ====<br /> The Unit test for Ucrmg module fails with the following message:<br /> &lt;pre&gt;<br /> ======================================================================<br /> ERROR: test_ucgen (test_ucrmg.Test_UCrmg)<br /> ----------------------------------------------------------------------<br /> Traceback (most recent call last):<br /> File &quot;.../bbp_2g/tests/test_ucrmg.py&quot;, line 59, in test_ucgen<br /> ucObj.run()<br /> File &quot;.../bbp_2g/comps/ucrmg.py&quot;, line 161, in run<br /> ps.run()<br /> File &quot;.../bbp_2g/comps/plot_srf.py&quot;, line 52, in run<br /> shutil.copy2(&quot;%s/%s.ps.png&quot; % (a_tmpdir, self.r_srffile[0:self.r_srffile.find(&quot;.srf&quot;)]), &quot;%s/%s.png&quot; % (a_outdir, self.r_srffile[0:self.r_srffile.find(&quot;.srf&quot;)]))<br /> File &quot;/usr/lib/python2.6/shutil.py&quot;, line 99, in copy2<br /> copyfile(src, dst)<br /> File &quot;/usr/lib/python2.6/shutil.py&quot;, line 52, in copyfile<br /> fsrc = open(src, 'rb')<br /> IOError: [Errno 2] No such file or directory: '.../bbp_2g/tmpdata/3309831/test_ucsb.ps.png'<br /> &lt;/pre&gt;<br /> <br /> '''Cause:''' The Ucrmg module calls the Plot_SRF module to the plot the SRF file. Plot_SRF uses C-shell code to locate and use GMT package to plot the SRF file. This shell code might fail on some flavors of Linux with a message like &quot;Newline in variable name&quot; in the Plot_SRF log file.<br /> <br /> '''Solution:''' This issue can be fixed by editing the plot_SRF.csh file. The steps to fix this issue are listed under the solution for &quot;ERROR: test_gensrf (test_genslip.Test_Genslip)&quot; above.<br /> <br /> ==== FAIL: test_site_amp (test_uc_site.Test_UC_Site) ====<br /> <br /> The unit test for UC-Site module might fail with the following message:<br /> &lt;pre&gt;<br /> ======================================================================<br /> FAIL: test_site_amp (test_uc_site.Test_UC_Site)<br /> ----------------------------------------------------------------------<br /> Traceback (most recent call last):<br /> File &quot;.../bbp_2g/tests/test_uc_site.py&quot;, line 92, in test_site_amp<br /> self.failIf(cmp_bbp.cmp_bbp(a_ref_file_no_header, test_file_no_header, tolerance=0.035)!=0,errmsg)<br /> AssertionError: Output file .../bbp_2g/tmpdata/3310633/s04.3comp does not match reference file .../bbp_2g/ref_data/ucsb/s04.site.3comp<br /> &lt;/pre&gt;<br /> <br /> '''Cause:''' The synthetic seismogram generated by the UC-Site module on the user system differs from the reference result included in the Broadband release.<br /> <br /> '''Solution:''' The stochastic nature of the high frequency simulations is considered, and a constant random seed as input for our tests. This is the same constant random seed used to generate the reference results included in the release. This ensures that the time-series generated with unit tests agree with reference results. However, the high frequency codes are more sensitive to changes in compilers and machines due to the algorithm, so small differences that cause the test to fail are generally acceptable. The user is however encouraged to plot the two time-series and visually inspect them to verify they look similar. We are trying to come up with a better comparison for these tests.<br /> <br /> == Appendix C: Technical Notes ==<br /> <br /> === Running Individual Acceptance Tests ===<br /> <br /> The acceptance test script ./tests/AcceptTest.py attempts to run all of the defined tests when executed. However, sometimes it is useful to run an acceptance test in isolation for troubleshooting purposes:<br /> <br /> * Identify the test you want to run. Eg: user-URS-UCSB-SDSU-SDSU<br /> * Move to the ./comps directory and execute that test's XML workflow with run_bbp_2G.py. Using the above example:<br /> &lt;pre&gt;<br /> $ ./run_bbp_2G.py -x ../ref_data/accept_inputs/user-URS-UCSB-SDSU-SDSU.xml<br /> &lt;/pre&gt;<br /> <br /> Since you are running the test outside of AcceptTest.py, you will not see a PASS/FAIL message once the simulation completes. However, you can review the contents of the ./outdata/&lt;SIMID&gt; directory to verify that the correct seismograms and response spectra tables were produced.<br /> <br /> === Manaully Setting Random Number Generator Seed Values ===<br /> <br /> Several of the platform codebases employ random number generators to produce SRFs and seismograms. These random number generators are generally seeded with an initial value (typically an integer) which are hard-coded in the platform. Advanced users may desire to change these seed values.<br /> <br /> Changing the seeds for seismogram synthesis varies depending on which codebase you want to use:<br /> <br /> * URS: Edit ./comps/hfsims_cfg.py, Line 43 &quot;self.RAND_NUM&quot;<br /> * UCSB: Edit ./src/ucsb/Syn1DSCEC/syn1D_LAH.f, Line 183 &quot;iseed&quot;, and recompile with &quot;make&quot;<br /> * SDSU:<br /> ** User event: Edit ./bbp_2g_gf/sdsu/scattering_generic.dat (seed values annotated in file)<br /> ** Validation event: Edit ./bbp_2g_gf/sdsu/&lt;event&gt;/scattering.dat</div> Patrices https://strike.scec.org/scecwiki/index.php?title=Broadband_User_Guide_v11.2.3&diff=5052 Broadband User Guide v11.2.3 2012-05-08T21:36:18Z <p>Patrices: </p> <hr /> <div>'''Version 11.2.3.'''<br /> <br /> If you find errors in this document or sections to be unclear, please either fix them yourself or contact software@scec.org.<br /> <br /> == Installing the Second-Generation Broadband Platform ==<br /> Installing the Broadband Platform involves obtaining a copy of the code and building the required executables. You can either download the platform from the Broadband web site ([http://www.scec.org/research/broadband http://www.scec.org/research/broadband]) or check the code out of SCEC's Subversion repository. Most users should download the platform.<br /> <br /> == System Dependencies ==<br /> The current version of the Broadband Platform is designed to run on standard 64-bit Linux machines. Testing has been performed on SCEC's development servers running Fedora Core 10 (kernel version 2.6.27.41-170.2.117.fc10.x86_64). In this guide we outline how to install the platform into your own account on a Linux computer using the simplest approach.<br /> <br /> == Software Dependencies ==<br /> The Broadband Platform has certain software dependencies.<br /> <br /> Required:<br /> <br /> *Python v2.7 with<br /> **PyGTK<br /> **Matplotlib<br /> **Numpy<br /> **Pyproj<br /> <br /> *Intel compilers (64-bit) v12.0.4<br /> *GNU compilers (gcc, gfortran) v4.5.1<br /> *GNU Fortran 77 v3.4.6<br /> *GMT (Generic Mapping Toolkit)<br /> *ImageMagick<br /> <br /> == Setting Up Your Account ==<br /> For simplicity of installation, we recommend users use a bash shell for the Broadband Platform account. It is possible to get the platform running using other shell's, but we will focus on a bash shell installation. The user environment is a common source of problems since certain environment variables must be defined for the platform to work correctly.<br /> <br /> To check your account, make sure you can run basic commands like ''ls'' and ''cd'' before proceeding.<br /> <br /> == Downloading the Platform ==<br /> &lt;nowiki&gt;Download 4 files from the Broadband website, the code (bbp_dist_&lt;version&gt;.tgz), the data (bbp_data_&lt;version&gt;.tgz), and their checksum files (bbp_dist_&lt;version&gt;.tgz.md5 and bbp_data_&lt;version&gt;.tgz.md5). &lt;/nowiki&gt;The code file is about 100 MB, the data file about 3 GB. After you've downloaded the files to your local Linux system, the next step is to calculate the checksums yourself and compare them to the checksums you downloaded.<br /> <br /> First, verify that the ''md5sum'' command is in your path:<br /> <br /> $&gt; which md5sum<br /> <br /> You should get something like /usr/bin/md5sum. If you see the message 'no md5sum in...', contact your Linux system administrator and ask to have md5sum added to your path.<br /> <br /> Once you can run the ''md5sum'' command, run:<br /> <br /> $&gt; md5sum -c bbp_dist_&lt;version&gt;.tgz.md5<br /> $&gt; md5sum -c bbp_data_&lt;version&gt;.tgz.md5<br /> <br /> You should get the messages<br /> bbp_dist_&lt;version&gt;.tgz.md5: OK<br /> bbp_data_&lt;version&gt;.tgz.md5: OK<br /> <br /> If you get FAILED instead, re-download the tgz files and try again. When it passes, that means the files were downloaded without error.<br /> <br /> Once both files have passed the checksum test, untar the files.<br /> <br /> $&gt; tar xzvf bbp_dist_&lt;version&gt;.tgz file<br /> $&gt; tar xzvf bbp_data_&lt;version&gt;.tgz file<br /> <br /> If multiple users are planning to use the platform on the same system, you only need one copy of the data files per machine. Each user will still need his or her own copy of the code files.<br /> <br /> Alternatively, if you would like access to the latest version of the platform and get frequent but less thoroughly tested improvements, you can check out the platform from SCEC's Subversion repository. Only advanced users should take this approach, outlined in detail in the [[#Advanced Users| Advanced Users section]].<br /> <br /> == User Account Setup ==<br /> <br /> The Broadband platform installation is divided into two parts (1) input Green Functions (GF) data directory (9.3Gb), and (2) BBP home directory (366Mb). <br /> <br /> First, the Green's function libraries are larger, but they are static. The broadband platform reads the data files, but does not change them. <br /> <br /> Second, the remainder of the broadband platform is organized in the BBP home directory. The BBP home directory has a specific directory structure that includes the source code for the scientific programs, the python scripts that link the scientific programs, simulation input directory, temporary and log file directories, and the output data directory where all the platform results are written.<br /> <br /> The BBP home directory will increase in size as you run the platform, because both output data and output log files are written to the home directory. Running the acceptance tests will produce nearly ( 10Gb) of input data (5.2Gb), output data (500Mb), temporary files (2.7Gb), and output log files (250Mb). Once these tests have passed much of this data can be removed. However, the BBP home directory should have at least 10Gb of disk space to insure the acceptance tests can be run when a particular broadband platform software distribution is first installed on a system.<br /> <br /> == Data Directory ==<br /> Input data files called Greens Functions are distributed with the platform. These files are generated using specific velocity structures, so they are often considered region specific. We have GF for three regions including near Loma Prieta, near Landers, and near Northridge.<br /> <br /> The data directory is static, and the data directories are read-only. A single copy can be installed in a shared disk, which can then be shared by multiple users.<br /> <br /> == Setting Environment Variables ==<br /> The BBP source codes and scripts are organized under the broadband platform home directory. The broadband platform home directory is specified in a couple of places during Broadband Platform installation. <br /> <br /> Internal to the Broadband platform software, all broadband platform files (except the Greens Function data files) are in sub-directories of the BBP home directory.<br /> <br /> == BBP Environment Variable ==<br /> We recommend setting both an alias and a environment variable to the BBP home directory. This will help avoid typing it many times.<br /> <br /> If you're running a Bash shell, add the following line to your .bash_profile with your favorite text editor:<br /> <br /> export BBP=/home/scec-00/kumar/bbp_2g<br /> <br /> If you're running a C-shell, add the following line to your .cshrc with your favorite text editor:<br /> <br /> setenv BBP /home/scec-00/kumar/bbp_2g<br /> <br /> * PYTHONPATH<br /> After you've obtained a copy of the project, you'll need to make sure the comps directory is on Python's path so Python can find all the project modules. If you're running a Bash shell, add the following line to your .bash_profile with your favorite text editor:<br /> <br /> export PYTHONPATH=$BBP/comps:$PYTHONPATH<br /> <br /> If you're running a C-shell, add the following line to your .cshrc with your favorite text editor:<br /> <br /> setenv PYTHONPATH $BBP/comps:$PYTHONPATH<br /> <br /> * PATH<br /> In order to successfully compile the project, you'll need to make sure the required compilers directories are in your PATH variable. Broadband requires Intel 64-bit compilers, icc and ifort and GNU Compilers, gcc, g77 and f77 to compile the scientific code.<br /> <br /> If you are planning to run Broadband on SCEC Development servers, make sure you have the following directories in your PATH:<br /> <br /> For Bash Shell (in .bash_profile)<br /> <br /> export PATH=/usr/usc/intel/composerxe-2011.4.191/bin/intel64:/usr/usc/intel/composerxe-2011.4.191/mpirt/bin/intel64:$PATH<br /> <br /> For C-shell (in .cshrc)<br /> <br /> setenv PATH /usr/usc/intel/composerxe-2011.4.191/bin/intel64:/usr/usc/intel/composerxe-2011.4.191/mpirt/bin/intel64:$PATH<br /> <br /> When running elements of the platform over ssh, be sure to enable ssh forwarding (with the -X or -Y options).<br /> <br /> After modifying your login script above, log out and log back into the machine so the changes are reflected in your environment.<br /> <br /> == Edit Install_cfg.py with Installation Directory Paths ==<br /> <br /> You need to tell the platform where it's installed by editing a single python file called &quot;install_cfg.py&quot;. Edit the file bbp_2g/comps/install_cfg.py with your favorite text editor, and edit the lines:<br /> <br /> self.A_INSTALL_ROOT = &lt;bbp_2g directory&gt;<br /> self.A_GF_DIR = &lt;bbp_2g_gf directory&gt;<br /> <br /> as one example:<br /> <br /> self.A_INSTALL_ROOT = /home/scec-00/kumar/bbp_2g<br /> self.A_GF_DIR = /home/scec-00/kumar/bbp_2g_gf<br /> <br /> with the paths on your system to the bbp_2g directory (the source) and the bbp_2g_gf directory (the data) that you unzipped. For example, it could be /home/scottcal/broadband_platform/bbp_2g and /home/scottcal/broadband_platform/bbp_2g_gf.<br /> <br /> Here is some information about these two directories that may be useful as you decide how, and where, to install these two parts of the Broadband Platform on your computer disk system. The data files, and therefore the &lt;bbp_2g_gf directory&gt; are nearly 3GB, but they are static and will not be modified and will not grow in size during use of the platform. The source directory is small to begin. However, this directory will increase as the platform is used, since the results produced by the platform will be stored here.<br /> <br /> == Directory Structure ==<br /> The platform consists of two top-level directories, bbp_2g and bbp_2g_gf. bbp_2g contains the source code, executables, scripts, tests, input, working, and output directories. bbp_2g_gf contains the Green's Functions, input files for the validation events, and other required input files for the various code bases. Note that indata, logs, outdata, tmpdata, and xml are created when the platform is first run, so they will be missing when you first install the platform.<br /> <br /> bbp_2g has the following directories:<br /> *checksums: Contains checksums for bbp_2g_gf files<br /> *comps: The Python scripts to run the platform<br /> *docs: Documentation for the platform<br /> *etc: Miscellaneous utility scripts<br /> *examples: Contains example input files<br /> *indata: An internal directory, used to stage input files<br /> *logs: Contains logs from BBP runs<br /> *outdata: Contains output files from a run<br /> *ref_data: Contains reference files for BBP tests<br /> *start: Put input files for an interactive run here<br /> *src: Source code for BBP modules<br /> *tests: Contains unit and acceptance tests<br /> *tmpdata: An internal directory, used during a run<br /> *xml: Contains XML files which describe simulations and can be used as input<br /> <br /> bbp_2g_gf has the following directories:<br /> *compare: Contains observed seismograms for validation events<br /> *plot: Data files for GMT plots<br /> *sdsu, ucsb, urs: Contains Green's functions, velocity files, and other required inputs for the codebases.<br /> <br /> In general, you will be interacting with the start directory for input files, comps to run the platform, tests to test the platform, and outdata to examine data products.<br /> <br /> === Adding aliases ===<br /> <br /> You may find it helpful to add aliases, so you can quickly and easily move to different broadband directories with a single command. We recommend creating aliases for the home, start, and outdata directories.<br /> <br /> If you are using the Bash shell, you can create aliases by adding the following lines to ~/.bash_profile:<br /> <br /> alias bbp= 'cd &lt;path to bbp_2g directory&gt;'<br /> alias start='cd &lt;path to bbp_2g directory&gt;/start'<br /> alias outdata='cd &lt;path to bbp_2g directory&gt;/outdata'<br /> <br /> If you're using a C shell, edit your ~/.cshrc and add:<br /> <br /> alias bbp cd &lt;path to bbp_2g directory&gt;<br /> alias start cd &lt;path to bbp_2g directory&gt;/start<br /> alias outdata cd &lt;path to bbp_2g directory&gt;/outdata<br /> <br /> Log out and log back in. You'll notice that now you can type the alias command as a shortcut to change directories:<br /> <br /> $&gt; pwd<br /> /home/scec-00/scottcal<br /> $&gt; start<br /> $&gt; pwd<br /> /home/scec-00/scottcal/bband/bbp_2g/start<br /> <br /> This can be a useful way to navigate around the broadband platform directories.<br /> <br /> == Building the Platform ==<br /> Once you have checked out the code, you need to build it. By default, every executable is compiled using the compiler recommended by the code developer. However, if you have limited compiler options or are building the codes on an untested system, you may need to specify non-standard alternative compilers, as described below.<br /> <br /> Before you can build the platform, you need to make sure that the Intel compilers are in your path. This is done automatically on broadband.usc.edu, but on other systems you can check by typing:<br /> <br /> $&gt;which icc<br /> <br /> If you get the message &quot;no icc in ...&quot;, then you'll need to add the Intel compilers to your path. Once the Intel compilers are in your path, you can make the code by cd-ing to the bbp_2g/src directory and typing make:<br /> <br /> $&gt; cd src<br /> $&gt; make<br /> <br /> It takes a minute or two to build the code. You may encounter build warnings; these are fine. However, if you get any build errors, this is a problem and should be investigated.<br /> <br /> By default, every executable is compiled using the compiler recommended by the code developer. Depending on the system, some compilers may not be available to you. You can override the C and Fortran compilers used by editing<br /> <br /> src/makefile<br /> <br /> Uncomment USER_C and set FC and CC to the compilers you wish. For example:<br /> <br /> Before:<br /> <br /> #USER_C=1<br /> FC=f77<br /> CC=gcc<br /> <br /> After (an example, you may choose different compilers):<br /> <br /> USER_C=1<br /> FC=gfortran<br /> CC=gcc<br /> <br /> Note that not all compiler combinations have been thoroughly tested. You may encounter build errors with untested compiler combinations. If you encounter any errors while building the platform, consult the Troubleshooting section at the end of this user guide for know issues and their solutions.<br /> <br /> Once the platform has been successfully built, you can move on to running the tests to verify that all components are working correctly.<br /> <br /> == Advanced Users ==<br /> Alternatively, if you would like access to the latest version of the platform, to get frequent but less thoroughly tested improvements, you can check out the platform from SCEC's Subversion version control repository on source.usc.edu. Only advanced users should follow this approach. If you are unsure, you should download the code as outlined in [[#Downloading the Platform|Downloading the Platform]] and skip this section.<br /> <br /> You may need to request access from the SCEC system administrator, John Yu ([mailto:johnyu@usc.edu johnyu@usc.edu]). Make sure you have subversion in your path before beginning.<br /> <br /> Once you have access, you'll need to decide if you want a stable tagged version, or the latest version in the repository. For a stable version, open a terminal window on the system of your choice and type:<br /> <br /> $&gt; svn checkout https://source.usc.edu/svn/broadband/tags/&lt;stable version&gt; bbp_2g<br /> <br /> For the latest version, type:<br /> <br /> $&gt; svn checkout https://source.usc.edu/svn/broadband/trunk bbp_2g<br /> <br /> This will check out the project to your local machine. It contains the source code, tests, and some example files. You also need to obtain a copy of the Broadband Platform data files, containing the Green's tensors. They are too large to be stored in version control. You can obtain a copy from SCEC software distribution server. If you are working on SCEC development server, you might be able to create a symbolic link to data folder. Please contact [[#User_Support|User Support]] to get a location of the data folder on the SCEC development server. If you are not working on SCEC development server, or don't have an SCEC Linux login account, you can get a archive (.tgz) file of the Green's functions from the same download site you obtained this guide.<br /> <br /> If you know where a read-accessible installation of the green functions data directories you can create a link to that location. This can save disk space in some cases.<br /> <br /> ln -s /home/scec-00/scottcal/bband/bbp_2g_gf &lt;path to your gf directory&gt;<br /> <br /> Periodically you should check for updates to the code. To do so, go to your bbp_2g directory and type<br /> <br /> $&gt; svn update<br /> <br /> This will pull down any code updates that have been made in the repository. After you update, make the code again (detailed in [[#Building the Platform|Building the Platform]]) so that any code changes are captured in the executables.<br /> <br /> == Running the Broadband Platform ==<br /> We recommend users initiate all Broadband Platform runs from the &quot;start&quot; directory. The start directory is a collection point for input files for a particular simulation.<br /> <br /> Assuming the user is starting at BBP home directory, the user should move to the start directory and then run the Checksum, Unit and Acceptance tests to confirm the Broadband Platform software installation is operating as expected.<br /> <br /> $&gt; cd start<br /> <br /> == Running Checksum, Unit, and Acceptance Tests ==<br /> The broadband platform contains three kinds of tests. The checksum tests verify that the data files were copied correctly and you have all the files that are expected. Unit tests run each module using a set of input files, and compare the results against known outputs. They verify that each module has been built and is working correctly. Acceptance tests verify that the modules are working correctly together. They test the platform end-to-end using different combinations with known inputs and compare the results. All the possible module combinations for both user-defined and validation events are tested as checks against integration errors.<br /> <br /> Begin with the checksum tests. Once they past, run the unit tests and finally the acceptance tests.<br /> <br /> == Running Checksum Tests ==<br /> To run the checksum tests, change to the checksums directory and run md5sum_check.py.<br /> <br /> From the BBP home directory:<br /> <br /> $&gt; cd checksums<br /> $&gt; ./md5sum_check.py<br /> <br /> It takes about 5 minutes to compute the checksums. If a checksum disagrees, that means that the contents of the datafile were not what was expected. Try reinstalling the data files and try again. If you continue to get a checksum error, contact support.<br /> <br /> Once the checksums agree, move on to the unit tests.<br /> <br /> == Running Unit Tests ==<br /> To run the unit tests, change to the tests directory and run UnitTests.py.<br /> <br /> From the BBP home directory:<br /> <br /> $&gt; cd tests<br /> $&gt; ./UnitTests.py<br /> <br /> The unit tests take about 15 minutes to run. When they're complete, the console will either print &quot;OK&quot; or how many tests failed. If a test has failed, first check that you have built the executables.You can rerun just the specific test that failed (test_&lt;module&gt;.py). If the test is still failing, also verify that you have the ref_data directory, since it contains the input and reference files. If you're looking for more information about the failure, you can consult the Unit Tests log file in bbp_2g/logs/unit_test.log . If you can't determine the reason for the failure, contact support.<br /> <br /> Once the unit tests all pass, proceed to the acceptance tests. If there are any failure or errors while running the unit tests, consult the Troubleshooting section at the end of this user guide for know issues and their solutions.<br /> <br /> == Running Acceptance Tests ==<br /> Make sure the unit tests pass before moving on to the acceptance tests. To run the acceptance tests, change to the tests directory (if you're not there already) and run AcceptTests.py. <br /> The acceptance tests take a long time to run, around 20 hours<br /> <br /> From the BBP home directory:<br /> <br /> $&gt; cd tests<br /> $&gt; ./AcceptTests.py &amp;&gt; accept.out &amp;<br /> <br /> Since the tests take so long to run (twenty hours), you should run them as a background process, and redirect their output to a log file, as shown in the command above.<br /> <br /> You can check the progress by tailing the log file.<br /> <br /> $&gt; tail accept.out<br /> <br /> When all the acceptance tests are completed, the AcceptTests.py script will either print &quot;OK&quot; or how many tests failed. <br /> <br /> Acceptance test failures indicate that the modules are not integrated correctly. Like with the unit tests, verify that you have the ref_data directory. If a certain acceptance test fails, you can get more information by consulting the acceptance test logs in bbp_2g/logs/acceptance_tests_logs/&lt;test that failed&gt;.log . If you can't determine the reason for the failure, contact [[support]].<br /> <br /> Since the acceptance tests can take a long time to run, you may wish to resume where you left off. This feature is supported automatically. If you do not wish to resume, delete the resume file in ref_data/accept_inputs/resume.txt. If there are any failure or errors while running the acceptance tests, consult the Troubleshooting section at the end of this user guide for know issues and their solutions.<br /> <br /> == Types of Broadband Platform Simulations == <br /> <br /> The platform supports two kinds of simulations, validation events and user-defined events. Validation simulations are performed using a historical event, and are directly compared to observed seismograms using goodness-of-fit. User-defined events are run using a rupture description provided by the user which may not necessarily be a historical earthquake.<br /> <br /> When you run a simulation, the platform assigns an ID to it. This ID can be used to track the simulation and locate the output data products.<br /> <br /> To supply input files to the platform, put them in the start directory. Extensions are important - the platform recognizes station lists (.stl), SRF files (.srf), and simple source descriptions (.src). If there are multiple files of a type, the platform will prompt the user to select one.<br /> <br /> To perform a simulation, a user selects between different required and optional modules. Below we present a summary of the various modules.<br /> <br /> == Modules ==<br /> The broadband platform consists of a series of modules. There are two main types of modules, science modules and utility modules. Science modules are those for which the platform has multiple implementations, provided by different coding research groups. Utility modules only have 1 implementation. A schematic of the available modules and their flow relationships is shown below:<br /> <br /> == Science Modules ==<br /> All simulations must include a low-frequency, high-frequency, and site response science module. Simulations may include an optional rupture generation science module. Users may select between the following different implementations of each of these modules:<br /> <br /> Rupture generation:URS, UCSB<br /> <br /> Low-frequency:URS, UCSB<br /> <br /> High-frequency:URS, UCSB, SDSU<br /> <br /> Site response:URS, UCSB, SDSU<br /> <br /> == Utility Modules ==<br /> A spectral response utility module is automatically run after the site response module. Additionally, users may select an optional goodness-of-fit utility module to run at the conclusion of the simulation. In the case of a user-defined event, users select a historical event or previously run simulation to use as the comparison for goodness-of-fit.<br /> <br /> == Platform Directory ==<br /> <br /> A broadband platform distribution is organized in a specific directory structure that separates the input data sets, the python scripts, the simulation configuration files, log files, and output data files.<br /> <br /> When running Broadband Platform simulations, standard procedure is to place the simulation input files in the start directory and invoke the Broadband platform scripts from there.<br /> <br /> From the BBP home directory:<br /> <br /> $&gt; cd start<br /> $&gt; run_bbp_2G.py<br /> <br /> Simulation output results will be written into the bbp_home/output<br /> <br /> == Validation Simulations ==<br /> To run a validation simulation, go to the comps directory and run run_bbp_2G.py. The platform will ask you a series of questions. Answer 'y' to &quot;Do you want to perform a validation run?&quot;<br /> <br /> From the BBP home directory:<br /> <br /> $&gt; cd start<br /> $&gt; run_bbp_2G.py<br /> Welcome to the SCEC Broadband Platform.<br /> Please select the modules you want to run.<br /> Do you want to perform a validation run (y/n)? y<br /> Do you want to validate with:<br /> Northridge (1)<br /> Loma Prieta (2)<br /> Landers (3)<br /> ?<br /> ...<br /> <br /> No input files are required by the user. However, you may wish to run with a reduced station list to speed up the computations. You can put your own station list into the start directory (the format is described in [[#Station File List|section 5.3]]). Note that any stations which do not have observed seismograms will not be included in the automatically generated goodness-of-fit comparison.<br /> <br /> In addition to the low-frequency modules which compute seismograms using 1D Green's Tensors, validation events can also be run using precomputed 3D seismograms to supply the low-frequency.<br /> <br /> == User-defined Simulations ==<br /> To run a user-defined simulation, two input files are required, a rupture description and a station list. The rupture description can either be in SRF format or a simplified source description (the format is described in [[#Simple source description|section 5.1]]). To run a user-defined simulation, run run_bbp_2G.py.<br /> <br /> From the BBP home directory:<br /> <br /> $&gt; cd start<br /> $&gt; run_bbp_2G.py<br /> Welcome to the SCEC Broadband Platform.<br /> Please select the modules you want to run.<br /> Do you want to perform a validation run (y/n)? y<br /> Do you want to run a rupture generator (y/n)? <br /> ...<br /> <br /> You may then choose if you want to run a rupture generator. This is necessary if you're supplying a simple rupture description. If you're supplying an SRF file, you can skip this. Next you can select from different module implementations. Finally, you have the option to run goodness-of-fit against either observed seismograms or another simulation.<br /> <br /> ...<br /> Do you want to run goodness of fit (y/n)? y<br /> What reference files would you like to compare to? Enter a simulation ID or a scenario name: &lt;comparison&gt;<br /> Enter a label to use for the comparison seismograms: &lt;label&gt;<br /> <br /> The label will be used in GoF plots to distinguish one set of results from the other.<br /> <br /> The user-defined events must be within one of the regions supported by the platform - Southern California, Northern California, or the Mojave. The platform will automatically select a region based on the event hypocenter. If the event falls outside of these regions, you'll get an error.<br /> <br /> == Logging ==<br /> During the run, log files will be produced in logs/&lt;simulation ID&gt;/&lt;simulation ID&gt;.&lt;module name&gt;.log. If the platform fails, this is a good place to look to determine the error. Additionally, any fatal errors will be recorded in fatal_error.log.<br /> <br /> Metadata capturing all the executable calls is located in tmpdata/&lt;simulation ID&gt;/metadata.txt for careful tracing of exactly what was called. Both the log files and metadata can be useful if troubleshooting an issue.<br /> <br /> == Data Products ==<br /> The platform produces a variety of data products. &lt;nowiki&gt;All data products are located in outdata/&lt;simulation ID&gt;. &lt;/nowiki&gt;On most Linux systems, you can show images using display:<br /> <br /> $&gt; display &lt;PNG file&gt;<br /> <br /> Make sure you have X11 forwarding enabled.<br /> <br /> === Station map ===<br /> To help visualize the stations in relationship to the fault, the platform produces a PNG file displaying station locations with red circles and the fault plane with a black line, on an image of California. You can find this file in outdata/&lt;simulation ID&gt;/station_map.png.<br /> <br /> === Seismograms ===<br /> When running the platform, you have the option to output velocity and acceleration seismograms, for each station. Plots of these files can be found in outdata/&lt;simulation ID&gt;/&lt;simulation ID&gt;.&lt;station&gt;_&lt;velocity or acceleration&gt;_seis.png.<br /> <br /> The raw seismogram data is available in outdata/&lt;simulation ID&gt;/&lt;simulation ID&gt;.&lt;station&gt;.vel.bbp (velocity) and outdata/&lt;simulation ID&gt;.&lt;station&gt;.acc.bbp (acceleration). Its format is described in [[#BBP seismograms|section 5.4]].<br /> <br /> To compare seismogram data, you can run comps/plotit.py with two seismograms. It will plot them both for comparison. From the comps directory, run:<br /> <br /> $&gt; plotit.py &lt;path to seismogram 1&gt; &lt;path to seismogram 2&gt;<br /> <br /> === Response spectra ===<br /> The respect code, run at the end of each simulation, calculates the response spectra for each station. The raw respect data is located at<br /> <br /> From the BBP home directory:<br /> <br /> outdata/&lt;simulation ID&gt;/&lt;simulation ID&gt;.&lt;station&gt;.rsp<br /> <br /> in the format described in [[#Response spectra|section 5.5]].<br /> <br /> === Goodness-of-fit ===<br /> If you run goodness-of-fit, several additional data products are produced. The goodness-of-fit comparison is performed by comparing the response spectra of a set of calculated seismograms to seismograms from another simulation or observed seismograms. For each station involved in the comparison, a plot comparing the response spectra can be found at outdata/&lt;simulation ID&gt;/&lt;comparison label&gt;_&lt;simulation ID&gt;_&lt;station&gt;_rsp.png. A plot showing the seismograms on top and bottom can be found at outdata/&lt;comparison label&gt;_&lt;simulation ID&gt;_&lt;station&gt;_overlay.png. The goodness-of-fit plot can be found at gof-&lt;comparison label&gt;-&lt;simulation ID&gt;_r0-&lt;cutoff distance&gt;.png.<br /> <br /> Note that at least 3 stations must be run for goodness-of-fit to be valid. If fewer than 3 stations are run, no goodness of fit calculation will be performed.<br /> <br /> === Rupture files ===<br /> When a user-defined event is simulated, the user has the option to run a rupture generator. This generator produces an SRF file, found in outdata/&lt;simulation ID&gt;/*.srf. This file can be put in the start directory and used in future runs. Additionally, the platform produces a plot of the cumulative slip on the fault surface, outdata/&lt;simulation ID&gt;/&lt;SRF prefix&gt;.png.<br /> <br /> == Platform Modes ==<br /> The platform can be run in multiple modes. The default is interactive mode, in which the user is prompted to answer a series of questions. Once all the information has been gathered, the run begins.<br /> <br /> For a large number of runs, or if the user is repeating a specific run, this can be tedious. The platform provides two other ways to describe a run, with an option file or an XML description.<br /> <br /> An option file provides responses to all the questions that the platform poses. The format is described in [[#Option File|section 5.6]], but it's basically a text file, 1 entry per line, with support for comments. It can be fed to the platform using the -o option.<br /> <br /> The platform will also accept XML files containing a full description of a run. The schema for these files is given in [[#XML workflow description schema|section 5.7]]. These files are also produced by the platform after every simulation, and placed in xml/&lt;simulation ID&gt;.xml. So if you want to rerun a simulation, you can point the platform to the XML file from that simulation using the -x option. Note that a new simulation ID will be assigned to the run, so there is no risk of overwriting previous simulation results.<br /> <br /> == Available Options ==<br /> To get a list of the current available options, run run_bbp_2G.py with the -h flag.<br /> <br /> $&gt; run_bbp_2G.py -h<br /> Usage: run_bbp_2G.py [options]<br /> Options:<br /> -h, --help Show this help message and exit<br /> -x XML_FILE, --xml-file=XML_FILE Run using XML description of workflow<br /> -s SIM_ID, --simID=SIM_ID Force a simID<br /> -o OPTFILE, --option-file=OPTFILE File containing responses to interactive platform prompts<br /> -v, --version Broadband platform version<br /> -c, --compact Compact output results. Remove temporary files for simulations that complete successfully.<br /> -g, --generate-xml Generates the XML description but does not run the platform<br /> -l LOG_FILE, --log=LOG_FILE Store all output in a file<br /> <br /> == Cleanup ==<br /> After a while, you may find that your indata, tmpdata, outdata, and logs directories are getting cluttered with files from past runs. If you wish to delete these old files, you can use the clean_directories.sh script in the etc directory.<br /> <br /> From the BBP home directory:<br /> <br /> $&gt; cd etc<br /> $&gt; ./clean_directories &lt;days&gt;<br /> <br /> Any simulation ID directories in the indata, tmpdata, outdata, and logs directories which were last accessed &lt;days&gt; days or longer ago will be deleted. If you have a few directories you want to keep, either copy them somewhere else, or copy them to a directory name that's not all digits and they won't be deleted.<br /> <br /> == Examples ==<br /> Below are some examples that you can try using the sample files in the examples directory. Make sure all the tests pass before you try this. You should be in the comps directory when you start these examples:<br /> <br /> From the BBP home directory:<br /> <br /> $&gt; cd comps<br /> <br /> == Sample Validation Run ==<br /> You don't need to move any files for this. Notice that 3D seismograms are a low-frequency option, since you're running a validation event.<br /> <br /> From the BBP home directory:<br /> <br /> $&gt; cd start<br /> $&gt; run_bbp_2G.py <br /> Welcome to the SCEC Broadband Platform.<br /> Please select the modules you want to run.<br /> Do you want to perform a validation run (y/n)? y<br /> Do you want to validate with:<br /> Northridge (1)<br /> Loma Prieta (2)<br /> Landers (3)<br /> ?1<br /> Do you want to<br /> run all validation stations (1)<br /> select a station list (2)<br /> ?1<br /> Choose a source of low frequency seismograms:<br /> URS module (1)<br /> URS 3D seismograms (2)<br /> UCSB module (3)<br /> SDSU module (4)<br /> SDSU 3D seismograms (5)<br /> ?2<br /> Choose a high frequency module:<br /> URS (1)<br /> UCSB (2)<br /> SDSU (3)<br /> ?1<br /> Choose a site response module:<br /> URS (1)<br /> UCSB (2)<br /> SDSU (3)<br /> ?1<br /> Do you want to plot velocity seismograms (y/n)? y<br /> Do you want to plot acceleration seismograms (y/n)? y<br /> <br /> This simulation takes about 10 minutes. Once it's complete the platform will tell you:<br /> <br /> You can find results in &lt;path to bbp_2g install&gt;/outdata/&lt;simulation ID&gt; .<br /> <br /> In that directory you will find:<br /> <br /> *Velocity seismograms (&lt;simulation ID&gt;.&lt;station&gt;.bbp)<br /> *Acceleration seismograms (&lt;simulation ID&gt;.&lt;station&gt;.acc.bbp)<br /> *Plots of velocity seismograms (&lt;simulation ID&gt;.&lt;station&gt;_velocity_seis.png)<br /> *Plots of acceleration seismograms (&lt;simulation ID&gt;.&lt;station&gt;_acceleration_seis.png)<br /> *Response spectra files (&lt;simulation ID&gt;.&lt;station&gt;.rsp)<br /> *Plots comparing simulated and observed seismograms (Northridge_&lt;simulation ID&gt;_&lt;station&gt;_overlay.png)<br /> *Plots comparing simulated and observed response spectra (Northridge_&lt;simulation ID&gt;_&lt;station&gt;_rsp.png)<br /> *Overall goodness-of-fit plots (gof-Northridge-&lt;simulation ID&gt;_r0-25.png)<br /> <br /> == Sample Validation run, custom stations ==<br /> If the validation runs aren't performed with 3D low-frequency, it can take a long time, up to 10 minutes per station. Sometimes you might want to run with a reduced station list so the simulation will run faster.<br /> <br /> Copy the files in example/valid_custom_stations into the start directory. Take a look at the format of the station file:<br /> <br /> $&gt; more valid_test_stat.stl <br /> #Required: lon, lat, station name, distance to fault plane, Vs30<br /> #Optional: low freq corner, high freq corner<br /> #Unused: station information<br /> #lon lat stationdist Vs30 LF corner HF corner station information<br /> -118.6417 34.5640 cast 20.47 450 0.120 23.0 CSMIP peer.berkeley.edu/nga<br /> -118.4180 34.0628 lacn 22.82 278 0.140 23.0 CSMIP peer.berkeley.edu/nga<br /> -118.8811 34.2886 moor 24.16 405 0.160 23.0 CSMIP peer.berkeley.edu/nga<br /> <br /> Now, run the platform, using a station list:<br /> <br /> From the BBP Home directory<br /> <br /> $&gt; cd start<br /> $&gt; run_bbp_2G.py <br /> Welcome to the SCEC Broadband Platform.<br /> Please select the modules you want to run.<br /> Do you want to perform a validation run (y/n)? y<br /> Do you want to validate with:<br /> Northridge (1)<br /> Loma Prieta (2)<br /> Landers (3)<br /> ?1<br /> Do you want to<br /> run all validation stations (1)<br /> select a station list (2)<br /> ?2<br /> <br /> If you have multiple station list files in your start directory, you may see the following prompt asking you to select one. If you only have one, the platform will select it automatically.<br /> <br /> Found multiple BBP station list files in the start directory. Please select one:<br /> nr_one_stat.stl (1)<br /> valid_test_stat.stl (2)<br /> ?2<br /> Choose a source of low frequency seismograms:<br /> URS module (1)<br /> URS 3D seismograms (2)<br /> UCSB module (3)<br /> SDSU module (4)<br /> SDSU 3D seismograms (5)<br /> ?3<br /> Choose a high frequency module:<br /> URS (1)<br /> UCSB (2)<br /> SDSU (3)<br /> ?2<br /> Choose a site response module:<br /> URS (1)<br /> UCSB (2)<br /> SDSU (3)<br /> ?2<br /> Do you want to plot velocity seismograms (y/n)? y<br /> Do you want to plot acceleration seismograms (y/n)? y<br /> <br /> Again, when the run completes in about 15 minutes you can find results in the output directory. You'll notice far fewer files, as only 3 stations were run instead of 133. The goodness-of-fit plots won't look very good - more stations are really needed to get an accurate plot.<br /> <br /> == Sample User-defined run with source description ==<br /> Next let's try running a user-defined event. Copy examples/user_rup_gen/nr_one_stat.stl and examples/user_rup_gen/user_eq.src to the start directory. user_eq.src is a simple source description. Its format is outlined in [[#XML workflow description schema|section 5.1]]. Since this is a user-defined event, precomputed 3D seismograms aren't a valid option.<br /> <br /> $&gt; run_bbp_2G.py <br /> Welcome to the SCEC Broadband Platform.<br /> Please select the modules you want to run.<br /> Do you want to perform a validation run (y/n)? n<br /> Do you want to run a rupture generator (y/n)? y<br /> Rupture generators:<br /> URS (1)<br /> UCSB (2)<br /> ?1<br /> Using region: Southern California<br /> Choose a low frequency module:<br /> URS (1)<br /> UCSB (2)<br /> ?2<br /> Found multiple BBP station list files in the start directory. Please select one:<br /> nr_one_stat.stl (1)<br /> valid_test_stat.stl (2)<br /> ?1<br /> Choose a high frequency module:<br /> URS (1)<br /> UCSB (2)<br /> SDSU (3)<br /> ?2<br /> Choose a site response module:<br /> URS (1)<br /> UCSB (2)<br /> SDSU (3)<br /> ?1<br /> Do you want to plot velocity seismograms (y/n)? y<br /> Do you want to plot acceleration seismograms (y/n)? y<br /> Do you want to run goodness of fit (y/n)? n<br /> <br /> Since this run only includes one station, it will run in about 5 minutes. In the output directory you'll notice there are no goodness-of-fit or files, since we didn't run goodness-of-fit. However, there is also a map file (station_map.png), showing the fault plane and the stations, and a plot of the rupture slip (user_eq.png). The SRF generated by the rupture generator is in user_eq.srf; this file could be used in future runs. The filenames of the rupture slip plot and SRF are taken from the rupture description filename.<br /> <br /> == Sample User-defined run with SRF file and goodness-of-fit ==<br /> Finally, try a run with an SRF file and run goodness-of-fit on the results. Copy in examples/user_no_rup_gen/ucsb_modSRF_0.srf and examples/user_no_rup_gen/nr_three_stat.stl<br /> <br /> $&gt; run_bbp_2G.py <br /> Welcome to the SCEC Broadband Platform.<br /> Please select the modules you want to run.<br /> Do you want to perform a validation run (y/n)? n<br /> Do you want to run a rupture generator (y/n)? n<br /> Using region: Southern California<br /> Choose a low frequency module:<br /> URS (1)<br /> UCSB (2)<br /> ?1<br /> Found multiple BBP station list files in the start directory. Please select one:<br /> nr_one_stat.stl (1)<br /> valid_test_stat.stl (2)<br /> nr_three_stat.stl (3)<br /> ?3<br /> Choose a high frequency module:<br /> URS (1)<br /> UCSB (2)<br /> SDSU (3)<br /> ?3<br /> Choose a site response module:<br /> URS (1)<br /> UCSB (2)<br /> SDSU (3)<br /> ?1<br /> Do you want to plot velocity seismograms (y/n)? y<br /> Do you want to plot acceleration seismograms (y/n)? y<br /> Do you want to run goodness of fit (y/n)? y<br /> What reference files would you like to compare to? Enter a simulation ID or a scenario name: Northridge<br /> Enter a label to use for the comparison seismograms: nr<br /> <br /> The reference files can either be a scenario event or a simulation ID previously run. The label is just for the figures when comparisons are plotted.<br /> <br /> This run will take about 15 minutes, and the results can be found in the appropriate outdir. Again, the goodness of fit measures will look poor due to the few stations involved in the comparison. If you had fewer than 3 stations, no goodness-of-fit plots would be produced. However, response spectra comparison plots will still be generated.<br /> <br /> == File Formats ==<br /> This section offers descriptions of various file formats in the broadband platform.<br /> <br /> == Simple source description ==<br /> This is the format for the simple source description. It is not whitespace sensitive. The filename must end in .src for the platform to identify it as a source description.<br /> <br /> MAGNITUDE = &lt;magnitude&gt;<br /> FAULT_LENGTH = &lt;length of fault&gt;<br /> DLEN = &lt;DX, along length&gt;<br /> FAULT_WIDTH = &lt;down-dip fault width&gt;<br /> DWID = &lt;DY, along width&gt;<br /> DEPTH_TO_TOP = &lt;depth of fault below surface&gt;<br /> STRIKE = &lt;nowiki&gt;&lt;strike&gt;&lt;/nowiki&gt;<br /> RAKE = &lt;rake&gt;<br /> DIP = &lt;dip&gt;<br /> LAT_TOP_CENTER = &lt;latitude of top center point in fault plane&gt;<br /> LON_TOP_CENTER = &lt;longitude of top center point in fault plane&gt;<br /> HYPO_ALONG_STK = &lt;along strike location of hypocenter (0.0 = middle)&gt;<br /> HYPO_DOWN_DIP = &lt;down dip location of hypocenter (0.0 = top)&gt;<br /> DT = &lt;nowiki&gt;&lt;dt&gt;&lt;/nowiki&gt;<br /> SEED = &lt;random seed used in calculations&gt;<br /> CORNER_FREQ = &lt;corner frequency to use&gt;<br /> <br /> == SRF rupture description ==<br /> Details of the Standard Rupture Format (SRF) are given in more detail in the accompanying document. The general fault surface is represented by a distribution of point sources, and it can support one or more planes. The platform produces SRFs as output from rupture generators, but a user can also supply an SRF file as input for user-defined simulations. SRF filenames must end with the suffix .srf for the platform to correctly identify them.<br /> <br /> == Station File List ==<br /> The user may specify a list of stations, matching the following format:<br /> <br /> #optional<br /> %comment<br /> # lines<br /> &lt;nowiki&gt;&lt;lon&gt; &lt;lat&gt; &lt;stat name&gt; &lt;distance to fault trace&gt; &lt;Vs30&gt; &lt;LF corner&gt; &lt;HF corner&gt; &lt;stat info&gt;&lt;/nowiki&gt;<br /> ...<br /> <br /> The station list filename needs to end in .stl for the platform to recognize it as a station list.<br /> <br /> == BBP seismograms ==<br /> All intermediate and output seismograms are produced in a 4-column text format, whether velocity or acceleration.<br /> <br /> # optional<br /> % comment<br /> # lines<br /> &lt;nowiki&gt;&lt;timestamp&gt; &lt;North/South&gt; &lt;East/West&gt; &lt;Up/Down&gt;&lt;/nowiki&gt;<br /> ...<br /> <br /> Time is in seconds and motion is in cm/s (velocity) or cm/s/s (acceleration) unless otherwise specified in the header. Velocity filenames end in .vel.bbp; accelerations in .acc.bbp.<br /> <br /> == Response spectra ==<br /> The response spectra file is in 4-column text format.<br /> <br /> # optional<br /> % comment<br /> # lines<br /> &lt;nowiki&gt;&lt;period (sec)&gt; &lt;North/South&gt; &lt;East/West&gt; &lt;Up/Down&gt;&lt;/nowiki&gt;<br /> ...<br /> <br /> The platform samples response spectra at 112 periods, 0.01-20 sec and outputs pseudo spectral acceleration in units of g.<br /> <br /> == Option File ==<br /> Option files contain responses to the prompts in the platform. You can use them with the -o option to run_bbp_2G.py. The responses have to match the prompts exactly. For example, if you craft an option file assuming there is only one station list in the start directory (and therefore the user isn't prompted to select one) but then it is run with multiple station lists in the start directory, this will cause the run to abort. Option files are recommended to perform a series of runs with different inputs or different modules. If you have a run you perform regularly, it's better practice to run the platform with the -g option and the option file to produce an XML description, which are more complete descriptions of the workflow.<br /> <br /> #optional comments<br /> %using either symbol<br /> n #comments<br /> y % can go<br /> 1 # here<br /> ...<br /> <br /> Use with:<br /> <br /> $&gt; run_bbp_2G.py -o &lt;option file&gt;<br /> <br /> == XML workflow description schema ==<br /> Each time the platform is invoked, an XML file is produced describing the workflow, obeying the following schema:<br /> <br /> &lt;nowiki&gt;&lt;xs:schema xmlns:xs=&quot;http://www.w3.org/2001/XMLSchema&quot;&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:element name= &quot;BBP_Run_Specification&quot; minOccurs= &quot;1&quot; maxOccurs= &quot;1&quot;&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:attribute name=&quot;version&quot; type = &quot;xs:string&quot; use = &quot;required&quot; /&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:complexType&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:sequence&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:element name= &quot;Validation_Run&quot; minOccurs= &quot;0&quot; maxOccurs = &quot;1&quot;&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:attribute name= &quot;event&quot; type= &quot;xs:string&quot; use= &quot;required&quot; /&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:attribute name= &quot;input_station_file&quot; type = &quot;xs:string&quot; /&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:attribute name= &quot;subset&quot; type = &quot;xs:boolean&quot; use = &quot;required&quot; /&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;/xs:element&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:element name= &quot;BBP_Modules&quot;&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:complexType&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:sequence&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:element name = &quot;BBP_Module&quot; maxOccurs = &quot;unbounded&quot; &gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:complexType&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:sequence&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:element name= &quot;name&quot; type=&quot;xs:string&quot; /&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:element name= &quot;staged_files&quot; &gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:complexType&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:sequence&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:element name=&quot;file&quot; type=&quot;xs:string&quot; maxOccurs= &quot;unbounded&quot;/&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;/xs:sequence&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;/xs:complexType&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;/xs:element&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:element name= &quot;arguments&quot; &gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:complexType&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:sequence&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:element name=&quot;argument&quot; type=&quot;xs:string&quot; maxOccurs=&quot;unbounded&quot;&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:attribute name= &quot;type&quot; type= &quot;xs:string&quot; user= &quot;required&quot; /&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;/xs:element&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;/xs:sequence&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;/xs:complexType&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;/xs:element&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;/xs:sequence&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;/xs:complexType&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;/xs:element&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;/xs:sequence&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;/xs:complexType&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;/xs:element&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;/xs:sequence&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;/xs:complexType&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;/xs:element&gt;&lt;/nowiki&gt;<br /> <br /> These files are difficult to construct by hand, but can be generated using the -g flag when running run_bbp_2G.py.<br /> <br /> == User Support ==<br /> If you run into bugs with the platform, you can open a trouble ticket at the [http://northridge.usc.edu/trac/broadband Broadband Trac site].<br /> <br /> Check to see if there has already been a ticket opened for the bug. If you are unable to get the platform to run, you can get direct user support by emailing [mailto:software@intensity.usc.edu software@intensity.usc.edu].<br /> <br /> == Appendix A: Possible Module Permutations ==<br /> === Validation Events ===<br /> <br /> {| class=&quot;wikitable&quot; | border=&quot;1&quot;<br /> | Permutation #<br /> | Low-frequency module<br /> | High-frequency module<br /> | Site response<br /> <br /> |-<br /> | &lt;center&gt;1&lt;/center&gt;<br /> | &lt;center&gt;URS 1D&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;2&lt;/center&gt;<br /> | &lt;center&gt;URS 1D&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;3&lt;/center&gt;<br /> | &lt;center&gt;URS 1D&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;4&lt;/center&gt;<br /> | &lt;center&gt;URS 1D&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;5&lt;/center&gt;<br /> | &lt;center&gt;URS 1D&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;6&lt;/center&gt;<br /> | &lt;center&gt;URS 1D&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;7&lt;/center&gt;<br /> | &lt;center&gt;URS 1D&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;8&lt;/center&gt;<br /> | &lt;center&gt;URS 1D&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;9&lt;/center&gt;<br /> | &lt;center&gt;URS 1D&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;10&lt;/center&gt;<br /> | &lt;center&gt;URS 3D precomputed&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;11&lt;/center&gt;<br /> | &lt;center&gt;URS 3D precomputed&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;12&lt;/center&gt;<br /> | &lt;center&gt;URS 3D precomputed&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;13&lt;/center&gt;<br /> | &lt;center&gt;URS 3D precomputed&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;14&lt;/center&gt;<br /> | &lt;center&gt;URS 3D precomputed&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;15&lt;/center&gt;<br /> | &lt;center&gt;URS 3D precomputed&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;16&lt;/center&gt;<br /> | &lt;center&gt;URS 3D precomputed&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;17&lt;/center&gt;<br /> | &lt;center&gt;URS 3D precomputed&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;18&lt;/center&gt;<br /> | &lt;center&gt;URS 3D precomputed&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;19&lt;/center&gt;<br /> | &lt;center&gt;UCSB 1D&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;20&lt;/center&gt;<br /> | &lt;center&gt;UCSB 1D&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;21&lt;/center&gt;<br /> | &lt;center&gt;UCSB 1D&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;22&lt;/center&gt;<br /> | &lt;center&gt;UCSB 1D&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;23&lt;/center&gt;<br /> | &lt;center&gt;UCSB 1D&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;24&lt;/center&gt;<br /> | &lt;center&gt;UCSB 1D&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;25&lt;/center&gt;<br /> | &lt;center&gt;UCSB 1D&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;26&lt;/center&gt;<br /> | &lt;center&gt;UCSB 1D&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;27&lt;/center&gt;<br /> | &lt;center&gt;UCSB 1D&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;28&lt;/center&gt;<br /> | &lt;center&gt;SDSU 1D&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;29&lt;/center&gt;<br /> | &lt;center&gt;SDSU 1D&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;30&lt;/center&gt;<br /> | &lt;center&gt;SDSU 1D&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;31&lt;/center&gt;<br /> | &lt;center&gt;SDSU 1D&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;32&lt;/center&gt;<br /> | &lt;center&gt;SDSU 1D&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;33&lt;/center&gt;<br /> | &lt;center&gt;SDSU 1D&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;34&lt;/center&gt;<br /> | &lt;center&gt;SDSU 1D&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;35&lt;/center&gt;<br /> | &lt;center&gt;SDSU 1D&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;36&lt;/center&gt;<br /> | &lt;center&gt;SDSU 1D&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;37&lt;/center&gt;<br /> | &lt;center&gt;SDSU 3D precomputed&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;38&lt;/center&gt;<br /> | &lt;center&gt;SDSU 3D precomputed&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;39&lt;/center&gt;<br /> | &lt;center&gt;SDSU 3D precomputed&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;40&lt;/center&gt;<br /> | &lt;center&gt;SDSU 3D precomputed&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;41&lt;/center&gt;<br /> | &lt;center&gt;SDSU 3D precomputed&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;42&lt;/center&gt;<br /> | &lt;center&gt;SDSU 3D precomputed&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;43&lt;/center&gt;<br /> | &lt;center&gt;SDSU 3D precomputed&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;44&lt;/center&gt;<br /> | &lt;center&gt;SDSU 3D precomputed&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;45&lt;/center&gt;<br /> | &lt;center&gt;SDSU 3D precomputed&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> |}<br /> <br /> ===User-Defined Events===<br /> <br /> {| class=&quot;wikitable&quot; | border=&quot;1&quot;<br /> | Permutation #<br /> | Rupture generator<br /> | Low-frequency<br /> | High-frequency<br /> | Site response<br /> <br /> |-<br /> | &lt;center&gt;1&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;2&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;3&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;4&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;5&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;6&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;7&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;8&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;9&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;10&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;11&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;12&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;13&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;14&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;15&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;16&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;17&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;18&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;19&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;20&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;21&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;22&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;23&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;24&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;25&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;26&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;27&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;28&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;29&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;30&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;31&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;32&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;33&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;34&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;35&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;36&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;37&lt;/center&gt;<br /> | &lt;center&gt;User-supplied SRF&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;38&lt;/center&gt;<br /> | &lt;center&gt;User-supplied SRF&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;39&lt;/center&gt;<br /> | &lt;center&gt;User-supplied SRF&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;40&lt;/center&gt;<br /> | &lt;center&gt;User-supplied SRF&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;41&lt;/center&gt;<br /> | &lt;center&gt;User-supplied SRF&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;42&lt;/center&gt;<br /> | &lt;center&gt;User-supplied SRF&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;43&lt;/center&gt;<br /> | &lt;center&gt;User-supplied SRF&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;44&lt;/center&gt;<br /> | &lt;center&gt;User-supplied SRF&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;45&lt;/center&gt;<br /> | &lt;center&gt;User-supplied SRF&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;46&lt;/center&gt;<br /> | &lt;center&gt;User-supplied SRF&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;47&lt;/center&gt;<br /> | &lt;center&gt;User-supplied SRF&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;48&lt;/center&gt;<br /> | &lt;center&gt;User-supplied SRF&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;49&lt;/center&gt;<br /> | &lt;center&gt;User-supplied SRF&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;50&lt;/center&gt;<br /> | &lt;center&gt;User-supplied SRF&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;51&lt;/center&gt;<br /> | &lt;center&gt;User-supplied SRF&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;52&lt;/center&gt;<br /> | &lt;center&gt;User-supplied SRF&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;53&lt;/center&gt;<br /> | &lt;center&gt;User-supplied SRF&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;54&lt;/center&gt;<br /> | &lt;center&gt;User-supplied SRF&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> |}<br /> <br /> == Appendix B: Troubleshooting ==<br /> If you experience trouble building the platform or successfully running test and simulations, try the following solutions.<br /> <br /> === Build Errors ===<br /> <br /> The instruction for installing Broadband Platform are listed in Section 1: &quot;Installing the Second-Generation Broadband Platform&quot; of the User guide. If after following all steps listed in this section of the user guide the build fails, check if the failure is listed in this section and try the solution to fix the issue you are facing.<br /> <br /> ==== 64-bit Intel Compiler Issue ====<br /> If you try to compile with:<br /> &lt;pre&gt;<br /> % cd bbp_2g/src<br /> % make<br /> &lt;/pre&gt; <br /> <br /> and you get:<br /> &lt;pre&gt;<br /> ... <br /> make[2]: Entering directory `.../bbp_2g/src/ucsb/getInFile'<br /> icc -o getfaultGlobal getfaultGlobal.c<br /> ld: cannot find -lgcc_s_32<br /> make[2]: *** [getfaultGlobal] Error 1<br /> make[2]: Leaving directory `.../bbp_2g/src/ucsb/getInFile'<br /> make[1]: *** [all] Error 2<br /> make[1]: Leaving directory `.../bbp_2g/src/ucsb'<br /> make: *** [all] Error 2<br /> &lt;/pre&gt;<br /> <br /> '''Cause:''' The Broadband Platform requires Intel 64-bit compilers to build successfully. In this case the 32-bit Intel compilers are being invoked as they are being picked up from the PATH environment variable. The error is due to a missing GNU-GCC 32-bit compatibility pack that has not been installed on your system. This is not required when 64-bit Intel compilers are used.<br /> <br /> '''Solution:''' Ensure that the path Intel 64-bit compilers are listed in you PATH variable and being picked up by running 'which icc' and 'which ifort'. If you are trying to build the platform on SCEC development servers like Intensity, verify your path variable has:<br /> &lt;pre&gt;<br /> PATH=...:/usr/usc/intel/composerxe-2011.4.191/mpirt/bin/intel64:/usr/usc/intel/composerxe-2011.4.191/bin/intel64<br /> &lt;/pre&gt;<br /> <br /> ==== 32-bit Platform Issue ====<br /> <br /> On trying to build the platform, the build fails with the following message:<br /> &lt;pre&gt;<br /> $ make all<br /> cd urs; make -f makefile FC=gfortran CC=icc USER_C=1;<br /> make[1]: Entering directory `.../bbp_2g/src/urs'<br /> mkdir -p bin;<br /> cd getpar/src; make -f Makefile CC=icc FC=gfortran USER_C=1;<br /> make[2]: Entering directory `.../bbp_2g/src/urs/getpar/src'<br /> icc -O3 -DENVIRONMENT -c -o defpar.o defpar.c<br /> icc -O3 -DENVIRONMENT -c -o getpar.o getpar.c<br /> icc -O3 -DENVIRONMENT -c -o getarg.o getarg.c<br /> getarg.c(112): warning #303: explicit type is missing (&quot;int&quot; assumed)<br /> register i;<br /> ^ <br /> icc -O3 -DENVIRONMENT -c -o getlocation.o getlocation.c<br /> getlocation.c(9): warning #147: declaration is incompatible with &quot;__ssize_t={int} getline(char **restrict, size_t={unsigned int} *restrict, FILE *restrict)&quot; (declared at line 671 of &quot;/usr/include/stdio.h&quot;)<br /> static int getline(FILE *fd, char *line)<br /> <br /> ...<br /> ...<br /> ...<br /> <br /> make[2]: Entering directory `.../bbp_2g/src/sdsu/srcV1.4'<br /> icc -w -Wall -c ray3DJHfor.c<br /> gfortran module_bbtoolbox.f90 module_interface.f90 main_bbtoolbox.f90 coda.f90 composition.f90 convolution.f90 fourier.f90 error.f90 geometry.f90 interpolation.f90 io.f90 random.f90 scattering.f90 source.f90 ray3DJHfor.o -o BBtoolbox.exe<br /> ray3DJHfor.o: In function `raytracing_':<br /> ray3DJHfor.c:(.text+0x8cf): undefined reference to `__libm_sse2_log'<br /> ray3DJHfor.c:(.text+0x96b): undefined reference to `__libm_sse2_asin'<br /> ray3DJHfor.c:(.text+0x9cd): undefined reference to `__libm_sse2_asin'<br /> ray3DJHfor.c:(.text+0xa00): undefined reference to `__libm_sse2_tan'<br /> ray3DJHfor.c:(.text+0xa3d): undefined reference to `__libm_sse2_tan'<br /> ray3DJHfor.c:(.text+0xa52): undefined reference to `__libm_sse2_log'<br /> collect2: ld returned 1 exit status<br /> make[2]: *** [BBtoolbox.exe] Error 1<br /> make[2]: Leaving directory `.../bbp_2g/src/sdsu/srcV1.4'<br /> make[1]: *** [all] Error 2<br /> make[1]: Leaving directory `.../bbp_2g/src/sdsu'<br /> make: *** [all] Error 2<br /> &lt;/pre&gt;<br /> <br /> '''Cause:''' In this case the user tried to build Broadband on a 32-bit platform. Broadband code was designed to be run on 64-bit platform. Any attempt to build Broadband on a 32-bit platform will result in numerous warnings and the build will fail with error messages similar to ones listed above.<br /> <br /> '''Solution:''' Try building Broadband on a 64-bit platform will the all the dependencies listed in Section 1.1: &quot;System Dependencies&quot; and Section 1.2: &quot;Software Dependencies&quot;<br /> <br /> === Unit/Acceptance Test Failures and Errors ===<br /> <br /> Unit and Acceptance tests are provided to verify the Broadband platform and it's supporting modules built by the user are functioning as designed. Under certain circumstances, some of these test might fail. While some of these failure might indicate serious problems that will have to be addressed before the platform can used, it is acceptable to ignore some of the failures. This section lists some failures and their solutions.<br /> <br /> ==== ERROR: test_syn1d (test_syn1d.Test_syn1D) ====<br /> The Unit test for Syn1d module fails with the following message:<br /> &lt;pre&gt;<br /> ERROR: test_syn1d (test_syn1d.Test_syn1D)<br /> ----------------------------------------------------------------------<br /> Traceback (most recent call last):<br /> File &quot;.../bbp_2g/tests/test_syn1d.py&quot;, line 62, in test_syn1d<br /> synObj.run()<br /> File &quot;.../bbp_2g/comps/syn1D.py&quot;, line 236, in run<br /> shutil.copy2(a_tmpfile, expected_file)<br /> File &quot;/usr/lib/python2.6/shutil.py&quot;, line 99, in copy2<br /> copyfile(src, dst)<br /> File &quot;/usr/lib/python2.6/shutil.py&quot;, line 52, in copyfile<br /> fsrc = open(src, 'rb')<br /> IOError: [Errno 2] No such file or directory: '.../bbp_2g/tmpdata/3310632/s01.3comp'<br /> &lt;/pre&gt;<br /> <br /> '''Cause:''' Syn1d module requires the Green's Function file to run and the path to this file might be incorrect in 'bbp_2g_gf/ucsb/GreenBank/Northridge/GreenBank.inf' file.<br /> <br /> '''Solution:''' This issue can be fixed by correcting the paths listed in the GreenBank.inf files in the Green's Function directory. Here are step by step instructions to fix this issue:<br /> <br /> 1. Locate your Greens Functions directory: 'bbp_2g_gf'<br /> 2. Navigate to bbp_2g_gf/ucsb/GreenBank/Northridge folder.<br /> 3. Open Green_Bank.inf files with a text editor.<br /> 4. Locate the text &quot;The name of file to store Green Bank&quot;<br /> 5. Note the location of the Green Bank file under the line found in step 4, similar to &quot;/home/scec-00/scottcal/bband/bbp_2g_gf/ucsb/GreenBank/Northridge/Green_1d.soil&quot;.<br /> 6. Replace the path found in Step 5 with just the file name, in the case of Northridge it is &quot;Green_1d.soil&quot;<br /> 7. Save and close the Green_Bank.inf.<br /> 8. Navigate to bbp_2g_gf/ucsb/GreenBank/LomaPrieta folder and repeat steps 3-7. The name of the Green Bank file for LomaPrieta is &quot;Green_1d.LoPr&quot;.<br /> 9. Navigate to bbp_2g_gf/ucsb/GreenBank/Landers folder and repeat steps 3-7. The name of the Green Bank file for Landers is &quot;Green1D.Landers&quot;<br /> <br /> ==== ERROR: test_gensrf (test_genslip.Test_Genslip) ====<br /> The Unit test for Genslip module fails with the following message:<br /> &lt;pre&gt;<br /> ======================================================================<br /> ERROR: test_gensrf (test_genslip.Test_Genslip)<br /> ----------------------------------------------------------------------<br /> Traceback (most recent call last):<br /> File &quot;.../bbp_2g/tests/test_genslip.py&quot;, line 51, in test_gensrf<br /> gen.run()<br /> File &quot;.../bbp_2g/comps/genslip.py&quot;, line 153, in run<br /> ps.run()<br /> File &quot;.../bbp_2g/comps/plot_srf.py&quot;, line 52, in run<br /> shutil.copy2(&quot;%s/%s.ps.png&quot; % (a_tmpdir, self.r_srffile[0:self.r_srffile.find(&quot;.srf&quot;)]), &quot;%s/%s.png&quot; % (a_outdir, self.r_srffile[0:self.r_srffile.find(&quot;.srf&quot;)]))<br /> File &quot;/usr/lib/python2.6/shutil.py&quot;, line 99, in copy2<br /> copyfile(src, dst)<br /> File &quot;/usr/lib/python2.6/shutil.py&quot;, line 52, in copyfile<br /> fsrc = open(src, 'rb')<br /> IOError: [Errno 2] No such file or directory: '.../bbp_2g/tmpdata/3309008/3309008_test_eq.ps.png'<br /> &lt;/pre&gt;<br /> <br /> '''Cause:''' The Genslip module calls the Plot_SRF module to the plot the SRF file. Plot_SRF uses C-shell code to locate and use GMT package to plot the SRF file. This shell code might fail on some flavors of Linux with a message like &quot;Newline in variable name&quot; in the Plot_SRF log file.<br /> <br /> '''Solution:''' This issue can be fixed by editing the plot_SRF.csh file. Here are step by step instructions to fix this issue:<br /> <br /> 1. Locate shell script file: bbp_2g/src/plot/plot_SRF.csh<br /> 2. Open the file in your preferred text editor<br /> 3. Locate the line 'set FIND_GMT = $?'<br /> 4. Replace the line found in step 3 with 'set FIND_GMT = $status'<br /> 5. Locate the section of code that starts with the statement &quot;# FIND MAX. SLIP&quot;<br /> 6. Replace the following line in section found in step 5:<br /> &lt;pre&gt;<br /> set SMAX = `$XYZCODE calc_xy=$CALC_XY type=&quot;${TYPE}&quot; nseg=-1 &lt; $SLIPFILE.srf | \<br /> gawk -v m=$SMAX '{if($3&gt;m)m=$3;}END{printf &quot;%.0f\n&quot;,m;}'`<br /> <br /> with (collapse the statement to a single line by removing '\' at the end of first part of the statement):<br /> <br /> set SMAX = `$XYZCODE calc_xy=$CALC_XY type=&quot;${TYPE}&quot; nseg=-1 &lt; $SLIPFILE.srf | gawk -v m=$SMAX '{if($3&gt;m)m=$3;}END{printf &quot;%.0f\n&quot;,m;}'`<br /> &lt;/pre&gt;<br /> 7. Save the file and exit<br /> <br /> ==== ERROR: test_ucgen (test_ucrmg.Test_UCrmg) ====<br /> The Unit test for Ucrmg module fails with the following message:<br /> &lt;pre&gt;<br /> ======================================================================<br /> ERROR: test_ucgen (test_ucrmg.Test_UCrmg)<br /> ----------------------------------------------------------------------<br /> Traceback (most recent call last):<br /> File &quot;.../bbp_2g/tests/test_ucrmg.py&quot;, line 59, in test_ucgen<br /> ucObj.run()<br /> File &quot;.../bbp_2g/comps/ucrmg.py&quot;, line 161, in run<br /> ps.run()<br /> File &quot;.../bbp_2g/comps/plot_srf.py&quot;, line 52, in run<br /> shutil.copy2(&quot;%s/%s.ps.png&quot; % (a_tmpdir, self.r_srffile[0:self.r_srffile.find(&quot;.srf&quot;)]), &quot;%s/%s.png&quot; % (a_outdir, self.r_srffile[0:self.r_srffile.find(&quot;.srf&quot;)]))<br /> File &quot;/usr/lib/python2.6/shutil.py&quot;, line 99, in copy2<br /> copyfile(src, dst)<br /> File &quot;/usr/lib/python2.6/shutil.py&quot;, line 52, in copyfile<br /> fsrc = open(src, 'rb')<br /> IOError: [Errno 2] No such file or directory: '.../bbp_2g/tmpdata/3309831/test_ucsb.ps.png'<br /> &lt;/pre&gt;<br /> <br /> '''Cause:''' The Ucrmg module calls the Plot_SRF module to the plot the SRF file. Plot_SRF uses C-shell code to locate and use GMT package to plot the SRF file. This shell code might fail on some flavors of Linux with a message like &quot;Newline in variable name&quot; in the Plot_SRF log file.<br /> <br /> '''Solution:''' This issue can be fixed by editing the plot_SRF.csh file. The steps to fix this issue are listed under the solution for &quot;ERROR: test_gensrf (test_genslip.Test_Genslip)&quot; above.<br /> <br /> ==== FAIL: test_site_amp (test_uc_site.Test_UC_Site) ====<br /> <br /> The unit test for UC-Site module might fail with the following message:<br /> &lt;pre&gt;<br /> ======================================================================<br /> FAIL: test_site_amp (test_uc_site.Test_UC_Site)<br /> ----------------------------------------------------------------------<br /> Traceback (most recent call last):<br /> File &quot;.../bbp_2g/tests/test_uc_site.py&quot;, line 92, in test_site_amp<br /> self.failIf(cmp_bbp.cmp_bbp(a_ref_file_no_header, test_file_no_header, tolerance=0.035)!=0,errmsg)<br /> AssertionError: Output file .../bbp_2g/tmpdata/3310633/s04.3comp does not match reference file .../bbp_2g/ref_data/ucsb/s04.site.3comp<br /> &lt;/pre&gt;<br /> <br /> '''Cause:''' The synthetic seismogram generated by the UC-Site module on the user system differs from the reference result included in the Broadband release.<br /> <br /> '''Solution:''' The stochastic nature of the high frequency simulations is considered, and a constant random seed as input for our tests. This is the same constant random seed used to generate the reference results included in the release. This ensures that the time-series generated with unit tests agree with reference results. However, the high frequency codes are more sensitive to changes in compilers and machines due to the algorithm, so small differences that cause the test to fail are generally acceptable. The user is however encouraged to plot the two time-series and visually inspect them to verify they look similar. We are trying to come up with a better comparison for these tests.<br /> <br /> == Appendix C: Technical Notes ==<br /> <br /> == Running Individual Acceptance Tests ==<br /> <br /> The acceptance test script ./tests/AcceptTest.py attempts to run all of the defined tests when executed. However, sometimes it is useful to run an acceptance test in isolation for troubleshooting purposes:<br /> <br /> * Identify the test you want to run. Eg: user-URS-UCSB-SDSU-SDSU<br /> * Move to the ./comps directory and execute that test's XML workflow with run_bbp_2G.py. Using the above example:<br /> &lt;pre&gt;<br /> $ ./run_bbp_2G.py -x ../ref_data/accept_inputs/user-URS-UCSB-SDSU-SDSU.xml<br /> &lt;/pre&gt;<br /> <br /> Since you are running the test outside of AcceptTest.py, you will not see a PASS/FAIL message once the simulation completes. However, you can review the contents of the ./outdata/&lt;SIMID&gt; directory to verify that the correct seismograms and response spectra tables were produced.<br /> <br /> == Manaully Setting Random Number Generator Seed Values ==<br /> <br /> Several of the platform codebases employ random number generators to produce SRFs and seismograms. These random number generators are generally seeded with an initial value (typically an integer) which are hard-coded in the platform. Advanced users may desire to change these seed values.<br /> <br /> Changing the seeds for seismogram synthesis varies depending on which codebase you want to use:<br /> <br /> * URS: Edit ./comps/hfsims_cfg.py, Line 43 &quot;self.RAND_NUM&quot;<br /> * UCSB: Edit ./src/ucsb/Syn1DSCEC/syn1D_LAH.f, Line 183 &quot;iseed&quot;, and recompile with &quot;make&quot;<br /> * SDSU:<br /> ** User event: Edit ./bbp_2g_gf/sdsu/scattering_generic.dat (seed values annotated in file)<br /> ** Validation event: Edit ./bbp_2g_gf/sdsu/&lt;event&gt;/scattering.dat</div> Patrices https://strike.scec.org/scecwiki/index.php?title=Broadband_User_Guide_v11.2.3&diff=5051 Broadband User Guide v11.2.3 2012-05-08T21:34:37Z <p>Patrices: </p> <hr /> <div>'''Version 11.2.3.'''<br /> <br /> If you find errors in this document or sections to be unclear, please either fix them yourself or contact software@scec.org.<br /> <br /> == Installing the Second-Generation Broadband Platform ==<br /> Installing the Broadband Platform involves obtaining a copy of the code and building the required executables. You can either download the platform from the Broadband web site ([http://www.scec.org/research/broadband http://www.scec.org/research/broadband]) or check the code out of SCEC's Subversion repository. Most users should download the platform.<br /> <br /> == System Dependencies ==<br /> The current version of the Broadband Platform is designed to run on standard 64-bit Linux machines. Testing has been performed on SCEC's development servers running Fedora Core 10 (kernel version 2.6.27.41-170.2.117.fc10.x86_64). In this guide we outline how to install the platform into your own account on a Linux computer using the simplest approach.<br /> <br /> == Software Dependencies ==<br /> The Broadband Platform has certain software dependencies.<br /> <br /> Required:<br /> <br /> *Python v2.7 with<br /> **PyGTK<br /> **Matplotlib<br /> **Numpy<br /> **Pyproj<br /> <br /> *Intel compilers (64-bit) v12.0.4<br /> *GNU compilers (gcc, gfortran) v4.5.1<br /> *GNU Fortran 77 v3.4.6<br /> *GMT (Generic Mapping Toolkit)<br /> *ImageMagick<br /> <br /> == Setting Up Your Account ==<br /> For simplicity of installation, we recommend users use a bash shell for the Broadband Platform account. It is possible to get the platform running using other shell's, but we will focus on a bash shell installation. The user environment is a common source of problems since certain environment variables must be defined for the platform to work correctly.<br /> <br /> To check your account, make sure you can run basic commands like ''ls'' and ''cd'' before proceeding.<br /> <br /> == Downloading the Platform ==<br /> &lt;nowiki&gt;Download 4 files from the Broadband website, the code (bbp_dist_&lt;version&gt;.tgz), the data (bbp_data_&lt;version&gt;.tgz), and their checksum files (bbp_dist_&lt;version&gt;.tgz.md5 and bbp_data_&lt;version&gt;.tgz.md5). &lt;/nowiki&gt;The code file is about 100 MB, the data file about 3 GB. After you've downloaded the files to your local Linux system, the next step is to calculate the checksums yourself and compare them to the checksums you downloaded.<br /> <br /> First, verify that the ''md5sum'' command is in your path:<br /> <br /> $&gt; which md5sum<br /> <br /> You should get something like /usr/bin/md5sum. If you see the message 'no md5sum in...', contact your Linux system administrator and ask to have md5sum added to your path.<br /> <br /> Once you can run the ''md5sum'' command, run:<br /> <br /> $&gt; md5sum -c bbp_dist_&lt;version&gt;.tgz.md5<br /> $&gt; md5sum -c bbp_data_&lt;version&gt;.tgz.md5<br /> <br /> You should get the messages<br /> bbp_dist_&lt;version&gt;.tgz.md5: OK<br /> bbp_data_&lt;version&gt;.tgz.md5: OK<br /> <br /> If you get FAILED instead, re-download the tgz files and try again. When it passes, that means the files were downloaded without error.<br /> <br /> Once both files have passed the checksum test, untar the files.<br /> <br /> $&gt; tar xzvf bbp_dist_&lt;version&gt;.tgz file<br /> $&gt; tar xzvf bbp_data_&lt;version&gt;.tgz file<br /> <br /> If multiple users are planning to use the platform on the same system, you only need one copy of the data files per machine. Each user will still need his or her own copy of the code files.<br /> <br /> Alternatively, if you would like access to the latest version of the platform and get frequent but less thoroughly tested improvements, you can check out the platform from SCEC's Subversion repository. Only advanced users should take this approach, outlined in detail in the [[#Advanced Users| Advanced Users section]].<br /> <br /> == User Account Setup ==<br /> <br /> The Broadband platform installation is divided into two parts (1) input Green Functions (GF) data directory (9.3Gb), and (2) BBP home directory (366Mb). <br /> <br /> First, the Green's function libraries are larger, but they are static. The broadband platform reads the data files, but does not change them. <br /> <br /> Second, the remainder of the broadband platform is organized in the BBP home directory. The BBP home directory has a specific directory structure that includes the source code for the scientific programs, the python scripts that link the scientific programs, simulation input directory, temporary and log file directories, and the output data directory where all the platform results are written.<br /> <br /> The BBP home directory will increase in size as you run the platform, because both output data and output log files are written to the home directory. Running the acceptance tests will produce nearly ( 10Gb) of input data (5.2Gb), output data (500Mb), temporary files (2.7Gb), and output log files (250Mb). Once these tests have passed much of this data can be removed. However, the BBP home directory should have at least 10Gb of disk space to insure the acceptance tests can be run when a particular broadband platform software distribution is first installed on a system.<br /> <br /> == Data Directory ==<br /> Input data files called Greens Functions are distributed with the platform. These files are generated using specific velocity structures, so they are often considered region specific. We have GF for three regions including near Loma Prieta, near Landers, and near Northridge.<br /> <br /> The data directory is static, and the data directories are read-only. A single copy can be installed in a shared disk, which can then be shared by multiple users.<br /> <br /> == Setting Environment Variables ==<br /> The BBP source codes and scripts are organized under the broadband platform home directory. The broadband platform home directory is specified in a couple of places during Broadband Platform installation. <br /> <br /> Internal to the Broadband platform software, all broadband platform files (except the Greens Function data files) are in sub-directories of the BBP home directory.<br /> <br /> == BBP Environment Variable ==<br /> We recommend setting both an alias and a environment variable to the BBP home directory. This will help avoid typing it many times.<br /> <br /> If you're running a Bash shell, add the following line to your .bash_profile with your favorite text editor:<br /> <br /> export BBP=/home/scec-00/kumar/bbp_2g<br /> <br /> If you're running a C-shell, add the following line to your .cshrc with your favorite text editor:<br /> <br /> setenv BBP /home/scec-00/kumar/bbp_2g<br /> <br /> * PYTHONPATH<br /> After you've obtained a copy of the project, you'll need to make sure the comps directory is on Python's path so Python can find all the project modules. If you're running a Bash shell, add the following line to your .bash_profile with your favorite text editor:<br /> <br /> export PYTHONPATH=$BBP/comps:$PYTHONPATH<br /> <br /> If you're running a C-shell, add the following line to your .cshrc with your favorite text editor:<br /> <br /> setenv PYTHONPATH $BBP/comps:$PYTHONPATH<br /> <br /> * PATH<br /> In order to successfully compile the project, you'll need to make sure the required compilers directories are in your PATH variable. Broadband requires Intel 64-bit compilers, icc and ifort and GNU Compilers, gcc, g77 and f77 to compile the scientific code.<br /> <br /> If you are planning to run Broadband on SCEC Development servers, make sure you have the following directories in your PATH:<br /> <br /> For Bash Shell (in .bash_profile)<br /> <br /> export PATH=/usr/usc/intel/composerxe-2011.4.191/bin/intel64:/usr/usc/intel/composerxe-2011.4.191/mpirt/bin/intel64:$PATH<br /> <br /> For C-shell (in .cshrc)<br /> <br /> setenv PATH /usr/usc/intel/composerxe-2011.4.191/bin/intel64:/usr/usc/intel/composerxe-2011.4.191/mpirt/bin/intel64:$PATH<br /> <br /> When running elements of the platform over ssh, be sure to enable ssh forwarding (with the -X or -Y options).<br /> <br /> After modifying your login script above, log out and log back into the machine so the changes are reflected in your environment.<br /> <br /> == Edit Install_cfg.py with Installation Directory Paths ==<br /> <br /> You need to tell the platform where it's installed by editing a single python file called &quot;install_cfg.py&quot;. Edit the file bbp_2g/comps/install_cfg.py with your favorite text editor, and edit the lines:<br /> <br /> self.A_INSTALL_ROOT = &lt;bbp_2g directory&gt;<br /> self.A_GF_DIR = &lt;bbp_2g_gf directory&gt;<br /> <br /> as one example:<br /> <br /> self.A_INSTALL_ROOT = /home/scec-00/kumar/bbp_2g<br /> self.A_GF_DIR = /home/scec-00/kumar/bbp_2g_gf<br /> <br /> with the paths on your system to the bbp_2g directory (the source) and the bbp_2g_gf directory (the data) that you unzipped. For example, it could be /home/scottcal/broadband_platform/bbp_2g and /home/scottcal/broadband_platform/bbp_2g_gf.<br /> <br /> Here is some information about these two directories that may be useful as you decide how, and where, to install these two parts of the Broadband Platform on your computer disk system. The data files, and therefore the &lt;bbp_2g_gf directory&gt; are nearly 3GB, but they are static and will not be modified and will not grow in size during use of the platform. The source directory is small to begin. However, this directory will increase as the platform is used, since the results produced by the platform will be stored here.<br /> <br /> == Directory Structure ==<br /> The platform consists of two top-level directories, bbp_2g and bbp_2g_gf. bbp_2g contains the source code, executables, scripts, tests, input, working, and output directories. bbp_2g_gf contains the Green's Functions, input files for the validation events, and other required input files for the various code bases. Note that indata, logs, outdata, tmpdata, and xml are created when the platform is first run, so they will be missing when you first install the platform.<br /> <br /> bbp_2g has the following directories:<br /> *checksums: Contains checksums for bbp_2g_gf files<br /> *comps: The Python scripts to run the platform<br /> *docs: Documentation for the platform<br /> *etc: Miscellaneous utility scripts<br /> *examples: Contains example input files<br /> *indata: An internal directory, used to stage input files<br /> *logs: Contains logs from BBP runs<br /> *outdata: Contains output files from a run<br /> *ref_data: Contains reference files for BBP tests<br /> *start: Put input files for an interactive run here<br /> *src: Source code for BBP modules<br /> *tests: Contains unit and acceptance tests<br /> *tmpdata: An internal directory, used during a run<br /> *xml: Contains XML files which describe simulations and can be used as input<br /> <br /> bbp_2g_gf has the following directories:<br /> *compare: Contains observed seismograms for validation events<br /> *plot: Data files for GMT plots<br /> *sdsu, ucsb, urs: Contains Green's functions, velocity files, and other required inputs for the codebases.<br /> <br /> In general, you will be interacting with the start directory for input files, comps to run the platform, tests to test the platform, and outdata to examine data products.<br /> <br /> === Adding aliases ===<br /> <br /> You may find it helpful to add aliases, so you can quickly and easily move to different broadband directories with a single command. We recommend creating aliases for the home, start, and outdata directories.<br /> <br /> If you are using the Bash shell, you can create aliases by adding the following lines to ~/.bash_profile:<br /> <br /> alias bbp= 'cd &lt;path to bbp_2g directory&gt;'<br /> alias start='cd &lt;path to bbp_2g directory&gt;/start'<br /> alias outdata='cd &lt;path to bbp_2g directory&gt;/outdata'<br /> <br /> If you're using a C shell, edit your ~/.cshrc and add:<br /> <br /> alias bbp cd &lt;path to bbp_2g directory&gt;<br /> alias start cd &lt;path to bbp_2g directory&gt;/start<br /> alias outdata cd &lt;path to bbp_2g directory&gt;/outdata<br /> <br /> Log out and log back in. You'll notice that now you can type the alias command as a shortcut to change directories:<br /> <br /> $&gt; pwd<br /> /home/scec-00/scottcal<br /> $&gt; start<br /> $&gt; pwd<br /> /home/scec-00/scottcal/bband/bbp_2g/start<br /> <br /> This can be a useful way to navigate around the broadband platform directories.<br /> <br /> == Building the Platform ==<br /> Once you have checked out the code, you need to build it. By default, every executable is compiled using the compiler recommended by the code developer. However, if you have limited compiler options or are building the codes on an untested system, you may need to specify non-standard alternative compilers, as described below.<br /> <br /> Before you can build the platform, you need to make sure that the Intel compilers are in your path. This is done automatically on broadband.usc.edu, but on other systems you can check by typing:<br /> <br /> $&gt;which icc<br /> <br /> If you get the message &quot;no icc in ...&quot;, then you'll need to add the Intel compilers to your path. Once the Intel compilers are in your path, you can make the code by cd-ing to the bbp_2g/src directory and typing make:<br /> <br /> $&gt; cd src<br /> $&gt; make<br /> <br /> It takes a minute or two to build the code. You may encounter build warnings; these are fine. However, if you get any build errors, this is a problem and should be investigated.<br /> <br /> By default, every executable is compiled using the compiler recommended by the code developer. Depending on the system, some compilers may not be available to you. You can override the C and Fortran compilers used by editing<br /> <br /> src/makefile<br /> <br /> Uncomment USER_C and set FC and CC to the compilers you wish. For example:<br /> <br /> Before:<br /> <br /> #USER_C=1<br /> FC=f77<br /> CC=gcc<br /> <br /> After (an example, you may choose different compilers):<br /> <br /> USER_C=1<br /> FC=gfortran<br /> CC=gcc<br /> <br /> Note that not all compiler combinations have been thoroughly tested. You may encounter build errors with untested compiler combinations. If you encounter any errors while building the platform, consult the Troubleshooting section at the end of this user guide for know issues and their solutions.<br /> <br /> Once the platform has been successfully built, you can move on to running the tests to verify that all components are working correctly.<br /> <br /> == Advanced Users ==<br /> Alternatively, if you would like access to the latest version of the platform, to get frequent but less thoroughly tested improvements, you can check out the platform from SCEC's Subversion version control repository on source.usc.edu. Only advanced users should follow this approach. If you are unsure, you should download the code as outlined in [[#Downloading the Platform|Downloading the Platform]] and skip this section.<br /> <br /> You may need to request access from the SCEC system administrator, John Yu ([mailto:johnyu@usc.edu johnyu@usc.edu]). Make sure you have subversion in your path before beginning.<br /> <br /> Once you have access, you'll need to decide if you want a stable tagged version, or the latest version in the repository. For a stable version, open a terminal window on the system of your choice and type:<br /> <br /> $&gt; svn checkout https://source.usc.edu/svn/broadband/tags/&lt;stable version&gt; bbp_2g<br /> <br /> For the latest version, type:<br /> <br /> $&gt; svn checkout https://source.usc.edu/svn/broadband/trunk bbp_2g<br /> <br /> This will check out the project to your local machine. It contains the source code, tests, and some example files. You also need to obtain a copy of the Broadband Platform data files, containing the Green's tensors. They are too large to be stored in version control. You can obtain a copy from SCEC software distribution server. If you are working on SCEC development server, you might be able to create a symbolic link to data folder. Please contact [[#User_Support|User Support]] to get a location of the data folder on the SCEC development server. If you are not working on SCEC development server, or don't have an SCEC Linux login account, you can get a archive (.tgz) file of the Green's functions from the same download site you obtained this guide.<br /> <br /> If you know where a read-accessible installation of the green functions data directories you can create a link to that location. This can save disk space in some cases.<br /> <br /> ln -s /home/scec-00/scottcal/bband/bbp_2g_gf &lt;path to your gf directory&gt;<br /> <br /> Periodically you should check for updates to the code. To do so, go to your bbp_2g directory and type<br /> <br /> $&gt; svn update<br /> <br /> This will pull down any code updates that have been made in the repository. After you update, make the code again (detailed in [[#Building the Platform|Building the Platform]]) so that any code changes are captured in the executables.<br /> <br /> == Running the Broadband Platform ==<br /> We recommend users initiate all Broadband Platform runs from the &quot;start&quot; directory. The start directory is a collection point for input files for a particular simulation.<br /> <br /> Assuming the user is starting at BBP home directory, the user should move to the start directory and then run the Checksum, Unit and Acceptance tests to confirm the Broadband Platform software installation is operating as expected.<br /> <br /> $&gt; cd start<br /> <br /> == Running Checksum, Unit, and Acceptance Tests ==<br /> The broadband platform contains three kinds of tests. The checksum tests verify that the data files were copied correctly and you have all the files that are expected. Unit tests run each module using a set of input files, and compare the results against known outputs. They verify that each module has been built and is working correctly. Acceptance tests verify that the modules are working correctly together. They test the platform end-to-end using different combinations with known inputs and compare the results. All the possible module combinations for both user-defined and validation events are tested as checks against integration errors.<br /> <br /> Begin with the checksum tests. Once they past, run the unit tests and finally the acceptance tests.<br /> <br /> == Running Checksum Tests ==<br /> To run the checksum tests, change to the checksums directory and run md5sum_check.py.<br /> <br /> From the BBP home directory:<br /> <br /> $&gt; cd checksums<br /> $&gt; ./md5sum_check.py<br /> <br /> It takes about 5 minutes to compute the checksums. If a checksum disagrees, that means that the contents of the datafile were not what was expected. Try reinstalling the data files and try again. If you continue to get a checksum error, contact support.<br /> <br /> Once the checksums agree, move on to the unit tests.<br /> <br /> == Running Unit Tests ==<br /> To run the unit tests, change to the tests directory and run UnitTests.py.<br /> <br /> From the BBP home directory:<br /> <br /> $&gt; cd tests<br /> $&gt; ./UnitTests.py<br /> <br /> The unit tests take about 15 minutes to run. When they're complete, the console will either print &quot;OK&quot; or how many tests failed. If a test has failed, first check that you have built the executables.You can rerun just the specific test that failed (test_&lt;module&gt;.py). If the test is still failing, also verify that you have the ref_data directory, since it contains the input and reference files. If you're looking for more information about the failure, you can consult the Unit Tests log file in bbp_2g/logs/unit_test.log . If you can't determine the reason for the failure, contact support.<br /> <br /> Once the unit tests all pass, proceed to the acceptance tests. If there are any failure or errors while running the unit tests, consult the Troubleshooting section at the end of this user guide for know issues and their solutions.<br /> <br /> == Running Acceptance Tests ==<br /> Make sure the unit tests pass before moving on to the acceptance tests. To run the acceptance tests, change to the tests directory (if you're not there already) and run AcceptTests.py. <br /> The acceptance tests take a long time to run, around 20 hours<br /> <br /> From the BBP home directory:<br /> <br /> $&gt; cd tests<br /> $&gt; ./AcceptTests.py &amp;&gt; accept.out &amp;<br /> <br /> Since the tests take so long to run (twenty hours), you should run them as a background process, and redirect their output to a log file, as shown in the command above.<br /> <br /> You can check the progress by tailing the log file.<br /> <br /> $&gt; tail accept.out<br /> <br /> When all the acceptance tests are completed, the AcceptTests.py script will either print &quot;OK&quot; or how many tests failed. <br /> <br /> Acceptance test failures indicate that the modules are not integrated correctly. Like with the unit tests, verify that you have the ref_data directory. If a certain acceptance test fails, you can get more information by consulting the acceptance test logs in bbp_2g/logs/acceptance_tests_logs/&lt;test that failed&gt;.log . If you can't determine the reason for the failure, contact [[support]].<br /> <br /> Since the acceptance tests can take a long time to run, you may wish to resume where you left off. This feature is supported automatically. If you do not wish to resume, delete the resume file in ref_data/accept_inputs/resume.txt. If there are any failure or errors while running the acceptance tests, consult the Troubleshooting section at the end of this user guide for know issues and their solutions.<br /> <br /> == Types of Broadband Platform Simulations == <br /> <br /> The platform supports two kinds of simulations, validation events and user-defined events. Validation simulations are performed using a historical event, and are directly compared to observed seismograms using goodness-of-fit. User-defined events are run using a rupture description provided by the user which may not necessarily be a historical earthquake.<br /> <br /> When you run a simulation, the platform assigns an ID to it. This ID can be used to track the simulation and locate the output data products.<br /> <br /> To supply input files to the platform, put them in the start directory. Extensions are important - the platform recognizes station lists (.stl), SRF files (.srf), and simple source descriptions (.src). If there are multiple files of a type, the platform will prompt the user to select one.<br /> <br /> To perform a simulation, a user selects between different required and optional modules. Below we present a summary of the various modules.<br /> <br /> == Modules ==<br /> The broadband platform consists of a series of modules. There are two main types of modules, science modules and utility modules. Science modules are those for which the platform has multiple implementations, provided by different coding research groups. Utility modules only have 1 implementation. A schematic of the available modules and their flow relationships is shown below:<br /> <br /> == Science Modules ==<br /> All simulations must include a low-frequency, high-frequency, and site response science module. Simulations may include an optional rupture generation science module. Users may select between the following different implementations of each of these modules:<br /> <br /> Rupture generation:URS, UCSB<br /> <br /> Low-frequency:URS, UCSB<br /> <br /> High-frequency:URS, UCSB, SDSU<br /> <br /> Site response:URS, UCSB, SDSU<br /> <br /> == Utility Modules ==<br /> A spectral response utility module is automatically run after the site response module. Additionally, users may select an optional goodness-of-fit utility module to run at the conclusion of the simulation. In the case of a user-defined event, users select a historical event or previously run simulation to use as the comparison for goodness-of-fit.<br /> <br /> == Platform Directory ==<br /> <br /> A broadband platform distribution is organized in a specific directory structure that separates the input data sets, the python scripts, the simulation configuration files, log files, and output data files.<br /> <br /> When running Broadband Platform simulations, standard procedure is to place the simulation input files in the start directory and invoke the Broadband platform scripts from there.<br /> <br /> From the BBP home directory:<br /> <br /> $&gt; cd start<br /> $&gt; run_bbp_2G.py<br /> <br /> Simulation output results will be written into the bbp_home/output<br /> <br /> == Validation Simulations ==<br /> To run a validation simulation, go to the comps directory and run run_bbp_2G.py. The platform will ask you a series of questions. Answer 'y' to &quot;Do you want to perform a validation run?&quot;<br /> <br /> From the BBP home directory:<br /> <br /> $&gt; cd start<br /> $&gt; run_bbp_2G.py<br /> Welcome to the SCEC Broadband Platform.<br /> Please select the modules you want to run.<br /> Do you want to perform a validation run (y/n)? y<br /> Do you want to validate with:<br /> Northridge (1)<br /> Loma Prieta (2)<br /> Landers (3)<br /> ?<br /> ...<br /> <br /> No input files are required by the user. However, you may wish to run with a reduced station list to speed up the computations. You can put your own station list into the start directory (the format is described in [[#Station File List|section 5.3]]). Note that any stations which do not have observed seismograms will not be included in the automatically generated goodness-of-fit comparison.<br /> <br /> In addition to the low-frequency modules which compute seismograms using 1D Green's Tensors, validation events can also be run using precomputed 3D seismograms to supply the low-frequency.<br /> <br /> == User-defined Simulations ==<br /> To run a user-defined simulation, two input files are required, a rupture description and a station list. The rupture description can either be in SRF format or a simplified source description (the format is described in [[#Simple source description|section 5.1]]). To run a user-defined simulation, run run_bbp_2G.py.<br /> <br /> From the BBP home directory:<br /> <br /> $&gt; cd start<br /> $&gt; run_bbp_2G.py<br /> Welcome to the SCEC Broadband Platform.<br /> Please select the modules you want to run.<br /> Do you want to perform a validation run (y/n)? y<br /> Do you want to run a rupture generator (y/n)? <br /> ...<br /> <br /> You may then choose if you want to run a rupture generator. This is necessary if you're supplying a simple rupture description. If you're supplying an SRF file, you can skip this. Next you can select from different module implementations. Finally, you have the option to run goodness-of-fit against either observed seismograms or another simulation.<br /> <br /> ...<br /> Do you want to run goodness of fit (y/n)? y<br /> What reference files would you like to compare to? Enter a simulation ID or a scenario name: &lt;comparison&gt;<br /> Enter a label to use for the comparison seismograms: &lt;label&gt;<br /> <br /> The label will be used in GoF plots to distinguish one set of results from the other.<br /> <br /> The user-defined events must be within one of the regions supported by the platform - Southern California, Northern California, or the Mojave. The platform will automatically select a region based on the event hypocenter. If the event falls outside of these regions, you'll get an error.<br /> <br /> == Logging ==<br /> During the run, log files will be produced in logs/&lt;simulation ID&gt;/&lt;simulation ID&gt;.&lt;module name&gt;.log. If the platform fails, this is a good place to look to determine the error. Additionally, any fatal errors will be recorded in fatal_error.log.<br /> <br /> Metadata capturing all the executable calls is located in tmpdata/&lt;simulation ID&gt;/metadata.txt for careful tracing of exactly what was called. Both the log files and metadata can be useful if troubleshooting an issue.<br /> <br /> == Data Products ==<br /> The platform produces a variety of data products. &lt;nowiki&gt;All data products are located in outdata/&lt;simulation ID&gt;. &lt;/nowiki&gt;On most Linux systems, you can show images using display:<br /> <br /> $&gt; display &lt;PNG file&gt;<br /> <br /> Make sure you have X11 forwarding enabled.<br /> <br /> === Station map ===<br /> To help visualize the stations in relationship to the fault, the platform produces a PNG file displaying station locations with red circles and the fault plane with a black line, on an image of California. You can find this file in outdata/&lt;simulation ID&gt;/station_map.png.<br /> <br /> === Seismograms ===<br /> When running the platform, you have the option to output velocity and acceleration seismograms, for each station. Plots of these files can be found in outdata/&lt;simulation ID&gt;/&lt;simulation ID&gt;.&lt;station&gt;_&lt;velocity or acceleration&gt;_seis.png.<br /> <br /> The raw seismogram data is available in outdata/&lt;simulation ID&gt;/&lt;simulation ID&gt;.&lt;station&gt;.vel.bbp (velocity) and outdata/&lt;simulation ID&gt;.&lt;station&gt;.acc.bbp (acceleration). Its format is described in [[#BBP seismograms|section 5.4]].<br /> <br /> To compare seismogram data, you can run comps/plotit.py with two seismograms. It will plot them both for comparison. From the comps directory, run:<br /> <br /> $&gt; plotit.py &lt;path to seismogram 1&gt; &lt;path to seismogram 2&gt;<br /> <br /> === Response spectra ===<br /> The respect code, run at the end of each simulation, calculates the response spectra for each station. The raw respect data is located at<br /> <br /> From the BBP home directory:<br /> <br /> outdata/&lt;simulation ID&gt;/&lt;simulation ID&gt;.&lt;station&gt;.rsp<br /> <br /> in the format described in [[#Response spectra|section 5.5]].<br /> <br /> === Goodness-of-fit ===<br /> If you run goodness-of-fit, several additional data products are produced. The goodness-of-fit comparison is performed by comparing the response spectra of a set of calculated seismograms to seismograms from another simulation or observed seismograms. For each station involved in the comparison, a plot comparing the response spectra can be found at outdata/&lt;simulation ID&gt;/&lt;comparison label&gt;_&lt;simulation ID&gt;_&lt;station&gt;_rsp.png. A plot showing the seismograms on top and bottom can be found at outdata/&lt;comparison label&gt;_&lt;simulation ID&gt;_&lt;station&gt;_overlay.png. The goodness-of-fit plot can be found at gof-&lt;comparison label&gt;-&lt;simulation ID&gt;_r0-&lt;cutoff distance&gt;.png.<br /> <br /> Note that at least 3 stations must be run for goodness-of-fit to be valid. If fewer than 3 stations are run, no goodness of fit calculation will be performed.<br /> <br /> === Rupture files ===<br /> When a user-defined event is simulated, the user has the option to run a rupture generator. This generator produces an SRF file, found in outdata/&lt;simulation ID&gt;/*.srf. This file can be put in the start directory and used in future runs. Additionally, the platform produces a plot of the cumulative slip on the fault surface, outdata/&lt;simulation ID&gt;/&lt;SRF prefix&gt;.png.<br /> <br /> == Platform Modes ==<br /> The platform can be run in multiple modes. The default is interactive mode, in which the user is prompted to answer a series of questions. Once all the information has been gathered, the run begins.<br /> <br /> For a large number of runs, or if the user is repeating a specific run, this can be tedious. The platform provides two other ways to describe a run, with an option file or an XML description.<br /> <br /> An option file provides responses to all the questions that the platform poses. The format is described in [[#Option File|section 5.6]], but it's basically a text file, 1 entry per line, with support for comments. It can be fed to the platform using the -o option.<br /> <br /> The platform will also accept XML files containing a full description of a run. The schema for these files is given in [[#XML workflow description schema|section 5.7]]. These files are also produced by the platform after every simulation, and placed in xml/&lt;simulation ID&gt;.xml. So if you want to rerun a simulation, you can point the platform to the XML file from that simulation using the -x option. Note that a new simulation ID will be assigned to the run, so there is no risk of overwriting previous simulation results.<br /> <br /> == Available Options ==<br /> To get a list of the current available options, run run_bbp_2G.py with the -h flag.<br /> <br /> $&gt; run_bbp_2G.py -h<br /> Usage: run_bbp_2G.py [options]<br /> Options:<br /> -h, --help Show this help message and exit<br /> -x XML_FILE, --xml-file=XML_FILE Run using XML description of workflow<br /> -s SIM_ID, --simID=SIM_ID Force a simID<br /> -o OPTFILE, --option-file=OPTFILE File containing responses to interactive platform prompts<br /> -v, --version Broadband platform version<br /> -c, --compact Compact output results. Remove temporary files for simulations that complete successfully.<br /> -g, --generate-xml Generates the XML description but does not run the platform<br /> -l LOG_FILE, --log=LOG_FILE Store all output in a file<br /> <br /> == Cleanup ==<br /> After a while, you may find that your indata, tmpdata, outdata, and logs directories are getting cluttered with files from past runs. If you wish to delete these old files, you can use the clean_directories.sh script in the etc directory.<br /> <br /> From the BBP home directory:<br /> <br /> $&gt; cd etc<br /> $&gt; ./clean_directories &lt;days&gt;<br /> <br /> Any simulation ID directories in the indata, tmpdata, outdata, and logs directories which were last accessed &lt;days&gt; days or longer ago will be deleted. If you have a few directories you want to keep, either copy them somewhere else, or copy them to a directory name that's not all digits and they won't be deleted.<br /> <br /> == Examples ==<br /> Below are some examples that you can try using the sample files in the examples directory. Make sure all the tests pass before you try this. You should be in the comps directory when you start these examples:<br /> <br /> From the BBP home directory:<br /> <br /> $&gt; cd comps<br /> <br /> == Sample Validation Run ==<br /> You don't need to move any files for this. Notice that 3D seismograms are a low-frequency option, since you're running a validation event.<br /> <br /> From the BBP home directory:<br /> <br /> $&gt; cd start<br /> $&gt; run_bbp_2G.py <br /> Welcome to the SCEC Broadband Platform.<br /> Please select the modules you want to run.<br /> Do you want to perform a validation run (y/n)? y<br /> Do you want to validate with:<br /> Northridge (1)<br /> Loma Prieta (2)<br /> Landers (3)<br /> ?1<br /> Do you want to<br /> run all validation stations (1)<br /> select a station list (2)<br /> ?1<br /> Choose a source of low frequency seismograms:<br /> URS module (1)<br /> URS 3D seismograms (2)<br /> UCSB module (3)<br /> SDSU module (4)<br /> SDSU 3D seismograms (5)<br /> ?2<br /> Choose a high frequency module:<br /> URS (1)<br /> UCSB (2)<br /> SDSU (3)<br /> ?1<br /> Choose a site response module:<br /> URS (1)<br /> UCSB (2)<br /> SDSU (3)<br /> ?1<br /> Do you want to plot velocity seismograms (y/n)? y<br /> Do you want to plot acceleration seismograms (y/n)? y<br /> <br /> This simulation takes about 10 minutes. Once it's complete the platform will tell you:<br /> <br /> You can find results in &lt;path to bbp_2g install&gt;/outdata/&lt;simulation ID&gt; .<br /> <br /> In that directory you will find:<br /> <br /> *Velocity seismograms (&lt;simulation ID&gt;.&lt;station&gt;.bbp)<br /> *Acceleration seismograms (&lt;simulation ID&gt;.&lt;station&gt;.acc.bbp)<br /> *Plots of velocity seismograms (&lt;simulation ID&gt;.&lt;station&gt;_velocity_seis.png)<br /> *Plots of acceleration seismograms (&lt;simulation ID&gt;.&lt;station&gt;_acceleration_seis.png)<br /> *Response spectra files (&lt;simulation ID&gt;.&lt;station&gt;.rsp)<br /> *Plots comparing simulated and observed seismograms (Northridge_&lt;simulation ID&gt;_&lt;station&gt;_overlay.png)<br /> *Plots comparing simulated and observed response spectra (Northridge_&lt;simulation ID&gt;_&lt;station&gt;_rsp.png)<br /> *Overall goodness-of-fit plots (gof-Northridge-&lt;simulation ID&gt;_r0-25.png)<br /> <br /> == Sample Validation run, custom stations ==<br /> If the validation runs aren't performed with 3D low-frequency, it can take a long time, up to 10 minutes per station. Sometimes you might want to run with a reduced station list so the simulation will run faster.<br /> <br /> Copy the files in example/valid_custom_stations into the start directory. Take a look at the format of the station file:<br /> <br /> $&gt; more valid_test_stat.stl <br /> #Required: lon, lat, station name, distance to fault plane, Vs30<br /> #Optional: low freq corner, high freq corner<br /> #Unused: station information<br /> #lon lat stationdist Vs30 LF corner HF corner station information<br /> -118.6417 34.5640 cast 20.47 450 0.120 23.0 CSMIP peer.berkeley.edu/nga<br /> -118.4180 34.0628 lacn 22.82 278 0.140 23.0 CSMIP peer.berkeley.edu/nga<br /> -118.8811 34.2886 moor 24.16 405 0.160 23.0 CSMIP peer.berkeley.edu/nga<br /> <br /> Now, run the platform, using a station list:<br /> <br /> From the BBP Home directory<br /> <br /> $&gt; cd start<br /> $&gt; run_bbp_2G.py <br /> Welcome to the SCEC Broadband Platform.<br /> Please select the modules you want to run.<br /> Do you want to perform a validation run (y/n)? y<br /> Do you want to validate with:<br /> Northridge (1)<br /> Loma Prieta (2)<br /> Landers (3)<br /> ?1<br /> Do you want to<br /> run all validation stations (1)<br /> select a station list (2)<br /> ?2<br /> <br /> If you have multiple station list files in your start directory, you may see the following prompt asking you to select one. If you only have one, the platform will select it automatically.<br /> <br /> Found multiple BBP station list files in the start directory. Please select one:<br /> nr_one_stat.stl (1)<br /> valid_test_stat.stl (2)<br /> ?2<br /> Choose a source of low frequency seismograms:<br /> URS module (1)<br /> URS 3D seismograms (2)<br /> UCSB module (3)<br /> SDSU module (4)<br /> SDSU 3D seismograms (5)<br /> ?3<br /> Choose a high frequency module:<br /> URS (1)<br /> UCSB (2)<br /> SDSU (3)<br /> ?2<br /> Choose a site response module:<br /> URS (1)<br /> UCSB (2)<br /> SDSU (3)<br /> ?2<br /> Do you want to plot velocity seismograms (y/n)? y<br /> Do you want to plot acceleration seismograms (y/n)? y<br /> <br /> Again, when the run completes in about 15 minutes you can find results in the output directory. You'll notice far fewer files, as only 3 stations were run instead of 133. The goodness-of-fit plots won't look very good - more stations are really needed to get an accurate plot.<br /> <br /> == Sample User-defined run with source description ==<br /> Next let's try running a user-defined event. Copy examples/user_rup_gen/nr_one_stat.stl and examples/user_rup_gen/user_eq.src to the start directory. user_eq.src is a simple source description. Its format is outlined in [[#XML workflow description schema|section 5.1]]. Since this is a user-defined event, precomputed 3D seismograms aren't a valid option.<br /> <br /> $&gt; run_bbp_2G.py <br /> Welcome to the SCEC Broadband Platform.<br /> Please select the modules you want to run.<br /> Do you want to perform a validation run (y/n)? n<br /> Do you want to run a rupture generator (y/n)? y<br /> Rupture generators:<br /> URS (1)<br /> UCSB (2)<br /> ?1<br /> Using region: Southern California<br /> Choose a low frequency module:<br /> URS (1)<br /> UCSB (2)<br /> ?2<br /> Found multiple BBP station list files in the start directory. Please select one:<br /> nr_one_stat.stl (1)<br /> valid_test_stat.stl (2)<br /> ?1<br /> Choose a high frequency module:<br /> URS (1)<br /> UCSB (2)<br /> SDSU (3)<br /> ?2<br /> Choose a site response module:<br /> URS (1)<br /> UCSB (2)<br /> SDSU (3)<br /> ?1<br /> Do you want to plot velocity seismograms (y/n)? y<br /> Do you want to plot acceleration seismograms (y/n)? y<br /> Do you want to run goodness of fit (y/n)? n<br /> <br /> Since this run only includes one station, it will run in about 5 minutes. In the output directory you'll notice there are no goodness-of-fit or files, since we didn't run goodness-of-fit. However, there is also a map file (station_map.png), showing the fault plane and the stations, and a plot of the rupture slip (user_eq.png). The SRF generated by the rupture generator is in user_eq.srf; this file could be used in future runs. The filenames of the rupture slip plot and SRF are taken from the rupture description filename.<br /> <br /> == Sample User-defined run with SRF file and goodness-of-fit ==<br /> Finally, try a run with an SRF file and run goodness-of-fit on the results. Copy in examples/user_no_rup_gen/ucsb_modSRF_0.srf and examples/user_no_rup_gen/nr_three_stat.stl<br /> <br /> $&gt; run_bbp_2G.py <br /> Welcome to the SCEC Broadband Platform.<br /> Please select the modules you want to run.<br /> Do you want to perform a validation run (y/n)? n<br /> Do you want to run a rupture generator (y/n)? n<br /> Using region: Southern California<br /> Choose a low frequency module:<br /> URS (1)<br /> UCSB (2)<br /> ?1<br /> Found multiple BBP station list files in the start directory. Please select one:<br /> nr_one_stat.stl (1)<br /> valid_test_stat.stl (2)<br /> nr_three_stat.stl (3)<br /> ?3<br /> Choose a high frequency module:<br /> URS (1)<br /> UCSB (2)<br /> SDSU (3)<br /> ?3<br /> Choose a site response module:<br /> URS (1)<br /> UCSB (2)<br /> SDSU (3)<br /> ?1<br /> Do you want to plot velocity seismograms (y/n)? y<br /> Do you want to plot acceleration seismograms (y/n)? y<br /> Do you want to run goodness of fit (y/n)? y<br /> What reference files would you like to compare to? Enter a simulation ID or a scenario name: Northridge<br /> Enter a label to use for the comparison seismograms: nr<br /> <br /> The reference files can either be a scenario event or a simulation ID previously run. The label is just for the figures when comparisons are plotted.<br /> <br /> This run will take about 15 minutes, and the results can be found in the appropriate outdir. Again, the goodness of fit measures will look poor due to the few stations involved in the comparison. If you had fewer than 3 stations, no goodness-of-fit plots would be produced. However, response spectra comparison plots will still be generated.<br /> <br /> = File Formats =<br /> This section offers descriptions of various file formats in the broadband platform.<br /> <br /> == Simple source description ==<br /> This is the format for the simple source description. It is not whitespace sensitive. The filename must end in .src for the platform to identify it as a source description.<br /> <br /> MAGNITUDE = &lt;magnitude&gt;<br /> FAULT_LENGTH = &lt;length of fault&gt;<br /> DLEN = &lt;DX, along length&gt;<br /> FAULT_WIDTH = &lt;down-dip fault width&gt;<br /> DWID = &lt;DY, along width&gt;<br /> DEPTH_TO_TOP = &lt;depth of fault below surface&gt;<br /> STRIKE = &lt;nowiki&gt;&lt;strike&gt;&lt;/nowiki&gt;<br /> RAKE = &lt;rake&gt;<br /> DIP = &lt;dip&gt;<br /> LAT_TOP_CENTER = &lt;latitude of top center point in fault plane&gt;<br /> LON_TOP_CENTER = &lt;longitude of top center point in fault plane&gt;<br /> HYPO_ALONG_STK = &lt;along strike location of hypocenter (0.0 = middle)&gt;<br /> HYPO_DOWN_DIP = &lt;down dip location of hypocenter (0.0 = top)&gt;<br /> DT = &lt;nowiki&gt;&lt;dt&gt;&lt;/nowiki&gt;<br /> SEED = &lt;random seed used in calculations&gt;<br /> CORNER_FREQ = &lt;corner frequency to use&gt;<br /> <br /> == SRF rupture description ==<br /> Details of the Standard Rupture Format (SRF) are given in more detail in the accompanying document. The general fault surface is represented by a distribution of point sources, and it can support one or more planes. The platform produces SRFs as output from rupture generators, but a user can also supply an SRF file as input for user-defined simulations. SRF filenames must end with the suffix .srf for the platform to correctly identify them.<br /> <br /> == Station File List ==<br /> The user may specify a list of stations, matching the following format:<br /> <br /> #optional<br /> %comment<br /> # lines<br /> &lt;nowiki&gt;&lt;lon&gt; &lt;lat&gt; &lt;stat name&gt; &lt;distance to fault trace&gt; &lt;Vs30&gt; &lt;LF corner&gt; &lt;HF corner&gt; &lt;stat info&gt;&lt;/nowiki&gt;<br /> ...<br /> <br /> The station list filename needs to end in .stl for the platform to recognize it as a station list.<br /> <br /> == BBP seismograms ==<br /> All intermediate and output seismograms are produced in a 4-column text format, whether velocity or acceleration.<br /> <br /> # optional<br /> % comment<br /> # lines<br /> &lt;nowiki&gt;&lt;timestamp&gt; &lt;North/South&gt; &lt;East/West&gt; &lt;Up/Down&gt;&lt;/nowiki&gt;<br /> ...<br /> <br /> Time is in seconds and motion is in cm/s (velocity) or cm/s/s (acceleration) unless otherwise specified in the header. Velocity filenames end in .vel.bbp; accelerations in .acc.bbp.<br /> <br /> == Response spectra ==<br /> The response spectra file is in 4-column text format.<br /> <br /> # optional<br /> % comment<br /> # lines<br /> &lt;nowiki&gt;&lt;period (sec)&gt; &lt;North/South&gt; &lt;East/West&gt; &lt;Up/Down&gt;&lt;/nowiki&gt;<br /> ...<br /> <br /> The platform samples response spectra at 112 periods, 0.01-20 sec and outputs pseudo spectral acceleration in units of g.<br /> <br /> == Option File ==<br /> Option files contain responses to the prompts in the platform. You can use them with the -o option to run_bbp_2G.py. The responses have to match the prompts exactly. For example, if you craft an option file assuming there is only one station list in the start directory (and therefore the user isn't prompted to select one) but then it is run with multiple station lists in the start directory, this will cause the run to abort. Option files are recommended to perform a series of runs with different inputs or different modules. If you have a run you perform regularly, it's better practice to run the platform with the -g option and the option file to produce an XML description, which are more complete descriptions of the workflow.<br /> <br /> #optional comments<br /> %using either symbol<br /> n #comments<br /> y % can go<br /> 1 # here<br /> ...<br /> <br /> Use with:<br /> <br /> $&gt; run_bbp_2G.py -o &lt;option file&gt;<br /> <br /> == XML workflow description schema ==<br /> Each time the platform is invoked, an XML file is produced describing the workflow, obeying the following schema:<br /> <br /> &lt;nowiki&gt;&lt;xs:schema xmlns:xs=&quot;http://www.w3.org/2001/XMLSchema&quot;&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:element name= &quot;BBP_Run_Specification&quot; minOccurs= &quot;1&quot; maxOccurs= &quot;1&quot;&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:attribute name=&quot;version&quot; type = &quot;xs:string&quot; use = &quot;required&quot; /&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:complexType&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:sequence&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:element name= &quot;Validation_Run&quot; minOccurs= &quot;0&quot; maxOccurs = &quot;1&quot;&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:attribute name= &quot;event&quot; type= &quot;xs:string&quot; use= &quot;required&quot; /&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:attribute name= &quot;input_station_file&quot; type = &quot;xs:string&quot; /&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:attribute name= &quot;subset&quot; type = &quot;xs:boolean&quot; use = &quot;required&quot; /&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;/xs:element&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:element name= &quot;BBP_Modules&quot;&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:complexType&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:sequence&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:element name = &quot;BBP_Module&quot; maxOccurs = &quot;unbounded&quot; &gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:complexType&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:sequence&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:element name= &quot;name&quot; type=&quot;xs:string&quot; /&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:element name= &quot;staged_files&quot; &gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:complexType&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:sequence&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:element name=&quot;file&quot; type=&quot;xs:string&quot; maxOccurs= &quot;unbounded&quot;/&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;/xs:sequence&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;/xs:complexType&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;/xs:element&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:element name= &quot;arguments&quot; &gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:complexType&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:sequence&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:element name=&quot;argument&quot; type=&quot;xs:string&quot; maxOccurs=&quot;unbounded&quot;&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:attribute name= &quot;type&quot; type= &quot;xs:string&quot; user= &quot;required&quot; /&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;/xs:element&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;/xs:sequence&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;/xs:complexType&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;/xs:element&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;/xs:sequence&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;/xs:complexType&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;/xs:element&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;/xs:sequence&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;/xs:complexType&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;/xs:element&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;/xs:sequence&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;/xs:complexType&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;/xs:element&gt;&lt;/nowiki&gt;<br /> <br /> These files are difficult to construct by hand, but can be generated using the -g flag when running run_bbp_2G.py.<br /> <br /> = User Support =<br /> If you run into bugs with the platform, you can open a trouble ticket at the [http://northridge.usc.edu/trac/broadband Broadband Trac site].<br /> <br /> Check to see if there has already been a ticket opened for the bug. If you are unable to get the platform to run, you can get direct user support by emailing [mailto:software@intensity.usc.edu software@intensity.usc.edu].<br /> <br /> = Appendix A: Possible Module Permutations =<br /> === Validation Events ===<br /> <br /> {| class=&quot;wikitable&quot; | border=&quot;1&quot;<br /> | Permutation #<br /> | Low-frequency module<br /> | High-frequency module<br /> | Site response<br /> <br /> |-<br /> | &lt;center&gt;1&lt;/center&gt;<br /> | &lt;center&gt;URS 1D&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;2&lt;/center&gt;<br /> | &lt;center&gt;URS 1D&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;3&lt;/center&gt;<br /> | &lt;center&gt;URS 1D&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;4&lt;/center&gt;<br /> | &lt;center&gt;URS 1D&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;5&lt;/center&gt;<br /> | &lt;center&gt;URS 1D&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;6&lt;/center&gt;<br /> | &lt;center&gt;URS 1D&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;7&lt;/center&gt;<br /> | &lt;center&gt;URS 1D&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;8&lt;/center&gt;<br /> | &lt;center&gt;URS 1D&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;9&lt;/center&gt;<br /> | &lt;center&gt;URS 1D&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;10&lt;/center&gt;<br /> | &lt;center&gt;URS 3D precomputed&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;11&lt;/center&gt;<br /> | &lt;center&gt;URS 3D precomputed&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;12&lt;/center&gt;<br /> | &lt;center&gt;URS 3D precomputed&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;13&lt;/center&gt;<br /> | &lt;center&gt;URS 3D precomputed&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;14&lt;/center&gt;<br /> | &lt;center&gt;URS 3D precomputed&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;15&lt;/center&gt;<br /> | &lt;center&gt;URS 3D precomputed&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;16&lt;/center&gt;<br /> | &lt;center&gt;URS 3D precomputed&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;17&lt;/center&gt;<br /> | &lt;center&gt;URS 3D precomputed&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;18&lt;/center&gt;<br /> | &lt;center&gt;URS 3D precomputed&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;19&lt;/center&gt;<br /> | &lt;center&gt;UCSB 1D&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;20&lt;/center&gt;<br /> | &lt;center&gt;UCSB 1D&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;21&lt;/center&gt;<br /> | &lt;center&gt;UCSB 1D&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;22&lt;/center&gt;<br /> | &lt;center&gt;UCSB 1D&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;23&lt;/center&gt;<br /> | &lt;center&gt;UCSB 1D&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;24&lt;/center&gt;<br /> | &lt;center&gt;UCSB 1D&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;25&lt;/center&gt;<br /> | &lt;center&gt;UCSB 1D&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;26&lt;/center&gt;<br /> | &lt;center&gt;UCSB 1D&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;27&lt;/center&gt;<br /> | &lt;center&gt;UCSB 1D&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;28&lt;/center&gt;<br /> | &lt;center&gt;SDSU 1D&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;29&lt;/center&gt;<br /> | &lt;center&gt;SDSU 1D&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;30&lt;/center&gt;<br /> | &lt;center&gt;SDSU 1D&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;31&lt;/center&gt;<br /> | &lt;center&gt;SDSU 1D&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;32&lt;/center&gt;<br /> | &lt;center&gt;SDSU 1D&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;33&lt;/center&gt;<br /> | &lt;center&gt;SDSU 1D&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;34&lt;/center&gt;<br /> | &lt;center&gt;SDSU 1D&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;35&lt;/center&gt;<br /> | &lt;center&gt;SDSU 1D&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;36&lt;/center&gt;<br /> | &lt;center&gt;SDSU 1D&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;37&lt;/center&gt;<br /> | &lt;center&gt;SDSU 3D precomputed&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;38&lt;/center&gt;<br /> | &lt;center&gt;SDSU 3D precomputed&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;39&lt;/center&gt;<br /> | &lt;center&gt;SDSU 3D precomputed&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;40&lt;/center&gt;<br /> | &lt;center&gt;SDSU 3D precomputed&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;41&lt;/center&gt;<br /> | &lt;center&gt;SDSU 3D precomputed&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;42&lt;/center&gt;<br /> | &lt;center&gt;SDSU 3D precomputed&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;43&lt;/center&gt;<br /> | &lt;center&gt;SDSU 3D precomputed&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;44&lt;/center&gt;<br /> | &lt;center&gt;SDSU 3D precomputed&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;45&lt;/center&gt;<br /> | &lt;center&gt;SDSU 3D precomputed&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> |}<br /> <br /> ===User-Defined Events===<br /> <br /> {| class=&quot;wikitable&quot; | border=&quot;1&quot;<br /> | Permutation #<br /> | Rupture generator<br /> | Low-frequency<br /> | High-frequency<br /> | Site response<br /> <br /> |-<br /> | &lt;center&gt;1&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;2&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;3&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;4&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;5&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;6&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;7&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;8&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;9&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;10&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;11&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;12&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;13&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;14&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;15&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;16&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;17&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;18&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;19&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;20&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;21&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;22&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;23&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;24&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;25&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;26&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;27&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;28&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;29&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;30&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;31&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;32&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;33&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;34&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;35&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;36&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;37&lt;/center&gt;<br /> | &lt;center&gt;User-supplied SRF&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;38&lt;/center&gt;<br /> | &lt;center&gt;User-supplied SRF&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;39&lt;/center&gt;<br /> | &lt;center&gt;User-supplied SRF&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;40&lt;/center&gt;<br /> | &lt;center&gt;User-supplied SRF&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;41&lt;/center&gt;<br /> | &lt;center&gt;User-supplied SRF&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;42&lt;/center&gt;<br /> | &lt;center&gt;User-supplied SRF&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;43&lt;/center&gt;<br /> | &lt;center&gt;User-supplied SRF&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;44&lt;/center&gt;<br /> | &lt;center&gt;User-supplied SRF&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;45&lt;/center&gt;<br /> | &lt;center&gt;User-supplied SRF&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;46&lt;/center&gt;<br /> | &lt;center&gt;User-supplied SRF&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;47&lt;/center&gt;<br /> | &lt;center&gt;User-supplied SRF&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;48&lt;/center&gt;<br /> | &lt;center&gt;User-supplied SRF&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;49&lt;/center&gt;<br /> | &lt;center&gt;User-supplied SRF&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;50&lt;/center&gt;<br /> | &lt;center&gt;User-supplied SRF&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;51&lt;/center&gt;<br /> | &lt;center&gt;User-supplied SRF&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;52&lt;/center&gt;<br /> | &lt;center&gt;User-supplied SRF&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;53&lt;/center&gt;<br /> | &lt;center&gt;User-supplied SRF&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;54&lt;/center&gt;<br /> | &lt;center&gt;User-supplied SRF&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> |}<br /> <br /> = Appendix B: Troubleshooting =<br /> If you experience trouble building the platform or successfully running test and simulations, try the following solutions.<br /> <br /> === Build Errors ===<br /> <br /> The instruction for installing Broadband Platform are listed in Section 1: &quot;Installing the Second-Generation Broadband Platform&quot; of the User guide. If after following all steps listed in this section of the user guide the build fails, check if the failure is listed in this section and try the solution to fix the issue you are facing.<br /> <br /> ==== 64-bit Intel Compiler Issue ====<br /> If you try to compile with:<br /> &lt;pre&gt;<br /> % cd bbp_2g/src<br /> % make<br /> &lt;/pre&gt; <br /> <br /> and you get:<br /> &lt;pre&gt;<br /> ... <br /> make[2]: Entering directory `.../bbp_2g/src/ucsb/getInFile'<br /> icc -o getfaultGlobal getfaultGlobal.c<br /> ld: cannot find -lgcc_s_32<br /> make[2]: *** [getfaultGlobal] Error 1<br /> make[2]: Leaving directory `.../bbp_2g/src/ucsb/getInFile'<br /> make[1]: *** [all] Error 2<br /> make[1]: Leaving directory `.../bbp_2g/src/ucsb'<br /> make: *** [all] Error 2<br /> &lt;/pre&gt;<br /> <br /> '''Cause:''' The Broadband Platform requires Intel 64-bit compilers to build successfully. In this case the 32-bit Intel compilers are being invoked as they are being picked up from the PATH environment variable. The error is due to a missing GNU-GCC 32-bit compatibility pack that has not been installed on your system. This is not required when 64-bit Intel compilers are used.<br /> <br /> '''Solution:''' Ensure that the path Intel 64-bit compilers are listed in you PATH variable and being picked up by running 'which icc' and 'which ifort'. If you are trying to build the platform on SCEC development servers like Intensity, verify your path variable has:<br /> &lt;pre&gt;<br /> PATH=...:/usr/usc/intel/composerxe-2011.4.191/mpirt/bin/intel64:/usr/usc/intel/composerxe-2011.4.191/bin/intel64<br /> &lt;/pre&gt;<br /> <br /> ==== 32-bit Platform Issue ====<br /> <br /> On trying to build the platform, the build fails with the following message:<br /> &lt;pre&gt;<br /> $ make all<br /> cd urs; make -f makefile FC=gfortran CC=icc USER_C=1;<br /> make[1]: Entering directory `.../bbp_2g/src/urs'<br /> mkdir -p bin;<br /> cd getpar/src; make -f Makefile CC=icc FC=gfortran USER_C=1;<br /> make[2]: Entering directory `.../bbp_2g/src/urs/getpar/src'<br /> icc -O3 -DENVIRONMENT -c -o defpar.o defpar.c<br /> icc -O3 -DENVIRONMENT -c -o getpar.o getpar.c<br /> icc -O3 -DENVIRONMENT -c -o getarg.o getarg.c<br /> getarg.c(112): warning #303: explicit type is missing (&quot;int&quot; assumed)<br /> register i;<br /> ^ <br /> icc -O3 -DENVIRONMENT -c -o getlocation.o getlocation.c<br /> getlocation.c(9): warning #147: declaration is incompatible with &quot;__ssize_t={int} getline(char **restrict, size_t={unsigned int} *restrict, FILE *restrict)&quot; (declared at line 671 of &quot;/usr/include/stdio.h&quot;)<br /> static int getline(FILE *fd, char *line)<br /> <br /> ...<br /> ...<br /> ...<br /> <br /> make[2]: Entering directory `.../bbp_2g/src/sdsu/srcV1.4'<br /> icc -w -Wall -c ray3DJHfor.c<br /> gfortran module_bbtoolbox.f90 module_interface.f90 main_bbtoolbox.f90 coda.f90 composition.f90 convolution.f90 fourier.f90 error.f90 geometry.f90 interpolation.f90 io.f90 random.f90 scattering.f90 source.f90 ray3DJHfor.o -o BBtoolbox.exe<br /> ray3DJHfor.o: In function `raytracing_':<br /> ray3DJHfor.c:(.text+0x8cf): undefined reference to `__libm_sse2_log'<br /> ray3DJHfor.c:(.text+0x96b): undefined reference to `__libm_sse2_asin'<br /> ray3DJHfor.c:(.text+0x9cd): undefined reference to `__libm_sse2_asin'<br /> ray3DJHfor.c:(.text+0xa00): undefined reference to `__libm_sse2_tan'<br /> ray3DJHfor.c:(.text+0xa3d): undefined reference to `__libm_sse2_tan'<br /> ray3DJHfor.c:(.text+0xa52): undefined reference to `__libm_sse2_log'<br /> collect2: ld returned 1 exit status<br /> make[2]: *** [BBtoolbox.exe] Error 1<br /> make[2]: Leaving directory `.../bbp_2g/src/sdsu/srcV1.4'<br /> make[1]: *** [all] Error 2<br /> make[1]: Leaving directory `.../bbp_2g/src/sdsu'<br /> make: *** [all] Error 2<br /> &lt;/pre&gt;<br /> <br /> '''Cause:''' In this case the user tried to build Broadband on a 32-bit platform. Broadband code was designed to be run on 64-bit platform. Any attempt to build Broadband on a 32-bit platform will result in numerous warnings and the build will fail with error messages similar to ones listed above.<br /> <br /> '''Solution:''' Try building Broadband on a 64-bit platform will the all the dependencies listed in Section 1.1: &quot;System Dependencies&quot; and Section 1.2: &quot;Software Dependencies&quot;<br /> <br /> === Unit/Acceptance Test Failures and Errors ===<br /> <br /> Unit and Acceptance tests are provided to verify the Broadband platform and it's supporting modules built by the user are functioning as designed. Under certain circumstances, some of these test might fail. While some of these failure might indicate serious problems that will have to be addressed before the platform can used, it is acceptable to ignore some of the failures. This section lists some failures and their solutions.<br /> <br /> ==== ERROR: test_syn1d (test_syn1d.Test_syn1D) ====<br /> The Unit test for Syn1d module fails with the following message:<br /> &lt;pre&gt;<br /> ERROR: test_syn1d (test_syn1d.Test_syn1D)<br /> ----------------------------------------------------------------------<br /> Traceback (most recent call last):<br /> File &quot;.../bbp_2g/tests/test_syn1d.py&quot;, line 62, in test_syn1d<br /> synObj.run()<br /> File &quot;.../bbp_2g/comps/syn1D.py&quot;, line 236, in run<br /> shutil.copy2(a_tmpfile, expected_file)<br /> File &quot;/usr/lib/python2.6/shutil.py&quot;, line 99, in copy2<br /> copyfile(src, dst)<br /> File &quot;/usr/lib/python2.6/shutil.py&quot;, line 52, in copyfile<br /> fsrc = open(src, 'rb')<br /> IOError: [Errno 2] No such file or directory: '.../bbp_2g/tmpdata/3310632/s01.3comp'<br /> &lt;/pre&gt;<br /> <br /> '''Cause:''' Syn1d module requires the Green's Function file to run and the path to this file might be incorrect in 'bbp_2g_gf/ucsb/GreenBank/Northridge/GreenBank.inf' file.<br /> <br /> '''Solution:''' This issue can be fixed by correcting the paths listed in the GreenBank.inf files in the Green's Function directory. Here are step by step instructions to fix this issue:<br /> <br /> 1. Locate your Greens Functions directory: 'bbp_2g_gf'<br /> 2. Navigate to bbp_2g_gf/ucsb/GreenBank/Northridge folder.<br /> 3. Open Green_Bank.inf files with a text editor.<br /> 4. Locate the text &quot;The name of file to store Green Bank&quot;<br /> 5. Note the location of the Green Bank file under the line found in step 4, similar to &quot;/home/scec-00/scottcal/bband/bbp_2g_gf/ucsb/GreenBank/Northridge/Green_1d.soil&quot;.<br /> 6. Replace the path found in Step 5 with just the file name, in the case of Northridge it is &quot;Green_1d.soil&quot;<br /> 7. Save and close the Green_Bank.inf.<br /> 8. Navigate to bbp_2g_gf/ucsb/GreenBank/LomaPrieta folder and repeat steps 3-7. The name of the Green Bank file for LomaPrieta is &quot;Green_1d.LoPr&quot;.<br /> 9. Navigate to bbp_2g_gf/ucsb/GreenBank/Landers folder and repeat steps 3-7. The name of the Green Bank file for Landers is &quot;Green1D.Landers&quot;<br /> <br /> ==== ERROR: test_gensrf (test_genslip.Test_Genslip) ====<br /> The Unit test for Genslip module fails with the following message:<br /> &lt;pre&gt;<br /> ======================================================================<br /> ERROR: test_gensrf (test_genslip.Test_Genslip)<br /> ----------------------------------------------------------------------<br /> Traceback (most recent call last):<br /> File &quot;.../bbp_2g/tests/test_genslip.py&quot;, line 51, in test_gensrf<br /> gen.run()<br /> File &quot;.../bbp_2g/comps/genslip.py&quot;, line 153, in run<br /> ps.run()<br /> File &quot;.../bbp_2g/comps/plot_srf.py&quot;, line 52, in run<br /> shutil.copy2(&quot;%s/%s.ps.png&quot; % (a_tmpdir, self.r_srffile[0:self.r_srffile.find(&quot;.srf&quot;)]), &quot;%s/%s.png&quot; % (a_outdir, self.r_srffile[0:self.r_srffile.find(&quot;.srf&quot;)]))<br /> File &quot;/usr/lib/python2.6/shutil.py&quot;, line 99, in copy2<br /> copyfile(src, dst)<br /> File &quot;/usr/lib/python2.6/shutil.py&quot;, line 52, in copyfile<br /> fsrc = open(src, 'rb')<br /> IOError: [Errno 2] No such file or directory: '.../bbp_2g/tmpdata/3309008/3309008_test_eq.ps.png'<br /> &lt;/pre&gt;<br /> <br /> '''Cause:''' The Genslip module calls the Plot_SRF module to the plot the SRF file. Plot_SRF uses C-shell code to locate and use GMT package to plot the SRF file. This shell code might fail on some flavors of Linux with a message like &quot;Newline in variable name&quot; in the Plot_SRF log file.<br /> <br /> '''Solution:''' This issue can be fixed by editing the plot_SRF.csh file. Here are step by step instructions to fix this issue:<br /> <br /> 1. Locate shell script file: bbp_2g/src/plot/plot_SRF.csh<br /> 2. Open the file in your preferred text editor<br /> 3. Locate the line 'set FIND_GMT = $?'<br /> 4. Replace the line found in step 3 with 'set FIND_GMT = $status'<br /> 5. Locate the section of code that starts with the statement &quot;# FIND MAX. SLIP&quot;<br /> 6. Replace the following line in section found in step 5:<br /> &lt;pre&gt;<br /> set SMAX = `$XYZCODE calc_xy=$CALC_XY type=&quot;${TYPE}&quot; nseg=-1 &lt; $SLIPFILE.srf | \<br /> gawk -v m=$SMAX '{if($3&gt;m)m=$3;}END{printf &quot;%.0f\n&quot;,m;}'`<br /> <br /> with (collapse the statement to a single line by removing '\' at the end of first part of the statement):<br /> <br /> set SMAX = `$XYZCODE calc_xy=$CALC_XY type=&quot;${TYPE}&quot; nseg=-1 &lt; $SLIPFILE.srf | gawk -v m=$SMAX '{if($3&gt;m)m=$3;}END{printf &quot;%.0f\n&quot;,m;}'`<br /> &lt;/pre&gt;<br /> 7. Save the file and exit<br /> <br /> ==== ERROR: test_ucgen (test_ucrmg.Test_UCrmg) ====<br /> The Unit test for Ucrmg module fails with the following message:<br /> &lt;pre&gt;<br /> ======================================================================<br /> ERROR: test_ucgen (test_ucrmg.Test_UCrmg)<br /> ----------------------------------------------------------------------<br /> Traceback (most recent call last):<br /> File &quot;.../bbp_2g/tests/test_ucrmg.py&quot;, line 59, in test_ucgen<br /> ucObj.run()<br /> File &quot;.../bbp_2g/comps/ucrmg.py&quot;, line 161, in run<br /> ps.run()<br /> File &quot;.../bbp_2g/comps/plot_srf.py&quot;, line 52, in run<br /> shutil.copy2(&quot;%s/%s.ps.png&quot; % (a_tmpdir, self.r_srffile[0:self.r_srffile.find(&quot;.srf&quot;)]), &quot;%s/%s.png&quot; % (a_outdir, self.r_srffile[0:self.r_srffile.find(&quot;.srf&quot;)]))<br /> File &quot;/usr/lib/python2.6/shutil.py&quot;, line 99, in copy2<br /> copyfile(src, dst)<br /> File &quot;/usr/lib/python2.6/shutil.py&quot;, line 52, in copyfile<br /> fsrc = open(src, 'rb')<br /> IOError: [Errno 2] No such file or directory: '.../bbp_2g/tmpdata/3309831/test_ucsb.ps.png'<br /> &lt;/pre&gt;<br /> <br /> '''Cause:''' The Ucrmg module calls the Plot_SRF module to the plot the SRF file. Plot_SRF uses C-shell code to locate and use GMT package to plot the SRF file. This shell code might fail on some flavors of Linux with a message like &quot;Newline in variable name&quot; in the Plot_SRF log file.<br /> <br /> '''Solution:''' This issue can be fixed by editing the plot_SRF.csh file. The steps to fix this issue are listed under the solution for &quot;ERROR: test_gensrf (test_genslip.Test_Genslip)&quot; above.<br /> <br /> ==== FAIL: test_site_amp (test_uc_site.Test_UC_Site) ====<br /> <br /> The unit test for UC-Site module might fail with the following message:<br /> &lt;pre&gt;<br /> ======================================================================<br /> FAIL: test_site_amp (test_uc_site.Test_UC_Site)<br /> ----------------------------------------------------------------------<br /> Traceback (most recent call last):<br /> File &quot;.../bbp_2g/tests/test_uc_site.py&quot;, line 92, in test_site_amp<br /> self.failIf(cmp_bbp.cmp_bbp(a_ref_file_no_header, test_file_no_header, tolerance=0.035)!=0,errmsg)<br /> AssertionError: Output file .../bbp_2g/tmpdata/3310633/s04.3comp does not match reference file .../bbp_2g/ref_data/ucsb/s04.site.3comp<br /> &lt;/pre&gt;<br /> <br /> '''Cause:''' The synthetic seismogram generated by the UC-Site module on the user system differs from the reference result included in the Broadband release.<br /> <br /> '''Solution:''' The stochastic nature of the high frequency simulations is considered, and a constant random seed as input for our tests. This is the same constant random seed used to generate the reference results included in the release. This ensures that the time-series generated with unit tests agree with reference results. However, the high frequency codes are more sensitive to changes in compilers and machines due to the algorithm, so small differences that cause the test to fail are generally acceptable. The user is however encouraged to plot the two time-series and visually inspect them to verify they look similar. We are trying to come up with a better comparison for these tests.<br /> <br /> = Appendix C: Technical Notes =<br /> <br /> == Running Individual Acceptance Tests ==<br /> <br /> The acceptance test script ./tests/AcceptTest.py attempts to run all of the defined tests when executed. However, sometimes it is useful to run an acceptance test in isolation for troubleshooting purposes:<br /> <br /> * Identify the test you want to run. Eg: user-URS-UCSB-SDSU-SDSU<br /> * Move to the ./comps directory and execute that test's XML workflow with run_bbp_2G.py. Using the above example:<br /> &lt;pre&gt;<br /> $ ./run_bbp_2G.py -x ../ref_data/accept_inputs/user-URS-UCSB-SDSU-SDSU.xml<br /> &lt;/pre&gt;<br /> <br /> Since you are running the test outside of AcceptTest.py, you will not see a PASS/FAIL message once the simulation completes. However, you can review the contents of the ./outdata/&lt;SIMID&gt; directory to verify that the correct seismograms and response spectra tables were produced.<br /> <br /> == Manaully Setting Random Number Generator Seed Values ==<br /> <br /> Several of the platform codebases employ random number generators to produce SRFs and seismograms. These random number generators are generally seeded with an initial value (typically an integer) which are hard-coded in the platform. Advanced users may desire to change these seed values.<br /> <br /> Changing the seeds for seismogram synthesis varies depending on which codebase you want to use:<br /> <br /> * URS: Edit ./comps/hfsims_cfg.py, Line 43 &quot;self.RAND_NUM&quot;<br /> * UCSB: Edit ./src/ucsb/Syn1DSCEC/syn1D_LAH.f, Line 183 &quot;iseed&quot;, and recompile with &quot;make&quot;<br /> * SDSU:<br /> ** User event: Edit ./bbp_2g_gf/sdsu/scattering_generic.dat (seed values annotated in file)<br /> ** Validation event: Edit ./bbp_2g_gf/sdsu/&lt;event&gt;/scattering.dat</div> Patrices https://strike.scec.org/scecwiki/index.php?title=Broadband_User_Guide_v11.2.3&diff=5050 Broadband User Guide v11.2.3 2012-05-08T21:17:41Z <p>Patrices: </p> <hr /> <div>'''Version 11.2.3.'''<br /> <br /> If you find errors in this document or sections to be unclear, please either fix them yourself or contact software@scec.org.<br /> <br /> == Installing the Second-Generation Broadband Platform ==<br /> Installing the Broadband Platform involves obtaining a copy of the code and building the required executables. You can either download the platform from the Broadband web site ([http://www.scec.org/research/broadband http://www.scec.org/research/broadband]) or check the code out of SCEC's Subversion repository. Most users should download the platform.<br /> <br /> == System Dependencies ==<br /> The current version of the Broadband Platform is designed to run on standard 64-bit Linux machines. Testing has been performed on SCEC's development servers running Fedora Core 10 (kernel version 2.6.27.41-170.2.117.fc10.x86_64). In this guide we outline how to install the platform into your own account on a Linux computer using the simplest approach.<br /> <br /> == Software Dependencies ==<br /> The Broadband Platform has certain software dependencies.<br /> <br /> Required:<br /> <br /> *Python v2.7 with<br /> **PyGTK<br /> **Matplotlib<br /> **Numpy<br /> **Pyproj<br /> <br /> *Intel compilers (64-bit) v12.0.4<br /> *GNU compilers (gcc, gfortran) v4.5.1<br /> *GNU Fortran 77 v3.4.6<br /> *GMT (Generic Mapping Toolkit)<br /> *ImageMagick<br /> <br /> == Setting Up Your Account ==<br /> For simplicity of installation, we recommend users use a bash shell for the Broadband Platform account. It is possible to get the platform running using other shell's, but we will focus on a bash shell installation. The user environment is a common source of problems since certain environment variables must be defined for the platform to work correctly.<br /> <br /> To check your account, make sure you can run basic commands like ''ls'' and ''cd'' before proceeding.<br /> <br /> == Downloading the Platform ==<br /> &lt;nowiki&gt;Download 4 files from the Broadband website, the code (bbp_dist_&lt;version&gt;.tgz), the data (bbp_data_&lt;version&gt;.tgz), and their checksum files (bbp_dist_&lt;version&gt;.tgz.md5 and bbp_data_&lt;version&gt;.tgz.md5). &lt;/nowiki&gt;The code file is about 100 MB, the data file about 3 GB. After you've downloaded the files to your local Linux system, the next step is to calculate the checksums yourself and compare them to the checksums you downloaded.<br /> <br /> First, verify that the ''md5sum'' command is in your path:<br /> <br /> $&gt; which md5sum<br /> <br /> You should get something like /usr/bin/md5sum. If you see the message 'no md5sum in...', contact your Linux system administrator and ask to have md5sum added to your path.<br /> <br /> Once you can run the ''md5sum'' command, run:<br /> <br /> $&gt; md5sum -c bbp_dist_&lt;version&gt;.tgz.md5<br /> $&gt; md5sum -c bbp_data_&lt;version&gt;.tgz.md5<br /> <br /> You should get the messages<br /> bbp_dist_&lt;version&gt;.tgz.md5: OK<br /> bbp_data_&lt;version&gt;.tgz.md5: OK<br /> <br /> If you get FAILED instead, re-download the tgz files and try again. When it passes, that means the files were downloaded without error.<br /> <br /> Once both files have passed the checksum test, untar the files.<br /> <br /> $&gt; tar xzvf bbp_dist_&lt;version&gt;.tgz file<br /> $&gt; tar xzvf bbp_data_&lt;version&gt;.tgz file<br /> <br /> If multiple users are planning to use the platform on the same system, you only need one copy of the data files per machine. Each user will still need his or her own copy of the code files.<br /> <br /> Alternatively, if you would like access to the latest version of the platform and get frequent but less thoroughly tested improvements, you can check out the platform from SCEC's Subversion repository. Only advanced users should take this approach, outlined in detail in the [[#Advanced Users| Advanced Users section]].<br /> <br /> == User Account Setup ==<br /> <br /> The Broadband platform installation is divided into two parts (1) input Green Functions (GF) data directory (9.3Gb), and (2) BBP home directory (366Mb). <br /> <br /> First, the Green's function libraries are larger, but they are static. The broadband platform reads the data files, but does not change them. <br /> <br /> Second, the remainder of the broadband platform is organized in the BBP home directory. The BBP home directory has a specific directory structure that includes the source code for the scientific programs, the python scripts that link the scientific programs, simulation input directory, temporary and log file directories, and the output data directory where all the platform results are written.<br /> <br /> The BBP home directory will increase in size as you run the platform, because both output data and output log files are written to the home directory. Running the acceptance tests will produce nearly ( 10Gb) of input data (5.2Gb), output data (500Mb), temporary files (2.7Gb), and output log files (250Mb). Once these tests have passed much of this data can be removed. However, the BBP home directory should have at least 10Gb of disk space to insure the acceptance tests can be run when a particular broadband platform software distribution is first installed on a system.<br /> <br /> == Data Directory ==<br /> Input data files called Greens Functions are distributed with the platform. These files are generated using specific velocity structures, so they are often considered region specific. We have GF for three regions including near Loma Prieta, near Landers, and near Northridge.<br /> <br /> The data directory is static, and the data directories are read-only. A single copy can be installed in a shared disk, which can then be shared by multiple users.<br /> <br /> == Setting Environment Variables ==<br /> The BBP source codes and scripts are organized under the broadband platform home directory. The broadband platform home directory is specified in a couple of places during Broadband Platform installation. <br /> <br /> Internal to the Broadband platform software, all broadband platform files (except the Greens Function data files) are in sub-directories of the BBP home directory.<br /> <br /> == BBP Environment Variable ==<br /> We recommend setting both an alias and a environment variable to the BBP home directory. This will help avoid typing it many times.<br /> <br /> If you're running a Bash shell, add the following line to your .bash_profile with your favorite text editor:<br /> <br /> export BBP=/home/scec-00/kumar/bbp_2g<br /> <br /> If you're running a C-shell, add the following line to your .cshrc with your favorite text editor:<br /> <br /> setenv BBP /home/scec-00/kumar/bbp_2g<br /> <br /> * PYTHONPATH<br /> After you've obtained a copy of the project, you'll need to make sure the comps directory is on Python's path so Python can find all the project modules. If you're running a Bash shell, add the following line to your .bash_profile with your favorite text editor:<br /> <br /> export PYTHONPATH=$BBP/comps:$PYTHONPATH<br /> <br /> If you're running a C-shell, add the following line to your .cshrc with your favorite text editor:<br /> <br /> setenv PYTHONPATH $BBP/comps:$PYTHONPATH<br /> <br /> * PATH<br /> In order to successfully compile the project, you'll need to make sure the required compilers directories are in your PATH variable. Broadband requires Intel 64-bit compilers, icc and ifort and GNU Compilers, gcc, g77 and f77 to compile the scientific code.<br /> <br /> If you are planning to run Broadband on SCEC Development servers, make sure you have the following directories in your PATH:<br /> <br /> For Bash Shell (in .bash_profile)<br /> <br /> export PATH=/usr/usc/intel/composerxe-2011.4.191/bin/intel64:/usr/usc/intel/composerxe-2011.4.191/mpirt/bin/intel64:$PATH<br /> <br /> For C-shell (in .cshrc)<br /> <br /> setenv PATH /usr/usc/intel/composerxe-2011.4.191/bin/intel64:/usr/usc/intel/composerxe-2011.4.191/mpirt/bin/intel64:$PATH<br /> <br /> When running elements of the platform over ssh, be sure to enable ssh forwarding (with the -X or -Y options).<br /> <br /> After modifying your login script above, log out and log back into the machine so the changes are reflected in your environment.<br /> <br /> == Edit Install_cfg.py with Installation Directory Paths ==<br /> <br /> You need to tell the platform where it's installed by editing a single python file called &quot;install_cfg.py&quot;. Edit the file bbp_2g/comps/install_cfg.py with your favorite text editor, and edit the lines:<br /> <br /> self.A_INSTALL_ROOT = &lt;bbp_2g directory&gt;<br /> self.A_GF_DIR = &lt;bbp_2g_gf directory&gt;<br /> <br /> as one example:<br /> <br /> self.A_INSTALL_ROOT = /home/scec-00/kumar/bbp_2g<br /> self.A_GF_DIR = /home/scec-00/kumar/bbp_2g_gf<br /> <br /> with the paths on your system to the bbp_2g directory (the source) and the bbp_2g_gf directory (the data) that you unzipped. For example, it could be /home/scottcal/broadband_platform/bbp_2g and /home/scottcal/broadband_platform/bbp_2g_gf.<br /> <br /> Here is some information about these two directories that may be useful as you decide how, and where, to install these two parts of the Broadband Platform on your computer disk system. The data files, and therefore the &lt;bbp_2g_gf directory&gt; are nearly 3GB, but they are static and will not be modified and will not grow in size during use of the platform. The source directory is small to begin. However, this directory will increase as the platform is used, since the results produced by the platform will be stored here.<br /> <br /> == Directory Structure ==<br /> The platform consists of two top-level directories, bbp_2g and bbp_2g_gf. bbp_2g contains the source code, executables, scripts, tests, input, working, and output directories. bbp_2g_gf contains the Green's Functions, input files for the validation events, and other required input files for the various code bases. Note that indata, logs, outdata, tmpdata, and xml are created when the platform is first run, so they will be missing when you first install the platform.<br /> <br /> bbp_2g has the following directories:<br /> *checksums: Contains checksums for bbp_2g_gf files<br /> *comps: The Python scripts to run the platform<br /> *docs: Documentation for the platform<br /> *etc: Miscellaneous utility scripts<br /> *examples: Contains example input files<br /> *indata: An internal directory, used to stage input files<br /> *logs: Contains logs from BBP runs<br /> *outdata: Contains output files from a run<br /> *ref_data: Contains reference files for BBP tests<br /> *start: Put input files for an interactive run here<br /> *src: Source code for BBP modules<br /> *tests: Contains unit and acceptance tests<br /> *tmpdata: An internal directory, used during a run<br /> *xml: Contains XML files which describe simulations and can be used as input<br /> <br /> bbp_2g_gf has the following directories:<br /> *compare: Contains observed seismograms for validation events<br /> *plot: Data files for GMT plots<br /> *sdsu, ucsb, urs: Contains Green's functions, velocity files, and other required inputs for the codebases.<br /> <br /> In general, you will be interacting with the start directory for input files, comps to run the platform, tests to test the platform, and outdata to examine data products.<br /> <br /> === Adding aliases ===<br /> <br /> You may find it helpful to add aliases, so you can quickly and easily move to different broadband directories with a single command. We recommend creating aliases for the home, start, and outdata directories.<br /> <br /> If you are using the Bash shell, you can create aliases by adding the following lines to ~/.bash_profile:<br /> <br /> alias bbp= 'cd &lt;path to bbp_2g directory&gt;'<br /> alias start='cd &lt;path to bbp_2g directory&gt;/start'<br /> alias outdata='cd &lt;path to bbp_2g directory&gt;/outdata'<br /> <br /> If you're using a C shell, edit your ~/.cshrc and add:<br /> <br /> alias bbp cd &lt;path to bbp_2g directory&gt;<br /> alias start cd &lt;path to bbp_2g directory&gt;/start<br /> alias outdata cd &lt;path to bbp_2g directory&gt;/outdata<br /> <br /> Log out and log back in. You'll notice that now you can type the alias command as a shortcut to change directories:<br /> <br /> $&gt; pwd<br /> /home/scec-00/scottcal<br /> $&gt; start<br /> $&gt; pwd<br /> /home/scec-00/scottcal/bband/bbp_2g/start<br /> <br /> This can be a useful way to navigate around the broadband platform directories.<br /> <br /> == Building the Platform ==<br /> Once you have checked out the code, you need to build it. By default, every executable is compiled using the compiler recommended by the code developer. However, if you have limited compiler options or are building the codes on an untested system, you may need to specify non-standard alternative compilers, as described below.<br /> <br /> Before you can build the platform, you need to make sure that the Intel compilers are in your path. This is done automatically on broadband.usc.edu, but on other systems you can check by typing:<br /> <br /> $&gt;which icc<br /> <br /> If you get the message &quot;no icc in ...&quot;, then you'll need to add the Intel compilers to your path. Once the Intel compilers are in your path, you can make the code by cd-ing to the bbp_2g/src directory and typing make:<br /> <br /> $&gt; cd src<br /> $&gt; make<br /> <br /> It takes a minute or two to build the code. You may encounter build warnings; these are fine. However, if you get any build errors, this is a problem and should be investigated.<br /> <br /> By default, every executable is compiled using the compiler recommended by the code developer. Depending on the system, some compilers may not be available to you. You can override the C and Fortran compilers used by editing<br /> <br /> src/makefile<br /> <br /> Uncomment USER_C and set FC and CC to the compilers you wish. For example:<br /> <br /> Before:<br /> <br /> #USER_C=1<br /> FC=f77<br /> CC=gcc<br /> <br /> After (an example, you may choose different compilers):<br /> <br /> USER_C=1<br /> FC=gfortran<br /> CC=gcc<br /> <br /> Note that not all compiler combinations have been thoroughly tested. You may encounter build errors with untested compiler combinations. If you encounter any errors while building the platform, consult the Troubleshooting section at the end of this user guide for know issues and their solutions.<br /> <br /> Once the platform has been successfully built, you can move on to running the tests to verify that all components are working correctly.<br /> <br /> == Advanced Users ==<br /> Alternatively, if you would like access to the latest version of the platform, to get frequent but less thoroughly tested improvements, you can check out the platform from SCEC's Subversion version control repository on source.usc.edu. Only advanced users should follow this approach. If you are unsure, you should download the code as outlined in [[#Downloading the Platform|Downloading the Platform]] and skip this section.<br /> <br /> You may need to request access from the SCEC system administrator, John Yu ([mailto:johnyu@usc.edu johnyu@usc.edu]). Make sure you have subversion in your path before beginning.<br /> <br /> Once you have access, you'll need to decide if you want a stable tagged version, or the latest version in the repository. For a stable version, open a terminal window on the system of your choice and type:<br /> <br /> $&gt; svn checkout https://source.usc.edu/svn/broadband/tags/&lt;stable version&gt; bbp_2g<br /> <br /> For the latest version, type:<br /> <br /> $&gt; svn checkout https://source.usc.edu/svn/broadband/trunk bbp_2g<br /> <br /> This will check out the project to your local machine. It contains the source code, tests, and some example files. You also need to obtain a copy of the Broadband Platform data files, containing the Green's tensors. They are too large to be stored in version control. You can obtain a copy from SCEC software distribution server. If you are working on SCEC development server, you might be able to create a symbolic link to data folder. Please contact [[#User_Support|User Support]] to get a location of the data folder on the SCEC development server. If you are not working on SCEC development server, or don't have an SCEC Linux login account, you can get a archive (.tgz) file of the Green's functions from the same download site you obtained this guide.<br /> <br /> If you know where a read-accessible installation of the green functions data directories you can create a link to that location. This can save disk space in some cases.<br /> <br /> ln -s /home/scec-00/scottcal/bband/bbp_2g_gf &lt;path to your gf directory&gt;<br /> <br /> Periodically you should check for updates to the code. To do so, go to your bbp_2g directory and type<br /> <br /> $&gt; svn update<br /> <br /> This will pull down any code updates that have been made in the repository. After you update, make the code again (detailed in [[#Building the Platform|Building the Platform]]) so that any code changes are captured in the executables.<br /> <br /> == Running the Broadband Platform ==<br /> We recommend users initiate all Broadband Platform runs from the &quot;start&quot; directory. The start directory is a collection point for input files for a particular simulation.<br /> <br /> Assuming the user is starting at BBP home directory, the user should move to the start directory and then run the Checksum, Unit and Acceptance tests to confirm the Broadband Platform software installation is operating as expected.<br /> <br /> $&gt; cd start<br /> <br /> == Running Checksum, Unit, and Acceptance Tests ==<br /> The broadband platform contains three kinds of tests. The checksum tests verify that the data files were copied correctly and you have all the files that are expected. Unit tests run each module using a set of input files, and compare the results against known outputs. They verify that each module has been built and is working correctly. Acceptance tests verify that the modules are working correctly together. They test the platform end-to-end using different combinations with known inputs and compare the results. All the possible module combinations for both user-defined and validation events are tested as checks against integration errors.<br /> <br /> Begin with the checksum tests. Once they past, run the unit tests and finally the acceptance tests.<br /> <br /> == Running Checksum Tests ==<br /> To run the checksum tests, change to the checksums directory and run md5sum_check.py.<br /> <br /> From the BBP home directory:<br /> <br /> $&gt; cd checksums<br /> $&gt; ./md5sum_check.py<br /> <br /> It takes about 5 minutes to compute the checksums. If a checksum disagrees, that means that the contents of the datafile were not what was expected. Try reinstalling the data files and try again. If you continue to get a checksum error, contact support.<br /> <br /> Once the checksums agree, move on to the unit tests.<br /> <br /> == Running Unit Tests ==<br /> To run the unit tests, change to the tests directory and run UnitTests.py.<br /> <br /> From the BBP home directory:<br /> <br /> $&gt; cd tests<br /> $&gt; ./UnitTests.py<br /> <br /> The unit tests take about 15 minutes to run. When they're complete, the console will either print &quot;OK&quot; or how many tests failed. If a test has failed, first check that you have built the executables.You can rerun just the specific test that failed (test_&lt;module&gt;.py). If the test is still failing, also verify that you have the ref_data directory, since it contains the input and reference files. If you're looking for more information about the failure, you can consult the Unit Tests log file in bbp_2g/logs/unit_test.log . If you can't determine the reason for the failure, contact support.<br /> <br /> Once the unit tests all pass, proceed to the acceptance tests. If there are any failure or errors while running the unit tests, consult the Troubleshooting section at the end of this user guide for know issues and their solutions.<br /> <br /> == Running Acceptance Tests ==<br /> Make sure the unit tests pass before moving on to the acceptance tests. To run the acceptance tests, change to the tests directory (if you're not there already) and run AcceptTests.py. <br /> The acceptance tests take a long time to run, around 20 hours<br /> <br /> From the BBP home directory:<br /> <br /> $&gt; cd tests<br /> $&gt; ./AcceptTests.py &amp;&gt; accept.out &amp;<br /> <br /> Since the tests take so long to run (twenty hours), you should run them as a background process, and redirect their output to a log file, as shown in the command above.<br /> <br /> You can check the progress by tailing the log file.<br /> <br /> $&gt; tail accept.out<br /> <br /> When all the acceptance tests are completed, the AcceptTests.py script will either print &quot;OK&quot; or how many tests failed. <br /> <br /> Acceptance test failures indicate that the modules are not integrated correctly. Like with the unit tests, verify that you have the ref_data directory. If a certain acceptance test fails, you can get more information by consulting the acceptance test logs in bbp_2g/logs/acceptance_tests_logs/&lt;test that failed&gt;.log . If you can't determine the reason for the failure, contact [[support]].<br /> <br /> Since the acceptance tests can take a long time to run, you may wish to resume where you left off. This feature is supported automatically. If you do not wish to resume, delete the resume file in ref_data/accept_inputs/resume.txt. If there are any failure or errors while running the acceptance tests, consult the Troubleshooting section at the end of this user guide for know issues and their solutions.<br /> <br /> == Types of Broadband Platform Simulations == <br /> <br /> The platform supports two kinds of simulations, validation events and user-defined events. Validation simulations are performed using a historical event, and are directly compared to observed seismograms using goodness-of-fit. User-defined events are run using a rupture description provided by the user which may not necessarily be a historical earthquake.<br /> <br /> When you run a simulation, the platform assigns an ID to it. This ID can be used to track the simulation and locate the output data products.<br /> <br /> To supply input files to the platform, put them in the start directory. Extensions are important - the platform recognizes station lists (.stl), SRF files (.srf), and simple source descriptions (.src). If there are multiple files of a type, the platform will prompt the user to select one.<br /> <br /> To perform a simulation, a user selects between different required and optional modules. Below we present a summary of the various modules.<br /> <br /> == Modules ==<br /> The broadband platform consists of a series of modules. There are two main types of modules, science modules and utility modules. Science modules are those for which the platform has multiple implementations, provided by different coding research groups. Utility modules only have 1 implementation. A schematic of the available modules and their flow relationships is shown below:<br /> <br /> == Science Modules ==<br /> All simulations must include a low-frequency, high-frequency, and site response science module. Simulations may include an optional rupture generation science module. Users may select between the following different implementations of each of these modules:<br /> <br /> Rupture generation:URS, UCSB<br /> <br /> Low-frequency:URS, UCSB<br /> <br /> High-frequency:URS, UCSB, SDSU<br /> <br /> Site response:URS, UCSB, SDSU<br /> <br /> == Utility Modules ==<br /> A spectral response utility module is automatically run after the site response module. Additionally, users may select an optional goodness-of-fit utility module to run at the conclusion of the simulation. In the case of a user-defined event, users select a historical event or previously run simulation to use as the comparison for goodness-of-fit.<br /> <br /> == Platform Directory ==<br /> <br /> A broadband platform distribution is organized in a specific directory structure that separates the input data sets, the python scripts, the simulation configuration files, log files, and output data files.<br /> <br /> When running Broadband Platform simulations, standard procedure is to place the simulation input files in the start directory and invoke the Broadband platform scripts from there.<br /> <br /> From the BBP home directory:<br /> <br /> $&gt; cd start<br /> $&gt; run_bbp_2G.py<br /> <br /> Simulation output results will be written into the bbp_home/output<br /> <br /> == Validation Simulations ==<br /> To run a validation simulation, go to the comps directory and run run_bbp_2G.py. The platform will ask you a series of questions. Answer 'y' to &quot;Do you want to perform a validation run?&quot;<br /> <br /> From the BBP home directory:<br /> <br /> $&gt; cd start<br /> $&gt; run_bbp_2G.py<br /> Welcome to the SCEC Broadband Platform.<br /> Please select the modules you want to run.<br /> Do you want to perform a validation run (y/n)? y<br /> Do you want to validate with:<br /> Northridge (1)<br /> Loma Prieta (2)<br /> Landers (3)<br /> ?<br /> ...<br /> <br /> No input files are required by the user. However, you may wish to run with a reduced station list to speed up the computations. You can put your own station list into the start directory (the format is described in [[#Station File List|section 5.3]]). Note that any stations which do not have observed seismograms will not be included in the automatically generated goodness-of-fit comparison.<br /> <br /> In addition to the low-frequency modules which compute seismograms using 1D Green's Tensors, validation events can also be run using precomputed 3D seismograms to supply the low-frequency.<br /> <br /> == User-defined Simulations ==<br /> To run a user-defined simulation, two input files are required, a rupture description and a station list. The rupture description can either be in SRF format or a simplified source description (the format is described in [[#Simple source description|section 5.1]]). To run a user-defined simulation, run run_bbp_2G.py.<br /> <br /> From the BBP home directory:<br /> <br /> $&gt; cd start<br /> $&gt; run_bbp_2G.py<br /> Welcome to the SCEC Broadband Platform.<br /> Please select the modules you want to run.<br /> Do you want to perform a validation run (y/n)? y<br /> Do you want to run a rupture generator (y/n)? <br /> ...<br /> <br /> You may then choose if you want to run a rupture generator. This is necessary if you're supplying a simple rupture description. If you're supplying an SRF file, you can skip this. Next you can select from different module implementations. Finally, you have the option to run goodness-of-fit against either observed seismograms or another simulation.<br /> <br /> ...<br /> Do you want to run goodness of fit (y/n)? y<br /> What reference files would you like to compare to? Enter a simulation ID or a scenario name: &lt;comparison&gt;<br /> Enter a label to use for the comparison seismograms: &lt;label&gt;<br /> <br /> The label will be used in GoF plots to distinguish one set of results from the other.<br /> <br /> The user-defined events must be within one of the regions supported by the platform - Southern California, Northern California, or the Mojave. The platform will automatically select a region based on the event hypocenter. If the event falls outside of these regions, you'll get an error.<br /> <br /> == Logging ==<br /> During the run, log files will be produced in logs/&lt;simulation ID&gt;/&lt;simulation ID&gt;.&lt;module name&gt;.log. If the platform fails, this is a good place to look to determine the error. Additionally, any fatal errors will be recorded in fatal_error.log.<br /> <br /> Metadata capturing all the executable calls is located in tmpdata/&lt;simulation ID&gt;/metadata.txt for careful tracing of exactly what was called. Both the log files and metadata can be useful if troubleshooting an issue.<br /> <br /> == Data Products ==<br /> The platform produces a variety of data products. &lt;nowiki&gt;All data products are located in outdata/&lt;simulation ID&gt;. &lt;/nowiki&gt;On most Linux systems, you can show images using display:<br /> <br /> $&gt; display &lt;PNG file&gt;<br /> <br /> Make sure you have X11 forwarding enabled.<br /> <br /> === Station map ===<br /> To help visualize the stations in relationship to the fault, the platform produces a PNG file displaying station locations with red circles and the fault plane with a black line, on an image of California. You can find this file in outdata/&lt;simulation ID&gt;/station_map.png.<br /> <br /> === Seismograms ===<br /> When running the platform, you have the option to output velocity and acceleration seismograms, for each station. Plots of these files can be found in outdata/&lt;simulation ID&gt;/&lt;simulation ID&gt;.&lt;station&gt;_&lt;velocity or acceleration&gt;_seis.png.<br /> <br /> The raw seismogram data is available in outdata/&lt;simulation ID&gt;/&lt;simulation ID&gt;.&lt;station&gt;.vel.bbp (velocity) and outdata/&lt;simulation ID&gt;.&lt;station&gt;.acc.bbp (acceleration). Its format is described in [[#BBP seismograms|section 5.4]].<br /> <br /> To compare seismogram data, you can run comps/plotit.py with two seismograms. It will plot them both for comparison. From the comps directory, run:<br /> <br /> $&gt; plotit.py &lt;path to seismogram 1&gt; &lt;path to seismogram 2&gt;<br /> <br /> === Response spectra ===<br /> The respect code, run at the end of each simulation, calculates the response spectra for each station. The raw respect data is located at<br /> <br /> From the BBP home directory:<br /> <br /> outdata/&lt;simulation ID&gt;/&lt;simulation ID&gt;.&lt;station&gt;.rsp<br /> <br /> in the format described in [[#Response spectra|section 5.5]].<br /> <br /> === Goodness-of-fit ===<br /> If you run goodness-of-fit, several additional data products are produced. The goodness-of-fit comparison is performed by comparing the response spectra of a set of calculated seismograms to seismograms from another simulation or observed seismograms. For each station involved in the comparison, a plot comparing the response spectra can be found at outdata/&lt;simulation ID&gt;/&lt;comparison label&gt;_&lt;simulation ID&gt;_&lt;station&gt;_rsp.png. A plot showing the seismograms on top and bottom can be found at outdata/&lt;comparison label&gt;_&lt;simulation ID&gt;_&lt;station&gt;_overlay.png. The goodness-of-fit plot can be found at gof-&lt;comparison label&gt;-&lt;simulation ID&gt;_r0-&lt;cutoff distance&gt;.png.<br /> <br /> Note that at least 3 stations must be run for goodness-of-fit to be valid. If fewer than 3 stations are run, no goodness of fit calculation will be performed.<br /> <br /> === Rupture files ===<br /> When a user-defined event is simulated, the user has the option to run a rupture generator. This generator produces an SRF file, found in outdata/&lt;simulation ID&gt;/*.srf. This file can be put in the start directory and used in future runs. Additionally, the platform produces a plot of the cumulative slip on the fault surface, outdata/&lt;simulation ID&gt;/&lt;SRF prefix&gt;.png.<br /> <br /> == Platform Modes ==<br /> The platform can be run in multiple modes. The default is interactive mode, in which the user is prompted to answer a series of questions. Once all the information has been gathered, the run begins.<br /> <br /> For a large number of runs, or if the user is repeating a specific run, this can be tedious. The platform provides two other ways to describe a run, with an option file or an XML description.<br /> <br /> An option file provides responses to all the questions that the platform poses. The format is described in [[#Option File|section 5.6]], but it's basically a text file, 1 entry per line, with support for comments. It can be fed to the platform using the -o option.<br /> <br /> The platform will also accept XML files containing a full description of a run. The schema for these files is given in [[#XML workflow description schema|section 5.7]]. These files are also produced by the platform after every simulation, and placed in xml/&lt;simulation ID&gt;.xml. So if you want to rerun a simulation, you can point the platform to the XML file from that simulation using the -x option. Note that a new simulation ID will be assigned to the run, so there is no risk of overwriting previous simulation results.<br /> <br /> == Available Options ==<br /> To get a list of the current available options, run run_bbp_2G.py with the -h flag.<br /> <br /> $&gt; run_bbp_2G.py -h<br /> Usage: run_bbp_2G.py [options]<br /> Options:<br /> -h, --help Show this help message and exit<br /> -x XML_FILE, --xml-file=XML_FILE Run using XML description of workflow<br /> -s SIM_ID, --simID=SIM_ID Force a simID<br /> -o OPTFILE, --option-file=OPTFILE File containing responses to interactive platform prompts<br /> -v, --version Broadband platform version<br /> -c, --compact Compact output results. Remove temporary files for simulations that complete successfully.<br /> -g, --generate-xml Generates the XML description but does not run the platform<br /> -l LOG_FILE, --log=LOG_FILE Store all output in a file<br /> <br /> == Cleanup ==<br /> After a while, you may find that your indata, tmpdata, outdata, and logs directories are getting cluttered with files from past runs. If you wish to delete these old files, you can use the clean_directories.sh script in the etc directory.<br /> <br /> From the BBP home directory:<br /> <br /> $&gt; cd etc<br /> $&gt; ./clean_directories &lt;days&gt;<br /> <br /> Any simulation ID directories in the indata, tmpdata, outdata, and logs directories which were last accessed &lt;days&gt; days or longer ago will be deleted. If you have a few directories you want to keep, either copy them somewhere else, or copy them to a directory name that's not all digits and they won't be deleted.<br /> <br /> = Examples =<br /> Below are some examples that you can try using the sample files in the examples directory. Make sure all the tests pass before you try this. You should be in the comps directory when you start these examples:<br /> <br /> From the BBP home directory:<br /> <br /> $&gt; cd comps<br /> <br /> == Sample Validation Run ==<br /> You don't need to move any files for this. Notice that 3D seismograms are a low-frequency option, since you're running a validation event.<br /> <br /> From the BBP home directory:<br /> <br /> $&gt; cd start<br /> $&gt; run_bbp_2G.py <br /> Welcome to the SCEC Broadband Platform.<br /> Please select the modules you want to run.<br /> Do you want to perform a validation run (y/n)? y<br /> Do you want to validate with:<br /> Northridge (1)<br /> Loma Prieta (2)<br /> Landers (3)<br /> ?1<br /> Do you want to<br /> run all validation stations (1)<br /> select a station list (2)<br /> ?1<br /> Choose a source of low frequency seismograms:<br /> URS module (1)<br /> URS 3D seismograms (2)<br /> UCSB module (3)<br /> SDSU module (4)<br /> SDSU 3D seismograms (5)<br /> ?2<br /> Choose a high frequency module:<br /> URS (1)<br /> UCSB (2)<br /> SDSU (3)<br /> ?1<br /> Choose a site response module:<br /> URS (1)<br /> UCSB (2)<br /> SDSU (3)<br /> ?1<br /> Do you want to plot velocity seismograms (y/n)? y<br /> Do you want to plot acceleration seismograms (y/n)? y<br /> <br /> This simulation takes about 10 minutes. Once it's complete the platform will tell you:<br /> <br /> You can find results in &lt;path to bbp_2g install&gt;/outdata/&lt;simulation ID&gt; .<br /> <br /> In that directory you will find:<br /> <br /> *Velocity seismograms (&lt;simulation ID&gt;.&lt;station&gt;.bbp)<br /> *Acceleration seismograms (&lt;simulation ID&gt;.&lt;station&gt;.acc.bbp)<br /> *Plots of velocity seismograms (&lt;simulation ID&gt;.&lt;station&gt;_velocity_seis.png)<br /> *Plots of acceleration seismograms (&lt;simulation ID&gt;.&lt;station&gt;_acceleration_seis.png)<br /> *Response spectra files (&lt;simulation ID&gt;.&lt;station&gt;.rsp)<br /> *Plots comparing simulated and observed seismograms (Northridge_&lt;simulation ID&gt;_&lt;station&gt;_overlay.png)<br /> *Plots comparing simulated and observed response spectra (Northridge_&lt;simulation ID&gt;_&lt;station&gt;_rsp.png)<br /> *Overall goodness-of-fit plots (gof-Northridge-&lt;simulation ID&gt;_r0-25.png)<br /> <br /> == Sample Validation run, custom stations ==<br /> If the validation runs aren't performed with 3D low-frequency, it can take a long time, up to 10 minutes per station. Sometimes you might want to run with a reduced station list so the simulation will run faster.<br /> <br /> Copy the files in example/valid_custom_stations into the start directory. Take a look at the format of the station file:<br /> <br /> $&gt; more valid_test_stat.stl <br /> #Required: lon, lat, station name, distance to fault plane, Vs30<br /> #Optional: low freq corner, high freq corner<br /> #Unused: station information<br /> #lon lat stationdist Vs30 LF corner HF corner station information<br /> -118.6417 34.5640 cast 20.47 450 0.120 23.0 CSMIP peer.berkeley.edu/nga<br /> -118.4180 34.0628 lacn 22.82 278 0.140 23.0 CSMIP peer.berkeley.edu/nga<br /> -118.8811 34.2886 moor 24.16 405 0.160 23.0 CSMIP peer.berkeley.edu/nga<br /> <br /> Now, run the platform, using a station list:<br /> <br /> From the BBP Home directory<br /> <br /> $&gt; cd start<br /> $&gt; run_bbp_2G.py <br /> Welcome to the SCEC Broadband Platform.<br /> Please select the modules you want to run.<br /> Do you want to perform a validation run (y/n)? y<br /> Do you want to validate with:<br /> Northridge (1)<br /> Loma Prieta (2)<br /> Landers (3)<br /> ?1<br /> Do you want to<br /> run all validation stations (1)<br /> select a station list (2)<br /> ?2<br /> <br /> If you have multiple station list files in your start directory, you may see the following prompt asking you to select one. If you only have one, the platform will select it automatically.<br /> <br /> Found multiple BBP station list files in the start directory. Please select one:<br /> nr_one_stat.stl (1)<br /> valid_test_stat.stl (2)<br /> ?2<br /> Choose a source of low frequency seismograms:<br /> URS module (1)<br /> URS 3D seismograms (2)<br /> UCSB module (3)<br /> SDSU module (4)<br /> SDSU 3D seismograms (5)<br /> ?3<br /> Choose a high frequency module:<br /> URS (1)<br /> UCSB (2)<br /> SDSU (3)<br /> ?2<br /> Choose a site response module:<br /> URS (1)<br /> UCSB (2)<br /> SDSU (3)<br /> ?2<br /> Do you want to plot velocity seismograms (y/n)? y<br /> Do you want to plot acceleration seismograms (y/n)? y<br /> <br /> Again, when the run completes in about 15 minutes you can find results in the output directory. You'll notice far fewer files, as only 3 stations were run instead of 133. The goodness-of-fit plots won't look very good - more stations are really needed to get an accurate plot.<br /> <br /> == Sample User-defined run with source description ==<br /> Next let's try running a user-defined event. Copy examples/user_rup_gen/nr_one_stat.stl and examples/user_rup_gen/user_eq.src to the start directory. user_eq.src is a simple source description. Its format is outlined in [[#XML workflow description schema|section 5.1]]. Since this is a user-defined event, precomputed 3D seismograms aren't a valid option.<br /> <br /> $&gt; run_bbp_2G.py <br /> Welcome to the SCEC Broadband Platform.<br /> Please select the modules you want to run.<br /> Do you want to perform a validation run (y/n)? n<br /> Do you want to run a rupture generator (y/n)? y<br /> Rupture generators:<br /> URS (1)<br /> UCSB (2)<br /> ?1<br /> Using region: Southern California<br /> Choose a low frequency module:<br /> URS (1)<br /> UCSB (2)<br /> ?2<br /> Found multiple BBP station list files in the start directory. Please select one:<br /> nr_one_stat.stl (1)<br /> valid_test_stat.stl (2)<br /> ?1<br /> Choose a high frequency module:<br /> URS (1)<br /> UCSB (2)<br /> SDSU (3)<br /> ?2<br /> Choose a site response module:<br /> URS (1)<br /> UCSB (2)<br /> SDSU (3)<br /> ?1<br /> Do you want to plot velocity seismograms (y/n)? y<br /> Do you want to plot acceleration seismograms (y/n)? y<br /> Do you want to run goodness of fit (y/n)? n<br /> <br /> Since this run only includes one station, it will run in about 5 minutes. In the output directory you'll notice there are no goodness-of-fit or files, since we didn't run goodness-of-fit. However, there is also a map file (station_map.png), showing the fault plane and the stations, and a plot of the rupture slip (user_eq.png). The SRF generated by the rupture generator is in user_eq.srf; this file could be used in future runs. The filenames of the rupture slip plot and SRF are taken from the rupture description filename.<br /> <br /> == Sample User-defined run with SRF file and goodness-of-fit ==<br /> Finally, try a run with an SRF file and run goodness-of-fit on the results. Copy in examples/user_no_rup_gen/ucsb_modSRF_0.srf and examples/user_no_rup_gen/nr_three_stat.stl<br /> <br /> $&gt; run_bbp_2G.py <br /> Welcome to the SCEC Broadband Platform.<br /> Please select the modules you want to run.<br /> Do you want to perform a validation run (y/n)? n<br /> Do you want to run a rupture generator (y/n)? n<br /> Using region: Southern California<br /> Choose a low frequency module:<br /> URS (1)<br /> UCSB (2)<br /> ?1<br /> Found multiple BBP station list files in the start directory. Please select one:<br /> nr_one_stat.stl (1)<br /> valid_test_stat.stl (2)<br /> nr_three_stat.stl (3)<br /> ?3<br /> Choose a high frequency module:<br /> URS (1)<br /> UCSB (2)<br /> SDSU (3)<br /> ?3<br /> Choose a site response module:<br /> URS (1)<br /> UCSB (2)<br /> SDSU (3)<br /> ?1<br /> Do you want to plot velocity seismograms (y/n)? y<br /> Do you want to plot acceleration seismograms (y/n)? y<br /> Do you want to run goodness of fit (y/n)? y<br /> What reference files would you like to compare to? Enter a simulation ID or a scenario name: Northridge<br /> Enter a label to use for the comparison seismograms: nr<br /> <br /> The reference files can either be a scenario event or a simulation ID previously run. The label is just for the figures when comparisons are plotted.<br /> <br /> This run will take about 15 minutes, and the results can be found in the appropriate outdir. Again, the goodness of fit measures will look poor due to the few stations involved in the comparison. If you had fewer than 3 stations, no goodness-of-fit plots would be produced. However, response spectra comparison plots will still be generated.<br /> <br /> = File Formats =<br /> This section offers descriptions of various file formats in the broadband platform.<br /> <br /> == Simple source description ==<br /> This is the format for the simple source description. It is not whitespace sensitive. The filename must end in .src for the platform to identify it as a source description.<br /> <br /> MAGNITUDE = &lt;magnitude&gt;<br /> FAULT_LENGTH = &lt;length of fault&gt;<br /> DLEN = &lt;DX, along length&gt;<br /> FAULT_WIDTH = &lt;down-dip fault width&gt;<br /> DWID = &lt;DY, along width&gt;<br /> DEPTH_TO_TOP = &lt;depth of fault below surface&gt;<br /> STRIKE = &lt;nowiki&gt;&lt;strike&gt;&lt;/nowiki&gt;<br /> RAKE = &lt;rake&gt;<br /> DIP = &lt;dip&gt;<br /> LAT_TOP_CENTER = &lt;latitude of top center point in fault plane&gt;<br /> LON_TOP_CENTER = &lt;longitude of top center point in fault plane&gt;<br /> HYPO_ALONG_STK = &lt;along strike location of hypocenter (0.0 = middle)&gt;<br /> HYPO_DOWN_DIP = &lt;down dip location of hypocenter (0.0 = top)&gt;<br /> DT = &lt;nowiki&gt;&lt;dt&gt;&lt;/nowiki&gt;<br /> SEED = &lt;random seed used in calculations&gt;<br /> CORNER_FREQ = &lt;corner frequency to use&gt;<br /> <br /> == SRF rupture description ==<br /> Details of the Standard Rupture Format (SRF) are given in more detail in the accompanying document. The general fault surface is represented by a distribution of point sources, and it can support one or more planes. The platform produces SRFs as output from rupture generators, but a user can also supply an SRF file as input for user-defined simulations. SRF filenames must end with the suffix .srf for the platform to correctly identify them.<br /> <br /> == Station File List ==<br /> The user may specify a list of stations, matching the following format:<br /> <br /> #optional<br /> %comment<br /> # lines<br /> &lt;nowiki&gt;&lt;lon&gt; &lt;lat&gt; &lt;stat name&gt; &lt;distance to fault trace&gt; &lt;Vs30&gt; &lt;LF corner&gt; &lt;HF corner&gt; &lt;stat info&gt;&lt;/nowiki&gt;<br /> ...<br /> <br /> The station list filename needs to end in .stl for the platform to recognize it as a station list.<br /> <br /> == BBP seismograms ==<br /> All intermediate and output seismograms are produced in a 4-column text format, whether velocity or acceleration.<br /> <br /> # optional<br /> % comment<br /> # lines<br /> &lt;nowiki&gt;&lt;timestamp&gt; &lt;North/South&gt; &lt;East/West&gt; &lt;Up/Down&gt;&lt;/nowiki&gt;<br /> ...<br /> <br /> Time is in seconds and motion is in cm/s (velocity) or cm/s/s (acceleration) unless otherwise specified in the header. Velocity filenames end in .vel.bbp; accelerations in .acc.bbp.<br /> <br /> == Response spectra ==<br /> The response spectra file is in 4-column text format.<br /> <br /> # optional<br /> % comment<br /> # lines<br /> &lt;nowiki&gt;&lt;period (sec)&gt; &lt;North/South&gt; &lt;East/West&gt; &lt;Up/Down&gt;&lt;/nowiki&gt;<br /> ...<br /> <br /> The platform samples response spectra at 112 periods, 0.01-20 sec and outputs pseudo spectral acceleration in units of g.<br /> <br /> == Option File ==<br /> Option files contain responses to the prompts in the platform. You can use them with the -o option to run_bbp_2G.py. The responses have to match the prompts exactly. For example, if you craft an option file assuming there is only one station list in the start directory (and therefore the user isn't prompted to select one) but then it is run with multiple station lists in the start directory, this will cause the run to abort. Option files are recommended to perform a series of runs with different inputs or different modules. If you have a run you perform regularly, it's better practice to run the platform with the -g option and the option file to produce an XML description, which are more complete descriptions of the workflow.<br /> <br /> #optional comments<br /> %using either symbol<br /> n #comments<br /> y % can go<br /> 1 # here<br /> ...<br /> <br /> Use with:<br /> <br /> $&gt; run_bbp_2G.py -o &lt;option file&gt;<br /> <br /> == XML workflow description schema ==<br /> Each time the platform is invoked, an XML file is produced describing the workflow, obeying the following schema:<br /> <br /> &lt;nowiki&gt;&lt;xs:schema xmlns:xs=&quot;http://www.w3.org/2001/XMLSchema&quot;&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:element name= &quot;BBP_Run_Specification&quot; minOccurs= &quot;1&quot; maxOccurs= &quot;1&quot;&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:attribute name=&quot;version&quot; type = &quot;xs:string&quot; use = &quot;required&quot; /&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:complexType&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:sequence&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:element name= &quot;Validation_Run&quot; minOccurs= &quot;0&quot; maxOccurs = &quot;1&quot;&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:attribute name= &quot;event&quot; type= &quot;xs:string&quot; use= &quot;required&quot; /&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:attribute name= &quot;input_station_file&quot; type = &quot;xs:string&quot; /&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:attribute name= &quot;subset&quot; type = &quot;xs:boolean&quot; use = &quot;required&quot; /&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;/xs:element&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:element name= &quot;BBP_Modules&quot;&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:complexType&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:sequence&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:element name = &quot;BBP_Module&quot; maxOccurs = &quot;unbounded&quot; &gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:complexType&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:sequence&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:element name= &quot;name&quot; type=&quot;xs:string&quot; /&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:element name= &quot;staged_files&quot; &gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:complexType&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:sequence&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:element name=&quot;file&quot; type=&quot;xs:string&quot; maxOccurs= &quot;unbounded&quot;/&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;/xs:sequence&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;/xs:complexType&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;/xs:element&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:element name= &quot;arguments&quot; &gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:complexType&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:sequence&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:element name=&quot;argument&quot; type=&quot;xs:string&quot; maxOccurs=&quot;unbounded&quot;&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:attribute name= &quot;type&quot; type= &quot;xs:string&quot; user= &quot;required&quot; /&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;/xs:element&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;/xs:sequence&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;/xs:complexType&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;/xs:element&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;/xs:sequence&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;/xs:complexType&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;/xs:element&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;/xs:sequence&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;/xs:complexType&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;/xs:element&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;/xs:sequence&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;/xs:complexType&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;/xs:element&gt;&lt;/nowiki&gt;<br /> <br /> These files are difficult to construct by hand, but can be generated using the -g flag when running run_bbp_2G.py.<br /> <br /> = User Support =<br /> If you run into bugs with the platform, you can open a trouble ticket at the [http://northridge.usc.edu/trac/broadband Broadband Trac site].<br /> <br /> Check to see if there has already been a ticket opened for the bug. If you are unable to get the platform to run, you can get direct user support by emailing [mailto:software@intensity.usc.edu software@intensity.usc.edu].<br /> <br /> = Appendix A: Possible Module Permutations =<br /> === Validation Events ===<br /> <br /> {| class=&quot;wikitable&quot; | border=&quot;1&quot;<br /> | Permutation #<br /> | Low-frequency module<br /> | High-frequency module<br /> | Site response<br /> <br /> |-<br /> | &lt;center&gt;1&lt;/center&gt;<br /> | &lt;center&gt;URS 1D&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;2&lt;/center&gt;<br /> | &lt;center&gt;URS 1D&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;3&lt;/center&gt;<br /> | &lt;center&gt;URS 1D&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;4&lt;/center&gt;<br /> | &lt;center&gt;URS 1D&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;5&lt;/center&gt;<br /> | &lt;center&gt;URS 1D&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;6&lt;/center&gt;<br /> | &lt;center&gt;URS 1D&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;7&lt;/center&gt;<br /> | &lt;center&gt;URS 1D&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;8&lt;/center&gt;<br /> | &lt;center&gt;URS 1D&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;9&lt;/center&gt;<br /> | &lt;center&gt;URS 1D&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;10&lt;/center&gt;<br /> | &lt;center&gt;URS 3D precomputed&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;11&lt;/center&gt;<br /> | &lt;center&gt;URS 3D precomputed&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;12&lt;/center&gt;<br /> | &lt;center&gt;URS 3D precomputed&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;13&lt;/center&gt;<br /> | &lt;center&gt;URS 3D precomputed&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;14&lt;/center&gt;<br /> | &lt;center&gt;URS 3D precomputed&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;15&lt;/center&gt;<br /> | &lt;center&gt;URS 3D precomputed&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;16&lt;/center&gt;<br /> | &lt;center&gt;URS 3D precomputed&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;17&lt;/center&gt;<br /> | &lt;center&gt;URS 3D precomputed&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;18&lt;/center&gt;<br /> | &lt;center&gt;URS 3D precomputed&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;19&lt;/center&gt;<br /> | &lt;center&gt;UCSB 1D&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;20&lt;/center&gt;<br /> | &lt;center&gt;UCSB 1D&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;21&lt;/center&gt;<br /> | &lt;center&gt;UCSB 1D&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;22&lt;/center&gt;<br /> | &lt;center&gt;UCSB 1D&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;23&lt;/center&gt;<br /> | &lt;center&gt;UCSB 1D&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;24&lt;/center&gt;<br /> | &lt;center&gt;UCSB 1D&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;25&lt;/center&gt;<br /> | &lt;center&gt;UCSB 1D&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;26&lt;/center&gt;<br /> | &lt;center&gt;UCSB 1D&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;27&lt;/center&gt;<br /> | &lt;center&gt;UCSB 1D&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;28&lt;/center&gt;<br /> | &lt;center&gt;SDSU 1D&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;29&lt;/center&gt;<br /> | &lt;center&gt;SDSU 1D&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;30&lt;/center&gt;<br /> | &lt;center&gt;SDSU 1D&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;31&lt;/center&gt;<br /> | &lt;center&gt;SDSU 1D&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;32&lt;/center&gt;<br /> | &lt;center&gt;SDSU 1D&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;33&lt;/center&gt;<br /> | &lt;center&gt;SDSU 1D&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;34&lt;/center&gt;<br /> | &lt;center&gt;SDSU 1D&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;35&lt;/center&gt;<br /> | &lt;center&gt;SDSU 1D&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;36&lt;/center&gt;<br /> | &lt;center&gt;SDSU 1D&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;37&lt;/center&gt;<br /> | &lt;center&gt;SDSU 3D precomputed&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;38&lt;/center&gt;<br /> | &lt;center&gt;SDSU 3D precomputed&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;39&lt;/center&gt;<br /> | &lt;center&gt;SDSU 3D precomputed&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;40&lt;/center&gt;<br /> | &lt;center&gt;SDSU 3D precomputed&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;41&lt;/center&gt;<br /> | &lt;center&gt;SDSU 3D precomputed&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;42&lt;/center&gt;<br /> | &lt;center&gt;SDSU 3D precomputed&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;43&lt;/center&gt;<br /> | &lt;center&gt;SDSU 3D precomputed&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;44&lt;/center&gt;<br /> | &lt;center&gt;SDSU 3D precomputed&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;45&lt;/center&gt;<br /> | &lt;center&gt;SDSU 3D precomputed&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> |}<br /> <br /> ===User-Defined Events===<br /> <br /> {| class=&quot;wikitable&quot; | border=&quot;1&quot;<br /> | Permutation #<br /> | Rupture generator<br /> | Low-frequency<br /> | High-frequency<br /> | Site response<br /> <br /> |-<br /> | &lt;center&gt;1&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;2&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;3&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;4&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;5&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;6&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;7&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;8&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;9&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;10&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;11&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;12&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;13&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;14&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;15&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;16&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;17&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;18&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;19&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;20&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;21&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;22&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;23&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;24&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;25&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;26&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;27&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;28&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;29&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;30&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;31&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;32&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;33&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;34&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;35&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;36&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;37&lt;/center&gt;<br /> | &lt;center&gt;User-supplied SRF&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;38&lt;/center&gt;<br /> | &lt;center&gt;User-supplied SRF&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;39&lt;/center&gt;<br /> | &lt;center&gt;User-supplied SRF&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;40&lt;/center&gt;<br /> | &lt;center&gt;User-supplied SRF&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;41&lt;/center&gt;<br /> | &lt;center&gt;User-supplied SRF&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;42&lt;/center&gt;<br /> | &lt;center&gt;User-supplied SRF&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;43&lt;/center&gt;<br /> | &lt;center&gt;User-supplied SRF&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;44&lt;/center&gt;<br /> | &lt;center&gt;User-supplied SRF&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;45&lt;/center&gt;<br /> | &lt;center&gt;User-supplied SRF&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;46&lt;/center&gt;<br /> | &lt;center&gt;User-supplied SRF&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;47&lt;/center&gt;<br /> | &lt;center&gt;User-supplied SRF&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;48&lt;/center&gt;<br /> | &lt;center&gt;User-supplied SRF&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;49&lt;/center&gt;<br /> | &lt;center&gt;User-supplied SRF&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;50&lt;/center&gt;<br /> | &lt;center&gt;User-supplied SRF&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;51&lt;/center&gt;<br /> | &lt;center&gt;User-supplied SRF&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;52&lt;/center&gt;<br /> | &lt;center&gt;User-supplied SRF&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;53&lt;/center&gt;<br /> | &lt;center&gt;User-supplied SRF&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;54&lt;/center&gt;<br /> | &lt;center&gt;User-supplied SRF&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> |}<br /> <br /> = Appendix B: Troubleshooting =<br /> If you experience trouble building the platform or successfully running test and simulations, try the following solutions.<br /> <br /> === Build Errors ===<br /> <br /> The instruction for installing Broadband Platform are listed in Section 1: &quot;Installing the Second-Generation Broadband Platform&quot; of the User guide. If after following all steps listed in this section of the user guide the build fails, check if the failure is listed in this section and try the solution to fix the issue you are facing.<br /> <br /> ==== 64-bit Intel Compiler Issue ====<br /> If you try to compile with:<br /> &lt;pre&gt;<br /> % cd bbp_2g/src<br /> % make<br /> &lt;/pre&gt; <br /> <br /> and you get:<br /> &lt;pre&gt;<br /> ... <br /> make[2]: Entering directory `.../bbp_2g/src/ucsb/getInFile'<br /> icc -o getfaultGlobal getfaultGlobal.c<br /> ld: cannot find -lgcc_s_32<br /> make[2]: *** [getfaultGlobal] Error 1<br /> make[2]: Leaving directory `.../bbp_2g/src/ucsb/getInFile'<br /> make[1]: *** [all] Error 2<br /> make[1]: Leaving directory `.../bbp_2g/src/ucsb'<br /> make: *** [all] Error 2<br /> &lt;/pre&gt;<br /> <br /> '''Cause:''' The Broadband Platform requires Intel 64-bit compilers to build successfully. In this case the 32-bit Intel compilers are being invoked as they are being picked up from the PATH environment variable. The error is due to a missing GNU-GCC 32-bit compatibility pack that has not been installed on your system. This is not required when 64-bit Intel compilers are used.<br /> <br /> '''Solution:''' Ensure that the path Intel 64-bit compilers are listed in you PATH variable and being picked up by running 'which icc' and 'which ifort'. If you are trying to build the platform on SCEC development servers like Intensity, verify your path variable has:<br /> &lt;pre&gt;<br /> PATH=...:/usr/usc/intel/composerxe-2011.4.191/mpirt/bin/intel64:/usr/usc/intel/composerxe-2011.4.191/bin/intel64<br /> &lt;/pre&gt;<br /> <br /> ==== 32-bit Platform Issue ====<br /> <br /> On trying to build the platform, the build fails with the following message:<br /> &lt;pre&gt;<br /> $ make all<br /> cd urs; make -f makefile FC=gfortran CC=icc USER_C=1;<br /> make[1]: Entering directory `.../bbp_2g/src/urs'<br /> mkdir -p bin;<br /> cd getpar/src; make -f Makefile CC=icc FC=gfortran USER_C=1;<br /> make[2]: Entering directory `.../bbp_2g/src/urs/getpar/src'<br /> icc -O3 -DENVIRONMENT -c -o defpar.o defpar.c<br /> icc -O3 -DENVIRONMENT -c -o getpar.o getpar.c<br /> icc -O3 -DENVIRONMENT -c -o getarg.o getarg.c<br /> getarg.c(112): warning #303: explicit type is missing (&quot;int&quot; assumed)<br /> register i;<br /> ^ <br /> icc -O3 -DENVIRONMENT -c -o getlocation.o getlocation.c<br /> getlocation.c(9): warning #147: declaration is incompatible with &quot;__ssize_t={int} getline(char **restrict, size_t={unsigned int} *restrict, FILE *restrict)&quot; (declared at line 671 of &quot;/usr/include/stdio.h&quot;)<br /> static int getline(FILE *fd, char *line)<br /> <br /> ...<br /> ...<br /> ...<br /> <br /> make[2]: Entering directory `.../bbp_2g/src/sdsu/srcV1.4'<br /> icc -w -Wall -c ray3DJHfor.c<br /> gfortran module_bbtoolbox.f90 module_interface.f90 main_bbtoolbox.f90 coda.f90 composition.f90 convolution.f90 fourier.f90 error.f90 geometry.f90 interpolation.f90 io.f90 random.f90 scattering.f90 source.f90 ray3DJHfor.o -o BBtoolbox.exe<br /> ray3DJHfor.o: In function `raytracing_':<br /> ray3DJHfor.c:(.text+0x8cf): undefined reference to `__libm_sse2_log'<br /> ray3DJHfor.c:(.text+0x96b): undefined reference to `__libm_sse2_asin'<br /> ray3DJHfor.c:(.text+0x9cd): undefined reference to `__libm_sse2_asin'<br /> ray3DJHfor.c:(.text+0xa00): undefined reference to `__libm_sse2_tan'<br /> ray3DJHfor.c:(.text+0xa3d): undefined reference to `__libm_sse2_tan'<br /> ray3DJHfor.c:(.text+0xa52): undefined reference to `__libm_sse2_log'<br /> collect2: ld returned 1 exit status<br /> make[2]: *** [BBtoolbox.exe] Error 1<br /> make[2]: Leaving directory `.../bbp_2g/src/sdsu/srcV1.4'<br /> make[1]: *** [all] Error 2<br /> make[1]: Leaving directory `.../bbp_2g/src/sdsu'<br /> make: *** [all] Error 2<br /> &lt;/pre&gt;<br /> <br /> '''Cause:''' In this case the user tried to build Broadband on a 32-bit platform. Broadband code was designed to be run on 64-bit platform. Any attempt to build Broadband on a 32-bit platform will result in numerous warnings and the build will fail with error messages similar to ones listed above.<br /> <br /> '''Solution:''' Try building Broadband on a 64-bit platform will the all the dependencies listed in Section 1.1: &quot;System Dependencies&quot; and Section 1.2: &quot;Software Dependencies&quot;<br /> <br /> === Unit/Acceptance Test Failures and Errors ===<br /> <br /> Unit and Acceptance tests are provided to verify the Broadband platform and it's supporting modules built by the user are functioning as designed. Under certain circumstances, some of these test might fail. While some of these failure might indicate serious problems that will have to be addressed before the platform can used, it is acceptable to ignore some of the failures. This section lists some failures and their solutions.<br /> <br /> ==== ERROR: test_syn1d (test_syn1d.Test_syn1D) ====<br /> The Unit test for Syn1d module fails with the following message:<br /> &lt;pre&gt;<br /> ERROR: test_syn1d (test_syn1d.Test_syn1D)<br /> ----------------------------------------------------------------------<br /> Traceback (most recent call last):<br /> File &quot;.../bbp_2g/tests/test_syn1d.py&quot;, line 62, in test_syn1d<br /> synObj.run()<br /> File &quot;.../bbp_2g/comps/syn1D.py&quot;, line 236, in run<br /> shutil.copy2(a_tmpfile, expected_file)<br /> File &quot;/usr/lib/python2.6/shutil.py&quot;, line 99, in copy2<br /> copyfile(src, dst)<br /> File &quot;/usr/lib/python2.6/shutil.py&quot;, line 52, in copyfile<br /> fsrc = open(src, 'rb')<br /> IOError: [Errno 2] No such file or directory: '.../bbp_2g/tmpdata/3310632/s01.3comp'<br /> &lt;/pre&gt;<br /> <br /> '''Cause:''' Syn1d module requires the Green's Function file to run and the path to this file might be incorrect in 'bbp_2g_gf/ucsb/GreenBank/Northridge/GreenBank.inf' file.<br /> <br /> '''Solution:''' This issue can be fixed by correcting the paths listed in the GreenBank.inf files in the Green's Function directory. Here are step by step instructions to fix this issue:<br /> <br /> 1. Locate your Greens Functions directory: 'bbp_2g_gf'<br /> 2. Navigate to bbp_2g_gf/ucsb/GreenBank/Northridge folder.<br /> 3. Open Green_Bank.inf files with a text editor.<br /> 4. Locate the text &quot;The name of file to store Green Bank&quot;<br /> 5. Note the location of the Green Bank file under the line found in step 4, similar to &quot;/home/scec-00/scottcal/bband/bbp_2g_gf/ucsb/GreenBank/Northridge/Green_1d.soil&quot;.<br /> 6. Replace the path found in Step 5 with just the file name, in the case of Northridge it is &quot;Green_1d.soil&quot;<br /> 7. Save and close the Green_Bank.inf.<br /> 8. Navigate to bbp_2g_gf/ucsb/GreenBank/LomaPrieta folder and repeat steps 3-7. The name of the Green Bank file for LomaPrieta is &quot;Green_1d.LoPr&quot;.<br /> 9. Navigate to bbp_2g_gf/ucsb/GreenBank/Landers folder and repeat steps 3-7. The name of the Green Bank file for Landers is &quot;Green1D.Landers&quot;<br /> <br /> ==== ERROR: test_gensrf (test_genslip.Test_Genslip) ====<br /> The Unit test for Genslip module fails with the following message:<br /> &lt;pre&gt;<br /> ======================================================================<br /> ERROR: test_gensrf (test_genslip.Test_Genslip)<br /> ----------------------------------------------------------------------<br /> Traceback (most recent call last):<br /> File &quot;.../bbp_2g/tests/test_genslip.py&quot;, line 51, in test_gensrf<br /> gen.run()<br /> File &quot;.../bbp_2g/comps/genslip.py&quot;, line 153, in run<br /> ps.run()<br /> File &quot;.../bbp_2g/comps/plot_srf.py&quot;, line 52, in run<br /> shutil.copy2(&quot;%s/%s.ps.png&quot; % (a_tmpdir, self.r_srffile[0:self.r_srffile.find(&quot;.srf&quot;)]), &quot;%s/%s.png&quot; % (a_outdir, self.r_srffile[0:self.r_srffile.find(&quot;.srf&quot;)]))<br /> File &quot;/usr/lib/python2.6/shutil.py&quot;, line 99, in copy2<br /> copyfile(src, dst)<br /> File &quot;/usr/lib/python2.6/shutil.py&quot;, line 52, in copyfile<br /> fsrc = open(src, 'rb')<br /> IOError: [Errno 2] No such file or directory: '.../bbp_2g/tmpdata/3309008/3309008_test_eq.ps.png'<br /> &lt;/pre&gt;<br /> <br /> '''Cause:''' The Genslip module calls the Plot_SRF module to the plot the SRF file. Plot_SRF uses C-shell code to locate and use GMT package to plot the SRF file. This shell code might fail on some flavors of Linux with a message like &quot;Newline in variable name&quot; in the Plot_SRF log file.<br /> <br /> '''Solution:''' This issue can be fixed by editing the plot_SRF.csh file. Here are step by step instructions to fix this issue:<br /> <br /> 1. Locate shell script file: bbp_2g/src/plot/plot_SRF.csh<br /> 2. Open the file in your preferred text editor<br /> 3. Locate the line 'set FIND_GMT = $?'<br /> 4. Replace the line found in step 3 with 'set FIND_GMT = $status'<br /> 5. Locate the section of code that starts with the statement &quot;# FIND MAX. SLIP&quot;<br /> 6. Replace the following line in section found in step 5:<br /> &lt;pre&gt;<br /> set SMAX = `$XYZCODE calc_xy=$CALC_XY type=&quot;${TYPE}&quot; nseg=-1 &lt; $SLIPFILE.srf | \<br /> gawk -v m=$SMAX '{if($3&gt;m)m=$3;}END{printf &quot;%.0f\n&quot;,m;}'`<br /> <br /> with (collapse the statement to a single line by removing '\' at the end of first part of the statement):<br /> <br /> set SMAX = `$XYZCODE calc_xy=$CALC_XY type=&quot;${TYPE}&quot; nseg=-1 &lt; $SLIPFILE.srf | gawk -v m=$SMAX '{if($3&gt;m)m=$3;}END{printf &quot;%.0f\n&quot;,m;}'`<br /> &lt;/pre&gt;<br /> 7. Save the file and exit<br /> <br /> ==== ERROR: test_ucgen (test_ucrmg.Test_UCrmg) ====<br /> The Unit test for Ucrmg module fails with the following message:<br /> &lt;pre&gt;<br /> ======================================================================<br /> ERROR: test_ucgen (test_ucrmg.Test_UCrmg)<br /> ----------------------------------------------------------------------<br /> Traceback (most recent call last):<br /> File &quot;.../bbp_2g/tests/test_ucrmg.py&quot;, line 59, in test_ucgen<br /> ucObj.run()<br /> File &quot;.../bbp_2g/comps/ucrmg.py&quot;, line 161, in run<br /> ps.run()<br /> File &quot;.../bbp_2g/comps/plot_srf.py&quot;, line 52, in run<br /> shutil.copy2(&quot;%s/%s.ps.png&quot; % (a_tmpdir, self.r_srffile[0:self.r_srffile.find(&quot;.srf&quot;)]), &quot;%s/%s.png&quot; % (a_outdir, self.r_srffile[0:self.r_srffile.find(&quot;.srf&quot;)]))<br /> File &quot;/usr/lib/python2.6/shutil.py&quot;, line 99, in copy2<br /> copyfile(src, dst)<br /> File &quot;/usr/lib/python2.6/shutil.py&quot;, line 52, in copyfile<br /> fsrc = open(src, 'rb')<br /> IOError: [Errno 2] No such file or directory: '.../bbp_2g/tmpdata/3309831/test_ucsb.ps.png'<br /> &lt;/pre&gt;<br /> <br /> '''Cause:''' The Ucrmg module calls the Plot_SRF module to the plot the SRF file. Plot_SRF uses C-shell code to locate and use GMT package to plot the SRF file. This shell code might fail on some flavors of Linux with a message like &quot;Newline in variable name&quot; in the Plot_SRF log file.<br /> <br /> '''Solution:''' This issue can be fixed by editing the plot_SRF.csh file. The steps to fix this issue are listed under the solution for &quot;ERROR: test_gensrf (test_genslip.Test_Genslip)&quot; above.<br /> <br /> ==== FAIL: test_site_amp (test_uc_site.Test_UC_Site) ====<br /> <br /> The unit test for UC-Site module might fail with the following message:<br /> &lt;pre&gt;<br /> ======================================================================<br /> FAIL: test_site_amp (test_uc_site.Test_UC_Site)<br /> ----------------------------------------------------------------------<br /> Traceback (most recent call last):<br /> File &quot;.../bbp_2g/tests/test_uc_site.py&quot;, line 92, in test_site_amp<br /> self.failIf(cmp_bbp.cmp_bbp(a_ref_file_no_header, test_file_no_header, tolerance=0.035)!=0,errmsg)<br /> AssertionError: Output file .../bbp_2g/tmpdata/3310633/s04.3comp does not match reference file .../bbp_2g/ref_data/ucsb/s04.site.3comp<br /> &lt;/pre&gt;<br /> <br /> '''Cause:''' The synthetic seismogram generated by the UC-Site module on the user system differs from the reference result included in the Broadband release.<br /> <br /> '''Solution:''' The stochastic nature of the high frequency simulations is considered, and a constant random seed as input for our tests. This is the same constant random seed used to generate the reference results included in the release. This ensures that the time-series generated with unit tests agree with reference results. However, the high frequency codes are more sensitive to changes in compilers and machines due to the algorithm, so small differences that cause the test to fail are generally acceptable. The user is however encouraged to plot the two time-series and visually inspect them to verify they look similar. We are trying to come up with a better comparison for these tests.<br /> <br /> = Appendix C: Technical Notes =<br /> <br /> == Running Individual Acceptance Tests ==<br /> <br /> The acceptance test script ./tests/AcceptTest.py attempts to run all of the defined tests when executed. However, sometimes it is useful to run an acceptance test in isolation for troubleshooting purposes:<br /> <br /> * Identify the test you want to run. Eg: user-URS-UCSB-SDSU-SDSU<br /> * Move to the ./comps directory and execute that test's XML workflow with run_bbp_2G.py. Using the above example:<br /> &lt;pre&gt;<br /> $ ./run_bbp_2G.py -x ../ref_data/accept_inputs/user-URS-UCSB-SDSU-SDSU.xml<br /> &lt;/pre&gt;<br /> <br /> Since you are running the test outside of AcceptTest.py, you will not see a PASS/FAIL message once the simulation completes. However, you can review the contents of the ./outdata/&lt;SIMID&gt; directory to verify that the correct seismograms and response spectra tables were produced.<br /> <br /> == Manaully Setting Random Number Generator Seed Values ==<br /> <br /> Several of the platform codebases employ random number generators to produce SRFs and seismograms. These random number generators are generally seeded with an initial value (typically an integer) which are hard-coded in the platform. Advanced users may desire to change these seed values.<br /> <br /> Changing the seeds for seismogram synthesis varies depending on which codebase you want to use:<br /> <br /> * URS: Edit ./comps/hfsims_cfg.py, Line 43 &quot;self.RAND_NUM&quot;<br /> * UCSB: Edit ./src/ucsb/Syn1DSCEC/syn1D_LAH.f, Line 183 &quot;iseed&quot;, and recompile with &quot;make&quot;<br /> * SDSU:<br /> ** User event: Edit ./bbp_2g_gf/sdsu/scattering_generic.dat (seed values annotated in file)<br /> ** Validation event: Edit ./bbp_2g_gf/sdsu/&lt;event&gt;/scattering.dat</div> Patrices https://strike.scec.org/scecwiki/index.php?title=Broadband_User_Guide_v11.2.3&diff=5049 Broadband User Guide v11.2.3 2012-05-08T21:03:29Z <p>Patrices: </p> <hr /> <div>'''Version 11.2.3.'''<br /> <br /> If you find errors in this document or sections to be unclear, please either fix them yourself or contact software@scec.org.<br /> <br /> == Installing the Second-Generation Broadband Platform ==<br /> Installing the Broadband Platform involves obtaining a copy of the code and building the required executables. You can either download the platform from the Broadband web site ([http://www.scec.org/research/broadband http://www.scec.org/research/broadband]) or check the code out of SCEC's Subversion repository. Most users should download the platform.<br /> <br /> == System Dependencies ==<br /> The current version of the Broadband Platform is designed to run on standard 64-bit Linux machines. Testing has been performed on SCEC's development servers running Fedora Core 10 (kernel version 2.6.27.41-170.2.117.fc10.x86_64). In this guide we outline how to install the platform into your own account on a Linux computer using the simplest approach.<br /> <br /> == Software Dependencies ==<br /> The Broadband Platform has certain software dependencies.<br /> <br /> Required:<br /> <br /> *Python v2.7 with<br /> **PyGTK<br /> **Matplotlib<br /> **Numpy<br /> **Pyproj<br /> <br /> *Intel compilers (64-bit) v12.0.4<br /> *GNU compilers (gcc, gfortran) v4.5.1<br /> *GNU Fortran 77 v3.4.6<br /> *GMT (Generic Mapping Toolkit)<br /> *ImageMagick<br /> <br /> == Setting Up Your Account ==<br /> For simplicity of installation, we recommend users use a bash shell for the Broadband Platform account. It is possible to get the platform running using other shell's, but we will focus on a bash shell installation. The user environment is a common source of problems since certain environment variables must be defined for the platform to work correctly.<br /> <br /> To check your account, make sure you can run basic commands like ''ls'' and ''cd'' before proceeding.<br /> <br /> == Downloading the Platform ==<br /> &lt;nowiki&gt;Download 4 files from the Broadband website, the code (bbp_dist_&lt;version&gt;.tgz), the data (bbp_data_&lt;version&gt;.tgz), and their checksum files (bbp_dist_&lt;version&gt;.tgz.md5 and bbp_data_&lt;version&gt;.tgz.md5). &lt;/nowiki&gt;The code file is about 100 MB, the data file about 3 GB. After you've downloaded the files to your local Linux system, the next step is to calculate the checksums yourself and compare them to the checksums you downloaded.<br /> <br /> First, verify that the ''md5sum'' command is in your path:<br /> <br /> $&gt; which md5sum<br /> <br /> You should get something like /usr/bin/md5sum. If you see the message 'no md5sum in...', contact your Linux system administrator and ask to have md5sum added to your path.<br /> <br /> Once you can run the ''md5sum'' command, run:<br /> <br /> $&gt; md5sum -c bbp_dist_&lt;version&gt;.tgz.md5<br /> $&gt; md5sum -c bbp_data_&lt;version&gt;.tgz.md5<br /> <br /> You should get the messages<br /> bbp_dist_&lt;version&gt;.tgz.md5: OK<br /> bbp_data_&lt;version&gt;.tgz.md5: OK<br /> <br /> If you get FAILED instead, re-download the tgz files and try again. When it passes, that means the files were downloaded without error.<br /> <br /> Once both files have passed the checksum test, untar the files.<br /> <br /> $&gt; tar xzvf bbp_dist_&lt;version&gt;.tgz file<br /> $&gt; tar xzvf bbp_data_&lt;version&gt;.tgz file<br /> <br /> If multiple users are planning to use the platform on the same system, you only need one copy of the data files per machine. Each user will still need his or her own copy of the code files.<br /> <br /> Alternatively, if you would like access to the latest version of the platform and get frequent but less thoroughly tested improvements, you can check out the platform from SCEC's Subversion repository. Only advanced users should take this approach, outlined in detail in the [[#Advanced Users| Advanced Users section]].<br /> <br /> == User Account Setup ==<br /> <br /> The Broadband platform installation is divided into two parts (1) input Green Functions (GF) data directory (9.3Gb), and (2) BBP home directory (366Mb). <br /> <br /> First, the Green's function libraries are larger, but they are static. The broadband platform reads the data files, but does not change them. <br /> <br /> Second, the remainder of the broadband platform is organized in the BBP home directory. The BBP home directory has a specific directory structure that includes the source code for the scientific programs, the python scripts that link the scientific programs, simulation input directory, temporary and log file directories, and the output data directory where all the platform results are written.<br /> <br /> The BBP home directory will increase in size as you run the platform, because both output data and output log files are written to the home directory. Running the acceptance tests will produce nearly ( 10Gb) of input data (5.2Gb), output data (500Mb), temporary files (2.7Gb), and output log files (250Mb). Once these tests have passed much of this data can be removed. However, the BBP home directory should have at least 10Gb of disk space to insure the acceptance tests can be run when a particular broadband platform software distribution is first installed on a system.<br /> <br /> == Data Directory ==<br /> Input data files called Greens Functions are distributed with the platform. These files are generated using specific velocity structures, so they are often considered region specific. We have GF for three regions including near Loma Prieta, near Landers, and near Northridge.<br /> <br /> The data directory is static, and the data directories are read-only. A single copy can be installed in a shared disk, which can then be shared by multiple users.<br /> <br /> == Setting Environment Variables ==<br /> The BBP source codes and scripts are organized under the broadband platform home directory. The broadband platform home directory is specified in a couple of places during Broadband Platform installation. <br /> <br /> Internal to the Broadband platform software, all broadband platform files (except the Greens Function data files) are in sub-directories of the BBP home directory.<br /> <br /> == BBP Environment Variable ==<br /> We recommend setting both an alias and a environment variable to the BBP home directory. This will help avoid typing it many times.<br /> <br /> If you're running a Bash shell, add the following line to your .bash_profile with your favorite text editor:<br /> <br /> export BBP=/home/scec-00/kumar/bbp_2g<br /> <br /> If you're running a C-shell, add the following line to your .cshrc with your favorite text editor:<br /> <br /> setenv BBP /home/scec-00/kumar/bbp_2g<br /> <br /> * PYTHONPATH<br /> After you've obtained a copy of the project, you'll need to make sure the comps directory is on Python's path so Python can find all the project modules. If you're running a Bash shell, add the following line to your .bash_profile with your favorite text editor:<br /> <br /> export PYTHONPATH=$BBP/comps:$PYTHONPATH<br /> <br /> If you're running a C-shell, add the following line to your .cshrc with your favorite text editor:<br /> <br /> setenv PYTHONPATH $BBP/comps:$PYTHONPATH<br /> <br /> * PATH<br /> In order to successfully compile the project, you'll need to make sure the required compilers directories are in your PATH variable. Broadband requires Intel 64-bit compilers, icc and ifort and GNU Compilers, gcc, g77 and f77 to compile the scientific code.<br /> <br /> If you are planning to run Broadband on SCEC Development servers, make sure you have the following directories in your PATH:<br /> <br /> For Bash Shell (in .bash_profile)<br /> <br /> export PATH=/usr/usc/intel/composerxe-2011.4.191/bin/intel64:/usr/usc/intel/composerxe-2011.4.191/mpirt/bin/intel64:$PATH<br /> <br /> For C-shell (in .cshrc)<br /> <br /> setenv PATH /usr/usc/intel/composerxe-2011.4.191/bin/intel64:/usr/usc/intel/composerxe-2011.4.191/mpirt/bin/intel64:$PATH<br /> <br /> When running elements of the platform over ssh, be sure to enable ssh forwarding (with the -X or -Y options).<br /> <br /> After modifying your login script above, log out and log back into the machine so the changes are reflected in your environment.<br /> <br /> == Edit Install_cfg.py with Installation Directory Paths ==<br /> <br /> You need to tell the platform where it's installed by editing a single python file called &quot;install_cfg.py&quot;. Edit the file bbp_2g/comps/install_cfg.py with your favorite text editor, and edit the lines:<br /> <br /> self.A_INSTALL_ROOT = &lt;bbp_2g directory&gt;<br /> self.A_GF_DIR = &lt;bbp_2g_gf directory&gt;<br /> <br /> as one example:<br /> <br /> self.A_INSTALL_ROOT = /home/scec-00/kumar/bbp_2g<br /> self.A_GF_DIR = /home/scec-00/kumar/bbp_2g_gf<br /> <br /> with the paths on your system to the bbp_2g directory (the source) and the bbp_2g_gf directory (the data) that you unzipped. For example, it could be /home/scottcal/broadband_platform/bbp_2g and /home/scottcal/broadband_platform/bbp_2g_gf.<br /> <br /> Here is some information about these two directories that may be useful as you decide how, and where, to install these two parts of the Broadband Platform on your computer disk system. The data files, and therefore the &lt;bbp_2g_gf directory&gt; are nearly 3GB, but they are static and will not be modified and will not grow in size during use of the platform. The source directory is small to begin. However, this directory will increase as the platform is used, since the results produced by the platform will be stored here.<br /> <br /> == Directory Structure ==<br /> The platform consists of two top-level directories, bbp_2g and bbp_2g_gf. bbp_2g contains the source code, executables, scripts, tests, input, working, and output directories. bbp_2g_gf contains the Green's Functions, input files for the validation events, and other required input files for the various code bases. Note that indata, logs, outdata, tmpdata, and xml are created when the platform is first run, so they will be missing when you first install the platform.<br /> <br /> bbp_2g has the following directories:<br /> *checksums: Contains checksums for bbp_2g_gf files<br /> *comps: The Python scripts to run the platform<br /> *docs: Documentation for the platform<br /> *etc: Miscellaneous utility scripts<br /> *examples: Contains example input files<br /> *indata: An internal directory, used to stage input files<br /> *logs: Contains logs from BBP runs<br /> *outdata: Contains output files from a run<br /> *ref_data: Contains reference files for BBP tests<br /> *start: Put input files for an interactive run here<br /> *src: Source code for BBP modules<br /> *tests: Contains unit and acceptance tests<br /> *tmpdata: An internal directory, used during a run<br /> *xml: Contains XML files which describe simulations and can be used as input<br /> <br /> bbp_2g_gf has the following directories:<br /> *compare: Contains observed seismograms for validation events<br /> *plot: Data files for GMT plots<br /> *sdsu, ucsb, urs: Contains Green's functions, velocity files, and other required inputs for the codebases.<br /> <br /> In general, you will be interacting with the start directory for input files, comps to run the platform, tests to test the platform, and outdata to examine data products.<br /> <br /> === Adding aliases ===<br /> <br /> You may find it helpful to add aliases, so you can quickly and easily move to different broadband directories with a single command. We recommend creating aliases for the home, start, and outdata directories.<br /> <br /> If you are using the Bash shell, you can create aliases by adding the following lines to ~/.bash_profile:<br /> <br /> alias bbp= 'cd &lt;path to bbp_2g directory&gt;'<br /> alias start='cd &lt;path to bbp_2g directory&gt;/start'<br /> alias outdata='cd &lt;path to bbp_2g directory&gt;/outdata'<br /> <br /> If you're using a C shell, edit your ~/.cshrc and add:<br /> <br /> alias bbp cd &lt;path to bbp_2g directory&gt;<br /> alias start cd &lt;path to bbp_2g directory&gt;/start<br /> alias outdata cd &lt;path to bbp_2g directory&gt;/outdata<br /> <br /> Log out and log back in. You'll notice that now you can type the alias command as a shortcut to change directories:<br /> <br /> $&gt; pwd<br /> /home/scec-00/scottcal<br /> $&gt; start<br /> $&gt; pwd<br /> /home/scec-00/scottcal/bband/bbp_2g/start<br /> <br /> This can be a useful way to navigate around the broadband platform directories.<br /> <br /> == Building the Platform ==<br /> Once you have checked out the code, you need to build it. By default, every executable is compiled using the compiler recommended by the code developer. However, if you have limited compiler options or are building the codes on an untested system, you may need to specify non-standard alternative compilers, as described below.<br /> <br /> Before you can build the platform, you need to make sure that the Intel compilers are in your path. This is done automatically on broadband.usc.edu, but on other systems you can check by typing:<br /> <br /> $&gt;which icc<br /> <br /> If you get the message &quot;no icc in ...&quot;, then you'll need to add the Intel compilers to your path. Once the Intel compilers are in your path, you can make the code by cd-ing to the bbp_2g/src directory and typing make:<br /> <br /> $&gt; cd src<br /> $&gt; make<br /> <br /> It takes a minute or two to build the code. You may encounter build warnings; these are fine. However, if you get any build errors, this is a problem and should be investigated.<br /> <br /> By default, every executable is compiled using the compiler recommended by the code developer. Depending on the system, some compilers may not be available to you. You can override the C and Fortran compilers used by editing<br /> <br /> src/makefile<br /> <br /> Uncomment USER_C and set FC and CC to the compilers you wish. For example:<br /> <br /> Before:<br /> <br /> #USER_C=1<br /> FC=f77<br /> CC=gcc<br /> <br /> After (an example, you may choose different compilers):<br /> <br /> USER_C=1<br /> FC=gfortran<br /> CC=gcc<br /> <br /> Note that not all compiler combinations have been thoroughly tested. You may encounter build errors with untested compiler combinations. If you encounter any errors while building the platform, consult the Troubleshooting section at the end of this user guide for know issues and their solutions.<br /> <br /> Once the platform has been successfully built, you can move on to running the tests to verify that all components are working correctly.<br /> <br /> == Advanced Users ==<br /> Alternatively, if you would like access to the latest version of the platform, to get frequent but less thoroughly tested improvements, you can check out the platform from SCEC's Subversion version control repository on source.usc.edu. Only advanced users should follow this approach. If you are unsure, you should download the code as outlined in [[#Downloading the Platform|Downloading the Platform]] and skip this section.<br /> <br /> You may need to request access from the SCEC system administrator, John Yu ([mailto:johnyu@usc.edu johnyu@usc.edu]). Make sure you have subversion in your path before beginning.<br /> <br /> Once you have access, you'll need to decide if you want a stable tagged version, or the latest version in the repository. For a stable version, open a terminal window on the system of your choice and type:<br /> <br /> $&gt; svn checkout https://source.usc.edu/svn/broadband/tags/&lt;stable version&gt; bbp_2g<br /> <br /> For the latest version, type:<br /> <br /> $&gt; svn checkout https://source.usc.edu/svn/broadband/trunk bbp_2g<br /> <br /> This will check out the project to your local machine. It contains the source code, tests, and some example files. You also need to obtain a copy of the Broadband Platform data files, containing the Green's tensors. They are too large to be stored in version control. You can obtain a copy from SCEC software distribution server. If you are working on SCEC development server, you might be able to create a symbolic link to data folder. Please contact [[#User_Support|User Support]] to get a location of the data folder on the SCEC development server. If you are not working on SCEC development server, or don't have an SCEC Linux login account, you can get a archive (.tgz) file of the Green's functions from the same download site you obtained this guide.<br /> <br /> If you know where a read-accessible installation of the green functions data directories you can create a link to that location. This can save disk space in some cases.<br /> <br /> ln -s /home/scec-00/scottcal/bband/bbp_2g_gf &lt;path to your gf directory&gt;<br /> <br /> Periodically you should check for updates to the code. To do so, go to your bbp_2g directory and type<br /> <br /> $&gt; svn update<br /> <br /> This will pull down any code updates that have been made in the repository. After you update, make the code again (detailed in [[#Building the Platform|Building the Platform]]) so that any code changes are captured in the executables.<br /> <br /> == Running the Broadband Platform ==<br /> We recommend users initiate all Broadband Platform runs from the &quot;start&quot; directory. The start directory is a collection point for input files for a particular simulation.<br /> <br /> Assuming the user is starting at BBP home directory, the user should move to the start directory and then run the Checksum, Unit and Acceptance tests to confirm the Broadband Platform software installation is operating as expected.<br /> <br /> $&gt; cd start<br /> <br /> == Running Checksum, Unit, and Acceptance Tests ==<br /> The broadband platform contains three kinds of tests. The checksum tests verify that the data files were copied correctly and you have all the files that are expected. Unit tests run each module using a set of input files, and compare the results against known outputs. They verify that each module has been built and is working correctly. Acceptance tests verify that the modules are working correctly together. They test the platform end-to-end using different combinations with known inputs and compare the results. All the possible module combinations for both user-defined and validation events are tested as checks against integration errors.<br /> <br /> Begin with the checksum tests. Once they past, run the unit tests and finally the acceptance tests.<br /> <br /> == Running Checksum Tests ==<br /> To run the checksum tests, change to the checksums directory and run md5sum_check.py.<br /> <br /> From the BBP home directory:<br /> <br /> $&gt; cd checksums<br /> $&gt; ./md5sum_check.py<br /> <br /> It takes about 5 minutes to compute the checksums. If a checksum disagrees, that means that the contents of the datafile were not what was expected. Try reinstalling the data files and try again. If you continue to get a checksum error, contact support.<br /> <br /> Once the checksums agree, move on to the unit tests.<br /> <br /> == Running Unit Tests ==<br /> To run the unit tests, change to the tests directory and run UnitTests.py.<br /> <br /> From the BBP home directory:<br /> <br /> $&gt; cd tests<br /> $&gt; ./UnitTests.py<br /> <br /> The unit tests take about 15 minutes to run. When they're complete, the console will either print &quot;OK&quot; or how many tests failed. If a test has failed, first check that you have built the executables.You can rerun just the specific test that failed (test_&lt;module&gt;.py). If the test is still failing, also verify that you have the ref_data directory, since it contains the input and reference files. If you're looking for more information about the failure, you can consult the Unit Tests log file in bbp_2g/logs/unit_test.log . If you can't determine the reason for the failure, contact support.<br /> <br /> Once the unit tests all pass, proceed to the acceptance tests. If there are any failure or errors while running the unit tests, consult the Troubleshooting section at the end of this user guide for know issues and their solutions.<br /> <br /> == Running Acceptance Tests ==<br /> Make sure the unit tests pass before moving on to the acceptance tests. To run the acceptance tests, change to the tests directory (if you're not there already) and run AcceptTests.py. <br /> The acceptance tests take a long time to run, around 20 hours<br /> <br /> From the BBP home directory:<br /> <br /> $&gt; cd tests<br /> $&gt; ./AcceptTests.py &amp;&gt; accept.out &amp;<br /> <br /> Since the tests take so long to run (twenty hours), you should run them as a background process, and redirect their output to a log file, as shown in the command above.<br /> <br /> You can check the progress by tailing the log file.<br /> <br /> $&gt; tail accept.out<br /> <br /> When all the acceptance tests are completed, the AcceptTests.py script will either print &quot;OK&quot; or how many tests failed. <br /> <br /> Acceptance test failures indicate that the modules are not integrated correctly. Like with the unit tests, verify that you have the ref_data directory. If a certain acceptance test fails, you can get more information by consulting the acceptance test logs in bbp_2g/logs/acceptance_tests_logs/&lt;test that failed&gt;.log . If you can't determine the reason for the failure, contact [[support]].<br /> <br /> Since the acceptance tests can take a long time to run, you may wish to resume where you left off. This feature is supported automatically. If you do not wish to resume, delete the resume file in ref_data/accept_inputs/resume.txt. If there are any failure or errors while running the acceptance tests, consult the Troubleshooting section at the end of this user guide for know issues and their solutions.<br /> <br /> == Types of Broadband Platform Simulations == <br /> <br /> The platform supports two kinds of simulations, validation events and user-defined events. Validation simulations are performed using a historical event, and are directly compared to observed seismograms using goodness-of-fit. User-defined events are run using a rupture description provided by the user which may not necessarily be a historical earthquake.<br /> <br /> When you run a simulation, the platform assigns an ID to it. This ID can be used to track the simulation and locate the output data products.<br /> <br /> To supply input files to the platform, put them in the start directory. Extensions are important - the platform recognizes station lists (.stl), SRF files (.srf), and simple source descriptions (.src). If there are multiple files of a type, the platform will prompt the user to select one.<br /> <br /> To perform a simulation, a user selects between different required and optional modules. Below we present a summary of the various modules.<br /> <br /> == Modules ==<br /> The broadband platform consists of a series of modules. There are two main types of modules, science modules and utility modules. Science modules are those for which the platform has multiple implementations, provided by different coding research groups. Utility modules only have 1 implementation. A schematic of the available modules and their flow relationships is shown below:<br /> <br /> == Science Modules ==<br /> All simulations must include a low-frequency, high-frequency, and site response science module. Simulations may include an optional rupture generation science module. Users may select between the following different implementations of each of these modules:<br /> <br /> Rupture generation:URS, UCSB<br /> <br /> Low-frequency:URS, UCSB<br /> <br /> High-frequency:URS, UCSB, SDSU<br /> <br /> Site response:URS, UCSB, SDSU<br /> <br /> == Utility Modules ==<br /> A spectral response utility module is automatically run after the site response module. Additionally, users may select an optional goodness-of-fit utility module to run at the conclusion of the simulation. In the case of a user-defined event, users select a historical event or previously run simulation to use as the comparison for goodness-of-fit.<br /> <br /> == Platform Directory ==<br /> <br /> A broadband platform distribution is organized in a specific directory structure that separates the input data sets, the python scripts, the simulation configuration files, log files, and output data files.<br /> <br /> When running Broadband Platform simulations, standard procedure is to place the simulation input files in the start directory and invoke the Broadband platform scripts from there.<br /> <br /> From the BBP home directory:<br /> <br /> $&gt; cd start<br /> $&gt; run_bbp_2G.py<br /> <br /> Simulation output results will be written into the bbp_home/output<br /> <br /> == Validation Simulations ==<br /> To run a validation simulation, go to the comps directory and run run_bbp_2G.py. The platform will ask you a series of questions. Answer 'y' to &quot;Do you want to perform a validation run?&quot;<br /> <br /> From the BBP home directory:<br /> <br /> $&gt; cd start<br /> $&gt; run_bbp_2G.py<br /> Welcome to the SCEC Broadband Platform.<br /> Please select the modules you want to run.<br /> Do you want to perform a validation run (y/n)? y<br /> Do you want to validate with:<br /> Northridge (1)<br /> Loma Prieta (2)<br /> Landers (3)<br /> ?<br /> ...<br /> <br /> No input files are required by the user. However, you may wish to run with a reduced station list to speed up the computations. You can put your own station list into the start directory (the format is described in [[#Station File List|section 5.3]]). Note that any stations which do not have observed seismograms will not be included in the automatically generated goodness-of-fit comparison.<br /> <br /> In addition to the low-frequency modules which compute seismograms using 1D Green's Tensors, validation events can also be run using precomputed 3D seismograms to supply the low-frequency.<br /> <br /> == User-defined Simulations ==<br /> To run a user-defined simulation, two input files are required, a rupture description and a station list. The rupture description can either be in SRF format or a simplified source description (the format is described in [[#Simple source description|section 5.1]]). To run a user-defined simulation, run run_bbp_2G.py.<br /> <br /> From the BBP home directory:<br /> <br /> $&gt; cd start<br /> $&gt; run_bbp_2G.py<br /> Welcome to the SCEC Broadband Platform.<br /> Please select the modules you want to run.<br /> Do you want to perform a validation run (y/n)? y<br /> Do you want to run a rupture generator (y/n)? <br /> ...<br /> <br /> You may then choose if you want to run a rupture generator. This is necessary if you're supplying a simple rupture description. If you're supplying an SRF file, you can skip this. Next you can select from different module implementations. Finally, you have the option to run goodness-of-fit against either observed seismograms or another simulation.<br /> <br /> ...<br /> Do you want to run goodness of fit (y/n)? y<br /> What reference files would you like to compare to? Enter a simulation ID or a scenario name: &lt;comparison&gt;<br /> Enter a label to use for the comparison seismograms: &lt;label&gt;<br /> <br /> The label will be used in GoF plots to distinguish one set of results from the other.<br /> <br /> The user-defined events must be within one of the regions supported by the platform - Southern California, Northern California, or the Mojave. The platform will automatically select a region based on the event hypocenter. If the event falls outside of these regions, you'll get an error.<br /> <br /> == Logging ==<br /> During the run, log files will be produced in logs/&lt;simulation ID&gt;/&lt;simulation ID&gt;.&lt;module name&gt;.log. If the platform fails, this is a good place to look to determine the error. Additionally, any fatal errors will be recorded in fatal_error.log.<br /> <br /> Metadata capturing all the executable calls is located in tmpdata/&lt;simulation ID&gt;/metadata.txt for careful tracing of exactly what was called. Both the log files and metadata can be useful if troubleshooting an issue.<br /> <br /> == Data Products ==<br /> The platform produces a variety of data products. &lt;nowiki&gt;All data products are located in outdata/&lt;simulation ID&gt;. &lt;/nowiki&gt;On most Linux systems, you can show images using display:<br /> <br /> $&gt; display &lt;PNG file&gt;<br /> <br /> Make sure you have X11 forwarding enabled.<br /> <br /> === Station map ===<br /> To help visualize the stations in relationship to the fault, the platform produces a PNG file displaying station locations with red circles and the fault plane with a black line, on an image of California. You can find this file in outdata/&lt;simulation ID&gt;/station_map.png.<br /> <br /> === Seismograms ===<br /> When running the platform, you have the option to output velocity and acceleration seismograms, for each station. Plots of these files can be found in outdata/&lt;simulation ID&gt;/&lt;simulation ID&gt;.&lt;station&gt;_&lt;velocity or acceleration&gt;_seis.png.<br /> <br /> The raw seismogram data is available in outdata/&lt;simulation ID&gt;/&lt;simulation ID&gt;.&lt;station&gt;.vel.bbp (velocity) and outdata/&lt;simulation ID&gt;.&lt;station&gt;.acc.bbp (acceleration). Its format is described in [[#BBP seismograms|section 5.4]].<br /> <br /> To compare seismogram data, you can run comps/plotit.py with two seismograms. It will plot them both for comparison. From the comps directory, run:<br /> <br /> $&gt; plotit.py &lt;path to seismogram 1&gt; &lt;path to seismogram 2&gt;<br /> <br /> === Response spectra ===<br /> The respect code, run at the end of each simulation, calculates the response spectra for each station. The raw respect data is located at<br /> <br /> From the BBP home directory:<br /> <br /> outdata/&lt;simulation ID&gt;/&lt;simulation ID&gt;.&lt;station&gt;.rsp<br /> <br /> in the format described in [[#Response spectra|section 5.5]].<br /> <br /> === Goodness-of-fit ===<br /> If you run goodness-of-fit, several additional data products are produced. The goodness-of-fit comparison is performed by comparing the response spectra of a set of calculated seismograms to seismograms from another simulation or observed seismograms. For each station involved in the comparison, a plot comparing the response spectra can be found at outdata/&lt;simulation ID&gt;/&lt;comparison label&gt;_&lt;simulation ID&gt;_&lt;station&gt;_rsp.png. A plot showing the seismograms on top and bottom can be found at outdata/&lt;comparison label&gt;_&lt;simulation ID&gt;_&lt;station&gt;_overlay.png. The goodness-of-fit plot can be found at gof-&lt;comparison label&gt;-&lt;simulation ID&gt;_r0-&lt;cutoff distance&gt;.png.<br /> <br /> Note that at least 3 stations must be run for goodness-of-fit to be valid. If fewer than 3 stations are run, no goodness of fit calculation will be performed.<br /> <br /> === Rupture files ===<br /> When a user-defined event is simulated, the user has the option to run a rupture generator. This generator produces an SRF file, found in outdata/&lt;simulation ID&gt;/*.srf. This file can be put in the start directory and used in future runs. Additionally, the platform produces a plot of the cumulative slip on the fault surface, outdata/&lt;simulation ID&gt;/&lt;SRF prefix&gt;.png.<br /> <br /> == Platform Modes ==<br /> The platform can be run in multiple modes. The default is interactive mode, in which the user is prompted to answer a series of questions. Once all the information has been gathered, the run begins.<br /> <br /> For a large number of runs, or if the user is repeating a specific run, this can be tedious. The platform provides two other ways to describe a run, with an option file or an XML description.<br /> <br /> An option file provides responses to all the questions that the platform poses. The format is described in [[#Option File|section 5.6]], but it's basically a text file, 1 entry per line, with support for comments. It can be fed to the platform using the -o option.<br /> <br /> The platform will also accept XML files containing a full description of a run. The schema for these files is given in [[#XML workflow description schema|section 5.7]]. These files are also produced by the platform after every simulation, and placed in xml/&lt;simulation ID&gt;.xml. So if you want to rerun a simulation, you can point the platform to the XML file from that simulation using the -x option. Note that a new simulation ID will be assigned to the run, so there is no risk of overwriting previous simulation results.<br /> <br /> == Available Options ==<br /> To get a list of the current available options, run run_bbp_2G.py with the -h flag.<br /> <br /> $&gt; run_bbp_2G.py -h<br /> Usage: run_bbp_2G.py [options]<br /> Options:<br /> -h, --help Show this help message and exit<br /> -x XML_FILE, --xml-file=XML_FILE Run using XML description of workflow<br /> -s SIM_ID, --simID=SIM_ID Force a simID<br /> -o OPTFILE, --option-file=OPTFILE File containing responses to interactive platform prompts<br /> -v, --version Broadband platform version<br /> -c, --compact Compact output results. Remove temporary files for simulations that complete successfully.<br /> -g, --generate-xml Generates the XML description but does not run the platform<br /> -l LOG_FILE, --log=LOG_FILE Store all output in a file<br /> <br /> == Cleanup ==<br /> After a while, you may find that your indata, tmpdata, outdata, and logs directories are getting cluttered with files from past runs. If you wish to delete these old files, you can use the clean_directories.sh script in the etc directory.<br /> <br /> From the BBP home directory:<br /> <br /> $&gt; cd etc<br /> $&gt; ./clean_directories &lt;days&gt;<br /> <br /> Any simulation ID directories in the indata, tmpdata, outdata, and logs directories which were last accessed &lt;days&gt; days or longer ago will be deleted. If you have a few directories you want to keep, either copy them somewhere else, or copy them to a directory name that's not all digits and they won't be deleted.<br /> <br /> = Examples =<br /> Below are some examples that you can try using the sample files in the examples directory. Make sure all the tests pass before you try this. You should be in the comps directory when you start these examples:<br /> <br /> From the BBP home directory:<br /> <br /> $&gt; cd comps<br /> <br /> == Sample Validation Run ==<br /> You don't need to move any files for this. Notice that 3D seismograms are a low-frequency option, since you're running a validation event.<br /> <br /> From the BBP home directory:<br /> <br /> $&gt; cd start<br /> $&gt; run_bbp_2G.py <br /> Welcome to the SCEC Broadband Platform.<br /> Please select the modules you want to run.<br /> Do you want to perform a validation run (y/n)? y<br /> Do you want to validate with:<br /> Northridge (1)<br /> Loma Prieta (2)<br /> Landers (3)<br /> ?1<br /> Do you want to<br /> run all validation stations (1)<br /> select a station list (2)<br /> ?1<br /> Choose a source of low frequency seismograms:<br /> URS module (1)<br /> URS 3D seismograms (2)<br /> UCSB module (3)<br /> SDSU module (4)<br /> SDSU 3D seismograms (5)<br /> ?2<br /> Choose a high frequency module:<br /> URS (1)<br /> UCSB (2)<br /> SDSU (3)<br /> ?1<br /> Choose a site response module:<br /> URS (1)<br /> UCSB (2)<br /> SDSU (3)<br /> ?1<br /> Do you want to plot velocity seismograms (y/n)? y<br /> Do you want to plot acceleration seismograms (y/n)? y<br /> <br /> This simulation takes about 10 minutes. Once it's complete the platform will tell you:<br /> <br /> You can find results in &lt;path to bbp_2g install&gt;/outdata/&lt;simulation ID&gt; .<br /> <br /> In that directory you will find:<br /> <br /> *Velocity seismograms (&lt;simulation ID&gt;.&lt;station&gt;.bbp)<br /> *Acceleration seismograms (&lt;simulation ID&gt;.&lt;station&gt;.acc.bbp)<br /> *Plots of velocity seismograms (&lt;simulation ID&gt;.&lt;station&gt;_velocity_seis.png)<br /> *Plots of acceleration seismograms (&lt;simulation ID&gt;.&lt;station&gt;_acceleration_seis.png)<br /> *Response spectra files (&lt;simulation ID&gt;.&lt;station&gt;.rsp)<br /> *Plots comparing simulated and observed seismograms (Northridge_&lt;simulation ID&gt;_&lt;station&gt;_overlay.png)<br /> *Plots comparing simulated and observed response spectra (Northridge_&lt;simulation ID&gt;_&lt;station&gt;_rsp.png)<br /> *Overall goodness-of-fit plots (gof-Northridge-&lt;simulation ID&gt;_r0-25.png)<br /> <br /> == Sample Validation run, custom stations ==<br /> If the validation runs aren't performed with 3D low-frequency, it can take a long time, up to 10 minutes per station. Sometimes you might want to run with a reduced station list so the simulation will run faster.<br /> <br /> Copy the files in example/valid_custom_stations into the start directory. Take a look at the format of the station file:<br /> <br /> $&gt; more valid_test_stat.stl <br /> #Required: lon, lat, station name, distance to fault plane, Vs30<br /> #Optional: low freq corner, high freq corner<br /> #Unused: station information<br /> #lon lat stationdist Vs30 LF corner HF corner station information<br /> -118.6417 34.5640 cast 20.47 450 0.120 23.0 CSMIP peer.berkeley.edu/nga<br /> -118.4180 34.0628 lacn 22.82 278 0.140 23.0 CSMIP peer.berkeley.edu/nga<br /> -118.8811 34.2886 moor 24.16 405 0.160 23.0 CSMIP peer.berkeley.edu/nga<br /> <br /> Now, run the platform, using a station list:<br /> <br /> From the BBP Home directory<br /> <br /> $&gt; cd start<br /> $&gt; run_bbp_2G.py <br /> Welcome to the SCEC Broadband Platform.<br /> Please select the modules you want to run.<br /> Do you want to perform a validation run (y/n)? y<br /> Do you want to validate with:<br /> Northridge (1)<br /> Loma Prieta (2)<br /> Landers (3)<br /> ?1<br /> Do you want to<br /> run all validation stations (1)<br /> select a station list (2)<br /> ?2<br /> <br /> If you have multiple station list files in your start directory, you may see the following prompt asking you to select one. If you only have one, the platform will select it automatically.<br /> <br /> Found multiple BBP station list files in the start directory. Please select one:<br /> nr_one_stat.stl (1)<br /> valid_test_stat.stl (2)<br /> ?2<br /> Choose a source of low frequency seismograms:<br /> URS module (1)<br /> URS 3D seismograms (2)<br /> UCSB module (3)<br /> SDSU module (4)<br /> SDSU 3D seismograms (5)<br /> ?3<br /> Choose a high frequency module:<br /> URS (1)<br /> UCSB (2)<br /> SDSU (3)<br /> ?2<br /> Choose a site response module:<br /> URS (1)<br /> UCSB (2)<br /> SDSU (3)<br /> ?2<br /> Do you want to plot velocity seismograms (y/n)? y<br /> Do you want to plot acceleration seismograms (y/n)? y<br /> <br /> Again, when the run completes in about 15 minutes you can find results in the output directory. You'll notice far fewer files, as only 3 stations were run instead of 133. The goodness-of-fit plots won't look very good - more stations are really needed to get an accurate plot.<br /> <br /> == Sample User-defined run with source description ==<br /> Next let's try running a user-defined event. Copy examples/user_rup_gen/nr_one_stat.stl and examples/user_rup_gen/user_eq.src to the start directory. user_eq.src is a simple source description. Its format is outlined in [[#XML workflow description schema|section 5.1]]. Since this is a user-defined event, precomputed 3D seismograms aren't a valid option.<br /> <br /> $&gt; run_bbp_2G.py <br /> Welcome to the SCEC Broadband Platform.<br /> Please select the modules you want to run.<br /> Do you want to perform a validation run (y/n)? n<br /> Do you want to run a rupture generator (y/n)? y<br /> Rupture generators:<br /> URS (1)<br /> UCSB (2)<br /> ?1<br /> Using region: Southern California<br /> Choose a low frequency module:<br /> URS (1)<br /> UCSB (2)<br /> ?2<br /> Found multiple BBP station list files in the start directory. Please select one:<br /> nr_one_stat.stl (1)<br /> valid_test_stat.stl (2)<br /> ?1<br /> Choose a high frequency module:<br /> URS (1)<br /> UCSB (2)<br /> SDSU (3)<br /> ?2<br /> Choose a site response module:<br /> URS (1)<br /> UCSB (2)<br /> SDSU (3)<br /> ?1<br /> Do you want to plot velocity seismograms (y/n)? y<br /> Do you want to plot acceleration seismograms (y/n)? y<br /> Do you want to run goodness of fit (y/n)? n<br /> <br /> Since this run only includes one station, it will run in about 5 minutes. In the output directory you'll notice there are no goodness-of-fit or files, since we didn't run goodness-of-fit. However, there is also a map file (station_map.png), showing the fault plane and the stations, and a plot of the rupture slip (user_eq.png). The SRF generated by the rupture generator is in user_eq.srf; this file could be used in future runs. The filenames of the rupture slip plot and SRF are taken from the rupture description filename.<br /> <br /> == Sample User-defined run with SRF file and goodness-of-fit ==<br /> Finally, try a run with an SRF file and run goodness-of-fit on the results. Copy in examples/user_no_rup_gen/ucsb_modSRF_0.srf and examples/user_no_rup_gen/nr_three_stat.stl<br /> <br /> $&gt; run_bbp_2G.py <br /> Welcome to the SCEC Broadband Platform.<br /> Please select the modules you want to run.<br /> Do you want to perform a validation run (y/n)? n<br /> Do you want to run a rupture generator (y/n)? n<br /> Using region: Southern California<br /> Choose a low frequency module:<br /> URS (1)<br /> UCSB (2)<br /> ?1<br /> Found multiple BBP station list files in the start directory. Please select one:<br /> nr_one_stat.stl (1)<br /> valid_test_stat.stl (2)<br /> nr_three_stat.stl (3)<br /> ?3<br /> Choose a high frequency module:<br /> URS (1)<br /> UCSB (2)<br /> SDSU (3)<br /> ?3<br /> Choose a site response module:<br /> URS (1)<br /> UCSB (2)<br /> SDSU (3)<br /> ?1<br /> Do you want to plot velocity seismograms (y/n)? y<br /> Do you want to plot acceleration seismograms (y/n)? y<br /> Do you want to run goodness of fit (y/n)? y<br /> What reference files would you like to compare to? Enter a simulation ID or a scenario name: Northridge<br /> Enter a label to use for the comparison seismograms: nr<br /> <br /> The reference files can either be a scenario event or a simulation ID previously run. The label is just for the figures when comparisons are plotted.<br /> <br /> This run will take about 15 minutes, and the results can be found in the appropriate outdir. Again, the goodness of fit measures will look poor due to the few stations involved in the comparison. If you had fewer than 3 stations, no goodness-of-fit plots would be produced. However, response spectra comparison plots will still be generated.<br /> <br /> = File Formats =<br /> This section offers descriptions of various file formats in the broadband platform.<br /> <br /> == Simple source description ==<br /> This is the format for the simple source description. It is not whitespace sensitive. The filename must end in .src for the platform to identify it as a source description.<br /> <br /> MAGNITUDE = &lt;magnitude&gt;<br /> FAULT_LENGTH = &lt;length of fault&gt;<br /> DLEN = &lt;DX, along length&gt;<br /> FAULT_WIDTH = &lt;down-dip fault width&gt;<br /> DWID = &lt;DY, along width&gt;<br /> DEPTH_TO_TOP = &lt;depth of fault below surface&gt;<br /> STRIKE = &lt;nowiki&gt;&lt;strike&gt;&lt;/nowiki&gt;<br /> RAKE = &lt;rake&gt;<br /> DIP = &lt;dip&gt;<br /> LAT_TOP_CENTER = &lt;latitude of top center point in fault plane&gt;<br /> LON_TOP_CENTER = &lt;longitude of top center point in fault plane&gt;<br /> HYPO_ALONG_STK = &lt;along strike location of hypocenter (0.0 = middle)&gt;<br /> HYPO_DOWN_DIP = &lt;down dip location of hypocenter (0.0 = top)&gt;<br /> DT = &lt;nowiki&gt;&lt;dt&gt;&lt;/nowiki&gt;<br /> SEED = &lt;random seed used in calculations&gt;<br /> CORNER_FREQ = &lt;corner frequency to use&gt;<br /> <br /> == SRF rupture description ==<br /> Details of the Standard Rupture Format (SRF) are given in more detail in the accompanying document. The general fault surface is represented by a distribution of point sources, and it can support one or more planes. The platform produces SRFs as output from rupture generators, but a user can also supply an SRF file as input for user-defined simulations. SRF filenames must end with the suffix .srf for the platform to correctly identify them.<br /> <br /> == Station File List ==<br /> The user may specify a list of stations, matching the following format:<br /> <br /> #optional<br /> %comment<br /> # lines<br /> &lt;nowiki&gt;&lt;lon&gt; &lt;lat&gt; &lt;stat name&gt; &lt;distance to fault trace&gt; &lt;Vs30&gt; &lt;LF corner&gt; &lt;HF corner&gt; &lt;stat info&gt;&lt;/nowiki&gt;<br /> ...<br /> <br /> The station list filename needs to end in .stl for the platform to recognize it as a station list.<br /> <br /> == BBP seismograms ==<br /> All intermediate and output seismograms are produced in a 4-column text format, whether velocity or acceleration.<br /> <br /> # optional<br /> % comment<br /> # lines<br /> &lt;nowiki&gt;&lt;timestamp&gt; &lt;North/South&gt; &lt;East/West&gt; &lt;Up/Down&gt;&lt;/nowiki&gt;<br /> ...<br /> <br /> Time is in seconds and motion is in cm/s (velocity) or cm/s/s (acceleration) unless otherwise specified in the header. Velocity filenames end in .vel.bbp; accelerations in .acc.bbp.<br /> <br /> == Response spectra ==<br /> The response spectra file is in 4-column text format.<br /> <br /> # optional<br /> % comment<br /> # lines<br /> &lt;nowiki&gt;&lt;period (sec)&gt; &lt;North/South&gt; &lt;East/West&gt; &lt;Up/Down&gt;&lt;/nowiki&gt;<br /> ...<br /> <br /> The platform samples response spectra at 112 periods, 0.01-20 sec and outputs pseudo spectral acceleration in units of g.<br /> <br /> == Option File ==<br /> Option files contain responses to the prompts in the platform. You can use them with the -o option to run_bbp_2G.py. The responses have to match the prompts exactly. For example, if you craft an option file assuming there is only one station list in the start directory (and therefore the user isn't prompted to select one) but then it is run with multiple station lists in the start directory, this will cause the run to abort. Option files are recommended to perform a series of runs with different inputs or different modules. If you have a run you perform regularly, it's better practice to run the platform with the -g option and the option file to produce an XML description, which are more complete descriptions of the workflow.<br /> <br /> #optional comments<br /> %using either symbol<br /> n #comments<br /> y % can go<br /> 1 # here<br /> ...<br /> <br /> Use with:<br /> <br /> $&gt; run_bbp_2G.py -o &lt;option file&gt;<br /> <br /> == XML workflow description schema ==<br /> Each time the platform is invoked, an XML file is produced describing the workflow, obeying the following schema:<br /> <br /> &lt;nowiki&gt;&lt;xs:schema xmlns:xs=&quot;http://www.w3.org/2001/XMLSchema&quot;&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:element name= &quot;BBP_Run_Specification&quot; minOccurs= &quot;1&quot; maxOccurs= &quot;1&quot;&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:attribute name=&quot;version&quot; type = &quot;xs:string&quot; use = &quot;required&quot; /&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:complexType&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:sequence&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:element name= &quot;Validation_Run&quot; minOccurs= &quot;0&quot; maxOccurs = &quot;1&quot;&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:attribute name= &quot;event&quot; type= &quot;xs:string&quot; use= &quot;required&quot; /&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:attribute name= &quot;input_station_file&quot; type = &quot;xs:string&quot; /&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:attribute name= &quot;subset&quot; type = &quot;xs:boolean&quot; use = &quot;required&quot; /&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;/xs:element&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:element name= &quot;BBP_Modules&quot;&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:complexType&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:sequence&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:element name = &quot;BBP_Module&quot; maxOccurs = &quot;unbounded&quot; &gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:complexType&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:sequence&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:element name= &quot;name&quot; type=&quot;xs:string&quot; /&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:element name= &quot;staged_files&quot; &gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:complexType&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:sequence&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:element name=&quot;file&quot; type=&quot;xs:string&quot; maxOccurs= &quot;unbounded&quot;/&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;/xs:sequence&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;/xs:complexType&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;/xs:element&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:element name= &quot;arguments&quot; &gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:complexType&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:sequence&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:element name=&quot;argument&quot; type=&quot;xs:string&quot; maxOccurs=&quot;unbounded&quot;&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;xs:attribute name= &quot;type&quot; type= &quot;xs:string&quot; user= &quot;required&quot; /&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;/xs:element&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;/xs:sequence&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;/xs:complexType&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;/xs:element&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;/xs:sequence&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;/xs:complexType&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;/xs:element&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;/xs:sequence&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;/xs:complexType&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;/xs:element&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;/xs:sequence&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;/xs:complexType&gt;&lt;/nowiki&gt;<br /> &lt;nowiki&gt;&lt;/xs:element&gt;&lt;/nowiki&gt;<br /> <br /> These files are difficult to construct by hand, but can be generated using the -g flag when running run_bbp_2G.py.<br /> <br /> = User Support =<br /> If you run into bugs with the platform, you can open a trouble ticket at the [http://northridge.usc.edu/trac/broadband Broadband Trac site].<br /> <br /> Check to see if there has already been a ticket opened for the bug. If you are unable to get the platform to run, you can get direct user support by emailing [mailto:software@intensity.usc.edu software@intensity.usc.edu].<br /> <br /> = Appendix A: Possible Module Permutations =<br /> === Validation Events ===<br /> <br /> {| class=&quot;wikitable&quot; | border=&quot;1&quot;<br /> | Permutation #<br /> | Low-frequency module<br /> | High-frequency module<br /> | Site response<br /> <br /> |-<br /> | &lt;center&gt;1&lt;/center&gt;<br /> | &lt;center&gt;URS 1D&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;2&lt;/center&gt;<br /> | &lt;center&gt;URS 1D&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;3&lt;/center&gt;<br /> | &lt;center&gt;URS 1D&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;4&lt;/center&gt;<br /> | &lt;center&gt;URS 1D&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;5&lt;/center&gt;<br /> | &lt;center&gt;URS 1D&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;6&lt;/center&gt;<br /> | &lt;center&gt;URS 1D&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;7&lt;/center&gt;<br /> | &lt;center&gt;URS 1D&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;8&lt;/center&gt;<br /> | &lt;center&gt;URS 1D&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;9&lt;/center&gt;<br /> | &lt;center&gt;URS 1D&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;10&lt;/center&gt;<br /> | &lt;center&gt;URS 3D precomputed&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;11&lt;/center&gt;<br /> | &lt;center&gt;URS 3D precomputed&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;12&lt;/center&gt;<br /> | &lt;center&gt;URS 3D precomputed&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;13&lt;/center&gt;<br /> | &lt;center&gt;URS 3D precomputed&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;14&lt;/center&gt;<br /> | &lt;center&gt;URS 3D precomputed&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;15&lt;/center&gt;<br /> | &lt;center&gt;URS 3D precomputed&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;16&lt;/center&gt;<br /> | &lt;center&gt;URS 3D precomputed&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;17&lt;/center&gt;<br /> | &lt;center&gt;URS 3D precomputed&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;18&lt;/center&gt;<br /> | &lt;center&gt;URS 3D precomputed&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;19&lt;/center&gt;<br /> | &lt;center&gt;UCSB 1D&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;20&lt;/center&gt;<br /> | &lt;center&gt;UCSB 1D&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;21&lt;/center&gt;<br /> | &lt;center&gt;UCSB 1D&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;22&lt;/center&gt;<br /> | &lt;center&gt;UCSB 1D&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;23&lt;/center&gt;<br /> | &lt;center&gt;UCSB 1D&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;24&lt;/center&gt;<br /> | &lt;center&gt;UCSB 1D&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;25&lt;/center&gt;<br /> | &lt;center&gt;UCSB 1D&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;26&lt;/center&gt;<br /> | &lt;center&gt;UCSB 1D&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;27&lt;/center&gt;<br /> | &lt;center&gt;UCSB 1D&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;28&lt;/center&gt;<br /> | &lt;center&gt;SDSU 1D&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;29&lt;/center&gt;<br /> | &lt;center&gt;SDSU 1D&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;30&lt;/center&gt;<br /> | &lt;center&gt;SDSU 1D&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;31&lt;/center&gt;<br /> | &lt;center&gt;SDSU 1D&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;32&lt;/center&gt;<br /> | &lt;center&gt;SDSU 1D&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;33&lt;/center&gt;<br /> | &lt;center&gt;SDSU 1D&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;34&lt;/center&gt;<br /> | &lt;center&gt;SDSU 1D&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;35&lt;/center&gt;<br /> | &lt;center&gt;SDSU 1D&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;36&lt;/center&gt;<br /> | &lt;center&gt;SDSU 1D&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;37&lt;/center&gt;<br /> | &lt;center&gt;SDSU 3D precomputed&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;38&lt;/center&gt;<br /> | &lt;center&gt;SDSU 3D precomputed&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;39&lt;/center&gt;<br /> | &lt;center&gt;SDSU 3D precomputed&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;40&lt;/center&gt;<br /> | &lt;center&gt;SDSU 3D precomputed&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;41&lt;/center&gt;<br /> | &lt;center&gt;SDSU 3D precomputed&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;42&lt;/center&gt;<br /> | &lt;center&gt;SDSU 3D precomputed&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;43&lt;/center&gt;<br /> | &lt;center&gt;SDSU 3D precomputed&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;44&lt;/center&gt;<br /> | &lt;center&gt;SDSU 3D precomputed&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | &lt;center&gt;45&lt;/center&gt;<br /> | &lt;center&gt;SDSU 3D precomputed&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> | &lt;center&gt;SDSU&lt;/center&gt;<br /> |}<br /> <br /> ===User-Defined Events===<br /> {| style=&quot;border-spacing:0;&quot;<br /> | style=&quot;background-color:#ffffff;border-top:0.0007in solid #000001;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;Permutation #&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:0.0007in solid #000001;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;Rupture generator&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:0.0007in solid #000001;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;Low-frequency&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:0.0007in solid #000001;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;High-frequency&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border:0.0007in solid #000001;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;Site response&lt;/center&gt;<br /> <br /> |-<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;1&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;URS&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;URS&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;URS&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:0.0007in solid #000001;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;2&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;URS&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;URS&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;URS&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:0.0007in solid #000001;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;3&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;URS&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;URS&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;URS&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:0.0007in solid #000001;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;4&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;URS&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;URS&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;UCSB&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:0.0007in solid #000001;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;5&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;URS&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;URS&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;UCSB&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:0.0007in solid #000001;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;6&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;URS&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;URS&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;UCSB&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:0.0007in solid #000001;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;7&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;URS&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;URS&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;SDSU&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:0.0007in solid #000001;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;8&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;URS&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;URS&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;SDSU&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:0.0007in solid #000001;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;9&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;URS&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;URS&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;SDSU&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:0.0007in solid #000001;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;10&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;URS&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;UCSB&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;URS&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:0.0007in solid #000001;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;11&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;URS&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;UCSB&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;URS&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:0.0007in solid #000001;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;12&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;URS&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;UCSB&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;URS&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:0.0007in solid #000001;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;13&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;URS&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;UCSB&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;UCSB&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:0.0007in solid #000001;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;14&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;URS&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;UCSB&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;UCSB&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:0.0007in solid #000001;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;15&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;URS&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;UCSB&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;UCSB&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:0.0007in solid #000001;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;16&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;URS&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;UCSB&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;SDSU&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:0.0007in solid #000001;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;17&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;URS&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;UCSB&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;SDSU&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:0.0007in solid #000001;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;18&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;URS&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;UCSB&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;SDSU&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:0.0007in solid #000001;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;19&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;UCSB&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;URS&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;URS&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:0.0007in solid #000001;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;20&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;UCSB&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;URS&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;URS&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:0.0007in solid #000001;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;21&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;UCSB&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;URS&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;URS&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:0.0007in solid #000001;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;22&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;UCSB&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;URS&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;UCSB&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:0.0007in solid #000001;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;23&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;UCSB&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;URS&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;UCSB&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:0.0007in solid #000001;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;24&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;UCSB&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;URS&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;UCSB&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:0.0007in solid #000001;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;25&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;UCSB&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;URS&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;SDSU&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:0.0007in solid #000001;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;26&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;UCSB&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;URS&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;SDSU&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:0.0007in solid #000001;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;27&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;UCSB&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;URS&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;SDSU&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:0.0007in solid #000001;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;28&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;UCSB&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;UCSB&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;URS&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:0.0007in solid #000001;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;29&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;UCSB&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;UCSB&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;URS&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:0.0007in solid #000001;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;30&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;UCSB&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;UCSB&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;URS&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:0.0007in solid #000001;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;31&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;UCSB&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;UCSB&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;UCSB&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:0.0007in solid #000001;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;32&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;UCSB&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;UCSB&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;UCSB&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:0.0007in solid #000001;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;33&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;UCSB&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;UCSB&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;UCSB&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:0.0007in solid #000001;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;34&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;UCSB&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;UCSB&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;SDSU&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:0.0007in solid #000001;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;35&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;UCSB&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;UCSB&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;SDSU&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:0.0007in solid #000001;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;36&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;UCSB&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;UCSB&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;SDSU&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:0.0007in solid #000001;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;37&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;User-supplied SRF&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;URS&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;URS&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:0.0007in solid #000001;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;38&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;User-supplied SRF&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;URS&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;URS&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:0.0007in solid #000001;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;39&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;User-supplied SRF&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;URS&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;URS&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:0.0007in solid #000001;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;40&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;User-supplied SRF&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;URS&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;UCSB&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:0.0007in solid #000001;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;41&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;User-supplied SRF&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;URS&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;UCSB&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:0.0007in solid #000001;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;42&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;User-supplied SRF&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;URS&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;UCSB&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:0.0007in solid #000001;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;43&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;User-supplied SRF&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;URS&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;SDSU&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:0.0007in solid #000001;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;44&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;User-supplied SRF&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;URS&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;SDSU&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:0.0007in solid #000001;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;45&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;User-supplied SRF&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;URS&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;SDSU&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:0.0007in solid #000001;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;46&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;User-supplied SRF&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;UCSB&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;URS&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:0.0007in solid #000001;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;47&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;User-supplied SRF&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;UCSB&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;URS&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:0.0007in solid #000001;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;48&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;User-supplied SRF&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;UCSB&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;URS&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:0.0007in solid #000001;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;49&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;User-supplied SRF&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;UCSB&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;UCSB&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:0.0007in solid #000001;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;50&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;User-supplied SRF&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;UCSB&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;UCSB&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:0.0007in solid #000001;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;51&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;User-supplied SRF&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;UCSB&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;UCSB&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:0.0007in solid #000001;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |-<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;52&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;User-supplied SRF&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;UCSB&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;SDSU&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:0.0007in solid #000001;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;URS&lt;/center&gt;<br /> <br /> |-<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;53&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;User-supplied SRF&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;UCSB&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;SDSU&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:0.0007in solid #000001;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;UCSB&lt;/center&gt;<br /> <br /> |-<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;54&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;User-supplied SRF&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;UCSB&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;SDSU&lt;/center&gt;<br /> | style=&quot;background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #000001;border-left:0.0007in solid #000001;border-right:0.0007in solid #000001;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;&quot;| &lt;center&gt;SDSU&lt;/center&gt;<br /> <br /> |}<br /> <br /> = Appendix B: Troubleshooting =<br /> If you experience trouble building the platform or successfully running test and simulations, try the following solutions.<br /> <br /> === Build Errors ===<br /> <br /> The instruction for installing Broadband Platform are listed in Section 1: &quot;Installing the Second-Generation Broadband Platform&quot; of the User guide. If after following all steps listed in this section of the user guide the build fails, check if the failure is listed in this section and try the solution to fix the issue you are facing.<br /> <br /> ==== 64-bit Intel Compiler Issue ====<br /> If you try to compile with:<br /> &lt;pre&gt;<br /> % cd bbp_2g/src<br /> % make<br /> &lt;/pre&gt; <br /> <br /> and you get:<br /> &lt;pre&gt;<br /> ... <br /> make[2]: Entering directory `.../bbp_2g/src/ucsb/getInFile'<br /> icc -o getfaultGlobal getfaultGlobal.c<br /> ld: cannot find -lgcc_s_32<br /> make[2]: *** [getfaultGlobal] Error 1<br /> make[2]: Leaving directory `.../bbp_2g/src/ucsb/getInFile'<br /> make[1]: *** [all] Error 2<br /> make[1]: Leaving directory `.../bbp_2g/src/ucsb'<br /> make: *** [all] Error 2<br /> &lt;/pre&gt;<br /> <br /> '''Cause:''' The Broadband Platform requires Intel 64-bit compilers to build successfully. In this case the 32-bit Intel compilers are being invoked as they are being picked up from the PATH environment variable. The error is due to a missing GNU-GCC 32-bit compatibility pack that has not been installed on your system. This is not required when 64-bit Intel compilers are used.<br /> <br /> '''Solution:''' Ensure that the path Intel 64-bit compilers are listed in you PATH variable and being picked up by running 'which icc' and 'which ifort'. If you are trying to build the platform on SCEC development servers like Intensity, verify your path variable has:<br /> &lt;pre&gt;<br /> PATH=...:/usr/usc/intel/composerxe-2011.4.191/mpirt/bin/intel64:/usr/usc/intel/composerxe-2011.4.191/bin/intel64<br /> &lt;/pre&gt;<br /> <br /> ==== 32-bit Platform Issue ====<br /> <br /> On trying to build the platform, the build fails with the following message:<br /> &lt;pre&gt;<br /> $ make all<br /> cd urs; make -f makefile FC=gfortran CC=icc USER_C=1;<br /> make[1]: Entering directory `.../bbp_2g/src/urs'<br /> mkdir -p bin;<br /> cd getpar/src; make -f Makefile CC=icc FC=gfortran USER_C=1;<br /> make[2]: Entering directory `.../bbp_2g/src/urs/getpar/src'<br /> icc -O3 -DENVIRONMENT -c -o defpar.o defpar.c<br /> icc -O3 -DENVIRONMENT -c -o getpar.o getpar.c<br /> icc -O3 -DENVIRONMENT -c -o getarg.o getarg.c<br /> getarg.c(112): warning #303: explicit type is missing (&quot;int&quot; assumed)<br /> register i;<br /> ^ <br /> icc -O3 -DENVIRONMENT -c -o getlocation.o getlocation.c<br /> getlocation.c(9): warning #147: declaration is incompatible with &quot;__ssize_t={int} getline(char **restrict, size_t={unsigned int} *restrict, FILE *restrict)&quot; (declared at line 671 of &quot;/usr/include/stdio.h&quot;)<br /> static int getline(FILE *fd, char *line)<br /> <br /> ...<br /> ...<br /> ...<br /> <br /> make[2]: Entering directory `.../bbp_2g/src/sdsu/srcV1.4'<br /> icc -w -Wall -c ray3DJHfor.c<br /> gfortran module_bbtoolbox.f90 module_interface.f90 main_bbtoolbox.f90 coda.f90 composition.f90 convolution.f90 fourier.f90 error.f90 geometry.f90 interpolation.f90 io.f90 random.f90 scattering.f90 source.f90 ray3DJHfor.o -o BBtoolbox.exe<br /> ray3DJHfor.o: In function `raytracing_':<br /> ray3DJHfor.c:(.text+0x8cf): undefined reference to `__libm_sse2_log'<br /> ray3DJHfor.c:(.text+0x96b): undefined reference to `__libm_sse2_asin'<br /> ray3DJHfor.c:(.text+0x9cd): undefined reference to `__libm_sse2_asin'<br /> ray3DJHfor.c:(.text+0xa00): undefined reference to `__libm_sse2_tan'<br /> ray3DJHfor.c:(.text+0xa3d): undefined reference to `__libm_sse2_tan'<br /> ray3DJHfor.c:(.text+0xa52): undefined reference to `__libm_sse2_log'<br /> collect2: ld returned 1 exit status<br /> make[2]: *** [BBtoolbox.exe] Error 1<br /> make[2]: Leaving directory `.../bbp_2g/src/sdsu/srcV1.4'<br /> make[1]: *** [all] Error 2<br /> make[1]: Leaving directory `.../bbp_2g/src/sdsu'<br /> make: *** [all] Error 2<br /> &lt;/pre&gt;<br /> <br /> '''Cause:''' In this case the user tried to build Broadband on a 32-bit platform. Broadband code was designed to be run on 64-bit platform. Any attempt to build Broadband on a 32-bit platform will result in numerous warnings and the build will fail with error messages similar to ones listed above.<br /> <br /> '''Solution:''' Try building Broadband on a 64-bit platform will the all the dependencies listed in Section 1.1: &quot;System Dependencies&quot; and Section 1.2: &quot;Software Dependencies&quot;<br /> <br /> === Unit/Acceptance Test Failures and Errors ===<br /> <br /> Unit and Acceptance tests are provided to verify the Broadband platform and it's supporting modules built by the user are functioning as designed. Under certain circumstances, some of these test might fail. While some of these failure might indicate serious problems that will have to be addressed before the platform can used, it is acceptable to ignore some of the failures. This section lists some failures and their solutions.<br /> <br /> ==== ERROR: test_syn1d (test_syn1d.Test_syn1D) ====<br /> The Unit test for Syn1d module fails with the following message:<br /> &lt;pre&gt;<br /> ERROR: test_syn1d (test_syn1d.Test_syn1D)<br /> ----------------------------------------------------------------------<br /> Traceback (most recent call last):<br /> File &quot;.../bbp_2g/tests/test_syn1d.py&quot;, line 62, in test_syn1d<br /> synObj.run()<br /> File &quot;.../bbp_2g/comps/syn1D.py&quot;, line 236, in run<br /> shutil.copy2(a_tmpfile, expected_file)<br /> File &quot;/usr/lib/python2.6/shutil.py&quot;, line 99, in copy2<br /> copyfile(src, dst)<br /> File &quot;/usr/lib/python2.6/shutil.py&quot;, line 52, in copyfile<br /> fsrc = open(src, 'rb')<br /> IOError: [Errno 2] No such file or directory: '.../bbp_2g/tmpdata/3310632/s01.3comp'<br /> &lt;/pre&gt;<br /> <br /> '''Cause:''' Syn1d module requires the Green's Function file to run and the path to this file might be incorrect in 'bbp_2g_gf/ucsb/GreenBank/Northridge/GreenBank.inf' file.<br /> <br /> '''Solution:''' This issue can be fixed by correcting the paths listed in the GreenBank.inf files in the Green's Function directory. Here are step by step instructions to fix this issue:<br /> <br /> 1. Locate your Greens Functions directory: 'bbp_2g_gf'<br /> 2. Navigate to bbp_2g_gf/ucsb/GreenBank/Northridge folder.<br /> 3. Open Green_Bank.inf files with a text editor.<br /> 4. Locate the text &quot;The name of file to store Green Bank&quot;<br /> 5. Note the location of the Green Bank file under the line found in step 4, similar to &quot;/home/scec-00/scottcal/bband/bbp_2g_gf/ucsb/GreenBank/Northridge/Green_1d.soil&quot;.<br /> 6. Replace the path found in Step 5 with just the file name, in the case of Northridge it is &quot;Green_1d.soil&quot;<br /> 7. Save and close the Green_Bank.inf.<br /> 8. Navigate to bbp_2g_gf/ucsb/GreenBank/LomaPrieta folder and repeat steps 3-7. The name of the Green Bank file for LomaPrieta is &quot;Green_1d.LoPr&quot;.<br /> 9. Navigate to bbp_2g_gf/ucsb/GreenBank/Landers folder and repeat steps 3-7. The name of the Green Bank file for Landers is &quot;Green1D.Landers&quot;<br /> <br /> ==== ERROR: test_gensrf (test_genslip.Test_Genslip) ====<br /> The Unit test for Genslip module fails with the following message:<br /> &lt;pre&gt;<br /> ======================================================================<br /> ERROR: test_gensrf (test_genslip.Test_Genslip)<br /> ----------------------------------------------------------------------<br /> Traceback (most recent call last):<br /> File &quot;.../bbp_2g/tests/test_genslip.py&quot;, line 51, in test_gensrf<br /> gen.run()<br /> File &quot;.../bbp_2g/comps/genslip.py&quot;, line 153, in run<br /> ps.run()<br /> File &quot;.../bbp_2g/comps/plot_srf.py&quot;, line 52, in run<br /> shutil.copy2(&quot;%s/%s.ps.png&quot; % (a_tmpdir, self.r_srffile[0:self.r_srffile.find(&quot;.srf&quot;)]), &quot;%s/%s.png&quot; % (a_outdir, self.r_srffile[0:self.r_srffile.find(&quot;.srf&quot;)]))<br /> File &quot;/usr/lib/python2.6/shutil.py&quot;, line 99, in copy2<br /> copyfile(src, dst)<br /> File &quot;/usr/lib/python2.6/shutil.py&quot;, line 52, in copyfile<br /> fsrc = open(src, 'rb')<br /> IOError: [Errno 2] No such file or directory: '.../bbp_2g/tmpdata/3309008/3309008_test_eq.ps.png'<br /> &lt;/pre&gt;<br /> <br /> '''Cause:''' The Genslip module calls the Plot_SRF module to the plot the SRF file. Plot_SRF uses C-shell code to locate and use GMT package to plot the SRF file. This shell code might fail on some flavors of Linux with a message like &quot;Newline in variable name&quot; in the Plot_SRF log file.<br /> <br /> '''Solution:''' This issue can be fixed by editing the plot_SRF.csh file. Here are step by step instructions to fix this issue:<br /> <br /> 1. Locate shell script file: bbp_2g/src/plot/plot_SRF.csh<br /> 2. Open the file in your preferred text editor<br /> 3. Locate the line 'set FIND_GMT = $?'<br /> 4. Replace the line found in step 3 with 'set FIND_GMT = $status'<br /> 5. Locate the section of code that starts with the statement &quot;# FIND MAX. SLIP&quot;<br /> 6. Replace the following line in section found in step 5:<br /> &lt;pre&gt;<br /> set SMAX = `$XYZCODE calc_xy=$CALC_XY type=&quot;${TYPE}&quot; nseg=-1 &lt; $SLIPFILE.srf | \<br /> gawk -v m=$SMAX '{if($3&gt;m)m=$3;}END{printf &quot;%.0f\n&quot;,m;}'`<br /> <br /> with (collapse the statement to a single line by removing '\' at the end of first part of the statement):<br /> <br /> set SMAX = `$XYZCODE calc_xy=$CALC_XY type=&quot;${TYPE}&quot; nseg=-1 &lt; $SLIPFILE.srf | gawk -v m=$SMAX '{if($3&gt;m)m=$3;}END{printf &quot;%.0f\n&quot;,m;}'`<br /> &lt;/pre&gt;<br /> 7. Save the file and exit<br /> <br /> ==== ERROR: test_ucgen (test_ucrmg.Test_UCrmg) ====<br /> The Unit test for Ucrmg module fails with the following message:<br /> &lt;pre&gt;<br /> ======================================================================<br /> ERROR: test_ucgen (test_ucrmg.Test_UCrmg)<br /> ----------------------------------------------------------------------<br /> Traceback (most recent call last):<br /> File &quot;.../bbp_2g/tests/test_ucrmg.py&quot;, line 59, in test_ucgen<br /> ucObj.run()<br /> File &quot;.../bbp_2g/comps/ucrmg.py&quot;, line 161, in run<br /> ps.run()<br /> File &quot;.../bbp_2g/comps/plot_srf.py&quot;, line 52, in run<br /> shutil.copy2(&quot;%s/%s.ps.png&quot; % (a_tmpdir, self.r_srffile[0:self.r_srffile.find(&quot;.srf&quot;)]), &quot;%s/%s.png&quot; % (a_outdir, self.r_srffile[0:self.r_srffile.find(&quot;.srf&quot;)]))<br /> File &quot;/usr/lib/python2.6/shutil.py&quot;, line 99, in copy2<br /> copyfile(src, dst)<br /> File &quot;/usr/lib/python2.6/shutil.py&quot;, line 52, in copyfile<br /> fsrc = open(src, 'rb')<br /> IOError: [Errno 2] No such file or directory: '.../bbp_2g/tmpdata/3309831/test_ucsb.ps.png'<br /> &lt;/pre&gt;<br /> <br /> '''Cause:''' The Ucrmg module calls the Plot_SRF module to the plot the SRF file. Plot_SRF uses C-shell code to locate and use GMT package to plot the SRF file. This shell code might fail on some flavors of Linux with a message like &quot;Newline in variable name&quot; in the Plot_SRF log file.<br /> <br /> '''Solution:''' This issue can be fixed by editing the plot_SRF.csh file. The steps to fix this issue are listed under the solution for &quot;ERROR: test_gensrf (test_genslip.Test_Genslip)&quot; above.<br /> <br /> ==== FAIL: test_site_amp (test_uc_site.Test_UC_Site) ====<br /> <br /> The unit test for UC-Site module might fail with the following message:<br /> &lt;pre&gt;<br /> ======================================================================<br /> FAIL: test_site_amp (test_uc_site.Test_UC_Site)<br /> ----------------------------------------------------------------------<br /> Traceback (most recent call last):<br /> File &quot;.../bbp_2g/tests/test_uc_site.py&quot;, line 92, in test_site_amp<br /> self.failIf(cmp_bbp.cmp_bbp(a_ref_file_no_header, test_file_no_header, tolerance=0.035)!=0,errmsg)<br /> AssertionError: Output file .../bbp_2g/tmpdata/3310633/s04.3comp does not match reference file .../bbp_2g/ref_data/ucsb/s04.site.3comp<br /> &lt;/pre&gt;<br /> <br /> '''Cause:''' The synthetic seismogram generated by the UC-Site module on the user system differs from the reference result included in the Broadband release.<br /> <br /> '''Solution:''' The stochastic nature of the high frequency simulations is considered, and a constant random seed as input for our tests. This is the same constant random seed used to generate the reference results included in the release. This ensures that the time-series generated with unit tests agree with reference results. However, the high frequency codes are more sensitive to changes in compilers and machines due to the algorithm, so small differences that cause the test to fail are generally acceptable. The user is however encouraged to plot the two time-series and visually inspect them to verify they look similar. We are trying to come up with a better comparison for these tests.<br /> <br /> = Appendix C: Technical Notes =<br /> <br /> == Running Individual Acceptance Tests ==<br /> <br /> The acceptance test script ./tests/AcceptTest.py attempts to run all of the defined tests when executed. However, sometimes it is useful to run an acceptance test in isolation for troubleshooting purposes:<br /> <br /> * Identify the test you want to run. Eg: user-URS-UCSB-SDSU-SDSU<br /> * Move to the ./comps directory and execute that test's XML workflow with run_bbp_2G.py. Using the above example:<br /> &lt;pre&gt;<br /> $ ./run_bbp_2G.py -x ../ref_data/accept_inputs/user-URS-UCSB-SDSU-SDSU.xml<br /> &lt;/pre&gt;<br /> <br /> Since you are running the test outside of AcceptTest.py, you will not see a PASS/FAIL message once the simulation completes. However, you can review the contents of the ./outdata/&lt;SIMID&gt; directory to verify that the correct seismograms and response spectra tables were produced.<br /> <br /> == Manaully Setting Random Number Generator Seed Values ==<br /> <br /> Several of the platform codebases employ random number generators to produce SRFs and seismograms. These random number generators are generally seeded with an initial value (typically an integer) which are hard-coded in the platform. Advanced users may desire to change these seed values.<br /> <br /> Changing the seeds for seismogram synthesis varies depending on which codebase you want to use:<br /> <br /> * URS: Edit ./comps/hfsims_cfg.py, Line 43 &quot;self.RAND_NUM&quot;<br /> * UCSB: Edit ./src/ucsb/Syn1DSCEC/syn1D_LAH.f, Line 183 &quot;iseed&quot;, and recompile with &quot;make&quot;<br /> * SDSU:<br /> ** User event: Edit ./bbp_2g_gf/sdsu/scattering_generic.dat (seed values annotated in file)<br /> ** Validation event: Edit ./bbp_2g_gf/sdsu/&lt;event&gt;/scattering.dat</div> Patrices