Changes between Version 337 and Version 338 of ReviewHeuristicLab3.3.0Application
- Timestamp:
- 05/07/10 21:16:32 (15 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
ReviewHeuristicLab3.3.0Application
v337 v338 120 120 * There is no Help menu, and also no About dialog. 121 121 * I am not completely happy about being asked if I want to clear all runs after each click on the reset button. I would prefer to have a button for this in the runs section. 122 * I like the graphical display of the twodimensional test function solutions - I would suggest adding the display o nf min and max displayed values.122 * I like the graphical display of the twodimensional test function solutions - I would suggest adding the display of min and max displayed values. 123 123 * The details of the GP grammar currently used are not displayed. 124 124 125 125 === Priority: LOW === 126 127 * Regarding the description of operators: 128 * 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. 129 * In the symbReg problem parameter "SymbolicExpressionTreeInterpreter:" I would remove the ":" 130 131 === OPEN DISCUSSIONS === 132 126 133 * Could it be reasonable to display a special icon for parameters that are not yet set properly (e.g., with a red exclamation mark etc.)? 127 134 * swagner: This will be quite hard as it is not easy to decide programmatically, if a parameter is properly set or not. But we can think about it. Maybe we can introduce constrained parameters? Although it will be a lot of work to enable users to define constraints of parameters in the GUI (for example when adding a new parameter to a `CombinedOperator`). … … 129 136 * swagner: Can you give me some hints where we can save space? Which information/controls might not be necessary? 130 137 * 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.). 131 * Regarding the description of operators:132 * 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.133 * In the symbReg problem parameter "SymbolicExpressionTreeInterpreter:" I would remove the ":"134 138 * IMHO the standard selection operators in gender specific selection should be flipped; this would more reflect behavior in nature. The reason for this is that these selectors do not specify how fe/male individuals select their mates, but rather how they are selected. 135 139