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
DBScan epsilon parameter cannot be logged with version 5.1
awchisholm
RapidMiner Certified Expert, Member Posts: 458 Unicorn
Hello all,
I'm trying to investigate how DBScan behaves as eplison and min_points are varied but I noticed warnings when the process attempts to log the min_points parameter of the DBScan operator.
"No such parameter in 'com.rapidminer.parameter.ParameterTypeValue$OperatorValueSelection@1bfa971b"
And sure enough, there are missing values in the log output.
I just upgraded to 5.1 and I'm fairly sure this worked with the last 5.0 version.
I'm working on a macro driven workaround which I will post when I get it working.
regards
Andrew
I'm trying to investigate how DBScan behaves as eplison and min_points are varied but I noticed warnings when the process attempts to log the min_points parameter of the DBScan operator.
"No such parameter in 'com.rapidminer.parameter.ParameterTypeValue$OperatorValueSelection@1bfa971b"
And sure enough, there are missing values in the log output.
I just upgraded to 5.1 and I'm fairly sure this worked with the last 5.0 version.
I'm working on a macro driven workaround which I will post when I get it working.
regards
Andrew
0
Answers
Andrew
I do not see the problem here. Logging works for me. Can you send me the example process?
Greetings,
Sebastian
If you run the process I already provided, it shows the problem.
However, I had a look at the XML and I noticed this... I then edited the entry by explicitly choosing another value from the "edit parameter list" dialog box and then re-choosing the epsilon value and lo and behold... So it looks like if the parameter being selected is the first one in the dropdown list, a missing value is put in the XML although it looks like it has been selected.
regards,
Andrew
now I see the problem. until you have chosen one of the possibilities explicitly, you don' have an entry at all.
I'll try to fix it.
Greetings,
Sebastian
can you do me the favor and request it as a bugfix in our bugtracker? It's not that easy and I won't get it finished before my xmas holidays.
Greetings,
Sebastian
merry christmas