ConwayLife.com

Psuedo p30 LWSS gun using 4 queen bees*: x = 49, y = 43, rule = B3/S23 29b2o$29b2o6$28b3o$27b2ob2o$27b2ob2o$27b5o$26b2o3b2o3$13bo2bo$12bo14b 4o$12bo3bo10bo3bo$12b4o11bo$2b2o24bo$bobo28bo$bo23b2ob3o7b2o$2o16b2o4b 6o7bobo$16bo3bo5b2ob2o5bo6b2o$15bo5bo14bo2bo2bo2bob2o$10b2o2b2obo3bo 14bo6b2o2b2o$10b2o3...

If the "non-Gosper gun" shows up instead of a proper GGG, I will still cheerfully admit defeat, of course. That's a 3QB, so I feel pretty safe. Well, Tropylium's second p30 gun in that thread does have an advantage over the regular GGG in that it can be built up one component at a time, allowing a ...

That reaction is missing one of the key components a fuse needs to have to be used in a ship: It needs to recreate the input to the fuse as (part of) its output so that it can be burned again in the same direction. This (13,4)c/41 fuse may burn gliders and output gliders, but the output gliders are ...

Here's a new conduit, HL82R (not to be confused with the almost identically named HL83R), along with an example Lx169 built from it: x = 75, y = 62, rule = LifeHistory 65.B2A$63.2BA2BAB$63.3B2A3B$61.12B$60.14B$61.13B$61.14B$60.15B$60.14B $60.13B$60.B3D4B.3B$60.2BD4B$60.2B3D2B$60.6B$59.7B$58.8B$57.8B...

I think the concept is good - and being able to have fully p1 logic is quite nice. However, the fact that signals take up space and cannot be cleanly (let alone selectively) deleted in-line seems like a considerable disadvantage to me - it's like the circuit has memory leaks everywhere that can't be...

I know it's been a while, but I've been taking a bit of a look into some methods of building the front end recently. But before I get to that, I'd like to clarify that the design I proposed previously, with a "glider sponge" off to the side the side and other strange elements other than just standar...

Final steps for xs17_08p78b5z321 using a hat->loop converter (probably unoptimal, unsure of the glider cost but I think it's less than 17): x = 52, y = 17, rule = B3/S23 11bo$11bobo$11b2o$2b2ob2o8bo26b2ob2o$3bobo8bo28bobo$3bobo8b3o26bo2bo$b 2obo36b2ob2o$2bo39bo$obo37bobo7b2o$2o38b2o8b2o$11bo$10b2o$1...

Here's a few other ways of cleaning up a climber's stabilized debris with a single incoming ship: x = 68, y = 295, rule = B3/S23 9b2o$9b2o26$15b2o$15b2o7$13bo$12bobo18bo$12bobo16bo3bo$13bo16bo$30bo4b o$30b5o8$14b2o$14b2o8$obobobobobobobobobobobobobobobobobobobobobobobob obobo11$23b2o$23b2o12$31b2o$3...

A for awesome wrote:Sorry to spoil the fun, but I found it about a year and a half ago.

No worries; the reaction is pretty straightforward and the eater was already known, so I initially figured somebody had found it previously.

Reburnable fuse which does not work in standard Life, velocity (8,3)c/66, p132: x = 270, y = 95, rule = B3/S238 268bo$267b2o$241b2o23bo2bo$240bo2bo23b2o$241b2o4$225b2o$224bo2bo$225b 2o4$209b2o$208bo2bo$209b2o4$193b2o$192bo2bo$193b2o4$177b2o$176bo2bo$ 177b2o4$161b2o$160bo2bo$161b2o4$145b2o$144bo2bo$1...

p14 oscillator formed by a known eater chomping on a recovering copy of itself, back and forth: x = 18, y = 13, rule = B3/S23 7b2o3b2o$6bobo3bobo$2b2o2bo7bo$2bobob2o5b2ob2o$4bo3bo5bobo$4bob2o3b3o 2bo$2b2o2b2o2bo3b2o$bo2b2o4b2obo$bobo9bo$2obo6b2obobo$3bo7bo2b2o$3bobo 3bobo$4b2o3b2o! Discussion in the...

Since this ship will travel slower than c/4 orthogonally, it actually might not be necessary to make a self-sustaining helix - it should be possible to throw forward gliders at a forwards stream of spaceships, sending back forward gliders and sideways xWSSs to build the start of the tracks. However,...

Here's a sketch for a potential (34,7)c/156 spaceship design plan: (34,7)c156 Spaceship Sketch.png The goal here is to exploit the fact that the climber is both a bit messy, and also able to burn gliders in addition to blocks. (It turns out it can also burn boats too, so there's 3 potential input fu...

90 degree block signal reflector, repeat time 17: x = 55, y = 60, rule = B2-ac3aei4ae6i8/S23-ejq8 40bo$38bo2bo$37bo2bobo2$36bobo2bo$37bo2bo$38bo2$33b2o$33b2o4$28b2o$28b 2o$27bo$25b2o$25b2o3$21b2o17b2o$21b2o17b2o2$38b4o$17b2o19bo3b2o2b2o$ 17b2o20bo4b2obo$38b2o$31b2o$4b2o7b2o16bo$4bo8b2o17bo9b2o$5bo26...

I haven't seen this transparent block before: x = 27, y = 39, rule = LifeHistory 5$17.A$6.2A7.3A$7.A6.A$7.A.AB3.2A$8.2AB.4B$10.4B$11.5B$9.8B$8.12B$7. 13B$6.15B$5.8B3A5B$4.8BA3BAB2DB$3.8BA5BA2DB$2.2B2A5BA5BA4B$2.2B2A5BA 5BA5B$3.9BA3BAB2.4B$6.7B3A5.3B$7.11B4.2B$7.7B2.2A5.B$7.7B2.A$8.5B4.3A $8.5B2A4.A$...

One issue with rule universality is that of defining when a rule has 'more' of some type of object than another when both have infinitely many objects of that type. Importantly, they can't be distinguished by cardinality anymore as the list of all possible [insert object here] has a cardinality of ℵ...

Really that's about as good a bait as we can reasonably hope for. Hmm... Yeah, I suppose so. I mean, I found this, but the bottom eater is unfortunately in such a position as to prevent a 5 glider total restoration: x = 32, y = 26, rule = B3/S23 30b2o$13b2o15bo$12bobo13bobo$13bo14b2o3$11b2ob2o$11b2...

Oscillator universality actually seems (to me, at least) like something that belongs in one of the main CA categories and not the Sandbox, since it's related to CA and has some theoretical interest.

Well, here's a potential starting bait that should serve as an improvement over the previously shared ones, seeing that it only needs a bi-block and a ship to be reconstructed: x = 21, y = 25, rule = B3/S23 13b2o$12bobo$13bo3$11b2ob2o$11b2ob2o2b2o$2b4o12bobo$19b2o$2bo2bo$bob2o bo$bo4bo2$bo4bo$b2o2b2...

I have another one---part of a 1155*1155 agar generated from (13,13,1) Also, just curious, what exactly do you mean by "generated from"? I think what GUYTU6J means is that the agar was found by using a repeat script in which the pattern is repeated with a spatial displacement of (13,13) and a tempo...

I'm curious about the way gInd and gRows are handled are utilized in particular, as some of the ideas I've got pertain to modifying them specifically. I had made a file with zfind-s source since I figured the lack of unnecessary code would help make it quicker and easier to implement changes to the ...

Okay, good to know. I'm unfortunately still not sure how I'm going to implement the honestly fairly simple idea I had, since it will require rewriting the structure of the lookup table itself and the way the code is written makes it difficult for me to understand how it works well enough to recreate...

Just a quick question - I had a few modifications I wanted to try implementing, but the comment on the MAX_WIDTH line makes me wonder - Aside from the assumption that there is enough memory (when there will almost definitely not be) to construct the required, are there any assumptions in the code ab...

I think the most intuitive approach with any promise would be to genetically evolve the search program itself. The search program has *less* chaotic behavior in regards to mutations than the patterns we want to find themselves, and it has a structure that better resembles 'genes' as well.

I have to say, that does sound like an interesting project. The description is ambiguous enough that I can't tell whether the problems that the AI is supposed to be able to address are simple engineering tasks, ground-breaking ones, or ones which push the limits of home computer hardware. Of course,...