Present: Lee, Tom, Jake, Daniel, Bill (hangout)

Projects

These projects are small-ish things that could be taken on by someone (though some are already claimed).

iOS Project

Broaden the call!

Keep Cool

• Climate change negotiation game
• We have basic infrastructure, it would be interesting to try to evolve something to play it.

Lab Website

Moving to WordPress by Daniel

Push Introduction

• We don’t have a good, updated description of Push.
• The most recent publications that describe Push well are outdated, from 2005, 2001, etc.
• Daniel may take this on after updating the website.

Push Visualization

This was started by Ian Herold in Clojure, but needs to be finished. It would be nice to have it done before GECCO in early July.

Brevis

Still working on fixing some reflection problems.

ALPS Paper Discussion

• It seems that ALPS is a parent selection technique that tries to maintain diversity and search different parts of the search space.
• It also injects new individuals into the gene pool, and tries to give them a chance, which may be good or bad.
• We all agree that there are some questionable parameters and specifics of the implementation, but that the general idea might be worthwhile.
• There is definitely a comparison to island models with migration.
• Implementation in Clojush:
  • Tom may work on this.
  • It may be difficult to do this within the current Clojush population structure, but might not be too bad.
  • Things that may need to be changed include: breed, parent selection, lexicase, trivial geography
  • There should be checks in the system for things that may break if done together, such as ALPS + trivial geography.
  • It may be worthwhile to do this “quick and dirty” to try it out, and then if we like it, do it “right” to incorporate into the main code base.
• Bill may also like to implement ALPS or another similar island model in his work.

Lexicase Paper

• We need to review the multiobjective optimization literature.
  • Should include looking into NSGA-II and SPEA-2 (i.e. pareto front things).
  • There might be something called “lexicographic ordering”, where the user decides which objectives are most important.
  • Wikipedia page might have some good info.
• Heatmaps: we might want to include these in the paper, unsure for now.

Special Lexicase

• Once per generation, figure out relative “specialness” of each test case
• This “specialness” is very similar to the “similarity” that Tom used previously in Historically-Assessed Similarity
• Then, you bias the lexicase ordering for “special” test cases nearer the beginning.