[KIEKER-1075] OPAD filters missing in OPAD integration branch

[rju]

JIRA Issue: KIEKER-1075 OPAD filters missing in OPAD integration branch Original Reporter: Imported User 22

---

The kieker JAR attached to wiki:opad includes filters that are missing in the integration branch:

1. kieker.tools.opad.filter.SendAndStoreDetectionResultFilter
1. kieker.tools.opad.filter.VariateForecastingFilter
1. kieker.tools.opad.filter.VariateTSPointAggregatorFilter
1. kieker.tools.opad.filter.VariateUniteFMPFilter

What's their purpose, where are the sources and shouldn't they be in the branch?

[rju]

author André van Hoorn -- Wed, 12 Feb 2014 17:20:50 +0100

Attached filter sources and corresponding JUnit tests from KIEKER-1052 Done to this ticket.

[rju]

author Thomas F. Düllmann -- Fri, 9 May 2014 12:34:56 +0200

Replying to KIEKER-1075 Done :
> The kieker JAR attached to wiki:opad includes filters that are missing in the integration branch:
>
> 1. kieker.tools.opad.filter.SendAndStoreDetectionResultFilter
> 1. kieker.tools.opad.filter.VariateForecastingFilter
> 1. kieker.tools.opad.filter.VariateTSPointAggregatorFilter
> 1. kieker.tools.opad.filter.VariateUniteFMPFilter
>
> What's their purpose, where are the sources and shouldn't they be in the branch?

The filters mentioned above are now in the opad-tslib-integration branch.

Their (new) names are:
1. kieker.tools.opad.filter.SendAndStoreDetectionResultFilter
1. kieker.tools.opad.filter.ForecastingFilter
1. kieker.tools.opad.filter.TimeSeriesPointAggregatorFilter
1. kieker.tools.opad.filter.UniteMeasurementPairFilter

Purpose:
1. Outputs the detection results and stores them in a MongoDB to keep a forecasting history
1. The filter that does the core forecasting being able to use several forecasting methods
1. Aggregates the incoming time series points
1. Combines the forecasted and actually measured values