My notation for non-isotropic non-totalistic 2 state moore1 rules

For discussion of other cellular automata.
Post Reply
.H!
Posts: 3
Joined: September 7th, 2021, 11:05 pm

My notation for non-isotropic non-totalistic 2 state moore1 rules

Post by .H! » September 7th, 2021, 11:10 pm

Here's my thing.

It's fully backwards compatible with regular hensel notation/INT rules/such.

Each of the standard INT transitions has a canonical 0deg unmirrored form,
which is taken to be the angle it's at in THAT table. Yes, you know which one i mean.

m after a transition means it's mirrored.

# 0deg
! 90deg
~ 180deg
@ 270deg

B2a, for example, now consists of B2a#, B2a!, B2a~, B2a@, B2a#m, B2a!m, B2a~m and B2a@m.
You can use - and combine in the normal ways.
B2a-# for example is B2a without

Code: Select all

##.
.c.
...
specifically.

Okay, so this is cool, but accounting for various permutations of cells can get tricky.
Introducing multiplication and division operations (* and %)

B1e!*7e! means B1e!, but it doesn't care about the cells in the shape of 7e!.
Effectively, if * can be any state, this means

Code: Select all

***
*c#
***
Division (%) means that it will happen if all of the cells in the first argument are *off*.
This means that b1e!%7e! is

Code: Select all

***
*c.
***
Oh yes, and if you want, for example, B2 but with B2a#*3i~,

Code: Select all

##.
.c.
***
Then you can use + to explicitly mark it as seperate. This makes it B2+a#*3i.
(this can happen after negation too)

This should maybe account for all cases in existence.
Please remind me to compile this to MAP strings sometime soon and inform me of problems or mistakes.

Example rules:

Everything unconditionally moves right: B1e!7e!/S1e!*7e!

CGOL but downright moving gliders implode: B35n#m/S23

Rule 90 (in place): B1e!@/S1e!@
Rule 90 (spacetime): B1c#!/S0*8

pzq_alex
Posts: 106
Joined: May 1st, 2021, 9:00 pm
Location: in the life universe

Re: My notation for non-isotropic non-totalistic 2 state moore1 rules

Post by pzq_alex » September 10th, 2021, 7:40 am

We have MAP strings already, it's both easy to read by a program, and will more probably not cause escape errors when you paste that into a piece of code. Plus, Golly and LifeViewer support it.

.H!
Posts: 3
Joined: September 7th, 2021, 11:05 pm

Re: My notation for non-isotropic non-totalistic 2 state moore1 rules

Post by .H! » September 17th, 2021, 12:54 pm

pzq_alex wrote:
September 10th, 2021, 7:40 am
We have MAP strings already, it's both easy to read by a program, and will more probably not cause escape errors when you paste that into a piece of code. Plus, Golly and LifeViewer support it.
I'm aware? Imagine if instead of notation like B3-e/S23, there was a 102 bit string that was converted into base64 that you had to use instead. Would interacting with INT rules be particularly easy then?

Post Reply