4.3.1.5. eqcorrscan.core.match_filter.match_filter

eqcorrscan.core.match_filter.match_filter(template_names, template_list, st, threshold, threshold_type, trig_int, plotvar, plotdir=u'.', cores=1, tempdir=False, debug=0, plot_format=u'png', output_cat=False, extract_detections=False, arg_check=True)[source]

Main matched-filter detection function. Over-arching code to run the correlations of given templates with a day of seismic data and output the detections based on a given threshold. For a functional example see the tutorials.

Parameters:
  • template_names (list) List of template names in the same order as template_list
  • template_list (list) A list of templates of which each template is a Stream of obspy traces containing seismic data and header information.
  • st (obspy.core.stream.Stream) An obspy.Stream object containing all the data available and required for the correlations with templates given. For efficiency this should contain no excess traces which are not in one or more of the templates. This will now remove excess traces internally, but will copy the stream and work on the copy, leaving your input stream untouched.
  • threshold (float) A threshold value set based on the threshold_type
  • threshold_type (str) The type of threshold to be used, can be MAD, absolute or av_chan_corr. MAD threshold is calculated as the threshold*(median(abs(cccsum))) where cccsum is the cross-correlation sum for a given template. absolute threhsold is a true absolute threshold based on the cccsum value av_chan_corr is based on the mean values of single-channel cross-correlations assuming all data are present as required for the template, e.g. av_chan_corr_thresh=threshold*(cccsum/len(template)) where template is a single template from the input and the length is the number of channels within this template.
  • trig_int (float) Minimum gap between detections in seconds.
  • plotvar (bool) Turn plotting on or off
  • plotdir (str) Path to plotting folder, plots will be output here, defaults to run location.
  • tempdir (str) Directory to put temporary files, or False
  • cores (int) Number of cores to use
  • debug (int) Debug output level, the bigger the number, the more the output.
  • plot_format (str) Specify format of output plots if saved
  • output_cat (bool) Specifies if matched_filter will output an obspy.Catalog class containing events for each detection. Default is False, in which case matched_filter will output a list of detection classes, as normal.
  • extract_detections (bool) Specifies whether or not to return a list of streams, one stream per detection.
  • arg_check (bool) Check arguments, defaults to True, but if running in bulk, and you are certain of your arguments, then set to False.
Returns:

class:‘DETECTIONS’ detections for each channel formatted as :class: ‘obspy.UTCDateTime’ objects.

Returns:

class:obspy.Catalog containing events for each detection.

Returns:

list of :class: obspy.Stream objects for each detection.

Note

Plotting within the match-filter routine uses the Agg backend with interactive plotting turned off. This is because the function is designed to work in bulk. If you wish to turn interactive plotting on you must import matplotlib in your script first, when you them import match_filter you will get the warning that this call to matplotlib has no effect, which will mean that match_filter has not changed the plotting behaviour.

Note

The output_cat flag will create an :class: obspy.Catalog containing one event for each :class: ‘DETECTIONS’ generated by match_filter. Each event will contain a number of comments dealing with correlation values and channels used for the detection. Each channel used for the detection will have a corresponding :class: Pick which will contain time and waveform information. HOWEVER, the user should note that, at present, the pick times do not account for the prepick times inherent in each template. For example, if a template trace starts 0.1 seconds before the actual arrival of that phase, then the pick time generated by match_filter for that phase will be 0.1 seconds early. We are looking towards a solution which will involve saving templates alongside associated metadata.