Attendance: Lee, Tom, Bill, Kwaku (yay!), Wren, Eddie, Noah, Tim, Karthik, Nic, Mike (scribe)
- FLY was down due to power outages
- Pucks – Shooters have been added, discussion of possibly using pixel data for proximity detection
- Introductions for new people, individual project discussions.
- Wren has data from her images of pollen tubes!
- Tim implemented a decision tree in the Bladder Cancer dataset.
- Bill has been using the UMASS computing cluster, can we use it?
- Kwaku – Evolution and ecology in software engineering. Learning how diversity occurs. Embedded systems. May collaborate with Karthik?
- Homology – How much of the population exhibits similarity structurally.
- Background
- Only takes structure and sequence into account, not function.
- Comes out of ULTRA in hopes of finding structurally similar individuals
- Plush replaced ULTRA
- Only doing crossover on the same parts of a program
- Want to measure how homology occurs/changes over time.
- Tom has been testing out using edit distance to measure homology (Levenshtein) only using instructions.
- Can we measure homology properly without executing the programs?
- We want to measure fitness and homology, some changes benefits may not benefit until further generations
- Should epigenetic markers influence homology? Probably.
- Could look at the push programs rather than the plush genome.
- Genomes are more important to look at.
- Tom want to start without epigenetic markers for simplicity’s sake.
- Can we use tags to assist us?
- Padding is used to normalize.
- Uncle Bob – SOSIES Paper code transformations, discuss next time.
- Databases – To implement in Push, we need to figure out the root parent issue or an alternative representation to make Ancestry linear so we can find clades.
- Find a way to eliminate duplicates?
- Using ancestry change crossover parameters.
- Background