Free cookie consent management tool by TermsFeed Policy Generator

Changes between Version 9 and Version 13 of Ticket #2431


Ignore:
Timestamp:
07/28/15 14:44:33 (9 years ago)
Author:
abeham
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #2431 – Description

    v9 v13  
    44
    55Necessary tasks:
    6  1. Create analyzers that calculate the quality progress with respect to function evaluations and also with respect to wall-clock time
    7  2. Create a run collection view that will calculate and compare the ECDF in one chart
     6~~1. Create analyzers that calculate the quality progress with respect to function evaluations and also with respect to wall-clock time~~
     7~~2. Create a run collection view that will calculate and compare the ECDF in one chart~~
    88
    99TODO:
    1010 * ECDF comparison view:
    11   * Minimization is assumed when comparing against levels -> extract Maximization parameter from run
    12   * Logscaling sometimes fails breaking the chart
    13   * Test with view open and new runs arriving
    14   * Add feature to calculate fixed-cost and fixed-target values and add them to the runs
     11  * ~~Minimization is assumed when comparing against levels -> extract Maximization parameter from run~~
     12  * ~~Logscaling sometimes fails breaking the chart~~
     13  * ~~Test with view open and new runs arriving~~
     14  * ~~Add feature to calculate fixed-cost and fixed-target values and add them to the runs~~
    1515 * IRRestarter:
    16   * Count number of restarts
    17   * Difficult to abort Algorithm earlier as the Analyzers may not have run
     16  * ~~Count number of restarts~~
     17  * ~~Difficult to abort Algorithm earlier as the Analyzers may not have run~~
    1818
    1919Design issues:
    20  * Algorithm Execution time is hard to obtain (similar problem with the introduction of terminators)
    21   * Here algorithms add this as a result
     20 * ~~Algorithm Execution time is hard to obtain (similar problem with the introduction of terminators)~~
     21  * The precision of execution time from the algorithm was not good enough (~200ms), so the analyzer counts execution time by itself
    2222 * ResultParameter's ActualValue property is confusing, I had to lookup usage of this parameter myself
    23  * Move-based algorithms often output EvaluatedMoves, we should probably have all algorithms output EvaluatedSolutions
     23 * ~~Move-based algorithms often output EvaluatedMoves, we should probably have all algorithms output EvaluatedSolutions~~
     24  * Instead, I added a cost factor for moves
    2425 * Analyzers depend on BestAverageWorstQualityAnalyzer, in my opinion best-so-far quality and execution time are results that the algorithm itself must provide and not an analyzer