Ok, I will try option 1 first.

Thanks

On Mon, Nov 4, 2013 at 6:14 AM, Geoffrey De Smet <[email protected]>wrote:

>  Either:
>
> 1) add a hard constraint to penalize what you don't want
>
> 2) look into ValueRangeProvider from entity (see docs), which effectively
> makes it a build-in hard constraint.
>
> 3) Use Filtering in both the Local Search selectors as the CH selectors
> (but the CH selector usage is not yet documented).
> This 3) option is very difficult, especially for SwapMove's.
>
> I recommend 1) by default.
> Also don't expect that CH's give you a feasible solution, use LS on top of
> CH's to get a good, feasible solution.
> See "phase overview" section in the docs.
>
>
> On 03-11-13 17:29, Tales Costa wrote:
>
> Hi all,
>
>  I am new to Optaplanner and would like some help on understanding how to
> control the planning value chosen by Optaplanner.
>
>  Based on the info on User Guide and the NQueen example, I understand
> that  for Local Search algorithms one can use the Move interface (for
> example  to forbid some specific row change).
>
>  However, for the  Construction heuristics have not found any similar
> option. For these algoritms the only option seems to be to make load
> adjustements on the score calculations (as the nqueens example does for
> queens on the same row).  Is this correct or am I missing something ?
>
>  Regards
>
>  Tales
>
>
> _______________________________________________
> rules-users mailing 
> [email protected]https://lists.jboss.org/mailman/listinfo/rules-users
>
>
>
> _______________________________________________
> rules-users mailing list
> [email protected]
> https://lists.jboss.org/mailman/listinfo/rules-users
>
_______________________________________________
rules-users mailing list
[email protected]
https://lists.jboss.org/mailman/listinfo/rules-users

Reply via email to