dvgrn wrote:Do you have a name for your new 180-degree-gliders design
Well it's "my idea" (although it's pretty obvious idea, I just executed it in Serizawa and thought of "actually doing" the same in Life, so my idea starts and ends on "lets do it", because we all were thinking it at some point), anyway it's probably more your design than mine (at least the execution).
I thought we are talking about two designs. One is armless UC, the other is VSUC (very small universal constructor). The working prototype we have, is too big for VSUC (although giving the right credit as for now it's the best VSUC we got), and too small for armless UC. Anyway they both belong to UC's based on 180-degree-"opposite glider collision" (OGC?). Not sure about VSUC and OGC but armless UC sound good to me. The first creature that actually "happy" to be without arms
---
Anyway "back to business" I was thinking of replication design, that will "fit" into the armless creature fully. More precisely it itself will fit inside itself. Because the armless UC is thin and wide, If we orient it 90% it will fit completely inside it's construction line. So the "full" replication will actually consist of two steps, one 90% turn and flip (or something along those lines), then 90 degree turn and flip again back to the original orientation, that will make kinda "steps" procedure. Now the tricky part is the "wiring", which need to be able to feed the construction from above, below, and from one side and the other side. But this "extra wiring weight" probably worth the full salvo construction.
dvgrn wrote:but not the kind of script that anyone else would have an easy time learning how to use!
I also use kinda "hardcore" scripts easily getting to few thousand rows. Like one that I've created Serizawa replicator with (actually ALL the replicator code is inside, you can run it as is, and will compile the whole replicator out of the box. And although it's not my "best script ever" it's actually not so bad, having a lot of classes and reusable code inside it - I actually intend to reuse it soon for the next Serizawa replicator). Somehow it seems people having hard time (me as well) use someone else's code, pretty much preferring or "run it out of the box" or write one on their own.
As I'm concerned, I will be glad to write the script fine enough so that I myself will prefer to reuse it rather than rewriting all from scratch. If I reach such level of coding, for me it can be called "good coding".
dvgrn wrote:Those recipes all include the new location of the target block
Looks great! At least one is covered
dvgrn wrote: I should really have a similar stamp collection for all the other Spartan objects -- just haven't gotten around to it yet.
You said you have a db of all those recipes, you just don't have time to compile a query? Or is it all somewhat more "messy"?
dvgrn wrote: that can start from an RLE pattern, or perhaps an ordered list of small objects, and reliably create a slow-salvo recipe that can build the full pattern
Recently I've posted a script that takes current state in golly, and counts the still life. Probably it can be adapted to "recognize" the objects, it shouldn't be too hard. Then we need some "system" that will translate those objects into salvos.
Because of my approach designing mostly by code from the beginning, what I did in Serizawa, is together with placing objects in the script (although in Serizawa there are two main object not dozens), I added them to some data list, and then wrote a small "compiler" that translate the data into glider stream (commands for arm movements and glider shoots, currently just sorted by diagonals as you saw). Anyway I think in Serizawa as well it would be nice to write a "pattern recognition script". I probably do it later today. What is fun in Serizawa, is that each object can be easily recognized as "duplicator" or "reflector" so it would be cool to have Serizawa geometry, translated into "input output" manner, as I usually code it.
dvgrn wrote:..."Blockic compiler" stage...
I was writing a Blockic compiler myself when I wanted to create p60 based replicator, using blockic. It was real mess. By the way it's not such a bad idea, having a replicator based on p60 (Gemini style). It works much faster but of course makes only blocks, but blocks are enough for any blockic setup so it's achievable and p60 is cheap so there is no need in thousands blocks. Probably it would end up somewhere near Gemini performance. My current guess the fastest approach for replicator would be adapting the current Geminoid for two arms. It's already works with 4 gliders inputs, just need to feed it to the other arm, and it will probably be the fastest Geminoid (maybe use tandems as well, and although not sure, but it's possible that more streams will make it more effective despite the sync issues).