Golly bugs

Has something gone haywire? Let us know about it!
User avatar
rowett
Moderator
Posts: 3776
Joined: January 31st, 2013, 2:34 am
Location: UK
Contact:

Re: Golly bugs

Post by rowett » August 28th, 2022, 11:13 am

GUYTU6J wrote:
August 28th, 2022, 10:25 am
1. Open a B3/S23V pattern.
2. Hit Alt+G to convert to Super; new rule name is displayed as "LifeVSuper".
3. Hit Alt+H; a Golly note says that "Conversion failed. This 'LifeV' rule is not supported by the Super algo. To revert to the original rule..."
3'. Alternatively, Hit Alt+J; a Lua error says that "golly-4.2-win-64bit\Scripts\Lua\toStandard.lua:64: Given rule is not valid in any algorithm."
3. Was fixed above.
I've also just committed the fix for 3'.

You'll need a new build of Golly to see the changes.

GUYTU6J
Posts: 2200
Joined: August 5th, 2016, 10:27 am
Location: 拆哪!I repeat, CHINA! (a.k.a. 种花家)
Contact:

Re: Golly bugs

Post by GUYTU6J » September 13th, 2022, 4:56 am

The following curvy python precedure reliably creates an obscure warning.

1. Save the following python script as repeat.py

Code: Select all

import golly as g
s = g.getselrect()
if s == []:
    s = g.getrect()
xy = [0, 0]
s = g.getcells(s)
if s == []:
    g.exit("Pattern is empty.")
disp = g.getstring("Enter displacement in form (x,y,t):", "2,14,14").split(",")
n = 0
try:
    disp = (int(disp[0]), int(disp[1]), int(disp[2]))
    n = int(g.getstring("How many times to repeat?", "1000"))
except:
    g.exit("Invalid input.")
g.new("repeated")
g.putcells(s, xy[0], xy[1], 1, 0, 0, 1, "xor")
for i in range(n):
    xy[0] += disp[0]
    xy[1] += disp[1]
    g.run(disp[2])
    g.putcells(s, xy[0], xy[1], 1, 0, 0, 1, "xor")
2. Start a new Golly
3. Set rule to W90 in QuickLife and draw a dot
4. Execute the script with predefined parameters
5. Before reaching full File size, click Cancel in the "Writing pattern file" popup window; a Golly warning saying File contains truncated pattern is expected.
6. Undo with ctrl+Z (NOT reset!)
7. Execute the script again
This will result in a Golly warning popping up, saying G_PyRun_SimpleString failed!, but then the first dialog in the script will pop up as usual.

User avatar
Andrew
Moderator
Posts: 919
Joined: June 2nd, 2009, 2:08 am
Location: Melbourne, Australia
Contact:

Re: Golly bugs

Post by Andrew » September 17th, 2022, 1:19 am

GUYTU6J wrote:
September 13th, 2022, 4:56 am
... This will result in a Golly warning popping up, saying G_PyRun_SimpleString failed! ...
I can reproduce this warning on my Mac but I've got no idea why it happens (the G_PyRun_SimpleString routine was added by Scorbie when we switched to support for Python 3, so maybe he could provide some clues). I suspect it's a spurious warning that can safely be ignored -- it doesn't seem to cause any problems if you run further Python scripts.
Use Glu to explore CA rules on non-periodic tilings: DominoLife and HatLife

User avatar
DroneBetter
Posts: 94
Joined: December 1st, 2021, 5:16 am
Location: The UK (a delightful place)
Contact:

Re: Golly bugs

Post by DroneBetter » November 18th, 2022, 1:54 pm

Perhaps not a bug but when pasting a LifeHistory RLE into a Life universe, the cells in the History state are converted to those in the Alive state, please add an exception for all history rules to prevent this, it is extremely frustrating when I am trying to paste in guns from the Catagolue gun census (which use it so that the RLE's bounding box is that of the gun irrespective of phase), I must change the rule in LifeViewer before pasting it, or change Golly's rule back and forth. Could the default behaviour for pasting RLEs in be changed to enact the process of conversion when a rule is changed, so that this (and other such issues) wouldn't have to be implemented twice?
That concludes my post (I hope you liked it)

User avatar
dvgrn
Moderator
Posts: 10612
Joined: May 17th, 2009, 11:00 pm
Location: Madison, WI
Contact:

Re: Golly bugs

Post by dvgrn » November 18th, 2022, 2:40 pm

DroneBetter wrote:
November 18th, 2022, 1:54 pm
Perhaps not a bug but when pasting a LifeHistory RLE into a Life universe, the cells in the History state are converted to those in the Alive state, please add an exception for all history rules to prevent this, it is extremely frustrating when I am trying to paste in guns from the Catagolue gun census (which use it so that the RLE's bounding box is that of the gun irrespective of phase), I must change the rule in LifeViewer before pasting it, or change Golly's rule back and forth. Could the default behaviour for pasting RLEs in be changed to enact the process of conversion when a rule is changed, so that this (and other such issues) wouldn't have to be implemented twice?
Yup, this is a long-standing usability issue with LifeHistory, where the current workaround is not at all obvious from the GUI.

I'm not sure how soon this feature request will be added to Golly; it would be a rather fiddly adjustment with a lot of rare weird special cases that might need to be handled.

In the meantime, are you aware of the keyboard shortcuts that shift Golly back and forth between [Rule]Super (Alt+G), [Rule]History (Alt+H), and the standard two-state [Rule] (Alt+J)?

Generally if you've copied a LifeHistory pattern to the clipboard, and you're now staring at a two-state universe in Golly and want to paste in the copied pattern as two-state, you have two options:

1) if the universe is empty or you want to clear it before pasting, hit Ctrl+Shift+O to open the clipboard as a new pattern, then hit Alt+J.
2) to add the LifeHistory pattern to your existing two-state pattern, hit Alt+H to switch the universe to History mode, paste in the pattern, then hit Alt+J.

User avatar
LaundryPizza03
Posts: 2297
Joined: December 15th, 2017, 12:05 am
Location: Unidentified location "https://en.wikipedia.org/wiki/Texas"

Re: Golly bugs

Post by LaundryPizza03 » November 19th, 2022, 6:06 am

dvgrn wrote:
November 18th, 2022, 2:40 pm
DroneBetter wrote:
November 18th, 2022, 1:54 pm
Perhaps not a bug but when pasting a LifeHistory RLE into a Life universe, the cells in the History state are converted to those in the Alive state, please add an exception for all history rules to prevent this, it is extremely frustrating when I am trying to paste in guns from the Catagolue gun census (which use it so that the RLE's bounding box is that of the gun irrespective of phase), I must change the rule in LifeViewer before pasting it, or change Golly's rule back and forth. Could the default behaviour for pasting RLEs in be changed to enact the process of conversion when a rule is changed, so that this (and other such issues) wouldn't have to be implemented twice?
Yup, this is a long-standing usability issue with LifeHistory, where the current workaround is not at all obvious from the GUI.

I'm not sure how soon this feature request will be added to Golly; it would be a rather fiddly adjustment with a lot of rare weird special cases that might need to be handled.

In the meantime, are you aware of the keyboard shortcuts that shift Golly back and forth between [Rule]Super (Alt+G), [Rule]History (Alt+H), and the standard two-state [Rule] (Alt+J)?

Generally if you've copied a LifeHistory pattern to the clipboard, and you're now staring at a two-state universe in Golly and want to paste in the copied pattern as two-state, you have two options:

1) if the universe is empty or you want to clear it before pasting, hit Ctrl+Shift+O to open the clipboard as a new pattern, then hit Alt+J.
2) to add the LifeHistory pattern to your existing two-state pattern, hit Alt+H to switch the universe to History mode, paste in the pattern, then hit Alt+J.
In the Mac edition, Option+G (equivalent to Alt) does nothing, Option+H fails to find LifeHistory in the rulefiles, and Option+J looks for "toLife.lua" which is now called "toStandard.lua"

Code: Select all

x = 4, y = 3, rule = B3-q4z5y/S234k5j
2b2o$b2o$2o!
LaundryPizza03 at Wikipedia

User avatar
dvgrn
Moderator
Posts: 10612
Joined: May 17th, 2009, 11:00 pm
Location: Madison, WI
Contact:

Re: Golly bugs

Post by dvgrn » November 19th, 2022, 9:25 am

LaundryPizza03 wrote:
November 19th, 2022, 6:06 am
In the Mac edition, Option+G (equivalent to Alt) does nothing, Option+H fails to find LifeHistory in the rulefiles, and Option+J looks for "toLife.lua" which is now called "toStandard.lua"...
This is what happens on any OS, when an older version of Golly is updated to a version that supports the Super algo and GollyPrefs is not re-generated. The only way that Golly would know about "toLife.lua" is if it's remembering the GollyPrefs settings from a previous version of Golly. It's a minor configuration problem, not so much a bug, and not at all specific to Macs.

There is an easy fix for this, as described here.

The whole situation is definitely not terribly user-friendly. However, this is a one-time upgrade problem, and it's good for people to know how to set up keyboard shortcuts -- they're so extremely useful for other reasons! There are all kinds of painful tasks in Golly that can be made un-painful by very short custom scripts mapped to keyboard shortcuts.

Anyway, eventually the news will get to everyone who had an old version of Golly installed, and all of those old GollyPrefs files will get adjusted to point to the new Super-algo Lua scripts.

User avatar
confocaloid
Posts: 2729
Joined: February 8th, 2022, 3:15 pm

Re: Golly bugs

Post by confocaloid » March 9th, 2023, 7:52 am

I just made index.php into a redirect to Main Page (diff), after it got recreated again. It seems like some ways remain for new members to arrive there, increasing likelihood of creating that page.
  • If my attempted fix (i.e. making it a redirect) is reasonable, I suggest to make the page "index.php" protected from editing (so that nobody accidentally changes it into something else).
  • On the other hand, if people decide that it's better to avoid having index.php in the first place, then I suggest to make it protected from creation (so that nobody will accidentally create it again).
GUYTU6J wrote:
May 8th, 2022, 11:47 pm
Last year a new LifeWiki page named "index.php" was created for no clear reason, and was soon deleted (see User talk:JsfasdF248).
...
127:1 B3/S234c User:Confocal/R (isotropic rules, 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.

User avatar
PHPBB12345
Posts: 1096
Joined: August 5th, 2015, 11:55 pm
Contact:

Re: Golly bugs

Post by PHPBB12345 » March 13th, 2023, 12:41 pm

golly().setmag(-2^31) crashes Golly

User avatar
Andrew
Moderator
Posts: 919
Joined: June 2nd, 2009, 2:08 am
Location: Melbourne, Australia
Contact:

Re: Golly bugs

Post by Andrew » March 14th, 2023, 1:57 am

PHPBB12345 wrote:
March 13th, 2023, 12:41 pm
golly().setmag(-2^31) crashes Golly
Thanks for the report. This bug will be fixed in the next release, whenever that is. You won't be able to set a mag value smaller than -2^20 (which is actually a scale of 2^(2^20) cells per pixel, so shouldn't be much of a restriction!).
Use Glu to explore CA rules on non-periodic tilings: DominoLife and HatLife

User avatar
muzik
Posts: 5614
Joined: January 28th, 2016, 2:47 pm
Location: Scotland

Re: Golly bugs

Post by muzik » March 14th, 2023, 3:09 am

Should Golly try to reject incorrectly formatted rulestrings such as the following? It accepts this pattern, but the number prefixed with B isn't used for births and the number with S before it isn't used for survivals.

Code: Select all

x = 4, y = 3, rule = B34/3/S12
A2.A$A2.A$.2A!

User avatar
rowett
Moderator
Posts: 3776
Joined: January 31st, 2013, 2:34 am
Location: UK
Contact:

Re: Golly bugs

Post by rowett » March 14th, 2023, 8:54 am

muzik wrote:
March 14th, 2023, 3:09 am
Should Golly try to reject incorrectly formatted rulestrings such as the following? It accepts this pattern, but the number prefixed with B isn't used for births and the number with S before it isn't used for survivals.

Code: Select all

x = 4, y = 3, rule = B34/3/S12
A2.A$A2.A$.2A!
A fix for this has been committed. Thanks for the report.

User avatar
muzik
Posts: 5614
Joined: January 28th, 2016, 2:47 pm
Location: Scotland

Re: Golly bugs

Post by muzik » March 31st, 2023, 5:14 pm

If we specify a Gaussian rule with a very high range, it's possible to crash Golly with an out of memory error. (The following pattern is in a quote because LifeViewer doesn't like it much either, and even the "pattern validity checking" thing seems to be reacting to it and stopping other boxes on the page from displaying "SHOW IN VIEWER".)
x = 2, y = 2, rule = R500,C2,S,B,NG
2o$2o!
Speaking of LifeViewer: should this pattern throw up an error instead of the +1 just being removed? This was discussed in the LifeViewer thread since LifeViewer rejects it as invalid. Golly rejects many similar invalid bounded grid definitions.

Code: Select all

x = 2, y = 2, rule = B3/S23:K6,5*+1
2o$2o!

User avatar
rowett
Moderator
Posts: 3776
Joined: January 31st, 2013, 2:34 am
Location: UK
Contact:

Re: Golly bugs

Post by rowett » March 31st, 2023, 6:04 pm

muzik wrote:
March 31st, 2023, 5:14 pm
If we specify a Gaussian rule with a very high range, it's possible to crash Golly with an out of memory error.
I've reduced the range in Golly and LifeViewer to 50 for the Gaussian rules. The change for Golly has been committed. LifeViewer is already deployed.

User avatar
muzik
Posts: 5614
Joined: January 28th, 2016, 2:47 pm
Location: Scotland

Re: Golly bugs

Post by muzik » March 31st, 2023, 6:51 pm

The following torus is not handled correctly:

Code: Select all

x = 5, y = 4, rule = B3/S23:T20,20-2147483648
bo2bo$o$o3bo$4o!
It should be converted to T20,20+8 (2147483648 mod 20 = eight), but is not.

Golly also rejects these, but ideally should not: it should just discard the bounded grid part of the rulestring entirely (since 0 in both dimensions means "unbounded in both dimensions", and P0, P0,0, T0 and T0,0 are discarded accordingly).

Code: Select all

x = 2, y = 2, rule = B3/S23:K0
2o$2o!

Code: Select all

x = 2, y = 2, rule = B3/S23:K0*
2o$2o!

Code: Select all

x = 2, y = 2, rule = B3/S23:K0,0
2o$2o!

Code: Select all

x = 2, y = 2, rule = B3/S23:K0,0*
2o$2o!

Code: Select all

x = 2, y = 2, rule = B3/S23:K0*,0
2o$2o!

Code: Select all

x = 2, y = 2, rule = B3/S23:C0
2o$2o!

Code: Select all

x = 2, y = 2, rule = B3/S23:C0,0
2o$2o!

Code: Select all

x = 2, y = 2, rule = B3/S23:S0
2o$2o!

User avatar
confocaloid
Posts: 2729
Joined: February 8th, 2022, 3:15 pm

Re: Golly bugs

Post by confocaloid » September 29th, 2023, 9:36 am

Added 2024-03-17: I tested the same steps in Golly 4.3b1, and this seems to be fixed now. (Others are welcome to test as well)

It seems like underscores in filenames can trigger bugs.
Steps to reproduce:
* Run Golly 4.2.
* (Optionally) Draw some pattern in the pattern area.
* Save the pattern under the filename "a__b.rle" (without quotes). (Note the double underscore.)
* Close Golly, and run again.
* The list "File -> Open Recent" has an item "a_b.rle" (note the single underscore). Clicking it displays "The file does not exist..." message.
* Further, open the saved file "a__b.rle" manually via the "File -> Open Pattern" dialog. It opens.
* Now, the list "File -> Open Recent" has two items, "a__b.rle" and "a_b.rle". Neither of these two items works (both display "The file does not exist..." message).
Last edited by confocaloid on March 17th, 2024, 12:28 pm, edited 1 time in total.
127:1 B3/S234c User:Confocal/R (isotropic rules, 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.

User avatar
rowett
Moderator
Posts: 3776
Joined: January 31st, 2013, 2:34 am
Location: UK
Contact:

Re: Golly bugs

Post by rowett » September 29th, 2023, 12:31 pm

confocaloid wrote:
September 29th, 2023, 9:36 am
It seems like underscores in filenames can trigger bugs.
Steps to reproduce:
* Run Golly 4.2.
* (Optionally) Draw some pattern in the pattern area.
* Save the pattern under the filename "a__b.rle" (without quotes). (Note the double underscore.)
* Close Golly, and run again.
* The list "File -> Open Recent" has an item "a_b.rle" (note the single underscore). Clicking it displays "The file does not exist..." message.
* Further, open the saved file "a__b.rle" manually via the "File -> Open Pattern" dialog. It opens.
* Now, the list "File -> Open Recent" has two items, "a__b.rle" and "a_b.rle". Neither of these two items works (both display "The file does not exist..." message).
I can reproduce it on Linux. It works fine on Windows.

Looking at the source there is some Linux specific code that's replacing double underscores with a single underscore to workaround some wxGTK bug. I don't know the history so Andrew will need to chime in.

User avatar
haaaaaands
Posts: 573
Joined: September 7th, 2023, 7:22 am
Location: on the deck of a lwss inside a b3s23 bottle
Contact:

Re: Golly bugs

Post by haaaaaands » September 29th, 2023, 1:03 pm

web version puts another cell when i put one and doesn't let me have more than 4 cells per pattern
-- haaaaaands with 6 a's



my hands are typing words!

currently offline. work sucks.

User avatar
b3s23love
Posts: 96
Joined: May 24th, 2023, 6:30 am
Location: The (Life?) Universe

Re: Golly bugs

Post by b3s23love » October 1st, 2023, 4:21 pm

(is it a bug or it has to do with HashLife?)
Steps to reproduce this bug (along with a description):
1. Run this pattern up to the moment when the loaves appear.

Code: Select all

x = 112, y = 89, rule = LifeSuper
3S18.8Q20.12Q4.5Q2.Q15.2M15.Q$2.S19.Q4.Q22.Q3.2Q8.2Q.Q.4Q.Q13.2M8.2Q
5.Q$.S42.2M4.Q4.2Q9.4Q8.2M17.Q2.Q4.Q$5.S.S37.M4.2Q25.2M19.2Q8.2Q$S3.S
40.M.M2.Q28.M5.2M21.Q.Q$S.2S.2S39.2M2.2Q33.2M22.Q$2.2S3.S9.2S31.Q14.
2M$.S.S13.S.S20.3O11.2M9.2M21.2M8.M$S4.S.S10.S.S10.2Q6.3O11.M.M32.2M
6.3M4.2M$3.4S12.2S10.2Q13.pA6.2M7.M32.M7.2M$S3.S2.S37.pA.pA13.2M32.2M
$2S.S.S.S38.pA14.M.M26.2M$24.2M17.pA5.pA27.2M12.M8.2M7.3M$S.S.3S17.2M
6.O9.pA.pA3.pA.pA18.Q6.M.3M8.M10.2M6.M.M$S.S29.2O9.pA5.pA5.2pA11.Q.Q
4.M5.M7.2M17.M$3S3.S25.2O6.pA5.pA8.pA.pA11.2Q5.3M.M22.M2.M.M.2M$3.S3.
S25.O5.pA.pA3.pA.pA8.2pA5.2Q13.2M23.2M3.2M.M$S.S.S.2S32.pA5.pA15.Q2.Q
41.M.M.M$25.M11.pA5.pA9.pA5.pA3.2Q44.2M$23.2M.2M8.pA.pA3.pA.pA7.pA.pA
3.pA.pA20.2M26.M$9.2S26.pA5.pA3.2pA4.pA5.pA20.M2.M$9.S4.2S6.M5.M11.pA
6.pA.pA6.pA21.3M.M6.3M$11.S2.S.S16.2pA4.pA.pA7.pA5.pA.pA3.2pA14.M4.2M
16.2M$.2S3.S3.2S4.S5.2M.M.2M4.2pA5.pA8.2pA5.pA4.pA.pA13.M.2M2.M15.M$S
2.S.S10.2S19.pA24.2pA10.2M.M.M.2M19.M$2S2.3S29.pA.pA4.2Q29.M.M15.2M6.
2M$S3.2S25.2pA4.pA5.2Q30.M16.M$6.S6.2O.2O12.pA.pA23.2M22.2M8.M.M$3S.
3S6.2O.O.O11.2pA24.M23.2M8.2M$S4.S12.O29.M5.M.M13.2pA$4S.S12.2O27.M.M
4.2M14.pA.pA13.2S$S2.2S9.2O6.2M5.pA5.2M9.M3.2M19.2pA4.2M6.S.S$3S11.2O
7.M4.pA.pA4.2M9.M3.2M15.pA9.2M6.2S$S2.S16.3M6.pA16.M3.2M7.pA6.pA.pA
13.S$2S.S2.S13.M5.pA5.pA14.M.M8.pA.pA6.pA6.S6.S.S23.Q.Q$.3S21.pA.pA3.
pA.pA14.M10.pA13.S.S4.S.S12.2M11.4Q$3.2S.S19.pA5.pA.pA27.pA10.S.S3.S.
S13.2M9.Q.2Q$29.pA3.pA6.pA20.pA.pA10.S5.S6.M18.Q4.Q$28.pA.pA8.pA.pA
10.2S8.pA8.S5.S7.3M18.3Q.2Q$29.pA10.pA5.2S5.S5.pA10.S.S3.S.S5.M7.2M
13.3Q.Q$35.2pA6.S3.S2.3S5.pA.pA10.S5.S6.2M6.2M12.Q3.2Q$7.O15.2W10.2pA
6.4S3.S8.pA.pA6.S5.S33.Q.Q$6.O.O14.2W31.O3.pA.pA4.S.S3.S.S12.Q17.Q2.Q
.Q$6.O.3O22.W11.2S8.O.O3.pA6.S5.S13.Q18.Q.Q$7.O3.O14.2W4.W.W5.2pA2.S
2.S8.O8.S5.S16.Q$8.O.O8.2W5.W.W4.2W4.pA.pA3.2S17.S.S3.S.S20.Q$6.O.O.
2O7.2W7.W10.2pA24.S5.S21.Q$6.2O19.W.2W17.2S.S10.S5.S24.Q$22.2W4.W2.W
4.2U10.S.2S9.S.S3.S.S$12.2W3.W4.W.W4.2W4.U.U24.S5.S12.3M$12.2W2.W.W5.
W10.2U5.2U15.S5.S14.M3.M$16.W.W4.W.2W16.U4.2U8.S.S3.S.S5.pA6.M5.M$15.
2W.2W4.W2.W5.U6.3U3.3U.U8.S5.S5.pA.pA6.M3.M$13.W2.W3.W4.2W5.U.U5.U4.U
5.U4.S5.S9.pA8.3M15.2Q$2.W.W.W2.W2.W3.W3.W12.U11.U2.3U4.S.S3.S.S5.pA
5.pA5.3M14.Q2.Q$3.2W4.W.W5.2W.W.2W6.U5.2U4.2U.U.U8.S5.S5.pA.pA3.pA.pA
22.Q.Q$4W2.W.2W2.W.W4.W.W.W5.U.U3.U2.U3.U2.U.2U4.S5.S9.pA5.pA16.2M6.Q
$7.2W3.3W4.W.W8.U5.2U5.2U7.S.S3.S.S11.pA5.pA5.2M6.2M$2W.W2.W2.2W2.W.
2W3.2W5.U5.U19.S5.S5.2S4.pA.pA3.pA.pA4.M$.2W.W4.2W3.2W10.U.U3.U.U21.S
7.S.S5.pA5.pA6.3M$.2W.W.2W2.W2.W2.W10.U5.U12.O8.S.S6.S.S.2S5.pA5.pA5.
M7.2M$W12.W2.W.W4.2U5.U14.O.O8.S8.2S.S5.pA.pA3.pA.pA12.2M9.Q2.Q.Q$2W
2.W.3W.W2.W8.U2.U3.U.U14.O5.S7.2S7.S5.pA5.pA25.Q.Q.Q$W2.W.2W4.W2.W3.W
3.U.U.U3.U3.2U4.O2.O7.S.S6.S2.5S.S8.pA5.pA7.2M14.Q$3W2.W5.2W.2W.3W3.U
2.U7.U5.4O8.S8.2S.S2.S.2S6.pA.pA3.pA.pA6.2M17.Q$W4.3W2.2W14.2U7.3U11.
S5.S22.pA5.pA24.Q$2W4.W.W3.2W16.U6.U2.2O6.S.S3.S.S24.pA25.2Q2.Q$.2W.W
2.2W3.2W3.4M8.U.U9.O7.S5.S24.pA.pA23.3Q.2Q$2W2.W2.W2.W2.W.2M4.2M7.U8.
O6.S5.S15.Q12.pA24.2Q3.Q$3W4.W4.2W.2M5.M4.U7.2O2.2O4.S.S3.S.S13.Q.Q
14.pA22.2Q.2Q$2W9.3W3.2M.M.M3.U.U4.3O.O.O6.S5.S9.2U3.2Q14.pA.pA21.Q$.
W3.3W5.W8.M4.U4.O4.O.O3.S5.S12.U8.2M11.pA21.3Q2.Q$4.W13.M3.M8.O.4O.O
3.S.S3.S.S9.U.U9.M34.Q.Q.Q$18.M4.M7.O4.O6.S5.S9.U.U32.2M3.2M2.2M2.Q$
20.3M3.M3.2O.2O.O9.S12.2U9.M23.2M2.M2.M2.M$20.2M4.M5.O2.O9.S.S3.2U.2U
.2U5.2M3.M3.2M23.M.2M.M$26.2M4.O.O11.S4.4U3.U6.M2.M4.M17.M7.M3.2M$28.
M4.O3.2S15.U3.U.U2.U5.M5.M2.M11.M.M.2M.M.M.2M6.M$28.3M6.S2.S9.U.U.3U
3.U9.2M2.5M11.M.M.M.2M.2M.M6.2M$34.M3.3S7.U7.U.U3.4U25.M15.M.M.M$32.M
8.2S5.U.U.U3.2U3.U.2U2.M8.3M3.M25.2M.M$28.M4.4M3.S2.S7.U2.U.U.U4.3U2.
M2.2M3.M2.M.M.M22.M.M.2M$30.M.M7.S.S7.4U3.U5.2U2.M2.4M4.2M.2M11.M13.M
$30.2M5.M3.S6.U2.U.U2.2U.3U5.M3.3M16.M.5M3.2M5.2Q.Q$29.2M3.M.2M15.2U.
U.U.U2.U2.UM2.M.2M.M16.2M.2M4.M4.Q.2Q.Q$28.M3.M4.M.M8.2U.2U4.U4.U2.2U
M13.M11.2M2.2M11.Q$30.M2.M17.U2.U4.U.2U.U4.3M2.M4.5M4.2M2.2M.M14.Q$
34.M.2M13.5U.U.4U5.2M.4M.6M6.M3.2M.6M2.2M$34.4M10.2U3.2U.4U.3U2.2M.M.
2M3.M2.2M2.M5.M2.M3.5Q2.2M!
2. Add one cell to the interior of the diehard.
3. Observe that the population changed by more than 1 cell.
4. Zoom out the pattern.
5. Zoom in to the big diagonal line that was just created by the 1-cell difference.
6. Observe that the patterns that are positioned in the diagonal are just pieces of the engineered diehard (hashtile?).
Very strange and annoying. I don't think it's fixable, though. Would someone like to explain why this does exist?

User avatar
rowett
Moderator
Posts: 3776
Joined: January 31st, 2013, 2:34 am
Location: UK
Contact:

Re: Golly bugs

Post by rowett » October 1st, 2023, 4:59 pm

b3s23love wrote:
October 1st, 2023, 4:21 pm
(is it a bug or it has to do with HashLife?)
Steps to reproduce this bug (along with a description):
1. Run this pattern up to the moment when the loaves appear.
What generation does this happen?
b3s23love wrote:
October 1st, 2023, 4:21 pm
2. Add one cell to the interior of the diehard.
Please give the XY location of this new cell.

User avatar
b3s23love
Posts: 96
Joined: May 24th, 2023, 6:30 am
Location: The (Life?) Universe

Re: Golly bugs

Post by b3s23love » October 1st, 2023, 5:09 pm

rowett wrote:
October 1st, 2023, 4:59 pm
What generation does this happen?
Every sufficiently large one. I tested this at the moment when the first loaf fuse starts, although it can happen at generations as low as 100 billion. I recommend much larger ones, like 10^15, though.
rowett wrote:
October 1st, 2023, 4:59 pm
Please give the XY location of this new cell.
Click the F button that fits the whole pattern. You should see a long diagonal line perpendicular to the crabstretcher one. Now zoom to this line, then to one of the dots when these appear. You should see the new cells (segments? I think it has to do with HashLife). It also impacts the population count. There's no definite XY location.

User avatar
confocaloid
Posts: 2729
Joined: February 8th, 2022, 3:15 pm

Re: Golly bugs

Post by confocaloid » October 1st, 2023, 5:34 pm

Added 2024-03-17: I tested the same steps for the same pattern in Golly 4.3b1, and this seems to be fixed now. (Others are welcome to test as well)

I got the following steps, when trying to reproduce this:

* Turn "View -> Show Exact Numbers" on.
* Open the pattern via "Open Clipboard". The top-left cell should get coordinates (0,0).
* Use goto.lua to go to the generation 1000000000000000 (10^15).
* The displayed population is 1,042,324,103,587,982.
* Add a single state-1 cell at X = 56, Y = 43 (inside the tub).
* Now the displayed population is 1,042,324,158,506,313. (Addition of one cell changed the population by more than 1.)
* Press F to zoom out. Instead of the expected single diagonal line, there are two intersecting diagonal lines.
b3s23love wrote:
October 1st, 2023, 4:21 pm
(is it a bug or it has to do with HashLife?)
Steps to reproduce this bug (along with a description):
1. Run this pattern up to the moment when the loaves appear.

Code: Select all

x = 112, y = 89, rule = LifeSuper
3S18.8Q20.12Q4.5Q2.Q15.2M15.Q$2.S19.Q4.Q22.Q3.2Q8.2Q.Q.4Q.Q13.2M8.2Q
5.Q$.S42.2M4.Q4.2Q9.4Q8.2M17.Q2.Q4.Q$5.S.S37.M4.2Q25.2M19.2Q8.2Q$S3.S
40.M.M2.Q28.M5.2M21.Q.Q$S.2S.2S39.2M2.2Q33.2M22.Q$2.2S3.S9.2S31.Q14.
2M$.S.S13.S.S20.3O11.2M9.2M21.2M8.M$S4.S.S10.S.S10.2Q6.3O11.M.M32.2M
6.3M4.2M$3.4S12.2S10.2Q13.pA6.2M7.M32.M7.2M$S3.S2.S37.pA.pA13.2M32.2M
$2S.S.S.S38.pA14.M.M26.2M$24.2M17.pA5.pA27.2M12.M8.2M7.3M$S.S.3S17.2M
6.O9.pA.pA3.pA.pA18.Q6.M.3M8.M10.2M6.M.M$S.S29.2O9.pA5.pA5.2pA11.Q.Q
4.M5.M7.2M17.M$3S3.S25.2O6.pA5.pA8.pA.pA11.2Q5.3M.M22.M2.M.M.2M$3.S3.
S25.O5.pA.pA3.pA.pA8.2pA5.2Q13.2M23.2M3.2M.M$S.S.S.2S32.pA5.pA15.Q2.Q
41.M.M.M$25.M11.pA5.pA9.pA5.pA3.2Q44.2M$23.2M.2M8.pA.pA3.pA.pA7.pA.pA
3.pA.pA20.2M26.M$9.2S26.pA5.pA3.2pA4.pA5.pA20.M2.M$9.S4.2S6.M5.M11.pA
6.pA.pA6.pA21.3M.M6.3M$11.S2.S.S16.2pA4.pA.pA7.pA5.pA.pA3.2pA14.M4.2M
16.2M$.2S3.S3.2S4.S5.2M.M.2M4.2pA5.pA8.2pA5.pA4.pA.pA13.M.2M2.M15.M$S
2.S.S10.2S19.pA24.2pA10.2M.M.M.2M19.M$2S2.3S29.pA.pA4.2Q29.M.M15.2M6.
2M$S3.2S25.2pA4.pA5.2Q30.M16.M$6.S6.2O.2O12.pA.pA23.2M22.2M8.M.M$3S.
3S6.2O.O.O11.2pA24.M23.2M8.2M$S4.S12.O29.M5.M.M13.2pA$4S.S12.2O27.M.M
4.2M14.pA.pA13.2S$S2.2S9.2O6.2M5.pA5.2M9.M3.2M19.2pA4.2M6.S.S$3S11.2O
7.M4.pA.pA4.2M9.M3.2M15.pA9.2M6.2S$S2.S16.3M6.pA16.M3.2M7.pA6.pA.pA
13.S$2S.S2.S13.M5.pA5.pA14.M.M8.pA.pA6.pA6.S6.S.S23.Q.Q$.3S21.pA.pA3.
pA.pA14.M10.pA13.S.S4.S.S12.2M11.4Q$3.2S.S19.pA5.pA.pA27.pA10.S.S3.S.
S13.2M9.Q.2Q$29.pA3.pA6.pA20.pA.pA10.S5.S6.M18.Q4.Q$28.pA.pA8.pA.pA
10.2S8.pA8.S5.S7.3M18.3Q.2Q$29.pA10.pA5.2S5.S5.pA10.S.S3.S.S5.M7.2M
13.3Q.Q$35.2pA6.S3.S2.3S5.pA.pA10.S5.S6.2M6.2M12.Q3.2Q$7.O15.2W10.2pA
6.4S3.S8.pA.pA6.S5.S33.Q.Q$6.O.O14.2W31.O3.pA.pA4.S.S3.S.S12.Q17.Q2.Q
.Q$6.O.3O22.W11.2S8.O.O3.pA6.S5.S13.Q18.Q.Q$7.O3.O14.2W4.W.W5.2pA2.S
2.S8.O8.S5.S16.Q$8.O.O8.2W5.W.W4.2W4.pA.pA3.2S17.S.S3.S.S20.Q$6.O.O.
2O7.2W7.W10.2pA24.S5.S21.Q$6.2O19.W.2W17.2S.S10.S5.S24.Q$22.2W4.W2.W
4.2U10.S.2S9.S.S3.S.S$12.2W3.W4.W.W4.2W4.U.U24.S5.S12.3M$12.2W2.W.W5.
W10.2U5.2U15.S5.S14.M3.M$16.W.W4.W.2W16.U4.2U8.S.S3.S.S5.pA6.M5.M$15.
2W.2W4.W2.W5.U6.3U3.3U.U8.S5.S5.pA.pA6.M3.M$13.W2.W3.W4.2W5.U.U5.U4.U
5.U4.S5.S9.pA8.3M15.2Q$2.W.W.W2.W2.W3.W3.W12.U11.U2.3U4.S.S3.S.S5.pA
5.pA5.3M14.Q2.Q$3.2W4.W.W5.2W.W.2W6.U5.2U4.2U.U.U8.S5.S5.pA.pA3.pA.pA
22.Q.Q$4W2.W.2W2.W.W4.W.W.W5.U.U3.U2.U3.U2.U.2U4.S5.S9.pA5.pA16.2M6.Q
$7.2W3.3W4.W.W8.U5.2U5.2U7.S.S3.S.S11.pA5.pA5.2M6.2M$2W.W2.W2.2W2.W.
2W3.2W5.U5.U19.S5.S5.2S4.pA.pA3.pA.pA4.M$.2W.W4.2W3.2W10.U.U3.U.U21.S
7.S.S5.pA5.pA6.3M$.2W.W.2W2.W2.W2.W10.U5.U12.O8.S.S6.S.S.2S5.pA5.pA5.
M7.2M$W12.W2.W.W4.2U5.U14.O.O8.S8.2S.S5.pA.pA3.pA.pA12.2M9.Q2.Q.Q$2W
2.W.3W.W2.W8.U2.U3.U.U14.O5.S7.2S7.S5.pA5.pA25.Q.Q.Q$W2.W.2W4.W2.W3.W
3.U.U.U3.U3.2U4.O2.O7.S.S6.S2.5S.S8.pA5.pA7.2M14.Q$3W2.W5.2W.2W.3W3.U
2.U7.U5.4O8.S8.2S.S2.S.2S6.pA.pA3.pA.pA6.2M17.Q$W4.3W2.2W14.2U7.3U11.
S5.S22.pA5.pA24.Q$2W4.W.W3.2W16.U6.U2.2O6.S.S3.S.S24.pA25.2Q2.Q$.2W.W
2.2W3.2W3.4M8.U.U9.O7.S5.S24.pA.pA23.3Q.2Q$2W2.W2.W2.W2.W.2M4.2M7.U8.
O6.S5.S15.Q12.pA24.2Q3.Q$3W4.W4.2W.2M5.M4.U7.2O2.2O4.S.S3.S.S13.Q.Q
14.pA22.2Q.2Q$2W9.3W3.2M.M.M3.U.U4.3O.O.O6.S5.S9.2U3.2Q14.pA.pA21.Q$.
W3.3W5.W8.M4.U4.O4.O.O3.S5.S12.U8.2M11.pA21.3Q2.Q$4.W13.M3.M8.O.4O.O
3.S.S3.S.S9.U.U9.M34.Q.Q.Q$18.M4.M7.O4.O6.S5.S9.U.U32.2M3.2M2.2M2.Q$
20.3M3.M3.2O.2O.O9.S12.2U9.M23.2M2.M2.M2.M$20.2M4.M5.O2.O9.S.S3.2U.2U
.2U5.2M3.M3.2M23.M.2M.M$26.2M4.O.O11.S4.4U3.U6.M2.M4.M17.M7.M3.2M$28.
M4.O3.2S15.U3.U.U2.U5.M5.M2.M11.M.M.2M.M.M.2M6.M$28.3M6.S2.S9.U.U.3U
3.U9.2M2.5M11.M.M.M.2M.2M.M6.2M$34.M3.3S7.U7.U.U3.4U25.M15.M.M.M$32.M
8.2S5.U.U.U3.2U3.U.2U2.M8.3M3.M25.2M.M$28.M4.4M3.S2.S7.U2.U.U.U4.3U2.
M2.2M3.M2.M.M.M22.M.M.2M$30.M.M7.S.S7.4U3.U5.2U2.M2.4M4.2M.2M11.M13.M
$30.2M5.M3.S6.U2.U.U2.2U.3U5.M3.3M16.M.5M3.2M5.2Q.Q$29.2M3.M.2M15.2U.
U.U.U2.U2.UM2.M.2M.M16.2M.2M4.M4.Q.2Q.Q$28.M3.M4.M.M8.2U.2U4.U4.U2.2U
M13.M11.2M2.2M11.Q$30.M2.M17.U2.U4.U.2U.U4.3M2.M4.5M4.2M2.2M.M14.Q$
34.M.2M13.5U.U.4U5.2M.4M.6M6.M3.2M.6M2.2M$34.4M10.2U3.2U.4U.3U2.2M.M.
2M3.M2.2M2.M5.M2.M3.5Q2.2M!
2. Add one cell to the interior of the diehard.
3. Observe that the population changed by more than 1 cell.
4. Zoom out the pattern.
5. Zoom in to the big diagonal line that was just created by the 1-cell difference.
6. Observe that the patterns that are positioned in the diagonal are just pieces of the engineered diehard (hashtile?).
Very strange and annoying. I don't think it's fixable, though. Would someone like to explain why this does exist?
Last edited by confocaloid on March 17th, 2024, 12:24 pm, edited 1 time in total.
127:1 B3/S234c User:Confocal/R (isotropic rules, 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.

User avatar
b3s23love
Posts: 96
Joined: May 24th, 2023, 6:30 am
Location: The (Life?) Universe

Re: Golly bugs

Post by b3s23love » October 1st, 2023, 5:37 pm

confocaloid wrote:
October 1st, 2023, 5:34 pm
I got the following steps, when trying to reproduce this:

* Turn "View -> Show Exact Numbers" on.
* Open the pattern via "Open Clipboard". The top-left cell should get coordinates (0,0).
* Use goto.lua to go to the generation 1000000000000000 (10^15).
* The displayed population is 1,042,324,103,587,982.
* Add a single state-1 cell at X = 56, Y = 43 (inside the tub).
* Now the displayed population is 1,042,324,158,506,313. (Addition of one cell changed the population by more than 1.)
* Press F to zoom out. Instead of the expected single diagonal line, there are two intersecting diagonal lines.
That was exactly what I did mean. Also, would you like to zoom in to the line perpendicular to the expected line, and then see the contents of one of the dots that will appear when nearing 1:1 scale? If you'll zoom in there, then please share here the contents of one dot.

User avatar
confocaloid
Posts: 2729
Joined: February 8th, 2022, 3:15 pm

Re: Golly bugs

Post by confocaloid » October 1st, 2023, 5:47 pm

b3s23love wrote:
October 1st, 2023, 5:37 pm
If you'll zoom in there, then please share here the contents of one dot.
I cannot copy the contents of the dot due to the known "Selection is outside +/- 10^9 boundary." limitation, but here is how it looks like:
the first "dot" is selected
the first "dot" is selected
dot0.png (1.68 KiB) Viewed 4328 times
the contents of the first "dot" from the selection
the contents of the first "dot" from the selection
dot1.png (3.18 KiB) Viewed 4328 times
127:1 B3/S234c User:Confocal/R (isotropic rules, 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.

User avatar
b3s23love
Posts: 96
Joined: May 24th, 2023, 6:30 am
Location: The (Life?) Universe

Re: Golly bugs

Post by b3s23love » October 1st, 2023, 5:49 pm

confocaloid wrote:
October 1st, 2023, 5:47 pm
b3s23love wrote:
October 1st, 2023, 5:37 pm
If you'll zoom in there, then please share here the contents of one dot.
I cannot copy the contents of the dot due to the known "Selection is outside +/- 10^9 boundary." limitation, but here is how it looks like:
dot0.png
dot1.png
Would you like to repeat this with 10^30?

Post Reply