Changes between Version 301 and Version 302 of ReviewHeuristicLab3.3.0Application


Ignore:
Timestamp:
05/07/10 09:26:04 (12 years ago)
Author:
gkronber
Comment:

added a few symb reg issues

Legend:

Unmodified
Added
Removed
Modified
  • ReviewHeuristicLab3.3.0Application

    v301 v302  
    8787=== Priority: HIGH ===
    8888 * Read-only parameters would be nice (similar to the data items of `HeuristicLab.Data`)
    89 
    90 === Priority: MEDIUM ===
     89 * Importing new data into a symbolic regression problem for which a solution already exists throws an exception.
     90
     91=== Priority: MEDIUM ===
     92 * Only the best R², best MSE and best relative error should be collected into the results.
     93 * Max, min and avg. tree size should not be collected into the results.
     94 * R², MSE, and relative Error of the best solution (for test and training set) should be collected into the results.
    9195 * It seems strange now that operators have the property `Breakpoint`. It is more usual to set breakpoints on invocations/calls of operators. Also isn't the engine responsible for breakpoints?
    9296   * swagner: As in HL 3.2 the `Breakpoint` property is implemented in operators and can be changed in the GUI of an `OperatorGraph`. Additionally, I decided to add a checkbox to each operator in order to be able to mark breakpoints there as well (this was not possible in HL 3.2). If an operator is marked as breakpoint, an engine stops its execution after this operator has been processed. I agree that it would be more intuitive to store it in some other location, which operators are currently breakpoints. However, I do not immediately know where. Any suggestions?
     
    9498
    9599=== Priority: LOW ===
    96 
     100 * All quality values tracked for symbolic regression problems should have nicely formatted names.
    97101----
    98102