You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
(I develop the RapidProM extension for RM).
I found a (severe) bug in the "Loop Parameters" operator
In my experiments (I'm a researcher) I use the "Loop Parameters" operator a lot (com.rapidminer.operator.meta.ParameterIteration.java).
I just found out that in the doWork() method, the actual number of combinations (int numberOfCombinations) is counted twice.
In case of a very large number of iterations (which tends to happen in large scale experiments), the variable reaches an overflow and becomes negative.
As a result I get a UserError related to the fact that no valid parameter combination can be generated, i.e.:
if (numberOfCombinations < 1 || values.length == 0) {
throw new UserError(this, 958);
}
I can see some ways how to fix this, however, since I'm not very familiar with the meaning of all variables within the operator I guess it is best if one of you guys fixs this.
cheers,
Bas.
The text was updated successfully, but these errors were encountered:
Dear RapidMiner team,
(I develop the RapidProM extension for RM).
I found a (severe) bug in the "Loop Parameters" operator
In my experiments (I'm a researcher) I use the "Loop Parameters" operator a lot (com.rapidminer.operator.meta.ParameterIteration.java).
I just found out that in the doWork() method, the actual number of combinations (int numberOfCombinations) is counted twice.
In case of a very large number of iterations (which tends to happen in large scale experiments), the variable reaches an overflow and becomes negative.
As a result I get a UserError related to the fact that no valid parameter combination can be generated, i.e.:
if (numberOfCombinations < 1 || values.length == 0) {
throw new UserError(this, 958);
}
I can see some ways how to fix this, however, since I'm not very familiar with the meaning of all variables within the operator I guess it is best if one of you guys fixs this.
cheers,
Bas.
The text was updated successfully, but these errors were encountered: