Free cookie consent management tool by TermsFeed Policy Generator

Opened 10 years ago

Closed 10 years ago

#2138 closed enhancement (done)

The successful offspring analyzer should be made more user friendly

Reported by: mkommend Owned by: mkommend
Priority: medium Milestone: HeuristicLab 3.3.10
Component: Algorithms.OffspringSelectionGeneticAlgorithm Version: 3.3.9
Keywords: Cc:

Description

The usability of the successful offspring analyzer should be improved:

  • By default the manipulators and crossovers should be collected
  • The selected operator parameter should be named automatically

Change History (10)

comment:1 Changed 10 years ago by svonolfe

  • Status changed from new to accepted

comment:2 Changed 10 years ago by svonolfe

improved usability of successful offspring analysis in r10346

comment:3 Changed 10 years ago by svonolfe

  • Owner changed from svonolfe to mkommend
  • Status changed from accepted to reviewing

comment:4 Changed 10 years ago by mkommend

It would be better if the result names were also configurable to display for example crossovers instead of selected crossover operator. A possible solution would be to use ScopeTreeLookupParameters, which would also improve the code quality.

Last edited 10 years ago by mkommend (previous) (diff)

comment:5 Changed 10 years ago by svonolfe

adapted remaining VRP operators to successful offspring analysis in r10348

comment:6 Changed 10 years ago by svonolfe

I aggree that the manual scope tree traversal should be removed from the SuccessfulOffspringAnalyzer and replaced with ScopeTreeLookupParameters. This would improve the overall design and also fix the problem of naming the analysis results correctly.

However, first the ScopeTreeLookupParameter must be changed to return null values instead of throwing an exception if a certain variable is not available in a scope. For instance, not all individuals have been manipulated and thus this variable ("SelectedManipulationOperator") is not available in some scopes.

comment:7 Changed 10 years ago by mkommend

  • Owner changed from mkommend to svonolfe
  • Status changed from reviewing to assigned

The ScopeTreeLookupParameter does not throw an exception if the variable is not found and can therefore be used in the SuccessfulOffspringAnalyzer without any modifications.

comment:8 Changed 10 years ago by gkronber

  • Owner changed from svonolfe to mkommend
  • Status changed from assigned to reviewing

comment:9 Changed 10 years ago by mkommend

  • Status changed from reviewing to readytorelease

r10917: Merged r10346, r10348 into stable.

comment:10 Changed 10 years ago by mkommend

  • Resolution set to done
  • Status changed from readytorelease to closed
Note: See TracTickets for help on using tickets.