data.edit.mentor.generate.spikefilter generates segments that represent detected spikes in data. The parameters used to detect them are defined by a spikefilter.conf.

Command Line Usage

data.segmentation.spikefilter [--type=type] [--feedback]
                              configFile station start end



The spikefilter.conf file to read the filters to apply from.

start and end

The time specifiers to calculate data on. Start is inclusive while end is exclusive, so all edits intersecting within the half open interval [start,end) will be returned. Any convertible time format is accepted. These are required even if input is being read from standard input (for the neph errors segmentation lookup).


The station identifier code. For example 'brw'. Case insensitive.


Select the source archive to request data from, defaulting to raw.


Enable progress feedback on standard error.


Output is a series of detected spike segments on standard output of the form:


start and end

The start and end of this edit in epoch time.


The type specified in the configuration file followed by all records defined as being affected by the filter series that detected this spike.


The list of variables that the spike applies to. This may include more than the variable(s) that actually spiked if the filter was defined as being applied to all variables in a set (for example a neph backscatter spike may apply to all neph wavelengths and total scattering).


An automatically generated comment about what caused the spike. This is a list of the sub-filters that are included in this spike segment.

Example Usage

data.segmentation.spikefilter /aer/db/etc/spikefilter.conf sgp 2008:290 2008:300