🎉 🎉 RAPIDMINER 9.10 IS OUT!!! 🎉🎉
Download the latest version helping analytics teams accelerate time-to-value for streaming and IIOT use cases.
Bug in Optimize Parameter operator?
I was using k-nn inside optimize parameter (inside X-Validation) operator... and I was using euklidean and camberra distance for opt parameter settings...
but I noticed, that when using name "k-NN (2)" inside opt. parameter, it does not change the numerical_measure type... when I use a standard name "k-NN", it does change the parameters during running... seems to be a minor bug caused by the naming of the parameter as I experienced it?