search

GNS-Science / eq-fault-geom

python tools for manipulating fault geometries
MIT License
0 stars 1 forks source link

Check that crustal data export excludes subduction geometries #24

Open chrisbc opened 4 years ago

chrisbc commented 4 years ago

@andy22b I found the CFM XML contains the following elements which look supspiciously like subduction data.

Can you help us figure out if they're considered Crustal or not? & If NOT, then we need a feature that can filter these out.

Hikurangi

(eq-fault-geom) chrisbc@tryharder-ubuntu:~/DEV/GNS/eq-fault-geom/src$>grep Hikurangi NZ_CFM_V0.3_crustal_opensha.xml
    <i152 sectionId="152" sectionName="Hikurangi Hawke Bay" aveLongTermSlipRate="44.0" slipRateStDev="3.0" aveDip="0.0" aveRake="90.0" aveUpperDepth="0.0" aveLowerDepth="20.0" aseismicSlipFactor="0.0" couplingCoeff="1.0" dipDirection="296.8" parentSectionId="-1" connector="false">
      <FaultTrace name="Hikurangi Hawke Bay">
    <i153 sectionId="153" sectionName="Hikurangi Raukumara" aveLongTermSlipRate="54.0" slipRateStDev="6.0" aveDip="0.0" aveRake="90.0" aveUpperDepth="0.0" aveLowerDepth="20.0" aseismicSlipFactor="0.0" couplingCoeff="1.0" dipDirection="301.4" parentSectionId="-1" connector="false">
      <FaultTrace name="Hikurangi Raukumara">
    <i154 sectionId="154" sectionName="Hikurangi Wellington" aveLongTermSlipRate="25.0" slipRateStDev="5.0" aveDip="0.0" aveRake="90.0" aveUpperDepth="0.0" aveLowerDepth="30.0" aseismicSlipFactor="0.0" couplingCoeff="1.0" dipDirection="336.4" parentSectionId="-1" connector="false">
      <FaultTrace name="Hikurangi Wellington">

Puysegur

(eq-fault-geom) chrisbc@tryharder-ubuntu:~/DEV/GNS/eq-fault-geom/src$ grep Puys NZ_CFM_V0.3_crustal_opensha.xml 
    <i431 sectionId="431" sectionName="Puysegur" aveLongTermSlipRate="27.0" slipRateStDev="9.0" aveDip="20.0" aveRake="115.0" aveUpperDepth="0.0" aveLowerDepth="15.0" aseismicSlipFactor="0.0" couplingCoeff="1.0" dipDirection="101.3" parentSectionId="-1" connector="false">
      <FaultTrace name="Puysegur">
    <i432 sectionId="432" sectionName="Puysegur Ridge" aveLongTermSlipRate="14.0" slipRateStDev="14.0" aveDip="85.0" aveRake="180.0" aveUpperDepth="0.0" aveLowerDepth="12.0" aseismicSlipFactor="0.0" couplingCoeff="1.0" dipDirection="107.8" parentSectionId="-1" connector="false">
      <FaultTrace name="Puysegur Ridge">
chrisbc commented 4 years ago

@andy22b I see it should be easy enough to filter out using standard dataframes in the calling script. For now, until we know the status, I'm going to remove those suspect fault sections as they're causing some issues in opensha.