Random posts 2

[yujh]

wadufi

[roolif]

... how to synthesize an eater.

Straight from golly\Patterns\Life\Syntheses\two-glider-collisions.rle :

Code: Select all

x = 5, y = 31, rule = LifeHistory
3.E$2.E2B$2.3E26$BE$2EB$EBE!

[JP21]

wadufi

Congratulations, I already memorized the link. And I see that it is a mobile link. (I hovered to see what the link is)

[Alexander Yu]

... how to synthesize an eater.

Straight from golly\Patterns\Life\Syntheses\two-glider-collisions.rle :

Code: Select all

x = 5, y = 31, rule = LifeHistory
3.E$2.E2B$2.3E26$BE$2EB$EBE!

I know, that part was just a joke.

[roolif]

Excuse me u all

[dvgrn]

UniPink-256px-1.gif

@Alexander Yu, the usual thing is to keep posts with joke content in the Sandbox, so I've moved this exchange there. Here. There's kind of an exception on a certain day that's coming up in a week or so, but we won't mention that by name or anything.

@roolif, everybody who is subscribed to a given topic will get an email notification every time there's a new post. As a result, people tend to be a little grumpy and stick post reports on posts that are just a reaction with no new information. There's a forum rule (rule 4) specifically aimed at this, to discourage low-signal high-noise one-liners (or zero-liners as in this case).

There's a Like button nowadays to let someone know that their post was read. I hate to be all old-fashioned and anti-animated-GIFfy, but it'd really be better to make do with the Like button in cases like the above.

[JP21]

UniPink-256px-1.gif

It's time that I use the "Click to Remove Element" google chrome extension on this.

[JP21]

I know I'm triple posting, but I have a whole bunch more partials.

p8

Code: Select all

x = 9, y = 7, rule = B3/S23
b2o3b2o$bobobobo$3bobo$b2o3b2o$bo5bo$o7bo$o7bo!

p18

Code: Select all

x = 28, y = 18, rule = B3/S23
24bo$23bobo$7b2o3bo10bobo$7bobobobo8b2o2b2o$9bobobo2b2o3bo2bobo$2bo5bo
2bobobobo2b5o2bo$2bo5bo2bobobo4bo4bobo$4bo6b3ob2o2b2o2b2obo$2b2o7b2o2b
o3b2o3bo$ob2o7b2o2bo3b2o3bo$bo9b3ob2o2b2o2b2obo$8bo2bobobo4bo4bobo$2o
6bo2bobobobo2b5o2bo$9bobobo2b2o3bo2bobo$7bobobobo8b2o2b2o$7b2o3bo10bob
o$23bobo$24bo!

p20

Code: Select all

x = 11, y = 11, rule = B3/S23
8b2o2$9bo$8bobo$7bo2bo$7bo2$4b2o$o2bo$obo$3b2o!

p21

Code: Select all

x = 54, y = 61, rule = B3/S23
bo2bo2bo38bo2bo2bo$b7o2bo32bo2b7o$8b3o32b3o$3b4o40b4o$2bobob3o36b3obob
o$2bobo4bo34bo4bobo$b2o2b4obo32bob4o2b2o$2bobo3bobo32bobo3bobo$2bo3b2o
2b2o30b2o2b2o3bo$b2o2bobobo34bobobo2b2o$3b2o2bobo34bobo2b2o$3bobobob2o
2b2o24b2o2b2obobobo$2obo2bobo4bobo22bobo4bobo2bob2o$o2b4obo5bo24bo5bob
4o2bo$2bo3bob2o34b2obo3bo$3b4o2bo12b2o6b2o12bo2b4o$7b3o4b2o4bo4bo2bo4b
o4b2o4b3o$3b4o2bo3bo2bo3bo4bo2bo4bo3bo2bo3bo2b4o$3bo2bob2o4b2o4bo4bo2b
o4bo4b2o4b2obo2bo$8bo13b2o6b2o13bo$6bobo36bobo$6b2o38b2o2$24b3o$23bo3b
o$23bo3bo$21bobo3bobo$24b3o6$24b3o$21bobo3bobo$23bo3bo$23bo3bo$24b3o2$
6b2o38b2o$6bobo36bobo$8bo13b2o6b2o13bo$3bo2bob2o4b2o4bo4bo2bo4bo4b2o4b
2obo2bo$3b4o2bo3bo2bo3bo4bo2bo4bo3bo2bo3bo2b4o$7b3o4b2o4bo4bo2bo4bo4b
2o4b3o$3b4o2bo12b2o6b2o12bo2b4o$2bo3bob2o34b2obo3bo$o2b4obo5bo24bo5bob
4o2bo$2obo2bobo4bobo22bobo4bobo2bob2o$3bobobob2o2b2o24b2o2b2obobobo$3b
2o2bobo34bobo2b2o$b2o2bobobo34bobobo2b2o$2bo3b2o2b2o30b2o2b2o3bo$2bobo
3bobo32bobo3bobo$b2o2b4obo32bob4o2b2o$2bobo4bo34bo4bobo$2bobob3o36b3ob
obo$3b4o40b4o$8b3o32b3o$b7o2bo32bo2b7o$bo2bo2bo38bo2bo2bo!

A p22 that works in LifeHistory with just two gray cells

Code: Select all

x = 54, y = 34, rule = LifeHistory
6.2A18.2A$5.A2.2A15.A2.A$5.A3.A7.A7.A2.A$5.A4.A4.2A.2A3.A.A2.A.A13.3A
$6.A.3A.A10.2A4.2A3.A8.A3.A$6.A.A3.A5.2A13.A.2A6.A4.A$7.2A5.A3.A.A11.
A4.A6.2A.A$2.2A10.A.3A.A12.A3.A8.A3.2A$.A.A3.2A.2A4.A4.A4.F7.3A13.A.A
$.A7.A7.A3.A30.A$2A15.2A2.A30.2A$19.2A$24.3A$25.A2.A$26.3A$27.A3$27.A
$26.3A$25.A2.A$24.3A$19.2A$2A15.2A2.A30.2A$.A7.A7.A3.A30.A$.A.A3.2A.
2A4.A4.A4.F7.3A13.A.A$2.2A10.A.3A.A12.A3.A8.A3.2A$7.2A5.A3.A.A11.A4.A
6.2A.A$6.A.A3.A5.2A13.A.2A6.A4.A$6.A.3A.A10.2A4.2A3.A8.A3.A$5.A4.A4.
2A.2A3.A.A2.A.A13.3A$5.A3.A7.A7.A2.A$5.A2.2A15.A2.A$6.2A18.2A!

p34

Code: Select all

x = 22, y = 10, rule = B3/S23
bo18bo$bo18bo$3o2bo10bo2b3o$b2o2bo10bo2b2o$b2obobo8bobob2o$b2o2bo10bo
2b2o$b2o2bo10bo2b2o$3o16b3o$bo18bo$bo18bo!

p38

Code: Select all

x = 11, y = 11, rule = B3/S23
10bo2$7b3o$7b3o$9b2o$8b2o$7b3o$2b2o2bobo$2b2ob3o$2b5o$o3bo!

p40; the issue is that the sparkers are too close to each other

Code: Select all

x = 30, y = 12, rule = B3/S23
b2o24b2o$b2o24b2o2$bo8bo8bo8bo$obo7bo8bo7bobo$o2bo4bo2bo6bo2bo4bo2bo$b
o2bo2b3o10b3o2bo2bo$6bo4bo6bo4bo$bo2bo2b6o4b6o2bo2bo$b2o5bo3bo4bo3bo5b
2o$10bobo4bobo$10b2o6b2o!

p42

Code: Select all

x = 9, y = 9, rule = B3/S23
5b2o2$6bo$5bobo$5bo2bo$o2b2ob3o$obo2bob2o$3bob2o$4b3o!

This is a (23,6) pre-pulsar push, shown here as a potential p46, but it can be combined with other 6-generation pushes if any compatible ones exist.

Code: Select all

x = 21, y = 27, rule = B3/S23
7b2o3b2o$7b2o3b2o10$bo17bo$bo17bo$3o4bo5bo4b3o$b2o3b3o3b3o3b2o$3o2bobo
bobobobo2b3o$bo2b3ob2ob2ob3o2bo$bo3bobobobobobo3bo$6b3o3b3o$7bo5bo6$7b
2o3b2o$7b2o3b2o!

p52

Code: Select all

x = 23, y = 33, rule = B3/S23
8b2o$9bo$4b2o3bob2o4b2o$3bobo4bobo4bobo$3bo15bo$2ob2o2b2o5b2o2b2ob2o$
2obo15bob2o$3bob4o5b4obo$3bobo3b5o3bobo$4bo13bo6$4bo13bo$3bo15bo$3b2o
2bo7bo2b2o$bo2bobo9bobo2bo$bo5bo7bo5bo3$11bo$4bo3bo5bo3bo$3bobo11bobo$
3bobo11bobo$2obobob9obobob2o$2obo15bob2o$3bo15bo$3bobo4bobo4bobo$4b2o
4b2obo3b2o$13bo$13b2o!

p58 gun with a single pair of cells that can't turn on; works with a domino, but the p29 pentadecathlon is way too wide

Code: Select all

x = 61, y = 61, rule = StateInvestigator
49.2A$49.A.A$51.A$47.4A.2A$47.A2.A3.A$50.A.A.A$51.3A.2A$43.2A9.A2.A$
36.2A5.2A9.2A.A$37.A16.A3.2A$37.A.A15.3A2.A$38.2A17.A.2A$57.A$49.A6.
2A$48.3A$43.A$26.E15.3A$34.A2.A$31.A.A$30.A.A5.A11.A$30.A3.A.3A10.A.A
$31.4A8.2A5.A$26.A5.2A9.2A$26.A$26.A2$16.E5.3A4$19.2A$18.A2.A$19.A.2A
$18.A2.2A$17.A2.2A2$8.A11.A$8.3A6.A2.A$11.A7.2A$10.2A3$16.A$7.2A6.2A
4.2A$7.2A7.A4.2A3$3.2A$3.A10.A$2A.A9.2A5.A$A2.3A8.A4.A.A$.2A3.A13.A$
3.A.2A$3.A2.A$4.2A.3A$6.A.A.A$6.A3.A2.A$7.2A.4A$9.A$9.A.A$10.2A!

p72, really seems doable, but can't get a good predecessor

Code: Select all

x = 13, y = 9, rule = B3/S23
2b3o3b3o$2o3bobo3b2o$3o2bobo2b3o$2bo7bo$4b2ob2o$2bo7bo$b2ob2ob2ob2o$bo
3bobo3bo$2b3o3b3o!

p74

Code: Select all

x = 25, y = 32, rule = B3/S23
2bo19bo$2b3o15b3o$5bo13bo$4b2o13b2o11$10bo3bo$6bobobo3bobobo$4b2o2bobo
3bobo2b2o$bo4b3o7b3o4bo$bo21bo$3o6bo5bo6b3o$b2o6b3ob3o6b2o$b2o2b3o2b2o
b2o2b3o2b2o$3o2b2o3b2ob2o3b2o2b3o$bo3bo13bo3bo$bo3b2obo7bob2o3bo$6b3o
7b3o$7bo9bo2$4b2o13b2o$5bo13bo$2b3o15b3o$2bo19bo!

p84, also seems doable; many spark locations work because the area just needs to die

Code: Select all

x = 17, y = 17, rule = B3/S23
13bo2$10bobob2o$16bo2$10b2obob2o$13bo$14b2o$14b2o2$2bo2bo6b3o$5bo$2bo
7bo$o4b2o3bo$2bo4b2obo$2bo2bob2o$3bobo!

p122, why does 61 have to be prime

Code: Select all

x = 38, y = 38, rule = B3/S23
17bo$17b3o$20bo$19b2o3$30bo$28b4o2bo$28b2o2bo$22b2o3bo4bo$21bobo4b4o$
22bo5b2o$23b2o$24bo$23bo$24bo$24bo$2o32b2o$bo26b3o3bobo$bobo20bo3bo7bo
$2b2o20b6o6b2o$10bo13b3o$9bobo13bobo$9b2obobo9b3o$12b2ob2o2b3obob2o$
20b5o$20b2ob2o$9bo10bobo$7b2ob2o6b3o$7b2ob2o6bobo$6b2o2bo7bo$7bo2bo$8b
2o2$7bo9b2o$17bo$18b3o$20bo!

p168

Code: Select all

x = 32, y = 17, rule = B3/S23
11bo8bo$8bobobo6bobobo$9bo3bo4bo3bo$10bo2bo4bo2bo$10bo2bo4bo2bo$2o9b2o
6b2o9b2o$2o28b2o$11b2o6b2o$10bo2bo4bo2bo$10bo2bo4bo2bo$9bo3bo4bo3bo$
10bobo6bobo$11bo8bo3$2o28b2o$2o28b2o!

this would have worked if it wasn't prime (97×2=194)

Code: Select all

x = 36, y = 21, rule = B3/S23
2bobo26bobo$7o22b7o$2b3o26b3o2$5bo24bo$5b2o22b2o$4bobo22bobo$3b2o26b2o
$3bob2obo18bob2obo$5bobobo5b2o2b2o5bobobo$5bo4bo3b3o2b3o3bo4bo$6bo2bo
5b2o2b2o5bo2bo$7b2o18b2o4$7b2o3b2o8b2o3b2o$7b2o2bo2bo6bo2bo2b2o2$5b2o
3bo2bo8bo2bo3b2o$5b2o4bo12bo4b2o!

194 is not prime. I think you mean it's semiprime?

Such a long quote. Should've just quoted the last part instead of quoting the whole thing, like this:

this would have worked if it wasn't prime (97×2=194)

Code: Select all

rle

194 is not prime. I think you mean it's semiprime?

Look how much shorter it is, compared to the previous one. Not only that, but it was clear that the prime being referred to is 97; otherwise, hotdogPi wouldn't have put the "(97x2=194)" part.

That particular number example could also be called a coprime.

[yujh]

Well, I already pinned them on discord[s](still policing the forums)[/s]

[JP21]

Well, I already pinned them on discord[s](still policing the forums)[/s]

But that would mean hotcrystal0 would not learn the mistakes(?)
Oh wait, am I even the one being referred to?
You should be using quotes, to avoid confusion, everytime.

Quick edit: And signatures are not required to be shown on every posts.

[yujh]

On the same thing lol

[JP21]

On the same thing lol

I accidentally clicked on wrong button, instead of quote.
You should really use the quoting feature.

[yujh]

It pins, which is sometimes really annoying.

[pzq_alex]

As of now, General Discussion has exactly 700 topics.

Edit

Note: this is obviously not my rulegolfing style, the original is made by dani.

What is a “rulegolfing style”?

[yujh]

As of now, General Discussion has exactly 700 topics.

Edit

Note: this is obviously not my rulegolfing style, the original is made by dani.

What is a “rulegolfing style”?

It’s how you rulegolf, or just usually which rulespaces do you go to, but sometimes object density or other things also matter.

[pzq_alex]

As of now, General Discussion has exactly 700 topics.

Edit

Note: this is obviously not my rulegolfing style, the original is made by dani.

What is a “rulegolfing style”?

It’s how you rulegolf, or just usually which rulespaces do you go to, but sometimes object density or other things also matter.

Does it involve the set of (INT) transitions you usually toggle?

Edit: I asked this because I sometimes look at a rule and wonder how people find such nice rules, and find out that the rule has some unusual transitions. But whenever I tried those transitions out, they never quite played well together for me.

[yujh]

As of now, General Discussion has exactly 700 topics.

Edit


What is a “rulegolfing style”?

It’s how you rulegolf, or just usually which rulespaces do you go to, but sometimes object density or other things also matter.

Does it involve the set of (INT) transitions you usually toggle?

Edit: I asked this because I sometimes look at a rule and wonder how people find such nice rules, and find out that the rule has some unusual transitions. But whenever I tried those transitions out, they never quite played well together for me.

No. Usually I do different transitions for different rules, but yes, sometimes I like to make a rule change a little and be better, then I usually changed the less important transitions(but I don’t especially like s4c or s4e for no good reason)

[pzq_alex]

Speaking of rulegolfing,

Code: Select all

x = 24, y = 3, rule = B35ei6c8/S23-a5i
3o18b3o$bo18bo2bo$20b2o!

[pzq_alex]

Is it due to some content on this subforum or?I made another thread and I am waiting for authorization but I will delete it by myself if I do not get it.

Kazyan locked Word Chains because someone reported it as a thread with a very low signal-to-noise ratio. There's still some ongoing discussion about whether it makes sense for the conwaylife forums to continue to support noisy Sandbox threads like Word Chains.

It seems like a Discord server would be a much better place for content like that that is completely unrelated to cellular automata. There have been several silly Sandbox squabbles recently, resulting in posts getting reported, which just means that moderators have to do more pointless cleanup work.

The Sandbox was intended to be a place where newcomers could experiment with rules and patterns (e.g., using LifeViewer) without worrying about notability issues... not so much a place where people can come and make random large irrelevant messes "just for fun".

Wait, “Kazyan” locked? Is Kazyan a moderator?

Edit: Sorry. I knew this was one year ago.

[hotdogPi]

Yes, and this is a one-year bump.

[GUYTU6J]

Wait, “Kazyan” locked? Is Kazyan a moderator?

Edit: Sorry. I knew this was one year ago.

Yes, and you can see some evidences in User:GUYTU6J/Loafer#Random_remarks_from_private_messages Like calcyman, there are some blue-named users with moderator power.

As for rule-seeking, I start with randomly adjusting transitions until spotting something of interest from random soup, then limit the rulespace with isorule.py, and continue. I typically avoid either birth or survival on 4jw. But the last time I have looked for rules is

As a start for interesting things, a glide-symmetric c/26d that doesn't need S2 and also makes a nice profile gif:

Code: Select all

x = 7, y = 7, rule = B3aijn4an/S3ai4a5ai6ac7c8
2bo2bo$b5o$7o$b4o$2b4o2$2o!

S3c makes an extra dot spark.

and it is a bit hard to find anything else notable in the proximity. The best I just come up with has a D2_2 symmetric p130 inhabiting only 16 rules:

Code: Select all

x = 27, y = 23, rule = B3aijn4ajkn5y/S2k3aeiy4ae5ai6aci7c8
b2o19bo2bo$b2o18b5o$20b7o$b2o18b4o$4o18b4o$b2o$20b2o14$24bo$20b5o$24bo!

---
Signature backup

Code: Select all

Lifequote:
[quote=In the drama The Peony Pavilion, Tang Xianzu]
原来姹紫嫣红开遍，似这般都付与断井颓垣。
(Here multiflorate splendour blooms forlorn
Midst broken fountains, mouldering walls.)[/quote]
I'm afraid there's arrival but no departure.

Code: Select all

[url=https://www.conwaylife.com/wiki/User:GUYTU6J/OCA:Glimmering_Garden]熠熠种花 - Glimmering Garden[/url] 

[url=viewtopic.php?f=11&t=4755]Harvest Moon[/url]

Apparently, [url=https://civilization.fandom.com/wiki/Soundtrack_(Civ6)]Civilization VI soundtracks[/url] accompany cellular automata development nicely.

Geoff Knorr, Phill Boucher - Russia - The Atomic Era

●━━━━━━━━────── 04:18
⇆ㅤㅤ◁ㅤㅤ❚❚ㅤㅤ▷ㅤㅤ↻

[hotdogPi]

Seeds CA in real life (the lit-up flashers). If you go back a step, it confirms that they actually do alternate.

https://www.google.com/maps/@42.6771852 ... 384!8i8192

It's a duoplet right now, but if I add a third on cell orthogonally adjacent to one of the ones that's currently on...

[ihatecorderships]

The short answer is "probably not". The back-most piece was found by doing a 4c/8, glide-symmetric odd, b2f search starting from that exact wick and looking to reach 2c/4 compatible "slices" (I required 4 rows, just 2 suffice for CA overlap reasons, but I find 2 row slices often end up impossible to extend further in the reduced period).

Unfortunately 4c/8 b2f is pretty rough so I could not run very wide searches. This is with my newer program which unfortunately has [yet] no way of trading off time for memory so once it hits the memory limit on my computer here there's nothing I can do. I had run quite a few searches with similar parameters (even, odd, GS even, GS odd, varying wick width, varying space around wick) and this is the only thing that showed up. I could try wider searches, but the widest I had already run were hitting memory limit and dying very quickly already.

What is this b2f that you keep talking about?

[amling]

The short answer is "probably not". The back-most piece was found by doing a 4c/8, glide-symmetric odd, b2f search starting from that exact wick and looking to reach 2c/4 compatible "slices" (I required 4 rows, just 2 suffice for CA overlap reasons, but I find 2 row slices often end up impossible to extend further in the reduced period).

Unfortunately 4c/8 b2f is pretty rough so I could not run very wide searches. This is with my newer program which unfortunately has [yet] no way of trading off time for memory so once it hits the memory limit on my computer here there's nothing I can do. I had run quite a few searches with similar parameters (even, odd, GS even, GS odd, varying wick width, varying space around wick) and this is the only thing that showed up. I could try wider searches, but the widest I had already run were hitting memory limit and dying very quickly already.

What is this b2f that you keep talking about?

Sorry, this is what I get for hiding away in a cave and programming without talking to anyone and thus having no shared terminology.

I've been writing "b2f" for "back to front", as in the search program has a partial pattern that is the "back" side of the ship and is extending that partial pattern towards the front of the ship. Similarly "f2b" for "front to back" and "s2s" for "side to side". Both programs I have written do best by far with f2b searches and mostly better with s2s than with b2f (depending on GCD of velocity numerator and denominator). I have not qualified any of these comparisons, it's just my impression from having worked with them.

For something like (1, 1)c/4 and (2, 1)c/6 what the "front" is is complicated since it's at an angle, although there are still mostly analogs. I haven't done that many non-orthogonal searches though.

This case (4c/8 b2f) is also particularly brutal because 4c/8 is quite a high period which both programs also very much do worse with.

[hotdogPi]

Idea for CGOL battleship: 12×12 grid, place these five objects, all of which have names that are real-life vessels. No water cell can have 3 neighbors, and vessels can only touch if they would remain stable (e.g. boat-ship-tie). Gameplay follows normal Battleship rules.

Code: Select all

x = 12, y = 12, rule = LifeHistory
2A5BA4B$ABA3BABA3B$B2A4BABA2B$8BA3B$12B$12B$10BAB$9BABA$3B2AB2A2B2A$
2BABABA5B$BABA4BA3B$2BA4B2A3B!