Details

Scribe: Emma Present: Lee, Micah, Tom, Zeke, Kwaku, Emma Reading for next week: None

Agenda

Tom wants to discuss GSXover random code generation and how we can fix it. It might be a good idea to re-skim the emails related to this if you wish to be involved in the discussion.

Lee’s updates

• Funding – current grants, upcoming projects, different directions
• New focus back on the calculator problem, modality, modularity, concepts related to our recent work using GSX, etc.
• number pressing to number, boolean output
• run program once to establish tag space
• map of button to tag (hard-coded) -> each button has a particular tag value
• tagging, boolean, float, exec stacks
• how wrong is it -> need a gradient, rather than 0-1 loss
• due to tag spaces, new genetic operators like “concatenation” might be useful. new one called “amalgamation’
• TODO: investigate tradeoffs between redundancy and modularity (Kwaku’s done much recent work on this)
• refactoring

Micah’s update

Kwaku’s update

<super secret things about modularity>

Tom’s update

• kata bowling runs – searching for consistency in what’s causing some runs to do well and what’s causing some to perform poorly
• gsxover – should we continue working on this? if yes, how can we make it work?
• tom’s recent work has raised the probability of getting something successful

– added scope -> lee suggesting a scope macro/interface -> how to get adfs without explicitly having adfs -> connection with mutation? – changed scope (specific function set for random code in GSX)

Zeke’s update

• validation, things related to the Domingos paper Lee forwarded.
• held up by chemdoodle release delay