The Altair Community is migrating to a new platform to provide a better experience for you. In preparation for the migration, the Altair Community is on read-only mode from October 28 - November 6, 2024. Technical support via cases will continue to work as is. For any urgent requests from Students/Faculty members, please submit the form linked here
no label after application of Series2WindowExamples in RM 4.4 CVS
Hi together,
what did once work with RapidMiner 4.3 unfortunately doesn't work with version 4.4 any more. I'm talking about the following scenario:
(Note: when i speak of RapidMiner 4.4 i actually mean the most recent CVS version as i am unable to install the officially released 4.4 version as it wants to update the already installed 4.3 version which i need.)
Thanks in advance,
Oliver
what did once work with RapidMiner 4.3 unfortunately doesn't work with version 4.4 any more. I'm talking about the following scenario:
(Note: when i speak of RapidMiner 4.4 i actually mean the most recent CVS version as i am unable to install the officially released 4.4 version as it wants to update the already installed 4.3 version which i need.)
- time series data read with ExampleSource (1 example, 4000 attributes, you might know it: sales_series.aml/dat)
- immediately after this: Series2WindowExamples with series_representation = encode_series_by_attributes, horizon = 1, window_size = 100, step_size = 5
As i have representation == SERIES_AS_ATTRIBUTES it is indeed correct that no label will be created. Now the code lets me believe that there is a good reason for this behavior which i might miss. I do remember that the help recommends encoding the series as examples in favor of efficiency with respect to the memory usage. Maybe with version 4.4 RapidMiner forces me to use another encoding by simply omitting the label attribute now? ;-) I mean, it is absolutely no problem to transpose the data prior to using Series2WindowExamples, i just wanted to know what's behind all this. Maybe i am really missing some important point here.
if (representation == SERIES_AS_EXAMPLES) {
Attribute seriesAttribute = exampleSet.getAttributes().iterator().next();
int valueType = seriesAttribute.getValueType();
return AttributeFactory.createAttribute("label", valueType);
} else {
return null;
}
Thanks in advance,
Oliver
Tagged:
0
Answers
the preferred way to transform series data into windowed examples is now the operator "MultivariateSeries2WindowExamples" for both the single and the multivariate cases (we seem to have forgotten to set the Single-variant to deprecated). Then the following process should still work:
The reason for the change actually was the new operators "WindowExamples2ModelingData" and "WindowExamples2OriginalData" which are additionally able to produce a relative value transformation usually delivering much better results for time series predictions. This, however, only works in the "encoding_as_examples" mode. Here is an example:
Cheers,
Ingo
I am not sure MultivariateSeries2WindowExamples will resolve this. Indeed, in RM 4.4 I am observing a similar problem with MultivariateSeries2WindowExamples. As long as the attribute which we want to be the label after windowing is a special attribute, MultivariateSeries2WindowExamples operator seems to fail to create a label attribute properly. You can observe what I've meant with the config file below. I just submitted a bug report regarding this.
Cheers,
Erk
thank you for committing a bug report and attaching the process. I will check that.
Greetings,
Sebastian