There is a need in data science to be able to create a new data series that is the result of performing a point-wise mathematical operation against two series having the same number of elements. The principal mathematical operations of interest being that of subtraction, addition, multiplication, and division. It is called a point-wise operation because it performs the mathematical operation on one sample point at a time. For example, if the mathematical operation being performed is subtraction, then for two series each with N sample points, a new series is generated in which: ResultSeries1 = MinuendSeries1 - SubtrahendSeries1 ; ResultSeries2 = MinuendSeries2 - SubtrahendSeries2 ; ResultSeries3 = MinuendSeries3 - SubtrahendSeries3 ; ..., up to ResultSeriesN = MinuendSeriesN - SubtrahendSeriesN. The result series/1D array produced by the TD_BINARYSERIES_OP is the same size, 'N', as its inputs and inherits the identifiers, SERIES_ID(), in this case, from the minuend series.. Thus the TD_BINARYSERIES_OP takes two equally sized logical-runtime series as input - the first series referenced in the function call is referred to as being the 'primary series', whereas the second series referenced is the secondary series. The result series always inherits the identifiers, SERIES_ID() from the primary series. Mathematically, the significance of being a primary series or secondary series is as follows:. For MATHOP(SUB), subtraction, the secondary series is subtracted from the primary series.. For MATHOP(ADD), addition, the secondary series is added to the primary series.. For MATHOP(MUL), multiply, the primary series is multiplied by the secondary series.. For MATHOP(DIV), divide, the primary series is divided by the secondary series.. The TD_BINARYSERIES_OP function can be configured to operate in one of three input modes - ONE2ONE, MANY2ONE, and MATCH. These modes determine the number of primary series and number of secondary series involved in the operation, as well as determining how the primary and secondary series will be matched together. See the INPUT_FMT section for more information.. Some Use Case Examples for these Operators include:. A use for the subtraction - MATHOP(SUB) - and addition - MATHOP(ADD) - operations is to respectively remove trends from the original series and to later restore the trends while engaged in forecasting with the model. Some background for this is: In building statistical ARMA-style forecasting models, a necessary precondition is that the time series being modelled be stationary: stationary with respect to mean; stationary with respect to covariance; and, stationary with respect to variance. Transforming a non-stationary series into a stationary series typically requires the completion of two main tasks: the first task requiring the data scientist to model the trend or periodicity inherent in the data, then use that model to generate a representative series; the second task being to execute an operator that forms a new series, formed by subtracting the just generated trend or periodicity series from the original series. The TD_BINARYSERIES_OP function supplies just such an operator, it forms one or more new series by enabling the data scientist to perform a point-wise subtraction between the original series, aka, the 'minuend-series', and the series to be subtracted, aka, the 'subtrahend', so minuend minus subtrahend.. A use case for the multiplication - MATHOP(SUB) - comes with respect to applying a filter function against a time series. To apply a filter function - low pass, band pass, high pass - to a time series in the time domain requires a complex operation known as conjugation. In contrast, if one first were to take the Fourier Transform of the time series and the Fourier Transform of the filter series; transitioning both data series from the time domain over to the frequency domain, then while in the frequency domain, the filter could be applied simply by running the two Fourier result series through a point-wise multiplier to produce a filtered result in the frequency domain. In other words, conjugation in the time domain (a complex process) is equivalent to point-wise multiplication in the frequency domain. Once the multiplication operation is complete, the data scientist could then take the inverse transform of the multiplied result set, obtaining the filtered version of the time series.. Use case for TD_BINARYSERIES_OP - Removal of trends present within a time series. One task frequently performed by the Forecast Model developer is the removal of a trend from a time series, prior to modelling that series. There are several different approaches available to the data scientist for removing trends. As inferred in the below diagram, most of those involve executing a function against the original series that produces a new series containing the “trend”. This initial processing step is followed by another processing step in which the original series and “trend” series is run through a point-wise subtractor, which subtracts - for each sample time point - the trend series from the original, producing a third 'detrended' series. In other words, given an original series and a 'trend' series with five sample points at times: T0, T1, T2, T2, T4; the subtractor performs, original(T0) - trend(T0); original(T1) - trend(T1); …; original(T4) - trend(T4); producing a detrended series with five sample points. The net effect of this operation, see diagram below, is to create a new series that is “rotated down”, once the trend has been removed. Forecast Modelling can then proceed on the 'detrended' series.
To use this component in KNIME, download it from the below URL and open it in KNIME:
Download ComponentDeploy, schedule, execute, and monitor your KNIME workflows locally, in the cloud or on-premises – with our brand new NodePit Runner.
Try NodePit Runner!Do you have feedback, questions, comments about NodePit, want to support this platform, or want your own nodes or workflows listed here as well? Do you think, the search results could be improved or something is missing? Then please get in touch! Alternatively, you can send us an email to mail@nodepit.com, follow @NodePit on Twitter or botsin.space/@nodepit on Mastodon.
Please note that this is only about NodePit. We do not provide general support for KNIME — please use the KNIME forums instead.