Free cookie consent management tool by TermsFeed Policy Generator

Opened 14 years ago

Last modified 12 years ago

#1185 closed defect

Moves are applied to different individuals than they were generated for — at Version 1

Reported by: svonolfe Owned by: abeham
Priority: low Milestone: HeuristicLab 3.3.4
Component: Algorithms.SimulatedAnnealing Version: 3.3.4
Keywords: Cc:

Description (last modified by svonolfe)

In the SimulatedAnnealingMainLoop there is an InnerIterations Parameter.

First of all, this number (InnerIterations) of moves are generated. Then, with a certain probability, these moves are applied.

Example scenario: InnerIterations = 5

  • Move 1 is not applied
  • Move 2 is applied (on the original individual)
  • Move 3 is not applied
  • Move 4 is not applied
  • Move 5 is applied (on the individual modified by move 2)

Move 5 was generated for the original individual, however it is applied to the modified one. This is a problem for instance for VRP moves where tours and cities are referenced. This means that the changed individual probably does not contain the tour anymore and thus the move is not valid.

The current solution is, that the VRP-moves contain a clone of the original individual and apply the move on it. However, in that case the usual semantic of the InnerIterations parameter is not followed.

Change History (1)

comment:1 Changed 14 years ago by svonolfe

  • Description modified (diff)
  • Summary changed from Moves werden auf einem anderen Individuum angewandt als das, für welches sie generiert wurden to Moves are applied to different individuals than they were generated for
Note: See TracTickets for help on using tickets.