Free cookie consent management tool by TermsFeed Policy Generator

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


Ignore:
Timestamp:
03/06/10 00:28:23 (14 years ago)
Author:
swagner
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • ReviewHeuristicLab3.3.0Application

    v12 v13  
    77 * 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.
    88 * 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.
     9   * swagner: Set the button to be invisible in r2947.
    910 * In the user defined algorithm:
    1011   * 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).
     
    1314   * Selecting an operator in "Operator Graph" does not bring up the details in the details view.
    1415   * Should there really be a view host in the operator graph group box? It's confusing being able to switch views there (also because these are always just views on the initial operator which can be viewed with view host in the details group box as well).
     16     * swagner: Removed view host in r2947.
    1517   * The flow chart is very nice, but sometimes arrows are a bit wild and going backwards which creates a not so nice strikethrough appearance. Would be good to have non-direct arrows as well.
    1618 * Creating a user defined algorithm from the SGA doesn't reconfigure the SGA operator with the parameters set in the SGA interface.
     
    2022   * How do I set the (allowed) evaluation operator?
    2123   * Why do I want to change e.g. "TSPRoundedEuclideanPathEvaluator" in the textbox "Name" when viewing Parameter "Evaluator"?
     24     * 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?
    2225   * Would be nice to have paste support (e.g. from Excel) in the datagrid of the string convertible matrix view.
    2326   * Would be nice to be able to view a "scatter plot" of the coordinates.
     
    3033   * The view host icon should act like a button that when single-clicked opens the context-menu, when hovering over it, there should be a frame around it like a button so that it's clear that it can be clicked.
    3134 * In my user defined algorithm:
    32    * I have added an SGAOperator and set it as initial operator. I added crossover, mutation, evaluation and selection: !ProportionalSelector has a Parameter "!CurrentScope" that cannot be changed in any way, is there a necessity to display this parameter? After selecting !CurrentScope, all further parameters will be displayed as !ParameterView and appear as if they cannot be changed. I had to change the view manually in the view host. Sometimes it seems to select the "wrong" default views. It reverts back to !ParameterView as default as soon as !CurrentScope is clicked again.
     35   * I have added an SGAOperator and set it as initial operator. I added crossover, mutation, evaluation and selection: !ProportionalSelector has a Parameter "!CurrentScope" that cannot be changed in any way, is there a necessity to display this parameter?
     36     * swagner: The scope parameter "!CurrentScope" indicates that the current scope (i.e. its sub-scopes) is manipulated by an operator. It is shown in order to give the user comprehensive information about what an operator does. Maybe this is not really helpful. Should I remove scope parameters in general? In the code of an operator they are not really required, as the current scope can always be accessed via the current execution context.
     37   * After selecting !CurrentScope, all further parameters will be displayed as !ParameterView and appear as if they cannot be changed. I had to change the view manually in the view host. Sometimes it seems to select the "wrong" default views. It reverts back to !ParameterView as default as soon as !CurrentScope is clicked again.
    3338   * !InversionManipulator has the "correct" actual name set already (Permutation), however in !OrderCrossover the default names are "Parents" and "Child" which have to be changed to Permutation. This isn't obvious right away when the string description of the parameter says: "Child: Child (Permutation)".
     39     * swagner: Set the actual name of the parents and child parameter to "Permutation" by default in r2947.
    3440   * My initial expectations probably weren't correct regarding the user defined algorithm. The SGA operator is not a complete SGA, but just the main loop (yes we discussed this).
    3541 
     
    3844   * swagner: Removed `Creatable` attribute in r2924.
    3945 * When creating e.g. a new TSP in the parameter collection view the tool tip doesn't really display the description of the parameter but just a very generic one.
     46   * swagner: Changed to more specific tool tips in r2947.
    4047 * There is a typo in the description of the parameters (tooltips), it says "it" instead of "in".
     48   * swagner: Fixed in r2947.
    4149 * "Breakpoint" doesn't explain if it breaks before or after executing the operator.
    4250 * Focus is not removed from a textbox if one clicks anywhere in the "gray" area.
     51   * swagner: This is the behavior of Windows Forms.
    4352 * The available parameters view lists just one namespace which is collapsed by default (should be expanded if it's just this one).
    4453 * There should be a nicer way of saying the chart controls are not installed instead of an exception.
     54   * swagner: The HeuristicLab setup will check if the Microsoft Chart Controls are installed and will show a meaningful error message.
    4555 
    4656----