Changes between Version 13 and Version 14 of ReviewHeuristicLab3.3.0Application

Timestamp:

03/06/10 03:36:32 (14 years ago)

Author:

swagner

Comment:

--

ReviewHeuristicLab3.3.0Application

@@ -6 +6 @@
 === Priority: HIGH ===
  * Creating a new TSP problem and viewing the parameter "Coordinates": The view can be switched to an "!OptionalValueParameterView" which adds a button to delete the value. However when clicked an exception is thrown that the value cannot be null. The !OptionalValueParameterView should not be selectable (Coordinates is not an optional parameter). This also holds for other parameters like the !SolutionCreator.
+   * swagner: Changed in r2948.
  * When one creates a new user defined algorithm, the user finds a button called "Create User Defined Algorithm" button on the form. This feels strange.
    * swagner: Set the button to be invisible in r2947.
  * In the user defined algorithm:
    * On the parameter tab: I press "+" to add a new Parameter. I select a !ValueParameter, term it "!MutationRate" and select !DoubleData as type I get a !MissingMethodException (Constructor on type !ValueParameter not found).
+     * swagner: Fixed in r2948.
  * The operator graph view is a bit confusing:
    * The successor parameter reads "Successor: !ResultsCollector", "Successor: !SubScopesSorter", ... It's more readable if "Successor" was not present all the time (in the operator graph group box).
@@ -21 +23 @@
  * The TSP problem view:
    * How do I set the (allowed) evaluation operator?
+     * swagner: Enabled changing values of value parameters in r2948.
    * Why do I want to change e.g. "TSPRoundedEuclideanPathEvaluator" in the textbox "Name" when viewing Parameter "Evaluator"?
      * swagner: It is always allowed to change the name of an operator in order to be able to use more descriptive names when building operator graphs. Of course, this feature is not meaningful for the operator parameters of the TSP. However, as it is a general feature of operators I cannot really remove it for the TSP operators. But maybe this feature is not required for all operators as only some operators (combined operators, placeholders, etc.) need to have a custom name?
@@ -87 +90 @@
    * swagner: Fixed in r2924.
  * Adding a new parameter, for example a `ValueParameter<IntData>`, leads to an exception.
+   * swagner: Fixed in r2948.
  * After starting a SGA with 130 cities TSP and population size 100 the memory consumption is 1.2 GB after approx. 6500 generations.
    * swagner: Memory and runtime performance has been drastically improved in r2932.