Changes between Version 17 and Version 18 of binder_ew


Ignore:
Timestamp:
05/05/12 11:52:59 (8 years ago)
Author:
branden
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • binder_ew

    v17 v18  
    834834}}} 
    835835 
    836 rmscut value                            bind_com                location 
    837  
    838  Sets a maximum value (seconds) for the 
    839 average absolute residual (rms) for a successful location. If this value is exceeded as a result of 
    840 culling, scavenging, or associating a new phase, the event is marked as 
    841 destroyed and all of its phases are deassigned.  
    842    
     836'''rmscut [value]'''[[BR]] 
     837Processed by: bind_com[[BR]] 
     838Function: location 
     839 
     840Sets a maximum value (seconds) for the average absolute residual (rms) for a successful location. If this value is exceeded as a result of culling, scavenging, or associating a new phase, the event is marked as destroyed and all of its phases are deassigned.  
     841{{{ 
    843842Default:  rmscut 1.0                    Calnet:  rmscut 1.0 
    844  
    845  
    846  
    847  
    848 rmscut_pick threshold number_of_picks                           bind_com                location 
    849  
    850  Sets a maximum value (seconds) threshold for the 
    851 average absolute residual (rms) 
    852 for a successful location that 
    853 must be met unless number_of_picks is observed. 
    854 If this value is exceeded as a result of 
    855 culling, scavenging, or associating a new phase, and not enough picks are observed, then the event is marked as 
    856 destroyed and all of its phases are deassigned. Please note that you can have as many of these rmscut_pick commands as you need but 
    857 the threshold must be in increasing order. At Caltech we found that when a mainshock and foreshock were close together 
    858 in time, then the mainshock event would get killed if just an RMS of 1.0 was used. By creating this 
    859 command  we allowed many picks (indicating it was a largish event, to overrule the rmscut threshold and allow the automatic location to go through). 
    860    
     843}}} 
     844 
     845'''rmscut_pick [threshold number_of_picks]'''[[BR]] 
     846Processed by: bind_com[[BR]] 
     847Function: location 
     848 
     849Sets a maximum value (seconds) threshold for the average absolute residual (rms) for a successful location that must be met unless number_of_picks is observed. If this value is exceeded as a result of culling, scavenging, or associating a new phase, and not enough picks are observed, then the event is marked as destroyed and all of its phases are deassigned. Please note that you can have as many of these rmscut_pick commands as you need but the threshold must be in increasing order. At Caltech we found that when a mainshock and foreshock were close together in time, then the mainshock event would get killed if just an RMS of 1.0 was used. By creating this command  we allowed many picks (indicating it was a largish event, to overrule the rmscut threshold and allow the automatic location to go through). 
     850{{{ 
    861851Default:  NOT USED                      Calnet:  rmscut_pick 1.0 100 
    862  
    863  
    864  
     852}}} 
    865853  
    866 rmsgrid value                           grid_com                stack 
    867  
    868  No longer used.  
    869  
    870  
    871  
    872 rstack rstack                           grid_com                stack 
    873  
    874  Defines the distance (km) over which 
    875 phases are 
    876 allowed to interact with other phases during the stacking analysis. rstack defines the 
    877 dimensions of the stacking travel-time template, whose cell size is 
    878 defined by "dspace" (an rstack of 100 and a dspace of 10 would yield a 
    879 10 x 10 travel time template). Phases from stations that are more than 
    880 2*rstack km apart will not stack together 
    881 other because their stacking templates will not overlap.  
    882    
     854'''rmsgrid [value]'''[[BR]] 
     855Processed by: grid_com[[BR]] 
     856Function: stack 
     857 
     858No longer used.  
     859 
     860'''rstack [rstack]'''[[BR]] 
     861Processed by: grid_com[[BR]] 
     862Function: stack 
     863 
     864Defines the distance (km) over which phases are allowed to interact with other phases during the stacking analysis. rstack defines the dimensions of the stacking travel-time template, whose cell size is defined by "dspace" (an rstack of 100 and a dspace of 10 would yield a 10 x 10 travel time template). Phases from stations that are more than 2*rstack km apart will not stack together other because their stacking templates will not overlap.  
     865{{{ 
    883866Default:  rstack  100.0                 Calnet:  rstack  100.0 
    884  
    885  
    886  
    887  
    888 site name latitude longitude            site_com                model 
    889  
    890  Enters a station location into the station 
    891 site table, 
    892 where name is the station code used by the 
    893 picker, and latitude and longitude 
    894 are expressed in decimal degrees (positive to the north and east). Use 
    895 either multiple "site" commands or one "site_file" command to load 
    896 the station list into binder_ew.  
    897  
    898  
    899  
    900 site_file filename                      site_com                model 
    901  
    902  Enters site codes and station 
    903 locations into the 
    904 site table by reading 
    905 a HYPOINVERSE format station file called filename. 
    906 In this file, 
    907 stations are described by a 5-letter site name, a 2-letter network 
    908 code and a 3-letter component code. The picker must also be using this 
    909 station-naming convention. The format of the file is described under "HYPOINVERSE STATION FILE FOR 
    910 FULL 12-LETTER (S-N-C-L) CHANNEL NAMES". Use either one "site_file" 
    911 command or 
    912 multiple "site" commands to load the station list into binder_ew. 
    913  
    914   
    915  
    916 stack mstack                            grid_com                stack 
    917  
    918  Determines how many previously received 
    919 picks are to 
    920 be considered in the stacking process. A value of 50 to 100 seems 
    921 appropriate, although 
    922 if the scatter in reporting delays is large, a larger value of mstack may be required.  
    923    
     867}}} 
     868'''site [name latitude longitude]'''[[BR]] 
     869Processed by: site_com[[BR]] 
     870Function: model 
     871 
     872Enters a station location into the station site table, where name is the station code used by the picker, and latitude and longitude are expressed in decimal degrees (positive to the north and east). Use either multiple "site" commands or one "site_file" command to load the station list into binder_ew.  
     873 
     874'''site_file [filename]'''[[BR]] 
     875Processed by: site_com[[BR]] 
     876Function: model 
     877 
     878Enters site codes and station locations into the site table by reading a HYPOINVERSE format station file called filename. In this file, stations are described by a 5-letter site name, a 2-letter network code and a 3-letter component code. The picker must also be using this station-naming convention. The format of the file is described under "HYPOINVERSE STATION FILE FOR FULL 12-LETTER (S-N-C-L) CHANNEL NAMES". Use either one "site_file" command or multiple "site" commands to load the station list into binder_ew.  
     879 
     880'''stack [mstack]'''[[BR]] 
     881Processed by: grid_com[[BR]] 
     882Function: stack 
     883 
     884Determines how many previously received picks are to be considered in the stacking process. A value of 50 to 100 seems appropriate, although if the scatter in reporting delays is large, a larger value of mstack may be required.  
     885{{{ 
    924886Default:  stack 20                      Calnet:  stack 50 
    925  
    926  
    927  
    928  
    929 t_dif tmin tmax                         bind_com                associaton 
    930  
    931  Defines a time range (seconds) around an 
    932 event 
    933 origin-time (origin-time minus tmin to origin-time plus tmax). If a 
    934 pick-time falls outside of this time range for a given event, binder_ew 
    935 will not 
    936 attempt to associate that pick with that event.  
    937    
     887}}} 
     888 
     889'''t_dif [tmin tmax]'''[[BR]] 
     890Processed by: bind_com[[BR]] 
     891Function: associaton 
     892 
     893Defines a time range (seconds) around an event origin-time (origin-time minus tmin to origin-time plus tmax). If a pick-time falls outside of this time range for a given event, binder_ew will not attempt to associate that pick with that event.  
     894{{{ 
    938895Default:  t_dif -1.0 120.0              Calnet:  t_dif -3.0 120.0 
    939  
    940  
    941  
    942   
    943 taper r resmax                          bind_com                association 
    944  
    945  Defines a distance-dependent tolerance 
    946 for 
    947 associating, culling, or scavenging a phase, where r 
    948 is the distance (km) and resmax is the 
    949 maximum allowed residual (seconds). Multiple taper commands (up to 100) 
    950 can be issued, in order of increasing r, to 
    951 define the tolerance function. Between the distances specified, the 
    952 value of the cutoff residual changes linearly between corresponding resmax values. For distances less than the lowest 
    953 value specified, the cutoff 
    954 residual is constant at the resmax value for 
    955 the smallest distance; for distances exceeding the maximum specified, 
    956 the cutoff is constant at the resmax value 
    957 set for the maximum distance. If no "taper" 
    958 commands are supplied, the cutoff residual is a constant 1.0 sec for 
    959 all distances.  
    960    
     896}}} 
     897 
     898'''taper [r resmax]'''[[BR]] 
     899Processed by: bind_com[[BR]] 
     900Function: association 
     901 
     902Defines a distance-dependent tolerance for associating, culling, or scavenging a phase, where r is the distance (km) and resmax is the maximum allowed residual (seconds). Multiple taper commands (up to 100) can be issued, in order of increasing r, to define the tolerance function. Between the distances specified, the 
     903value of the cutoff residual changes linearly between corresponding resmax values. For distances less than the lowest value specified, the cutoff residual is constant at the resmax value for the smallest distance; for distances exceeding the maximum specified, the cutoff is constant at the resmax value set for the maximum distance. If no "taper" commands are supplied, the cutoff residual is a constant 1.0 sec for all distances.  
     904{{{ 
    961905Default:  constant 1.0 sec              Calnet:  taper   0.0   1.0 
    962                                                  taper  50.0   1.0 
     906                                                 taper  50.0   1.0 
    963907                                                 taper  200.0  2.5 
    964908                                                 taper  400.0  4.5 
    965  
    966  
    967  
    968  
    969 taper_OT const1 const2                  bind_com                association 
    970  
    971  Sets constants for two additional 
    972 terms to be 
    973 added to the residual- tolerance function (described for "taper" 
    974 command). These 2 terms widen the residual-tolerance for events with 
    975 greater location uncertainty. The first added term (multiplied by const1) depends on the event rms and the number of 
    976 picks associated with the event. The second additional term is: const2 * log10(distance of closest station) 
    977 To eliminate the event origin-time uncertainty terms, use the command: 
     909}}} 
     910 
     911'''taper_OT [const1 const2]'''[[BR]] 
     912Processed by: bind_com[[BR]] 
     913Function: association 
     914 
     915Sets constants for two additional terms to be added to the residual- tolerance function (described for "taper" command). These 2 terms widen the residual-tolerance for events with greater location uncertainty. The first added term (multiplied by const1) depends on the event rms and the number of picks associated with the event. The second additional term is: const2 * log10(distance of closest station) To eliminate the event origin-time uncertainty terms, use the command: 
    978916taper_OT 0.0 0.0  
     917{{{ 
     918Default:  taper_OT 2.0 2.0              Calnet:  taper_OT 2.0 1.0 
     919}}} 
     920  
     921'''thresh [mthresh]'''[[BR]] 
     922Processed by: grid_com[[BR]] 
     923Function: stack 
     924 
     925Sets the cell-count above which to consider declaring an earthquake from a stack. A completed stack is examined to prepare a list of cells that share the maximum count value and the same minimum distance to the initiating phase. The associator declares a new hypocenter from the stack only if the maximum count value is greater than mthresh and the number of cells in the list is less than nfocus (see "focus" command). The trial hypocenter for the declared event is calculated by averaging the center positions of all the cells in the maximum-count list. mthresh should be greater than 3 times the maximum increment specified by "grid_wt" commands to ensure that at least 4 phases contribute to declaration of a new earthquake.   
     926{{{ 
     927Default:  thresh 6                      Calnet:  thresh 14 
     928}}} 
     929 
     930'''tstack [tstack]'''[[BR]] 
     931Processedby: grid_com[[BR]] 
     932Function: stack 
     933 
     934Defines how close (in seconds) the back-projection of one phase must lie with respect to the back-projection of another phase for the two phases to be considered coherent (ie, from the same source). The value of tstack should reflect the degree of crustal heterogeneity as shown in the range of station delays. As a first approximation, tstack should be at least the number of seconds it takes for a P-wave to cross a grid cell of dspace km.  
     935{{{ 
     936Default:  tstack 0.5                    Calnet:  tstack  0.65 
     937}}} 
     938 
     939'''v_halfspace [vel]'''[[BR]] 
     940Processed by: assess_com[[BR]] 
     941Function: pick assess 
     942 
     943Sets the P-wave velocity vel in km/sec of the halfspace used in the pick-assessing process to locate events by the Ingelada method and to calculate travel-times residuals (see "assess_pk" command).  
     944{{{   
     945Default:  v_halfspace 5.0               Calnet:  v_halfspace 5.0 
     946}}} 
     947  
     948'''wt [quality weight]'''[[BR]] 
     949Processed by: bind_com[[BR]] 
     950Function: location 
     951 
     952Controls the weight of a pick in the event location process based on the quality assigned to the pick by the picker. Picks with a quality of 0 are the most reliable, those with quality 4 are least reliable.  
    979953   
    980 Default:  taper_OT 2.0 2.0              Calnet:  taper_OT 2.0 1.0 
    981  
    982  
    983  
    984   
    985 thresh mthresh                          grid_com                stack 
    986  
    987  Sets the cell-count above which to 
    988 consider 
    989 declaring an earthquake from a stack. A completed stack is examined to 
    990 prepare a list of cells that share the maximum count value and the same 
    991 minimum distance to the initiating phase. The associator declares a new 
    992 hypocenter from the stack only if the maximum count value is greater 
    993 than mthresh and the number of cells in the 
    994 list is less than nfocus (see "focus" command). The trial hypocenter 
    995 for the declared event is calculated by averaging the center positions 
    996 of all the cells in the maximum-count list. mthresh 
    997 should be greater than 3 times 
    998 the maximum increment specified by "grid_wt" commands to ensure that at 
    999 least 4 phases contribute to declaration of a new earthquake.  
    1000    
    1001 Default:  thresh 6                      Calnet:  thresh 14 
    1002  
    1003  
    1004  
    1005  
    1006 tstack tstack                           grid_com                stack 
    1007  
    1008  Defines how close (in seconds) the 
    1009 back-projection 
    1010 of one phase must lie with respect to the back-projection of another 
    1011 phase for the two 
    1012 phases to be considered coherent (ie, from the same source). The value 
    1013 of tstack should reflect the degree of 
    1014 crustal heterogeneity as shown in the range of station delays. As a 
    1015 first approximation, tstack should be at 
    1016 least the number of seconds it takes for a P-wave to cross a grid cell 
    1017 of dspace km.  
    1018    
    1019 Default:  tstack 0.5                    Calnet:  tstack  0.65 
    1020  
    1021  
    1022  
    1023  
    1024 v_halfspace vel                         assess_com              pick assess 
    1025  
    1026  Sets the P-wave velocity vel 
    1027 in km/sec of the halfspace used in the pick-assessing process to locate 
    1028 events by the Ingelada method and to calculate travel-times residuals 
    1029 (see "assess_pk" command).  
    1030    
    1031 Default:  v_halfspace 5.0               Calnet:  v_halfspace 5.0 
    1032  
    1033  
    1034  
    1035   
    1036 wt quality weight                       bind_com                location 
    1037  
    1038  Controls the weight of a pick in the event 
    1039 location 
    1040 process based on the quality assigned to the pick by the picker. Picks 
    1041 with a quality 
    1042 of 0 are the most reliable, those with quality 4 are least reliable.  
    1043    
    1044 quality is any of 
    1045 the values 0, 1, 2, 3, or 4 
    1046  
    1047     weight is a number between 0.0 and 1.0, 
    1048 inclusive.  
    1049  
    1050   If no "wt" commands are supplied, all picks receive a 
    1051 quality-weight 
    1052 of 1.0. If at least one "wt" command is supplied, other qualites that 
    1053 have not been listed by "wt" are weighted 0.0. The overall weight of a 
    1054 pick in the location is the product of its phase-weight (see "ph" 
    1055 command) and quality-weight divided by the taper value (see "taper" 
    1056 command) at the appropriate distance.  
    1057    
     954quality is any of the values 0, 1, 2, 3, or 4 
     955 
     956weight is a number between 0.0 and 1.0, inclusive.  
     957 
     958If no "wt" commands are supplied, all picks receive a quality-weight of 1.0. If at least one "wt" command is supplied, other qualites that have not been listed by "wt" are weighted 0.0. The overall weight of a pick in the location is the product of its phase-weight (see "ph" command) and quality-weight divided by the taper value (see "taper" command) at the appropriate distance.  
     959{{{   
    1058960Default:  all qualities/1.0 weight      Calnet:  wt 0 1.0 
    1059961                                                 wt 1 0.5 
    1060962                                                 wt 2 0.25 
    1061963                                                 wt 3 0.125 
    1062  
    1063  
    1064  
    1065  
    1066 zrange zmin zmax                        hyp_com                 location 
    1067  
    1068  Defines the valid range (km) for 
    1069 computed 
    1070 hypocentral depth. The range specified by zmin 
    1071 and zmax must span the depth range set in the 
    1072 "grdz" command; otherwise, events may stack outside of the zrange limit 
    1073 and this could cause locator logic errors. If during the iteration 
    1074 process, the depth falls outside of the zmin-zmax range, a fixed-depth 
    1075 solution is calculated starting at the previous iteration's hypocenter. 
    1076 This feature is useful in controlling locations from network "glitches" 
    1077 where all picks are concurrent and the apparent high phase velocity 
    1078 would try to locate the quake at the center of the Earth.  
    1079    
     964}}} 
     965 
     966'''zrange [zmin zmax]'''[[BR]] 
     967Processed by: hyp_com[[BR]] 
     968Function: location 
     969 
     970Defines the valid range (km) for computed hypocentral depth. The range specified by zmin and zmax must span the depth range set in the "grdz" command; otherwise, events may stack outside of the zrange limit and this could cause locator logic errors. If during the iteration process, the depth falls outside of the zmin-zmax range, a fixed-depth solution is calculated starting at the previous iteration's hypocenter. This feature is useful in controlling locations from network  glitches" where all picks are concurrent and the apparent high phase velocity would try to locate the quake at the center of the Earth.  
     971{{{   
    1080972Default:  zrange 2.0 20.0               Calnet:  zrange 1.0 30.0 
    1081  
     973}}} 
    1082974 
    1083975== Helpful Hints ==