HartmutHolzwart wrote:Btw., couldn't we feed the overall four left alone constructor arms after the construction of the next generation with another glider recipe to delete the four constructors of the previous generation? David Bell suggested something like this.
I guess this might work, but then again it might be too slow to be an improvement. If you're using a standard kickback reaction, you have to make sure the returning SW-travelling glider doesn't hit any recipe gliders in the channels (for the southeast replicator unit), and it has to avoid colliding with the construction-arm elbow as well. The repeat rate will be much slower than the usual 576 ticks, because you can't fire kickback glider #2 on the same or a nearby path until kickback glider #1 has passed the westward arm. I think that's something like 15,000 ticks between SW gliders. And then you need several of those hitting some junk to produce each SE glider that will actually do the deletions. You might end up averaging 50,000 or 100,000 ticks or more between these SE deletion gliders.
The current Gemini spaceship takes a little under 17 million ticks to complete a replicator construction/destruction cycle. The destructor arm is running for over half that time -- almost 10 million ticks. (I may not have these numbers quite right, but I think they're in the ballpark.) Now, getting rid of the destructor arm would mean there are fewer still lifes to shoot down, but it still seems as if you'll need more deletion gliders than you can produce in a reasonable amount of time -- especially because, if you're using just the east and west construction guns, you can't run the destruction in parallel with the construction as well as in the current design, so the period is likely to get much longer. Please feel free to come up with better estimates if the above numbers don't look right --
HartmutHolzwart wrote:But I agree just having a different slope and seeing the whole thing run would be a great thing. Optimising the design might be a second stage, if possible.
This evening I finished running a (x,2x) knightship through its paces -- it turns out to be a (4096,8192)/c35567490 spaceship
(macrocell file). I only had to make a one-line change in program.yaml, recompile the gliders for the twelve channels using asm.py, and feed them into two standard copies of the replicator unit. Just changing the relative output location for the new copy doesn't alter any of the math for the glider stream crossings, or any of the other "magic numbers" in lifelib.py.
Keep the cheer,