-
Feature Request
-
Resolution: Done
-
Major
-
None
-
None
Each property would get a MatrixAxis alternative:
<acceptor> <propertyTabuMatrixAxis> <value>5</> <value>7</> <value>11</> </> <moveTabuMatrixAxis> <value>5</> <value>7</> <value>11</> <value>13</> </> </>
In the case above we would have 3 * 4 = 12 benchmarks, would could result in saying that propertyTabu 5 + moveTabu 13 is best but that propertyTabu 7 + moveTabu 11 is the runner up.
Technical problem: Don't want to litter AcceptorConfig with private MatrixAxis<int> propertyTabuMatrixAxis because non benchmark configs should not use it.
- is related to
-
-
- Open
-
-
-
- Open
-