Changes between Version 237 and Version 238 of ReviewHeuristicLab3.3.0Application

Timestamp:

04/29/10 02:06:22 (14 years ago)

Author:

swagner

Comment:

--

ReviewHeuristicLab3.3.0Application

@@ -19 +19 @@
   * The breakpoint icon looks a bit big
  * In some way we need to make the best solution available to view. When you're optimizing something other than benchmark problems you'll probably want to make use of the best solution.
- * Run collection: By drag-drop runs can be duplicated (also reported by vdorfer)
+ * Run collection: By drag-drop runs can be duplicated (also reported by vdorfer).
+   * swagner: Dropping runs into a run collection is allowed to enable users to copy/move interesting runs into a run collection and to analyze these runs later on. If we disable drop operations on run collections to avoid the duplication of runs, this will not be possible anymore. Do you think that this feature is not required?
 
 === Priority: HIGH ===
@@ -175 +176 @@
 
  * Is it really intended that runs in the run tab can be copied (through drag&drop)?
+   * swagner: Dropping runs into a run collection is allowed to enable users to copy/move interesting runs into a run collection and to analyze these runs later on. If we disable drop operations on run collections to avoid the duplication of runs, this will not be possible anymore. Do you think that this feature is not required?
  * The "Show Algorithm" button in the run tab opens a new tab containing the algorithm but no runs and no results - shouldn't it rather show the problem tab in the current algorithm?
+   * swagner: A new algorithm view is shown as the algorithm stored in a run is cloned when "Show Algorithm" is clicked to avoid any manipulation of the algorithm that created the run. The algorithm stored in a run does not contain any runs or results as this would require too much memory.
  * In the results view I would show by default the quality data table (instead of first having to stop (pause) the algorithm, select the data table and resume the algorithm). When the tour visualization is done, this would be best to show by default.
    * swagner: Showing results by default is critical, as the continuous redraw of a result's value (e.g. quality chart, tour visualization) might consume a lot of runtime. Therefore the user should have to select a result manually, if he wants to look at a result.