Tom Helmuth

Oh, and I'm not a big fan of sets of individuals/genomes -- I'd prefer each operator know how many parents it requires. YMMV

Yes? But how is that related to this conversation?

Oh, do you mean because we're talking about genetic operators? Selection isn't a genetic operator IMO.

> Where is the responsibility for recording ancestors going to be, if the genetic operators don't write it down in the offspring? In the breed caller? Yes, that is what...

Ok, that's fine with me! If we have individuals as inputs, I think it makes more sense to have individuals as outputs, even if it means duplicated code. I think...

I don't know what would be considered "standard" for Clojure here. Personally, I would just put it in a regular-ol' comment at the top of `genetic_operators.clj`.

There's a lot of stuff here. Some of it sounds amazing (like live monitoring of stats of runs, which we've discussed for years and never convinced someone to do). Some...

The scripts (which are actually in Python) are specific for scraping data from mass-runs (often performed on the cluster). I often have offered to share them with people, but thus...

I don't have time to organize them or make them pretty, but I just pushed all of my Python scripts to a new GitHub repo for your perusal: https://github.com/thelmuth/Clojush-Tools

This is a Clojure namespace thing, not a Clojush thing. Clojure files are supposed to use underscores, where the namespaces are supposed to be equivalent except replacing underscores with hyphens....