ConwayLife.com

summoning lifeisawesome and gameoflifemaniac

Majestas32 wrote:summoning lifeisawesome and gameoflifemaniac

For example, 'bo' (or 'ponieważ') means 'because'.

gameoflifemaniac wrote:'bo' (or 'ponieważ')

Eh? Are they the same word?

I think bo means as or since and ponieważ means because so there's a subtle difference like in English between those two words

Majestas32 wrote:I think bo means as or since and ponieważ means because so there's a subtle difference like in English between those two words

Rzeczywiście! Get it?

Tak, oczywiście

hi gmc_nxtman

I frequent Bay12.

why doesn't the alphabet start with aeioubcd

It should start with cekainyqjrtwz what are you talking about

Majestas32 wrote:It should start with cekainjqrytwz what are you talking about

Wait, have I been spelling it wrong all this time? I've been using ceaiknjqrytwz as the canonical order: https://gitlab.com/apgoucher/lifelib/bl ... ist.py#L10

Phew, Golly agrees with me as well:
https://sourceforge.net/p/golly/code/ci ... es.cpp#l28

According to neighbors2 it's cekainyqjrtwz

The LifeWiki also uses the cekain order.

I usually use aceijknqrtwyz

danny wrote:I usually use aceijknqrtwyz

77topaz wrote:The LifeWiki also uses the cekain order.

Woah those are some weird keyboard layouts

77topaz wrote:The LifeWiki also uses the cekain order.

Ooh, so we now have two rival competing factions: the Golly/lifelib 'ceaikn' clan and the LifeWiki/neighbors2 'cekain' clan. This causes slightly less of a problem than the 'v' did, but means that certain rules are canonised differently by different conventions. Fortunately, because Golly and lifelib agree, Catagolue has a consistent convention.

calcyman wrote:

77topaz wrote:The LifeWiki also uses the cekain order.

Ooh, so we now have two rival competing factions: the Golly/lifelib 'ceaikn' clan and the LifeWiki/neighbors2 'cekain' clan. This causes slightly less of a problem than the 'v' did, but means that certain rules are canonised differently by different conventions. Fortunately, because Golly and lifelib agree, Catagolue has a consistent convention.

No, we don't. Neither order is correct. The canonical order is alphabetical and defined in the Golly documentation under the diagram:

Golly uses the following steps to convert a given non-totalistic rule into its canonical version:

• An underscore can be used instead of a slash, but the canonical version always uses a slash.
• The lowercase letters are listed in alphabetical order. For example, B2nic/S will become B2cin/S.
• A given rule is converted to its shortest equivalent version. For example, B2ceikn/S will become B2-a/S. If equivalent rules have the same length then the version without the minus sign is preferred. For example, B4-qjrtwz/S will become B4aceikny/S.
• It's possible for a non-totalistic rule to be converted to a totalistic rule. If you supply all the letters for a specific neighbor count then the canonical version removes the letters. For example, B2aceikn3/S will become B23/S. (Note that B2-3/S is equivalent to B2aceikn3/S so will also become B23/S.)
• If you supply a minus sign and all the letters for a specific neighbor count then the letters and the neighbor count are removed. For example, B2-aceikn3/S will become B3/S.

LifeViewer also agrees with Golly - for obvious reasons.

rowett wrote: No, we don't. Neither order is correct. The canonical order is alphabetical and defined in the Golly documentation under the diagram:

Golly uses the following steps to convert a given non-totalistic rule into its canonical version:

• An underscore can be used instead of a slash, but the canonical version always uses a slash.
• The lowercase letters are listed in alphabetical order. For example, B2nic/S will become B2cin/S.
• A given rule is converted to its shortest equivalent version. For example, B2ceikn/S will become B2-a/S. If equivalent rules have the same length then the version without the minus sign is preferred. For example, B4-qjrtwz/S will become B4aceikny/S.
• It's possible for a non-totalistic rule to be converted to a totalistic rule. If you supply all the letters for a specific neighbor count then the canonical version removes the letters. For example, B2aceikn3/S will become B23/S. (Note that B2-3/S is equivalent to B2aceikn3/S so will also become B23/S.)
• If you supply a minus sign and all the letters for a specific neighbor count then the letters and the neighbor count are removed. For example, B2-aceikn3/S will become B3/S.

LifeViewer also agrees with Golly - for obvious reasons.

Thank goodness! I'd forgotten that my own Python implementation also orders them alphabetically.

Woah, my comment was sarcastic, haha. Although that is very interesting...

Yeah, I wasn't suggesting that rulestrings use the cekain order - they've always been alphabetical. The graphical illustrations, however, make more sense with cekain or ceaikn because of the groupings.

Or just use my method which numbers them all bSed on a binary number formes by a spiral around the saquare which is a system that can be infinitely extended to other neighborhoods

"Your" system? You're just describing MAP strings.

I had a really weird dream where I was talking to Danny in person and then this happened:

wwei23, in my dream wrote:Can you unban me from Conwaylife Lounge?

danny, in my dream wrote:Sure!

77topaz wrote:"Your" system? You're just describing MAP strings.

Except it's isotropic and it's the transitions that are numbered, not the rules themselves.

77topaz wrote:"Your" system? You're just describing MAP strings.

*uses MAP string as seed for random map*