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

GridParameterOptimization won't work with only one value

keithkeith Member Posts: 157 Maven
edited November 2018 in Help
I have a process where I am using GridParameterOptimization, where I intend to test a list of 5 or so values.  However, while I am developing the rest of the process, I want to have a single value in the list, to make sure the process runs successfully all the way through.  However, RapidMiner gives me an error when I try to run the process without multiple values to test:

Error in: GridParameterOptimization
No parameters were specified which should be optimized
You need to specify parameters of inner operators in order to allow the ParameterOptimization operation for optimization.

I realize this is a special case, as there is really no "optimizing" going on with only one value to test, but it seems like RM should execute the process with the single value, which obviously is chosen as "optimal".  Giving an error instead of a warning seems like an overreaction.  Am I missing something?

To be clear, this code fragment works:

        <operator name="GridParameterOptimization" class="GridParameterOptimization" expanded="yes">
            <list key="parameters">
              <parameter key="W-LWL.K" value="1000,10,100"/>
            </list>

This one does not:

        <operator name="GridParameterOptimization" class="GridParameterOptimization" expanded="yes">
            <list key="parameters">
              <parameter key="W-LWL.K" value="1000"/>
            </list>

Is this something fixable, or is there a reason I'm not aware of that explains this behavior?

Thanks,
Keith

Answers

  • TobiasMalbrechtTobiasMalbrecht Moderator, Employee-RapidMiner, Member Posts: 295 RM Product Management
    Hi Keith,
    keith wrote:

    I realize this is a special case, as there is really no "optimizing" going on with only one value to test, but it seems like RM should execute the process with the single value, which obviously is chosen as "optimal".  Giving an error instead of a warning seems like an overreaction.  Am I missing something?
    no, you are absolutely right. We should change that reaction in so far that RM only yields a warning message when only one parameter value is specified. Maybe we will be able to change that behaviour already for the next release which is about to come soon.

    Regards,
    Tobias
Sign In or Register to comment.