Opened 14 years ago
Last modified 7 years ago
#1420 assigned defect
Renaming of column names (and row names) of a DoubleMatrix is reset after some time
Reported by: | vdorfer | Owned by: | gkronber |
---|---|---|---|
Priority: | low | Milestone: | HeuristicLab 4.x Backlog |
Component: | Data.Views | Version: | 3.3.3 |
Keywords: | Cc: |
Description
In the NSGA-II a DoubleMatrix represents the resulting pareto front. After renaming the column names of this matrix the correct headers are shown, however quickly reset to "Objective 1", "Objective 2",... This whole process is performed each generation leading to a flickering of the view. Renaming is performed by:
DoubleMatrix front = new DoubleMatrix(frontSize, objectives); front.ColumnNames = colNames; if (results.ContainsKey("Pareto Front")) results["Pareto Front"].Value = front; else results.Add(new Result("Pareto Front", front));
Removing the second line of code leads to name changings from "Objective 1", "Objective 2",... to "Column 1", "Column 2". Row names change from "Solution 1" to "Row 1".
Attachments (2)
Change History (7)
Changed 14 years ago by vdorfer
Changed 14 years ago by vdorfer
comment:1 Changed 12 years ago by mkommend
- Owner changed from mkommend to abeham
- Status changed from new to assigned
comment:2 follow-up: ↓ 3 Changed 12 years ago by abeham
- Owner changed from abeham to vdorfer
I don't know how the columns get named to B, C, D. Can you check if this is still the case vdorfer?
comment:3 in reply to: ↑ 2 Changed 11 years ago by gkronber
- Priority changed from low to medium
Replying to abeham:
I don't know how the columns get named to B, C, D. Can you check if this is still the case vdorfer?
Renaming is not possible through the GUI but only through code. See the code in the ticket description.
comment:4 Changed 11 years ago by gkronber
- Owner changed from vdorfer to gkronber
comment:5 Changed 7 years ago by gkronber
- Milestone changed from HeuristicLab 3.3.x Backlog to HeuristicLab 4.x Backlog
- Priority changed from medium to low
The reason for this behavior is that the Pareto-front is updated in each generation.
We should not allow users to change 'results'. I.e. results should be read-only even if the algorithm is pause.
Instead users should change the names of objectives in the problem parameters and these objective names should also be shown in the result.
I don't think that the issue is still present in the current version of HL 3.3.8. Could you please check the behavior and eventually close the ticket.