Re: [rules-users] [Optaplanner] Filter values => immovable planning entities

[Geoffrey De Smet]

On 12-12-13 18:11, Mats Norén wrote: Hi, I've got a domain with the following entities: entities? you mean classes? - Person (planning entity) - Desk (planning variable) a class cannot be a variable. This probably a problem fact that and person.getDesk() nor DeskAssignement.getPerson() is the planning variables. - DeskAssignment (solution) Now I am totally confused :) in the official examples, something called Assignment is a planning entity. All persons should be assigned to a desk according to some rules. What I would like to do is to make certain Persons and their Desk immovable, ie, they are assigned a desk in the initial solution and should be fixed there. They are only there for the score calculation. agreed, "immovable" is the correct concept to use for that I looked at 14.3.1 Immovable planning entities but couldn't really see how I would apply it to my use case. Take a look at the course scheduling example. Here's a demo of immovable planning entities in that example:   http://www.youtube.com/watch?v=4meWIhPRVn8 Why is the filter applied at the planning entity level? Since it's the planning variable that changes I thought that I should somehow filter the allowed values for the Desk. Don't mix the concept of "(im)movable entities" (which is what you want) with the concept of "limiting value ranges per entity" or the concept of "filtering specific move selectors" (which is overkill and convoluted for your needs). Regards, Mats   _______________________________________________ rules-users mailing list rules-users@lists.jboss.org https://lists.jboss.org/mailman/listinfo/rules-users

_______________________________________________
rules-users mailing list
rules-users@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users