[JBoss JIRA] (JBRULES-3451) Planner Benchmarker should detect a bad BEST_SOLUTION_CHANGED graph and warn about it
6:40 a.m.
Geoffrey De Smet created JBRULES-3451:
-----------------------------------------
Summary: Planner Benchmarker should detect a bad BEST_SOLUTION_CHANGED graph
and warn about it
Key: JBRULES-3451
URL: https://issues.jboss.org/browse/JBRULES-3451
Project: Drools
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: drools-planner
Reporter: Geoffrey De Smet
Assignee: Geoffrey De Smet
See the screenshot of the difference between a good graph and a bad graph.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:46 a.m.
[
https://issues.jboss.org/browse/JBRULES-3451?page=com.atlassian.jira.plug...
]
Geoffrey De Smet updated JBRULES-3451:
--------------------------------------
Attachment: good_vs_bad_graph.png
Planner Benchmarker should detect a bad BEST_SOLUTION_CHANGED graph
and warn about it
-------------------------------------------------------------------------------------
Key: JBRULES-3451
URL: https://issues.jboss.org/browse/JBRULES-3451
Project: Drools
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: drools-planner
Reporter: Geoffrey De Smet
Assignee: Geoffrey De Smet
Attachments: good_vs_bad_graph.png
See the screenshot of the difference between a good graph and a bad graph.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:54 a.m.
[
https://issues.jboss.org/browse/JBRULES-3451?page=com.atlassian.jira.plug...
]
Geoffrey De Smet updated JBRULES-3451:
--------------------------------------
Description:
See the screenshot of the difference between a good graph and a bad graph.
The quality of the graph can be determinated by taking the 10% of time Score relative to
the (final Score minus the first feasible score)
Extra difficulty is that this needs to be Score implementation agnostic.
Use Score.toDoubleArray() to this on every level (notice that the first feasible score
means the first feasible for that level).
was:See the screenshot of the difference between a good graph and a bad graph.
Planner Benchmarker should detect a bad BEST_SOLUTION_CHANGED graph
and warn about it
-------------------------------------------------------------------------------------
Key: JBRULES-3451
URL: https://issues.jboss.org/browse/JBRULES-3451
Project: Drools
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: drools-planner
Reporter: Geoffrey De Smet
Assignee: Geoffrey De Smet
Attachments: good_vs_bad_graph.png
See the screenshot of the difference between a good graph and a bad graph.
The quality of the graph can be determinated by taking the 10% of time Score relative to
the (final Score minus the first feasible score)
Extra difficulty is that this needs to be Score implementation agnostic.
Use Score.toDoubleArray() to this on every level (notice that the first feasible score
means the first feasible for that level).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
4928
days inactive
4928
days old
2 comments
1 participants
participants (1)
-
Geoffrey De Smet (JIRA)