Changes between Version 1 and Version 2 of FaultSystemSolution


Ignore:
Timestamp:
Jul 23, 2013, 4:40:56 PM (11 years ago)
Author:
Kevin Milner
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • FaultSystemSolution

    v1 v2  
    77You must write a parser for each of the following file formats in order to load in a fault system solution.
    88
    9 === Double array binary file ====
     9=== Double array binary file ===
    1010
    1111These files contain an array of double values in a binary format. These files simply contain a series of big endian 8 bit double precision floating point numbers. The size of this file will be equal to the number of values x 8 bits.
     
    2424
    2525'''[[span(style=color: #FF0000, 3)]] [[span(style=color: #0000FF, 4)]] 0 6 2 4 [[span(style=color: #0000FF, 3)]] 3 6 2 [[span(style=color: #0000FF, 6)]] 3 7 9 1 4 7'''
     26
     27In this example, '''[[span(style=color: #FF0000, the number of arrays is in red)]]''', '''[[span(style=color: #0000FF, each array's size in blue)]]''', '''and array data is in black'''.
     28
     29=== Fault section data XML file ===
     30
     31Each fault subsection is stored in an XML file, an example of which is shown below.
     32
     33{{{
     34<?xml version="1.0" encoding="UTF-8"?>
     35
     36<OpenSHA>
     37  <FaultSectionPrefDataList>
     38    <!--- Each fault subsection is listed in it's own element so ensure correct ordering.
     39Each subsection element name will be i0, i1, i2, ... i[N-1] for N subsections. Note that
     40some fields may be NaN for certain solutions. -->
     41    <i0 sectionId="0" sectionName="Los Alamos extension, Subsection 0" aveLongTermSlipRate="NaN"
     42slipRateStdDev="0.0" aveDip="30.0" aveRake="NaN" aveUpperDepth="0.0" aveLowerDepth="12.0"
     43aseismicSlipFactor="0.1" couplingCoeff="1.0" dipDirection="205.15857"
     44parentSectionName="Los Alamos extension" parentSectionId="780" connector="false">
     45      <!-- This defines a polygon representing the geologic fault zone. Note that UCERF3 uses
     46a combination of this polygon and a buffered fault trace as described in UCERF3 Appendix O. -->
     47      <ZonePolygon name="Unnamed Region">
     48        <LocationList>
     49          <Location Latitude="34.562639" Longitude="-119.867803" Depth="0.0"/>
     50          <Location Latitude="34.54856" Longitude="-119.878996" Depth="0.0"/>
     51          <Location Latitude="34.586297" Longitude="-119.926461" Depth="0.0"/>
     52          <Location Latitude="34.630493" Longitude="-120.091308" Depth="0.0"/>
     53          <Location Latitude="34.647866" Longitude="-120.086651" Depth="0.0"/>
     54          <Location Latitude="34.60288" Longitude="-119.919064" Depth="0.0"/>
     55        </LocationList>
     56      </ZonePolygon>
     57      <!-- This is the actual fault trace. Note that order is important and should follow the
     58Aki-Richards definition -->
     59      <FaultTrace name="Los Alamos extension 1">
     60        <Location Latitude="34.63918" Longitude="-120.08897999999999" Depth="0.0"/>
     61        <Location Latitude="34.608190666873426" Longitude="-119.97328407378366" Depth="0.0"/>
     62      </FaultTrace>
     63    </i0>
     64    <i1 sectionId="1" ...>
     65        ...
     66    </i1>
     67    ...
     68    <i[N-1] sectionId="[N-1]" ...>
     69        ...
     70    </i[N-1]>
     71  </FaultSectionPrefDataList>
     72</OpenSHA>
     73}}}