Just put a breakpoint in AbstractTabuAccepter and debug your app and you
'll see what actually happens. You 'll probably want to use a
conditional breakpoint, so it only breaks when it's dealing with that move.
Are you using completePropertyTabu?
That shouldn't take a step back to where it cam
Hi Geoffrey,
I tried to follow your advice, but by debugging I noticed that he still did not
consider taboo the right moves.
For not implementing the changes to the solver I modified the data object model.
But now I have another problem, I do not understand the log.
Normally when I make a mo
Macro
You're making it way to complicated I think :)
You can probably revert all that fancy stuff and just do:
class MyMove ... {
private A a;
private B b;
private C c;
// I think this is what you need
// It's tabu if the other Move has a AND b
public Collection getTabuProperties() {
retur
Hi Geoffrey,
Today I tried to follow the process for selecting a tabu move through
propertytabuList. correct me if I misunderstood:
Make a moveCreate a collection of objects through the method
getTabuProperties()In the class AbstractTabuAccepter I check if at least one of
these objects is conta
