[JBoss JIRA] Created: (JBRULES-2911) Planner: simulated annealing should work for planning problems with many hard constraints broken
9:52 p.m.
Planner: simulated annealing should work for planning problems with many hard constraints
broken
------------------------------------------------------------------------------------------------
Key: JBRULES-2911
URL: https://issues.jboss.org/browse/JBRULES-2911
Project: Drools
Issue Type: Enhancement
Security Level: Public (Everyone can see)
Components: drools-planner
Reporter: Geoffrey De Smet
Assignee: Geoffrey De Smet
Priority: Minor
Fix For: 5.2.0.M2
This code is bad in SimulatedAnnealingAcceptor:
// TODO don't abuse translateScoreToGraphValue
// TODO do hard and soft separately and then average their acceptChance
Double diff =
localSearchSolverScope.getScoreDefinition().translateScoreToGraphValue(scoreDifference);
if (diff == null) {
// more hard constraints broken, ignore it for now
return 0.0;
}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:52 p.m.
New subject: [JBoss JIRA] Updated: (JBRULES-2911) Planner: simulated annealing should work for planning problems with hard constraints often broken too
[
https://issues.jboss.org/browse/JBRULES-2911?page=com.atlassian.jira.plug...
]
Geoffrey De Smet updated JBRULES-2911:
--------------------------------------
Summary: Planner: simulated annealing should work for planning problems with hard
constraints often broken too (was: Planner: simulated annealing should work for planning
problems with many hard constraints broken)
Planner: simulated annealing should work for planning problems with
hard constraints often broken too
-----------------------------------------------------------------------------------------------------
Key: JBRULES-2911
URL: https://issues.jboss.org/browse/JBRULES-2911
Project: Drools
Issue Type: Enhancement
Security Level: Public(Everyone can see)
Components: drools-planner
Reporter: Geoffrey De Smet
Assignee: Geoffrey De Smet
Priority: Minor
Fix For: 5.2.0.M2
This code is bad in SimulatedAnnealingAcceptor:
// TODO don't abuse translateScoreToGraphValue
// TODO do hard and soft separately and then average their acceptChance
Double diff =
localSearchSolverScope.getScoreDefinition().translateScoreToGraphValue(scoreDifference);
if (diff == null) {
// more hard constraints broken, ignore it for now
return 0.0;
}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:35 a.m.
New subject: [JBoss JIRA] Resolved: (JBRULES-2911) Planner: simulated annealing should work for planning problems with hard constraints often broken too
[
https://issues.jboss.org/browse/JBRULES-2911?page=com.atlassian.jira.plug...
]
Geoffrey De Smet resolved JBRULES-2911.
---------------------------------------
Resolution: Done
fixed, see reference manual and Upgrade recipe txt
Planner: simulated annealing should work for planning problems with
hard constraints often broken too
-----------------------------------------------------------------------------------------------------
Key: JBRULES-2911
URL: https://issues.jboss.org/browse/JBRULES-2911
Project: Drools
Issue Type: Enhancement
Security Level: Public(Everyone can see)
Components: drools-planner
Reporter: Geoffrey De Smet
Assignee: Geoffrey De Smet
Priority: Minor
Fix For: 5.2.0.M2
This code is bad in SimulatedAnnealingAcceptor:
// TODO don't abuse translateScoreToGraphValue
// TODO do hard and soft separately and then average their acceptChance
Double diff =
localSearchSolverScope.getScoreDefinition().translateScoreToGraphValue(scoreDifference);
if (diff == null) {
// more hard constraints broken, ignore it for now
return 0.0;
}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:39 a.m.
New subject: [JBoss JIRA] Issue Comment Edited: (JBRULES-2911) Planner: simulated annealing should work for planning problems with hard constraints often broken too
[
https://issues.jboss.org/browse/JBRULES-2911?page=com.atlassian.jira.plug...
]
Geoffrey De Smet edited comment on JBRULES-2911 at 3/1/11 2:37 AM:
-------------------------------------------------------------------
Fixed, from the upgrade recipe:
Simulated annealing now supports working with hard constraints too (JBRULES-2911)
The starting temperature (usually close the maximum score delta) is now a Score instead of
a double.
Before in *Config.xml:
<simulatedAnnealingStartingTemperature>20.0</simulatedAnnealingStartingTemperature>
After in *Config.xml (if you're using HardAndSoftScore):
<simulatedAnnealingStartingTemperature>0hard/20soft</simulatedAnnealingStartingTemperature>
After in *Config.xml (if you're using SimpleScore):
<simulatedAnnealingStartingTemperature>20</simulatedAnnealingStartingTemperature>
was (Author: ge0ffrey):
fixed, see reference manual and Upgrade recipe txt
Planner: simulated annealing should work for planning problems with
hard constraints often broken too
-----------------------------------------------------------------------------------------------------
Key: JBRULES-2911
URL: https://issues.jboss.org/browse/JBRULES-2911
Project: Drools
Issue Type: Enhancement
Security Level: Public(Everyone can see)
Components: drools-planner
Reporter: Geoffrey De Smet
Assignee: Geoffrey De Smet
Priority: Minor
Fix For: 5.2.0.M2
This code is bad in SimulatedAnnealingAcceptor:
// TODO don't abuse translateScoreToGraphValue
// TODO do hard and soft separately and then average their acceptChance
Double diff =
localSearchSolverScope.getScoreDefinition().translateScoreToGraphValue(scoreDifference);
if (diff == null) {
// more hard constraints broken, ignore it for now
return 0.0;
}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
4805
days inactive
4808
days old
3 comments
1 participants
participants (1)
-
Geoffrey De Smet (JIRA)