[solver] Selector refactor: configurable subset selections,
topList usage etc
------------------------------------------------------------
-----------------
Key: JBRULES-1232
URL: http:/
/jira.jboss.com/jira/browse/JBRULES-1232
Project: JBoss Rules
Issue Type: Task
Security Level: Public (Everyone can see)
Components: Solver
Reporter: Geoffrey De Smet
Assigned To: Geoffrey De Smet
Currently all moves are evaluated at every step (with a
MaxAllForager at least) if you use the basic cached move
factory selector.
This doesn't scale well, especially for big data problems
where in the beginning, just about every moves improves.
The neighbourhood size (= amount of selected moves) could
for example increase block-wise or timeGradient-wise until
an improving solution is found.
Notice the difference with the usage of
FirstImprovingForager.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the
administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atl
assian.com/software/jira
_______________________________________________
jboss-jira mailing list
jboss-jira lists.jboss.org
h
ttps://lists.jboss.org/mailman/listinfo/jboss-jira
|
