Skip to content

Finalisation Matters

noneill edited this page Aug 8, 2015 · 7 revisions

###Configuration Freeze No changes to codebase before discussing and agreeing the change

###1.Review of add_function functionality which implements the following add_function is used to create all branches (RPB & ADF’s)

  • True - do not change

ADF branches will always use all the ARG’s (dummy variables) in it's signature (subpset).

  • True - do not change

RPB branches will always use all the ARG’s (actual variables of the problem) in it's signature (subpset).

  • True - do not change

For each branches signature, there will be GROWTH.MAX.ATTEMPTS to grow an ADF containing all dummy variables in the signature (subpset) named contiguously from ARG0 upwards (likewise for RPB)

  • Restore this functionality (was removed with commit: e49ed2e157)

If the maximum attempts to grow an ADF of a specified signature fail, the process of growing and checking that all dummy variables are used will repeat GROWTH.MAX.SIGNATURES times before returning an error message

  • Restore this functionality (was removed with commit: e49ed2e157)

###2.Height Restriction Management

  • Talk Nigel through the way it is implemented currently (is it done in the grow_twig function only or elsewhere as well? If so then why?)
  • Nigel to specify any changes that may be desired

###3.Changes to Crossover Operation Make necessary changes to mate, is_compatible or find_slice in order to ensure a recipient branch as a whole will still use all the ARG’s in it’s pset Ok. Will require changes to all three: mate, is_compat, and find_slice.

Clone this wiki locally