Changes between Version 24 and Version 25 of ReviewHeuristicLab3.3.0Application
- Timestamp:
- 03/11/10 01:08:54 (14 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
ReviewHeuristicLab3.3.0Application
v24 v25 6 6 7 7 === Priority: HIGH === 8 * 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.9 * swagner: Changed in r2948.10 * 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.11 * swagner: Set the button to be invisible in r2947.12 * In the user defined algorithm:13 * 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).14 * swagner: Fixed in r2948.15 8 * The operator graph view is a bit confusing: 16 9 * 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). 17 10 * swagner: "Successor" is required to identify an operator parameter. Of course, in the case of `ResultsCollector`, `SubScopesSorter`, etc. there is only one operator parameter, but there are other operators which have multiple operator parameters (e.g. branches). If we skip the parameter name, the user will not be able to tell which operator parameter is shown in the tree view. 18 * Selecting an operator in "Operator Graph" does not bring up the details in the details view.19 * swagner: Fixed in r2949.20 * 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).21 * swagner: Removed view host in r2947.22 11 * 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. 23 12 * swagner: In a discussion with maffenze it was decided to address this issue after the release of HeuristicLab 3.3.0. 24 * Creating a user defined algorithm from the SGA doesn't reconfigure the SGA operator with the parameters set in the SGA interface.25 * swagner: Fixed as described in ticket #898.26 13 * Adding a `ValueParameter<T>` in a `VariableCreator` and selecting a generic type e.g. `ItemList<T>` fails because no choice can be made on the generic type of the `ItemList` (ticket #42). 27 14 * Even when a control is not displayed (e.g. the global scope tab) its view is updated which costs a lot of time. The optimization runs noticeably faster (~2x) when HeuristicLab isn't the active application in Windows (at least in Win7). … … 29 16 === Priority: MEDIUM === 30 17 * The TSP problem view: 31 * How do I set the (allowed) evaluation operator?32 * swagner: Enabled changing values of value parameters in r2948.33 18 * Why do I want to change e.g. "TSPRoundedEuclideanPathEvaluator" in the textbox "Name" when viewing Parameter "Evaluator"? 34 19 * 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? … … 37 22 * `BestKnownTour` is missing as parameter. 38 23 * All Parameters have the same icon, can we have different ones for values and operators? 39 * The `ViewHost` menu contains a lot of views which are quite similar. `ItemView` doesn't display anything, should it be selectable? `ParameterView` and `NamedItemView` are very similar. Sometimes there are only very fine differences between the views (e.g. a `ParameterView` and a `NamedItemView`).40 * mkommend: Changed in r2992 as described in ticket #902.41 24 * 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. 42 25 * swagner: When hovering over the view host icon a tool tip is displayed that explains how the different views can be selected. 43 26 * In my user defined algorithm: 44 * I have added an SGAOperator and set it as initial operator. I added crossover, mutation, evaluation and selection: !ProportionalSelectorhas a Parameter "!CurrentScope" that cannot be changed in any way, is there a necessity to display this parameter?27 * 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? 45 28 * 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. 46 * 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. 47 * swagner: Fixed in r2949. 48 * !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)". 49 * swagner: Set the actual name of the parents and child parameter to "Permutation" by default in r2947. 29 * swagner: In a discussion with maffenze it was decided to keep scope parameters. 50 30 * 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). 51 31 * `LeftSelector` and `RightSelector` should not be displayed as selection operators in an SGA (there is a related ticket #673). 52 32 * When clicking "start" to start the engine disabling of the user interface elements has similar problems to what we fixed a few revisions ago (ticket #887) 53 * I'd wish there was just a value view as well. Sometimes I want to hide name, description, type, set, remove, ... elements and just display the value (e.g. when viewing the quality chart) (we discussed this)54 * swagner: Added `VariableValueView` in r2989.55 33 * In the operator graph chart view: 56 34 * The vertical scroll bar allows scrolling way past the graph. … … 65 43 66 44 === Priority: LOW === 67 * Sequential engine should probably not be createable. At least currently there's nothing one could do with just an engine.68 * swagner: Removed `Creatable` attribute in r2924.69 * 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.70 * swagner: Changed to more specific tool tips in r2947.71 * There is a typo in the description of the parameters (tooltips), it says "it" instead of "in".72 * swagner: Fixed in r2947.73 * "Breakpoint" doesn't explain if it breaks before or after executing the operator.74 * swagner: Added tool tip in r2949.75 45 * Focus is not removed from a textbox if one clicks anywhere in the "gray" area. 76 46 * swagner: This is the behavior of Windows Forms. 77 * The available parameters view lists just one namespace which is collapsed by default (should be expanded if it's just this one).78 * swagner: Changed in r2953.79 47 * There should be a nicer way of saying the chart controls are not installed instead of an exception. 80 48 * swagner: The HeuristicLab setup will check if the Microsoft Chart Controls are installed and will show a meaningful error message. … … 82 50 * The button for changing the evaluation in the TSP view features "+" which is used for adding, not setting in other views. 83 51 * swagner: In a discussion with maffenze it was decided to use the "+" icon for adding and for setting values as long as there is no better idea which icon to use for setting values. 84 * When you remove the value of the results (such as " BestQuality") the text in the box does not update.52 * When you remove the value of the results (such as "!BestQuality") the text in the box does not update. 85 53 * swagner: Fixed updating in r2989. 86 * Does it make sense to remove these values? 87 * Does it make sense to change the name of the variables under "Results"? 54 * Does it make sense to change the name of result variables or to remove their values? 88 55 * The quality chart looks great! 89 56 * We should probably use the same colors we had in 1.1 for best/average/worst qualities. 90 * " BestKnownQuality" is not displayed currently.57 * "!BestKnownQuality" is not displayed currently. 91 58 * Would be good to be able to hide certain lines. 92 59 * At some point we'll certainly need export to png,eps functionality (would be great to be able to specify resolution and width/height). … … 100 67 101 68 == Reviewer: gkronber == 69 102 70 === Priority: HIGH === 103 71 * The plugin management GUI is not finished. … … 117 85 === Priority: LOW === 118 86 * `ProgrammableOperator`: 'Compile' is a normal button but 'Show Generated Code' looks like a label. I think the style should be unified. 119 * Are keyboard shortcuts for groupboxes necessary? E.g. __D__etails groupbox and __D__escription shortcuts are conflicting. __V__alue groupbox and __V__alue textbox are conflicting.120 * swagner: Removed keyboard shortcuts for all groupboxes in r2924.121 * Description of !RandomCreator should contain a hint about the type of PRNG that is created.122 * swagner: Done in r2924.123 87 124 88 ---- … … 127 91 128 92 === Priority: HIGH === 129 * After starting an SGA the user is able to add a new problem; the OK button in the following dialog is initially enabled, clicking it causes no (?) action.130 * swagner: Fixed in r2924.131 * Adding a new parameter, for example a `ValueParameter<IntData>`, leads to an exception.132 * swagner: Fixed in r2948.133 * After starting a SGA with 130 cities TSP and population size 100 the memory consumption is 1.2 GB after approx. 6500 generations.134 * swagner: Memory and runtime performance has been drastically improved in r2932.135 93 136 94 === Priority: MEDIUM === 137 95 138 96 * After starting a new SGA and loading a problem the "play" button is enabled; clicking it leads to a error report that might be not interpretable by each potential user. A rather complicated check of all parameters would be needed here (as we had it for example in HL 2) - this might be not essentially necessary for the initial release (?), but maybe we could keep it in mind. 139 * swagner: This issue is similar to one of the issues described by maffenze. Changed in r2924 that a selection and a crossover operator are automatically selected if available to avoid the cryptic error message. In general I would prefer to set reasonable parameters by default instead of implementing some (probably quite sophisticated) parameter validation procedure. 140 * After starting the SGA the current generation index is not displayed; I have to switch to the qualities chart to see the current generation. 141 * swagner: Added generations counter to results in r2924. 142 * During the run of an algorithm the values displayed for the variables `BestQuality`, `AverageQuality`, and `WorstQuality` flicker. 143 * swagner: Fixed in r2924. 97 * swagner: Changed in r2924 that a selection and a crossover operator are automatically selected if available to avoid the cryptic error message. In general I would prefer to set reasonable parameters by default instead of implementing some (probably quite sophisticated) parameter validation procedure. 144 98 145 99 === Priority: LOW === … … 148 102 * On a screen with resolution 1280x800 I can for example not change the group size of tournament selection because the text box is not visible (unless the !OptionalValueParameter View is chosen). 149 103 * swagner: Can you give me some hints where we can save space? Which information/controls might not be necessary? 150 * swinkler: As names and data types cannot be edited in the details sections of parameters, I would suggest combining these two into one TextBox and showing data types in brackets (as it is done in the list box shown left, e.g.).104 * swinkler: As names and data types cannot be edited in the details sections of parameters, I would suggest combining these two into one !TextBox and showing data types in brackets (as it is done in the list box shown left, e.g.). 151 105 * Regarding the description of operators (1): I would prefer to not to capitalize names of algorithms, i.e., for example I would prefer "... the standard genetic algorithm ..." over "... the Standard Genetic Algorithm ...". 152 106 * Regarding the description of operators (2): As the references to articles and books are incorporated in grammatically meaningful sentences (which I like a lot!) I would not use full stops (.) within references; I would use semicola (;) instead. … … 158 112 159 113 === Priority: HIGH === 160 * When no crossover is selected an error message is thrown which gives no hint about the reason.161 * swagner: This issue is similar to one of the issues described by swinkler. Changed in r2924 that a selection and a crossover operator are automatically selected if available to avoid the cryptic error message.162 114 * Something like a starter package of problems (which do not have to be imported before) should also be included in the release version. 163 115 * swagner: We can include several problems in the setup as it was the case in HL 1.1 or we can offer a set of problems on the same web page where the HL setup can be downloaded. I would prefer the second solution, as it is simpler to realize and the user can easily choose where he wants to save the sample problems. Furthermore, he can download the sample problems again if necessary without having to reinstall HL. However, the first solution has the benefit that the user does not have to download two files. Is the second solution acceptable? … … 171 123 172 124 === Priority: LOW === 173 * It is not obvious what is meant with the breakpoint option in an operator.174 * swagner: Added tool tip in r2949.175 125 176 126 ----
