small period 9 oscillator in B34/S25

[Lanulos]

B34/S25 tends to form self contained boiling masses which either eventually dissipate with little ash, or if of sufficient size, expand indefinitely. I have found a small period-9 oscillator in this system, its smallest iteration being an 8 cell diamond:

--o--
-o-o-
o---o
-o-o-
--o--

It also has the blinker, an extended "blinker" (line of four cells) and two small period 4 oscillators:

-o--
o-o-
o-oo

and

-oo-
oooo

As I am using Underscore Life on an iPod Touch, I was unable to save files in the .lif format.

[Ntsimp]

This rule also has a small p54:

Code: Select all

----OOOOO
---------
----OOOOO
---------
O-O------
O-O------
O-O------
O-O------
O-O------

[Lewis]

Stamp Colletcion (New periods are 3, 6, 7, 8, 12 and 15):

Code: Select all

x = 100, y = 57, rule = 25/34
89bobo2$90bo$87b7o$86bo7bo$obobo10bo12bo40bo3bobobo7bo9bo$9b3o
2b4o3b3o2bobo10bobobo40bo3bo3bo3bo$4bo11bo3b3o4bobo39bo7bo6bo
2bo5bo2bo$27bo15bo37bo2bo11bo2bo$obobo44b3ob3o13bo3bobobo5b2o
11b2o$43bo5b3ob3o25bo2bo11bo2bo$o48b3ob3o13bo3bo10bo2bo5bo2bo
$14bo4bo23bo40bo3bo3bo3bo$obobo4b2o3b2o3b2o5bo42bo3bobobo7bo9b
o$10bo3bo4bo4bo2b2o14bo42bo7bo$9bo5bo4bo3bo2b3o57b7o$9b2o3b2o
3b2o4bo64bo$20bo$39bobobo45bobo2$39bo3bo4bo$47bo2bo$obobo34bo
bobo3bo2bo$48bo2b2o$4bo34bo3bo$50bo2bo15bo3bobobo$obobo3b4obo
25bobobo7b2o30bob4obo$11bobo55bo3bo8bo8bo$4bo7bo69bo2bo2bo2bo
$69bo3bobobo4bo2b4o2bo$obobo77bo2bo2bo2bo$39bobobo25bo7bo4bo8b
o$50b3o30bob4obo$39bo3bo25bo3bobobo$o3bo43bob3obo$9bo13bo15bo
bobo4bobobobo$o3bo3bo2bo9bobo24bob3obo$9b3o2b4o3bobo19bo$obob
o10b2o5bo27b3o$39bobobo$4bo2$4bo60bobobo3bo3bo$89b5o$65bo7bo3b
o$89b5o$obobo60bobobo3bobobo$21bo63bobo$o9bo10b2o46bo7bo7bobo
$9bo2bo8bo63bobo$obobo4bo2b2o7bo43bobobo7bo7bobo$9bo9b2o64bob
o$o3bo5bo3bo4b2o$11b3o7bo$obobo16bo$21b2o$21bo!

A small census made using Winlife32 and thrown together rather terribly using Paint (in order to show pictures of each pattern). I didn't run the census for too long, because the resulting image would take much longer to make (at least until a naming system for this rule is made):

[Karatorian]

Well, for a naming system, you could probably adapt the system used for unnamed Life patterns. I've yet to find it formally documented anywhere (there really should be a wiki article), but I'll try to explain it as best I've figured it out. Basically a pattern ID looks like this:

<cells>P<period>H<horizontal movement>V<vertical movement>A<cells added>.<unique>

Cell count is at the smallest phases. Generally, the parts you don't need are left out.

P is only used if the period is greater than one. H and V are used by spaceships. Orthogonal movement is considered to be horizontal, so (in Life anyway), V is only non-zero (and equal to H) for diagonal movement. However, if H is present, so is V, even if zero. Presumably, oblique movement would put the larger number in H. A is used by puffers and guns.

The only tricky part is the number after the dot at the end. It's function is to differentiate patterns which would have the same ID otherwise. For small sizes, which can be exhaustively searched, this is relatively basic. Either a sorting criteria is defined, and then the patterns are assigned numbers in order, or a full list can be constructed and the numbers given "by definition".

However, for larger sizes, I don't really know how it works. I presume it's by date of discovery, or publication, or database entry. This is unfortunate, because as computing power increases and larger spaces can be searched, it'd be handy to be able to use systematic names. However, changing the names of existing objects would cause confusion.

Perhaps it'd be a good idea to add a letter after the dot, but before the number (or something) to differentiate these "arbitrary" numbers from systematic ones. That way, if full searches can be conducted in the future, some objects might have two names, but at least there wouldn't be two objects with the same name. (However, it seems to be a little late to adopt this idea for Life.)

Edit: see http://pentadecathlon.com/objects/defin ... comparison

[Naszvadi]

No more necroposting, just this last one - I am pretty sure that this glider is in Eppstein's vintage glider database floating around (p.ex. on archive.org)

Code: Select all

#C |sed '/^[.o]\+!*$/{y/./b/;s/b*$/\$/;b};s/^Length:/!\n#C &/;t;s/^/#C /'
#C ntzfind 3.0 by "zdr", Matthias Merzenich, Aidan Pierce, and Tomas Rokicki, 24 February 2018
#C - ./ntzfind B34/S25 p3 k1 w9 a n
#C Rule: B34/S25
#C Period: 3
#C Offset: 1
#C Width:  9
#C Symmetry: asymmetric
#C Depth limit: 2000
#C Stop search if a ship is found.
#C Use min population search order.
#C Starting search
#C
x = 10 , y = 36 , rule = B34/S25
bbbbbo$bbbbobo$bbboobbo$bbbboobbo$bbooo$bbbooboo$booo$bobo$obbo$$booo$bobo!
#C Length: 36
#C Spaceship found. (1)
#C 
#C Current depth: 2001
#C Calculations: 12677
#C CPU time: 0.132271 seconds
#C Search terminated: spaceship found.

[LaundryPizza03]

No more necroposting, just this last one - I am pretty sure that this glider is in Eppstein's vintage glider database floating around (p.ex. on archive.org)

Code: Select all

#C |sed '/^[.o]\+!*$/{y/./b/;s/b*$/\$/;b};s/^Length:/!\n#C &/;t;s/^/#C /'
#C ntzfind 3.0 by "zdr", Matthias Merzenich, Aidan Pierce, and Tomas Rokicki, 24 February 2018
#C - ./ntzfind B34/S25 p3 k1 w9 a n
#C Rule: B34/S25
#C Period: 3
#C Offset: 1
#C Width:  9
#C Symmetry: asymmetric
#C Depth limit: 2000
#C Stop search if a ship is found.
#C Use min population search order.
#C Starting search
#C
x = 10 , y = 36 , rule = B34/S25
bbbbbo$bbbbobo$bbboobbo$bbbboobbo$bbooo$bbbooboo$booo$bobo$obbo$$booo$bobo!
#C Length: 36
#C Spaceship found. (1)
#C 
#C Current depth: 2001
#C Calculations: 12677
#C CPU time: 0.132271 seconds
#C Search terminated: spaceship found.

Surprisingly, the one in the database is two non-interacting copies of this!

Code: Select all

x = 12, y = 9, rule = B34/S25
8bo$6b2o2b2o$4bobo3bo$2bob5ob2o$b5o$o2bo$bo3bo$2bo2bo$3bo!

[Naszvadi]

No more necroposting, just this last one - I am pretty sure that this glider is in Eppstein's vintage glider database floating around (p.ex. on archive.org)

Code: Select all

#C |sed '/^[.o]\+!*$/{y/./b/;s/b*$/\$/;b};s/^Length:/!\n#C &/;t;s/^/#C /'
#C ntzfind 3.0 by "zdr", Matthias Merzenich, Aidan Pierce, and Tomas Rokicki, 24 February 2018
#C - ./ntzfind B34/S25 p3 k1 w9 a n
#C Rule: B34/S25
#C Period: 3
#C Offset: 1
#C Width:  9
#C Symmetry: asymmetric
#C Depth limit: 2000
#C Stop search if a ship is found.
#C Use min population search order.
#C Starting search
#C
x = 10 , y = 36 , rule = B34/S25
bbbbbo$bbbbobo$bbboobbo$bbbboobbo$bbooo$bbbooboo$booo$bobo$obbo$$booo$bobo!
#C Length: 36
#C Spaceship found. (1)
#C 
#C Current depth: 2001
#C Calculations: 12677
#C CPU time: 0.132271 seconds
#C Search terminated: spaceship found.

Surprisingly, the one in the database is two non-interacting copies of this!

Code: Select all

x = 12, y = 9, rule = B34/S25
8bo$6b2o2b2o$4bobo3bo$2bob5ob2o$b5o$o2bo$bo3bo$2bo2bo$3bo!

Does prior art count? Dug a little among the *gliders.db.txt archives, and before 2020.03.27 only the symmetric version had been published, but I might be wrong.