def detect(self, st, threshold, trig_int, moveout=<NUM_LIT:0>, min_trig=<NUM_LIT:0>,<EOL>process=True, extract_detections=False, cores=<NUM_LIT:1>, debug=<NUM_LIT:0>):
return _detect(detector=self, st=st, threshold=threshold,<EOL>trig_int=trig_int, moveout=moveout, min_trig=min_trig,<EOL>process=process, extract_detections=extract_detections,<EOL>debug=debug, cores=cores)<EOL>
Detect within continuous data using the subspace method.

:type st: obspy.core.stream.Stream
:param st:
    Un-processed stream to detect within using the subspace detector.
:type threshold: float
:param threshold: Threshold value for detections between 0-1
:type trig_int: float
:param trig_int: Minimum trigger interval in seconds.
:type moveout: float
:param moveout:
    Maximum allowable moveout window for non-multiplexed, network
    detection.  See note.
:type min_trig: int
:param min_trig:
    Minimum number of stations exceeding threshold for non-multiplexed,
    network detection. See note.
:type process: bool
:param process:
    Whether or not to process the stream according to the parameters
    defined by the detector.  Default is True, which will process the
    data.
:type extract_detections: bool
:param extract_detections:
    Whether to extract waveforms for each detection or not, if True
    will return detections and streams.
:type cores: int
:param cores: Number of threads to process data with.
:type debug: int
:param debug: Debug output level from 0-5.

:return: list of :class:`eqcorrscan.core.match_filter.Detection`
:rtype: list

.. warning::
    Subspace is currently in beta, see note in the subspace tutorial
    for information.

.. note::
    If running in bulk with detectors that all have the same
    parameters then you can pre-process the data and set process to
    False.  This will speed up this detect function dramatically.

.. warning::
    If the detector and stream are multiplexed then they must
    contain the same channels and multiplexed in the same order. This
    is handled internally when process=True, but if running in bulk
    you must take care.

.. note::
    Non-multiplexed, network detection.  When the detector is
    not multiplexed, but there are multiple channels within the
    detector, we do not stack the single-channel detection statistics
    because we do not have a one-size-fits-all solution for computing
    delays for a subspace detector (if you want to implement one, then
    please contribute it!).  Therefore, these parameters provide a
    means for declaring a network coincidence trigger using
    single-channel detection statistics, in a similar fashion to the
    commonly used network-coincidence trigger with energy detection
    statistics.