I'm relatively happy with my sweeps - not because the data's that great, but because my sweeping tool is getting to the point that I can use it for anything. And with a little tweaking and a PVM refresher, it will be ready to be thrown on the Turtles (Alphas) once I figure out how to get them running.
I need to write, and I've started, but it all seems like "here are shapes - they are interesting, maybe look at them and let me know". There's no solid trend I can see across simulations, so it's hard to extract results. I'd like to get into the innards of RUNIT, and try to work on my topology problem, but I guess walk before I run. Besides, a whole lot of prep work needs to be done if Dave, Ben, Shaft and I are going to be working on runit, like getting a CVS repository up and running, and fixing flawed assumptions. Also, I get the distinct feeling that the runit code is horribly monolithic, making it hard to deal with runit/punit compatibilities. It may be that it's necessary because there are assumptions you can make to make runit faster which you can't make for punit and vice-versa, but I think while the heart of runit seems to be ok (just by assumption - I haven't really looked), we may need to make it easier to maintain.
Besides that, in order to get my topology project off the ground, I need to do some serious research/thinking into how to specify connection topologies in relatively arbitrary ways. (For example - imagine the visual cortex - you need to map each retinal ganglial cell to simple/complex cells in a particular way, where the synaptic pattern is of a certain form, and the topology of neighboring complex cells is fairly simple, but needs to be expressed in a way in which it can be expanded automatically to create a large region from a simple specification. It sounds easier now that I've written it down, but I still don't know how to do it.)
All this, and besides it looks like I'll have to finish up this TC paper after Dave leaves... Hmm... things to think about, but right now, bed time.