Golly/LV inconsistency

Has something gone haywire? Let us know about it!
Post Reply
User avatar
d/dx
Posts: 480
Joined: March 22nd, 2024, 2:41 pm
Location: in your walls

Golly/LV inconsistency

Post by d/dx » October 4th, 2024, 2:53 pm

d/dx wrote:
October 4th, 2024, 2:50 pm
A bug:

Code: Select all

x = 26, y = 21, rule = LifeHistory
2.A$A.A15.2A$.2A14.A.A$16.A2.A.A$16.A.A.A.A$15.2A.A3.A$18.A2.2A.2A$
15.2A.A.A2.A.A$11.2E2.2A.A.2A.A$7.A3.2E6.A2.A.A$6.A.A12.A2.A$5.A.A14.
2A$5.A6.2A.A2.A$4.2A6.2A.4A2$12.5A$11.A5.A$12.2A2.2A$7.2A.A.A$7.A.2A
2.A$12.2A!
If you view in Golly the state5 block becomes state3. In LV it does not.
Reposting here to hopefully bring the issue to more light than it would get in my sandbox thread.
my shtuffs


DieciFseis when?

User avatar
confocaloid
Posts: 4547
Joined: February 8th, 2022, 3:15 pm
Location: https://catagolue.hatsya.com/census/b3s234c/C4_4/xp62

Re: Golly/LV inconsistency

Post by confocaloid » October 4th, 2024, 3:22 pm

[R]History is indeed designed so that "state 5" means "a marked alive cell that was alive since generation 0, never changing its state". So Golly works correctly here, the block should become state-3.

LifeViewer implements it differently, due to a performance optimization. See this post: viewtopic.php?p=191092#p191092
d/dx wrote:
October 4th, 2024, 2:50 pm
A bug:

Code: Select all

x = 26, y = 21, rule = LifeHistory
2.A$A.A15.2A$.2A14.A.A$16.A2.A.A$16.A.A.A.A$15.2A.A3.A$18.A2.2A.2A$
15.2A.A.A2.A.A$11.2E2.2A.A.2A.A$7.A3.2E6.A2.A.A$6.A.A12.A2.A$5.A.A14.
2A$5.A6.2A.A2.A$4.2A6.2A.4A2$12.5A$11.A5.A$12.2A2.2A$7.2A.A.A$7.A.2A
2.A$12.2A!
If you view in Golly the state5 block becomes state3. In LV it does not.
127:1 B3/S234c User:Confocal/R (isotropic CA, incomplete)
Unlikely events happen.
My silence does not imply agreement, nor indifference. If I disagreed with something in the past, then please do not construe my silence as something that could change that.

Post Reply