[
https://issues.jboss.org/browse/JBRULES-3490?page=com.atlassian.jira.plug...
]
Geoffrey De Smet commented on JBRULES-3490:
-------------------------------------------
"winner" is ambiguous (scope plannerBenchmark vs problemBenchmark). Proposal:
call the plannerBenchmark winner the "favorite". Then ranking becomes problem
ranking and favorite ranking.
Otherwise, if plannerBenchmark would get a better name, we can just always scope the
winner term: "problemWinner" and "plannerBenchmarkWinner".
Planner: Benchmark report improvements wish list
------------------------------------------------
Key: JBRULES-3490
URL:
https://issues.jboss.org/browse/JBRULES-3490
Project: Drools
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: drools-planner
Reporter: Geoffrey De Smet
Assignee: Geoffrey De Smet
A) I really miss the yellow line in benchmark results table - it was
pretty obvious what the winning result is. Now it's just the green box
around ranking and that is hard to find. If the whole line was green,
that'd be different...
B) Wouldn't Twitter Bootstrap allow for sorting the table if I click on
the header? That way, I could sort the table by rank, average etc.
C) The "(winner)" text only appears in the "Winning score difference
summary chart". No other chart shows what the winner is, and that's too
bad. => Fixed on summary charts, but not on problem charts at the moment, because
"winner" is ambiguous. It's clear though we want to "overall
winner" there.
So we need a different term then winner.
D) Also, locating the winner visually among 20 or 30 lines is very hard.
What about drawing it differently? A thick line in line graphs and some
different filling in bar graphs?
--
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