Free cookie consent management tool by TermsFeed Policy Generator

Opened 15 years ago

Closed 15 years ago

Last modified 14 years ago

#898 closed defect (done)

Linkage between algorithms and problems does not work correctly

Reported by: swagner Owned by: swagner
Priority: high Milestone: HeuristicLab 3.3.0
Component: Optimization Version: 3.3
Keywords: Cc:

Description

When linking a problem with an algorithm, the values of various parameters have to be set on both sides. At the moment not all dependencies are handled correctly. Furthermore, events on parameter value changes are not restored after deserialization.

Change History (16)

comment:1 Changed 15 years ago by swagner

  • Status changed from new to assigned

comment:2 Changed 15 years ago by swagner

Corrected parameter settings in TSP and started to work on SGA in r2975.

comment:3 Changed 15 years ago by swagner

Corrected parameter settings in SGA in r2986.

comment:4 Changed 15 years ago by swagner

Restructured HeuristicLab.Problems.TSP project and adapted TSP evaluators class hierarchy in r2988.

comment:5 Changed 15 years ago by swagner

  • Resolution set to fixed
  • Status changed from assigned to closed

comment:6 Changed 15 years ago by swagner

  • Resolution fixed deleted
  • Status changed from closed to reopened

Selecting a previously selected operator in UpdateSelectors, UpdateCrossovers and UpdateMutators does not work correctly in SGA.

comment:7 Changed 15 years ago by swagner

  • Status changed from reopened to new

comment:8 Changed 15 years ago by swagner

  • Status changed from new to assigned

comment:9 Changed 15 years ago by swagner

  • Resolution set to fixed
  • Status changed from assigned to closed

Fixed bug when selecting a previously selected operator in SGA in r3076.

comment:10 Changed 15 years ago by abeham

I still have an open issue in tabu search which is also what we've discussed today, but the solution doesn't solve it fully.

In a move generator it is possible to change the actual name of the move parameter which gets automatically changed in all operators. This linkage is done on the problem side as I only have access to the move parameter there. So far so good. However, when the move generator itself is changed the problem side doesn't know about it and can't set the move parameter of the other move operators to that of the changed move generator. The algorithm side can't do it either, because it doesn't know anything specific about the move generator.

I'd like to discuss possible solutions, but it's probably not the most urgent thing.

comment:11 Changed 15 years ago by abeham

  • Resolution fixed deleted
  • Status changed from closed to reopened

comment:12 Changed 15 years ago by abeham

fixed linkage in TS and LS in r3079

comment:13 Changed 15 years ago by abeham

fixed the issue above by setting the name also in all other move generators in r3099

comment:14 Changed 15 years ago by abeham

  • Resolution set to fixed
  • Status changed from reopened to closed

comment:15 Changed 14 years ago by swagner

  • Milestone changed from Iteration 4 to Current

Milestone Iteration 4 deleted

comment:11 Changed 14 years ago by swagner

  • Milestone changed from Current to HeuristicLab 3.3.0

Milestone Current deleted

Note: See TracTickets for help on using tickets.