HeptaFish

[Saka]

HeptaFish is a new rule I made, and as the name suggests, there is a 7-cell glider

Code: Select all

x = 5, y = 3, rule = HeptaFish
2b3o$b2o$2o!

The WSS family does work

Code: Select all

x = 7, y = 18, rule = HeptaFish
bo2bo$o$o3bo$4o3$3bo$bo3bo$o$o4bo$5o3$3b2o$bo4bo$o$o5bo$6o!

Patterns last very long but are stablizing, there are new still lifes and a new p5:

Code: Select all

x = 51, y = 9, rule = HeptaFish
40bo$19bo19bobo$18bobo18bobo$2bo7bo6bo3bo18bo$bobo5bobo4bobobo18bo$o3b
o5bo4bobobo10b2o6bobo8bo$bobo5bo4bo3bo7b2obo2bo4bo3bo6b3o$2bo5bobo4bob
o8bobo2bo6bobo6bobo$9bo6bo12b2o8bo7b2o!

Also, the LWSS is a lot more common, even the b-heptomino makes one:

Code: Select all

x = 4, y = 3, rule = HeptaFish
bo$3o$ob2o!

[Saka]

More still lifes and p2

Code: Select all

x = 4, y = 7, rule = HeptaFish
b2o$o2bo$obo$bo$2bo$bobo$2bo!

Code: Select all

x = 8, y = 5, rule = HeptaFish
bo$obo$bobob2o$4bo2bo$5b2o!

Code: Select all

x = 6, y = 6, rule = HeptaFish
3bo$2bobo$bobobo$obobo$bobo$2bo!

[BlinkerSpawn]

Could you edit the first post to include the rule table for HeptaFish?

[SuperSupermario24]

...Where's the rule?

[drc]

Please post the rule.

[Saka]

Sorry! I had no internet because of a thunderstorm, here's the rule

Code: Select all

@RULE HeptaFish
@TABLE
n_states:2
neighborhood:Moore
symmetries:rotate4reflect
0,1,1,1,0,0,0,0,0,1
0,1,1,0,1,0,0,0,0,1
0,1,1,0,0,1,0,0,0,1
0,1,1,0,0,0,1,0,0,1
0,1,1,0,0,0,0,1,0,1
0,1,1,0,0,0,0,0,1,1
0,1,0,1,0,0,1,0,0,1
0,1,0,0,1,0,1,0,0,1
0,0,1,0,1,0,1,0,0,1
1,0,0,0,0,0,0,0,0,0
1,1,0,0,0,0,0,0,0,0
1,0,1,0,0,0,0,0,0,0
1,1,1,0,0,0,0,0,0,1
1,1,0,1,0,0,0,0,0,1
1,1,0,0,1,0,0,0,0,1
1,1,0,0,0,1,0,0,0,1
1,0,1,0,1,0,0,0,0,1
1,0,1,0,0,0,1,0,0,1
1,1,1,1,0,0,0,0,0,1
1,1,1,0,1,0,0,0,0,1
1,1,1,0,0,1,0,0,0,1
1,1,1,0,0,0,1,0,0,1
1,1,1,0,0,0,0,1,0,1
1,1,1,0,0,0,0,0,1,1
1,1,0,1,0,1,0,0,0,1
1,1,0,1,0,0,1,0,0,1
1,1,0,0,1,0,1,0,0,1
1,1,1,0,1,1,0,0,0,0
1,1,1,1,1,0,0,0,0,0
1,1,1,1,0,1,0,0,0,0
1,1,1,1,0,0,1,0,0,0
1,1,1,0,1,0,1,0,0,0
1,1,1,0,1,0,0,1,0,0
1,1,1,0,1,0,0,0,1,0
1,1,1,0,0,1,1,0,0,0
1,1,1,0,0,1,0,1,0,0
1,1,1,0,0,1,0,0,1,0
1,1,1,0,0,0,1,1,0,0
1,0,1,0,1,0,1,0,1,0
1,0,0,0,1,1,1,1,1,0
1,0,0,1,0,1,1,1,1,0
1,0,0,1,1,0,1,1,1,0
1,0,0,1,1,1,0,1,1,0
1,0,0,1,1,1,1,0,1,0
1,0,0,1,1,1,1,1,0,0
1,0,1,0,1,0,1,1,1,0
1,0,1,0,1,1,0,1,1,0
1,0,1,1,0,1,0,1,1,0
1,1,0,1,0,1,0,1,1,0
1,0,0,1,1,1,1,1,1,0
1,0,1,0,1,1,1,1,1,0
1,0,1,1,0,1,1,1,1,0
1,0,1,1,1,0,1,1,1,0
1,1,0,1,0,1,1,1,1,0
1,1,0,1,1,1,0,1,1,0
1,0,1,1,1,1,1,1,1,0
1,1,0,1,1,1,1,1,1,0
1,1,1,1,1,1,1,1,1,0
1,1,0,1,0,1,0,0,0,0
0,1,1,0,1,1,0,0,0,1
0,1,1,1,1,1,0,0,0,1

[Sphenocorona]

The common polyplet form of the B and the actual B-heptomino evolve differently in this rule. In this case, the difference is actually extremely drastic - the polyomino stabilizes at gen 488...

... but the polyplet finally stabilizes on gen 19024:

Code: Select all

x = 5, y = 3, rule = HeptaFish
2bo$b3o$o2b2o!

[Saka]

The common polyplet form of the B and the actual B-heptomino evolve differently in this rule. In this case, the difference is actually extremely drastic - the polyomino stabilizes at gen 488...

... but the polyplet finally stabilizes on gen 19024:

Code: Select all

x = 5, y = 3, rule = HeptaFish
2bo$b3o$o2b2o!

Yes, I have noticed that

[praosylen]

A reaction creates both a temporary weird still life and a permanent one:

Code: Select all

x = 10, y = 10, rule = HeptaFish
7b2o$6bo2bo$6bobo$7bo4$2b2o$2obo$3bo!

Edit: Two more interesting things:

Code: Select all

x = 20, y = 7, rule = HeptaFish
bo15b3o$3o$18bo$17bo$3bo12bobo$2bobo12bo$3b2o!

[Billabob]

Another P2:

Code: Select all

x = 3, y = 5, rule = HeptaFish
3o2$obo$bo$bo!

Lasts 23K generations and creates some very weird temporary still lifes:

Code: Select all

x = 20, y = 20, rule = HeptaFish
b2obob3o4b3ob3o$9o2bo3b3o$o2bobo2b3o4bobo$b5o5b2ob2o2bo$3ob4obob4o2bo$
2o4bobo2bobob4o$4obo2bo2bob2ob2o$b3o2bobo2b7obo$2o2b2o2bobob2o2b2obo$o
2b3o2bobob2o2b4o$b2ob3o5b2o4b2o$4b3ob2o3b2obo$bobobobob3obobob3o$2ob
10obob2o$o3b2obo2bo5b3o$2b4ob2ob3obo2bobo$bob4ob4obo3b2o$o3bobobob3obo
2b3o$b2o4bo5bo2b2obo$2o2bo2b3o3bobo2b2o!

EDIT: Roughly 37K gens.

Code: Select all

x = 20, y = 20, rule = HeptaFish
o6b5ob5o$2obo2bob2o8b2o$ob5o2b2ob2obo2bo$o2bob3o2bob4o$3o4b3ob2obo2bo$
bo2b2obobo2bobo3bo$b2ob2obo3b5o$b5ob4o3bobob2o$o5bo2b2o3bob4o$bo4bo3bo
bob6o$3bob6obo5bo$b5o10bo$3bobo2bob2o2bo2bo$4obo3bob2ob2o$b3o3bob2o5bo
b2o$3obo3b4o2bob2obo$obobob4ob3ob5o$b4obobo2b2ob2o$3bob2obobobo2b3o$ob
o4bo3b2o2bobo!

EDIT2: And this one lasts... Drumroll please... About 87K generations.

Code: Select all

x = 20, y = 20, rule = HeptaFish
obo3bob2o2b2obob2o$b4obo2b3obob2ob2o$4bo3b4ob5obo$3b3obob2o2b3o3bo$bob
obob4o3bo2bobo$4b6obo4bo$5o3b4o5bo$3o6bo2bo2b2ob2o$obobobob2obob5o$2bo
bo2b2o2b3o$obob3obo4bob5o$o5bo2bo4bo4bo$2bo2b4o2bo2b3obo$2o2bo3b2o2bo
2bobo$2o3bob6o2b2o$obob2obobobobobobobo$o2b2ob2o2bo2b3o2bo$2b2obo2b2ob
ob2o2b3o$4bo3bob3o3b3o$obo2bo3b3o5b3o!

This rule is probably explosive.

[Sphenocorona]

EDIT2: And this one lasts... Drumroll please... About 87K generations.

Code: Select all

rle

This rule is probably explosive.

This 10-cell 34x5 gets you over 350K with it still going strong:

Code: Select all

x = 34, y = 5, rule = HeptaFish
o30bo$o31bo$o31b2o$31b2o$31bo!

It looks as it if explodes forever, but it does encounter an active area bottleneck inbetween 200K and 260K... No idea if it actually explodes forever or not. Pretty sure that very large soups will tend to explode forever more often as they get bigger.

[Billabob]

This 10-cell 34x5 gets you over 350K with it still going strong:

Code: Select all

x = 34, y = 5, rule = HeptaFish
o30bo$o31bo$o31b2o$31b2o$31bo!

It looks as it if explodes forever, but it does encounter an active area bottleneck inbetween 200K and 260K... No idea if it actually explodes forever or not. Pretty sure that very large soups will tend to explode forever more often as they get bigger.

I have run the pattern to 1.2M generations and it is still chaotic. It might stabilise at some point, but that point will likely be after trillions of generations...

[Saka]

Can anybody please tell me:
What is this rule in alan hensel's notation?
(http://www.ibiblio.org/lifepatterns/neighbors2.html)

[wildmyron]

Can anybody please tell me:
What is this rule in alan hensel's notation?
(http://www.ibiblio.org/lifepatterns/neighbors2.html)

This rule's specification in Hensel's notation is: B3-e4i5i/S234e

There are a few confusing aspects of the rule table:

• Having most of the birth conditions at the top but two extras down the bottom makes it harder to find relevant transitions for determining birth criteria.
• The survival transitions are almost fully specified, i.e. there are transitions for survival conditions and for all death conditions. In this case the survival conditions are redundant because the default is for a cell to remain unchanged when there is no matching transition. In theory, including the survival conditions helps to make the rule table more understandable because there are less of them than death conditions, however at least one of the survival conditions is missing [1,0,1,0,1,0,1,0,0,1 #3c]. This was initially very confusing when I tried to verify the rule's behaviour.

Personally, I prefer to use variables to change the default behaviour to be death and to only specify the survival conditions. You can see this technique in the rules created by isotropicRulegen.py
Example:

Code: Select all

# Just Friends - a rule by David Bell
B2-a/S12

n_states:2
neighborhood:Moore
symmetries:rotate4reflect

var a={0,1}
var b={0,1}
var c={0,1}
var d={0,1}
var e={0,1}
var f={0,1}
var g={0,1}
var h={0,1}

# Birth
0,1,0,1,0,0,0,0,0,1
0,1,0,0,1,0,0,0,0,1
0,1,0,0,0,1,0,0,0,1
0,0,1,0,1,0,0,0,0,1
0,0,1,0,0,0,1,0,0,1

# Survival
1,1,0,0,0,0,0,0,0,1
1,0,1,0,0,0,0,0,0,1
1,1,1,0,0,0,0,0,0,1
1,1,0,1,0,0,0,0,0,1
1,1,0,0,1,0,0,0,0,1
1,1,0,0,0,1,0,0,0,1
1,0,1,0,1,0,0,0,0,1
1,0,1,0,0,0,1,0,0,1

# Death
1,a,b,c,d,e,f,g,h,0

[Saka]

Can anybody please tell me:
What is this rule in alan hensel's notation?
(http://www.ibiblio.org/lifepatterns/neighbors2.html)

This rule's specification in Hensel's notation is: B3-e4i5i/S234e

There are a few confusing aspects of the rule table:

• Having most of the birth conditions at the top but two extras down the bottom makes it harder to find relevant transitions for determining birth criteria.
• The survival transitions are almost fully specified, i.e. there are transitions for survival conditions and for all death conditions. In this case the survival conditions are redundant because the default is for a cell to remain unchanged when there is no matching transition. In theory, including the survival conditions helps to make the rule table more understandable because there are less of them than death conditions, however at least one of the survival conditions is missing [1,0,1,0,1,0,1,0,0,1 #3c]. This was initially very confusing when I tried to verify the rule's behaviour.

Personally, I prefer to use variables to change the default behaviour to be death and to only specify the survival conditions. You can see this technique in the rules created by isotropicRulegen.py
Example:

Code: Select all

# Just Friends - a rule by David Bell
B2-a/S12

n_states:2
neighborhood:Moore
symmetries:rotate4reflect

var a={0,1}
var b={0,1}
var c={0,1}
var d={0,1}
var e={0,1}
var f={0,1}
var g={0,1}
var h={0,1}

# Birth
0,1,0,1,0,0,0,0,0,1
0,1,0,0,1,0,0,0,0,1
0,1,0,0,0,1,0,0,0,1
0,0,1,0,1,0,0,0,0,1
0,0,1,0,0,0,1,0,0,1

# Survival
1,1,0,0,0,0,0,0,0,1
1,0,1,0,0,0,0,0,0,1
1,1,1,0,0,0,0,0,0,1
1,1,0,1,0,0,0,0,0,1
1,1,0,0,1,0,0,0,0,1
1,1,0,0,0,1,0,0,0,1
1,0,1,0,1,0,0,0,0,1
1,0,1,0,0,0,1,0,0,1

# Death
1,a,b,c,d,e,f,g,h,0

Ah, I see, I'm sorry, I'll try to change the rule file.

[wildmyron]

Ah, I see, I'm sorry, I'll try to change the rule file.

Hey, don't worry about it, I think I came across a bit brusquely. I solely intended my comments about the rule as helpful advice for you to consider when you are creating and publishing other rules in the future.

[Saka]

c/4 from modified gfind

Code: Select all

x = 14, y = 6, rule = HeptaFish
2b2ob4ob2o$o5b2o5bo$2o3bo2bo3b2o$bo3bo2bo3bo$5bo2bo$3b3o2b3o!

[Saka]

Some more results

Code: Select all

x = 63, y = 36, rule = HeptaFish
38bobobo4bobobo$60bo$38bo3bo8bo7bobo$58bo3bo$38bobobo4bobobo5bo3bo$56b
o3bo$38bo12bo3bo3bo$56bobo$38bo8bobobo5bo2$18b2o2b2o$obobo4bobobo5b4o
2$o12bo5bo2bo$20bo$o8bobobo7bo$18bo3b3o$o12bo4b4o$18b2ob3obo$obobo4bob
obo6bo3b2o$22bob2o$21b2o6$obobo4bobobo2b2o11b2o$17bo11bo$o12bo3b2o9b2o
$18b3o5b3o$o8bobobo8bobo$20b2o3b2o$o8bo11bobobo$21b2ob2o$obobo4bobobo
8b3o!

[Bullet51]

Found via A for Awesome's hacked apgsearch:

Code: Select all

x = 31, y = 17, rule = heptafish
8bo$7bobo$7bobo2$6bobobo$6b2ob2o$4b2o5b2o12b2o2b2o$b2o2bo5bo2b2o8bobo
2b2o$o3bo7bo3bo7b3o$b2o2bo5bo2b2o$4b2o5b2o$6b2ob2o13b2o$6bobobo13b2o2$
7bobo$7bobo$8bo!

[Saka]

Apparently, one of life's lakes is a p3

Code: Select all

x = 9, y = 9, rule = HeptaFish
4bo$3bobo$3bobo$b2o3b2o$o7bo$b2o3b2o$3bobo$3bobo$4bo!

[Sphenocorona]

Found via A for Awesome's hacked apgsearch:

Code: Select all

rle

A p14 and a p11, very nice! Their minimal pop. appears to be 24 and 14 respectively. Additionally, the p14 can be turned into a p5 with some eaters:

Code: Select all

x = 21, y = 21, rule = HeptaFish
5bo$5b3o$8bo$7bo$7bo3bo$19b2o$8bo3bo6bo$8b2ob2o3b2obo$6b2o5b2o3bo$4bo
2bo5bo2$7bo5bo2bo$2bo3b2o5b2o$bob2o3b2ob2o$bo6bo3bo$2o$9bo3bo$13bo$12b
o$13b3o$15bo!