Apgcode - Revision history

SecondTypist: Corrected suffix information for linear growth

2026-07-26T00:59:41Z

Corrected suffix information for linear growth

← Older revision		Revision as of 00:59, 26 July 2026
Line 30:		Line 30:
	* The second value represents the period at which the population of the debris fluctuates.		* The second value represents the period at which the population of the debris fluctuates.
	* The third value represents how much the population grows after the amount of generations specified in the first value have elapsed.		* The third value represents how much the population grows after the amount of generations specified in the first value have elapsed.
	* ~~What the~~ fourth value corresponds to ~~is currently not known; it appears to be a hashing function~~.		* The fourth value corresponds to the Extended Wechsler Format of the linear growth pattern.

	=== Unencodable objects ===		=== Unencodable objects ===

HotdogPi: what is "a example"

2024-10-13T14:52:04Z

what is "a example"

← Older revision		Revision as of 14:52, 13 October 2024
Line 16:		Line 16:

	The number following the type represents the [[population]] for a still life, the lifespan for a methuselah or diehard, or otherwise the [[period]] of the object.		The number following the type represents the [[population]] for a still life, the lifespan for a methuselah or diehard, or otherwise the [[period]] of the object.
	For a example, see [[xp2]].		For an example, see [[xp2]].

	Note that despite always having a constant shape and population, spaceships of period 1 are classified under <tt>xq</tt> rather than under <tt>xs</tt> or a dedicated period-1 spaceship prefix.		Note that despite always having a constant shape and population, spaceships of period 1 are classified under <tt>xq</tt> rather than under <tt>xs</tt> or a dedicated period-1 spaceship prefix.

Apple Bottom: /* Encoding objects */

2023-10-08T10:57:51Z

Encoding objects

← Older revision		Revision as of 10:57, 8 October 2023
Line 10:		Line 10:
	* <tt>xp</tt> for an [[oscillator]];		* <tt>xp</tt> for an [[oscillator]];
	* <tt>xq</tt> for a [[spaceship]];		* <tt>xq</tt> for a [[spaceship]];
	* <tt>yl</tt> for a periodic linearly growing object, such as a [[puffer]] or [[gun]]; ~~and~~		* <tt>yl</tt> for a periodic linearly growing object, such as a [[puffer]] or [[gun]];
	* <tt>methuselah</tt> for a [[methuselah]].		* <tt>methuselah</tt> for a [[methuselah]];
	* <tt>messless</tt> for a [[diehard]].		* <tt>messless</tt> for a [[diehard]]; and
	* <tt>megasized</tt> for a soup with a large final population.		* <tt>megasized</tt> for a soup with a large final population.

TYCF: /* Prefix */

2023-09-21T16:30:37Z

Prefix

← Older revision		Revision as of 16:30, 21 September 2023
Line 16:		Line 16:

	The number following the type represents the [[population]] for a still life, the lifespan for a methuselah or diehard, or otherwise the [[period]] of the object.		The number following the type represents the [[population]] for a still life, the lifespan for a methuselah or diehard, or otherwise the [[period]] of the object.
			For a example, see [[xp2]].

	Note that despite always having a constant shape and population, spaceships of period 1 are classified under <tt>xq</tt> rather than under <tt>xs</tt> or a dedicated period-1 spaceship prefix.		Note that despite always having a constant shape and population, spaceships of period 1 are classified under <tt>xq</tt> rather than under <tt>xs</tt> or a dedicated period-1 spaceship prefix.

Confocal: /* References */ category

2023-03-24T06:53:53Z

References: category

← Older revision		Revision as of 06:53, 24 March 2023
Line 283:		Line 283:
	[[Category:Everything else]]		[[Category:Everything else]]
	[[Category:File formats]]		[[Category:File formats]]
			[[Category:Algorithms]]

	{{DISPLAYTITLE:apgcode}}		{{DISPLAYTITLE:apgcode}}

Carson Cheng: Changing one word to get the complete description of the previous edit published: The linear-growth detection algorithm only detects the population of the mechanism, (e.g., the GPSE produces debris that oscillates at period 2 and has period-4 escaping spaceships, the debris period is marked as "1" because the population of the ash remains stable at all times.

2022-09-03T00:12:52Z

Changing one word to get the complete description of the previous edit published: The linear-growth detection algorithm only detects the population of the mechanism, (e.g., the GPSE produces debris that oscillates at period 2 and has period-4 escaping spaceships, the debris period is marked as "1" because the population of the ash remains stable at all times.

← Older revision		Revision as of 00:12, 3 September 2022
Line 27:		Line 27:
	** Despite the [[block-laying switch engine]] having a period of 288, its value is 144 due to [[glide symmetry]].		** Despite the [[block-laying switch engine]] having a period of 288, its value is 144 due to [[glide symmetry]].
	** Likewise, a diagonal puffer from [[HighLife]] has a value of 960 rather than the expected 192 due to creating period-10 oscillators out of phase with each other.		** Likewise, a diagonal puffer from [[HighLife]] has a value of 960 rather than the expected 192 due to creating period-10 oscillators out of phase with each other.
	* The second value represents the period at which the population of the debris ~~oscillates~~.		* The second value represents the period at which the population of the debris fluctuates.
	* The third value represents how much the population grows after the amount of generations specified in the first value have elapsed.		* The third value represents how much the population grows after the amount of generations specified in the first value have elapsed.
	* What the fourth value corresponds to is currently not known; it appears to be a hashing function.		* What the fourth value corresponds to is currently not known; it appears to be a hashing function.

Carson Cheng: The linear-growth algorithm only detects the population (e.g., while the GPSE

2022-09-03T00:08:31Z

The linear-growth algorithm only detects the population (e.g., while the GPSE

← Older revision		Revision as of 00:08, 3 September 2022
Line 27:		Line 27:
	** Despite the [[block-laying switch engine]] having a period of 288, its value is 144 due to [[glide symmetry]].		** Despite the [[block-laying switch engine]] having a period of 288, its value is 144 due to [[glide symmetry]].
	** Likewise, a diagonal puffer from [[HighLife]] has a value of 960 rather than the expected 192 due to creating period-10 oscillators out of phase with each other.		** Likewise, a diagonal puffer from [[HighLife]] has a value of 960 rather than the expected 192 due to creating period-10 oscillators out of phase with each other.
	* The second value represents the period at which the debris oscillates.		* The second value represents the period at which the population of the debris oscillates.
	* The third value represents how much the population grows after the amount of generations specified in the first value have elapsed.		* The third value represents how much the population grows after the amount of generations specified in the first value have elapsed.
	* What the fourth value corresponds to is currently not known; it appears to be a hashing function.		* What the fourth value corresponds to is currently not known; it appears to be a hashing function.

Confocal: LifeWiki:Tiki bar/Archive/2020#"Non-Lifelike" CAs -- cleanup suggested

2022-08-10T03:12:55Z

LifeWiki:Tiki bar/Archive/2020#"Non-Lifelike" CAs -- cleanup suggested

← Older revision		Revision as of 03:12, 10 August 2022
Line 216:		Line 216:

	== Limitations ==		== Limitations ==
	An apgcode does not encode the rule with the pattern. An apgcode can be ambiguous if a rule is neither specified nor implicitly assumed, with the same code being assigned to different patterns evolving differently. For example, the code <tt>xp2_2a54</tt> describes at least three different period-2 oscillators in outer-totalistic rules which are all titled as "[[clock]]"; further variants exist in [[non-totalistic ~~Life-like~~ cellular automaton\|non-totalistic rules]]:		An apgcode does not encode the rule with the pattern. An apgcode can be ambiguous if a rule is neither specified nor implicitly assumed, with the same code being assigned to different patterns evolving differently. For example, the code <tt>xp2_2a54</tt> describes at least three different period-2 oscillators in outer-totalistic rules which are all titled as "[[clock]]"; further variants exist in [[non-totalistic cellular automaton\|non-totalistic rules]]:

	{\| style="margin-left: auto; margin-right: auto;" class="wikitable"		{\| style="margin-left: auto; margin-right: auto;" class="wikitable"

Carson Cheng at 15:33, 5 August 2022

2022-08-05T15:33:14Z

← Older revision		Revision as of 15:33, 5 August 2022
Line 230:		Line 230:
	\|}		\|}

	Apgcode was not designed to encode arbitrary patterns in an unambiguous way (including infinite growth patterns and active regions).<ref>{{LinkForumThread\|p=132285\|title=Re: Thread for basic questions\|format=ref}}</ref> The exact location and orientation of a pattern and the specific phase of a periodic pattern are ~~lost~~ in an apgcode.<ref>{{LinkForumThread\|p=132288\|title=Re: Thread for basic questions\|format=ref}}</ref>		Apgcode was not designed to encode arbitrary patterns in an unambiguous way (including infinite growth patterns and active regions).<ref>{{LinkForumThread\|p=132285\|title=Re: Thread for basic questions\|format=ref}}</ref> The exact location and orientation of a pattern and the specific phase of a periodic pattern are not encoded in an apgcode.<ref>{{LinkForumThread\|p=132288\|title=Re: Thread for basic questions\|format=ref}}</ref>

	== See also ==		== See also ==

Confocal: /* Limitations */ +

2022-08-05T14:29:02Z

Limitations: +

← Older revision		Revision as of 14:29, 5 August 2022
Line 216:		Line 216:

	== Limitations ==		== Limitations ==
	~~apgcodes~~ can be ambiguous if a rule is neither specified nor implicitly assumed, with the same code being assigned to different patterns evolving differently. For example, the code <tt>xp2_2a54</tt> describes at least three different period-2 oscillators in outer-totalistic rules which are all titled as "[[clock]]"; further variants exist in [[non-totalistic Life-like cellular automaton\|non-totalistic rules]]:		An apgcode does not encode the rule with the pattern. An apgcode can be ambiguous if a rule is neither specified nor implicitly assumed, with the same code being assigned to different patterns evolving differently. For example, the code <tt>xp2_2a54</tt> describes at least three different period-2 oscillators in outer-totalistic rules which are all titled as "[[clock]]"; further variants exist in [[non-totalistic Life-like cellular automaton\|non-totalistic rules]]:

	{\| style="margin-left: auto; margin-right: auto;" class="wikitable"		{\| style="margin-left: auto; margin-right: auto;" class="wikitable"
Line 229:		Line 229:
	\| B4/S1 to B45678/S01245678		\| B4/S1 to B45678/S01245678
	\|}		\|}

			Apgcode was not designed to encode arbitrary patterns in an unambiguous way (including infinite growth patterns and active regions).<ref>{{LinkForumThread\|p=132285\|title=Re: Thread for basic questions\|format=ref}}</ref> The exact location and orientation of a pattern and the specific phase of a periodic pattern are lost in an apgcode.<ref>{{LinkForumThread\|p=132288\|title=Re: Thread for basic questions\|format=ref}}</ref>

	== See also ==		== See also ==