Changes between Version 304 and Version 305 of ReviewHeuristicLab3.3.0Application

Timestamp:

05/07/10 09:35:51 (15 years ago)

Author:

gkronber

Comment:

exception in architecture altering manipulators

ReviewHeuristicLab3.3.0Application

@@ -88 +88 @@
  * Read-only parameters would be nice (similar to the data items of `HeuristicLab.Data`)
  * Importing new data into a symbolic regression problem for which a solution already exists throws an exception.
-
-=== Priority: MEDIUM ===
- * Only the best R², best MSE and best relative error should be collected into the results.
- * Max, min and avg. tree size should not be collected into the results.
+ * Using an architecture manipulation operator when the number of function defining branches or function arguments is set to 0 leads to an exception.
+
+=== Priority: MEDIUM ===
  * R², MSE, and relative Error of the best solution (for test and training set) should be collected into the results.
  * 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?
    * 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?
+ * Min selection granularity for the x-axis should be adapted to the range of displayed values in all line charts and scatter plots. 
+
+=== Priority: LOW ===
+ * Only the best R², best MSE and best relative error should be collected into the results.
+ * Max, min and avg. tree size should not be collected into the results.
+ * All quality values tracked for symbolic regression problems should have nicely formatted names.
  * Min selection granularity for zooming should be 1 for the x-axis in `SymbolicRegressionSolutionLineChartView`
- * Min selection granularity for the x-axis should be adapted to the range of displayed values in all line charts and scatter plots. 
  * Relative errors should be displayed as percentage values and rounded to ~4 digits after the decimal point.
-
-=== Priority: LOW ===
- * All quality values tracked for symbolic regression problems should have nicely formatted names.
 ----