Pattern viewer for forum threads

[muzik]

An old issue: the grid edge kills the same pattern in the same rule run in two different algorithms differently. The first gets far closer to the edge before being deleted fully in generation 123, while the latter is deleted at a farther distance in generation 119.

Code: Select all

#CXRLE Pos=-600,-600
x = 5, y = 4, rule = B3/S23
bo$o$o3bo$4o!
[[ MAXGRIDSIZE 9 THEME Red STARTFROM 115 ZOOM 8 X -240 Y -192 GPS 2 SHOWGENSTATS ]]

Code: Select all

#CXRLE Pos=-600,-600
x = 5, y = 4, rule = R1,C2,S2-3,B3
bo$o$o3bo$4o!
[[ MAXGRIDSIZE 9 THEME Red STARTFROM 115 ZOOM 8 X -240 Y -192 GPS 2 SHOWGENSTATS ]]

Notably, this example highlights a second bug: while all cells are killed off in generation 119, the viewer does not register this as everything dying (even though it accepts that there are 0 cells alive), and the message is displayed during the next generation instead, with the births and deaths counter ticking to 0. It also may be worth pointing out that the second example creates some dead history cells that were never alive in the first place; the first does not do this.

----

Is there any reason why Rainbow is forbidden for rulespaces such as general 2-state outer-totalistic rules and Margolus? To my knowledge, they're two-state, so they should be able to support the effect.

[rowett]

An old issue: the grid edge kills the same pattern in the same rule run in two different algorithms differently.

It's because they are different algorithms.

Is there any reason why Rainbow is forbidden for rulespaces such as general 2-state outer-totalistic rules and Margolus?

Yes they use different renderers.

[rowett]

Theme suggestion: a "Night" theme which uses a color palette comprised of reds and yellows for an overall warmer color temperature

I'm not planning on adding more Themes.

Could the zoom bar be made to display another digit after the decimal point instead of just one? It's possible to set the zoom to a value which is displayed as "4.0", but disallows things like the grid, cell borders, non-rectangular cell shapes and others from rendering due to being slightly further out, so this would probably solve that alongside showing the current zoom level slightly more precisely.

No because that doesn't solve the problem. It could still display 4.00 and be slightly below 4x Zoom.

Use Settings->Display->Integer Zoom to set the zoom to the nearest integer (hotkey Shift 1), or just press hokey 4 to go directly to 4x zoom if you have a keyboard.

[rowett]

Cells in pasted/advanced selections, which appear yellow for some reason

This can now be set with [[ COLOR SELECTED R G B|name ]]

[muzik]

An old issue: the grid edge kills the same pattern in the same rule run in two different algorithms differently.

It's because they are different algorithms.

Shouldn't the latter case still display a death message on generation 119 rather than 120?

[muzik]

The triangular grid does not appear to be correctly aligned with the actual rectangular cells:

Code: Select all

x = 12, y = 8, rule = B3/S23L
b!
[[ GRID THEME Life32 ZOOM 24
COLOR ARROW 0 255 0
ARROW 5 -10 5 15 24
LABEL 9 0 24 "Use Rectangles"
COLOR ARROW 0 0 255
ARROW -5.26 -10 -5.26 15 24
LABEL -3 0 24 "Triangles" ]]

The green line should pass through the triangular grid's vertices, and the blue line should not, like what is seen with the rectangular version of the triangular grid in which the green line passes through the midpoints of each rectangle and the blue line not doing so.

[rowett]

Shouldn't the latter case still display a death message on generation 119 rather than 120?

Yes, fixed.

[muzik]

In this example (bounded grid is northwest), the selection rectangle appears to be one cell upwards of where it actually is.

Code: Select all

#CXRLE Pos=192,192
x = 5, y = 4, rule = B3/S23:T192,192
24o!
[[ MAXGRIDSIZE 9 ZOOM 4 X 200 Y 200 ]]

Likely unwanted behaviour: Identify used on a spaceship which is alternated with a "do nothing" rule sometimes reports it as a still life in the general-range outer-totalistic rulespace (classic range-1 OT works fine):

Code: Select all

x = 12, y = 14, rule = B3457/S4568
4bo2bo$4b4o$2b8o$2b2ob2ob2o$obobo2bobobo$2ob6ob2o$ob3o2b3obo$3ob4ob3o$
2ob6ob2o$b3o4b3o$b3o4b3o$3b2o2b2o$3bo4bo$5b2o!

Code: Select all

x = 12, y = 14, rule = B3457/S4568|B/S012345678
4bo2bo$4b4o$2b8o$2b2ob2ob2o$obobo2bobobo$2ob6ob2o$ob3o2b3obo$3ob4ob3o$
2ob6ob2o$b3o4b3o$b3o4b3o$3b2o2b2o$3bo4bo$5b2o!

Code: Select all

x = 12, y = 14, rule = R1,C2,S4-6,8,B3-5,7
4bo2bo$4b4o$2b8o$2b2ob2ob2o$obobo2bobobo$2ob6ob2o$ob3o2b3obo$3ob4ob3o$
2ob6ob2o$b3o4b3o$b3o4b3o$3b2o2b2o$3bo4bo$5b2o!

Code: Select all

x = 12, y = 14, rule = R1,C2,S4-6,8,B3-5,7|R1,C2,S0-8,B
4bo2bo$4b4o$2b8o$2b2ob2ob2o$obobo2bobobo$2ob6ob2o$ob3o2b3obo$3ob4ob3o$
2ob6ob2o$b3o4b3o$b3o4b3o$3b2o2b2o$3bo4bo$5b2o!

It doesn't always occur, though. I've had more luck reproducing it with a 4c/273954 solid ship and can provide that instead if you can't reproduce this with the above examples.

----

For embedded viewers, would it make sense for the "shrink viewer" button at the bottom right of Settings to be present, but grayed out, like how other buttons behave?

[muzik]

Identifying this pattern, which stops it at generation 4, gives a different result from autostart/stop and startfrom:

Code: Select all

x = 29, y = 9, rule = 23/3/3
21.2A4.2A$18.3A6.2A$15.3A$13.2A$A10.2A$A8.2A$A6.2A$.A3.2A$.4A!

Code: Select all

x = 29, y = 9, rule = 23/3/3
21.2A4.2A$18.3A6.2A$15.3A$13.2A$A10.2A$A8.2A$A6.2A$.A3.2A$.4A!
[[ STARTFROM 4 ]]

Code: Select all

x = 29, y = 9, rule = 23/3/3
21.2A4.2A$18.3A6.2A$15.3A$13.2A$A10.2A$A8.2A$A6.2A$.A3.2A$.4A!
[[ AUTOSTART STOP 4 ]]

If the none rule's colors are overwritten, those colors are not actually shown in Help --> Info --> [Theme/Colours]:

Code: Select all

x = 4, y = 6, rule = none
2bo$2obo$3bo$bobo$o$b3o!
[[ COLOR 0 0 0 0 COLOR 1 255 255 255 ]]

Code: Select all

x = 4, y = 6, rule = Life-RuleLoader
2bo$2obo$3bo$bobo$o$b3o!
[[ COLOR 0 0 0 0 COLOR 1 255 255 255 ]]

Mousing over the region outside of the boundary of a non-bounded grid still displays "dead", rather than the "[boundary]" which is seen for bounded grids, an inconsistency which should probably be resolved:

Code: Select all

#CXRLE Pos=192,192
x = 5, y = 4, rule = B3/S23
24o!
[[ MAXGRIDSIZE 9 ZOOM 4 X 200 Y 200 ]]

Code: Select all

x = 5, y = 4, rule = B3/S23:T60,60
24o!
[[ ZOOM 4 ]]

[rowett]

Identifying this pattern, which stops it at generation 4, gives a different result from autostart/stop and startfrom:

What's the difference?

[rowett]

Identify used on a spaceship which is alternated with a "do nothing" rule sometimes reports it as a still life in the general-range outer-totalistic rulespace (classic range-1 OT works fine)

I can't reproduce this.

[muzik]

Identifying this pattern, which stops it at generation 4, gives a different result from autostart/stop and startfrom:

What's the difference?

A dying cell is absent to the left of the block.

[muzik]

Identify used on a spaceship which is alternated with a "do nothing" rule sometimes reports it as a still life in the general-range outer-totalistic rulespace (classic range-1 OT works fine)

I can't reproduce this.

Code: Select all

x = 100, y = 100, rule = R45,C2,S2884-4922,B2500-4973
40b20o$36b9o10b9o$34b7o5b8o5b7o$32b6o6b12o6b6o$30b6o6b16o6b6o$28b6o5b
22o5b6o$27b5o5b26o5b5o$25b6o3b32o3b6o$24b5o4b34o4b5o$22b6o3b38o3b6o$
21b6o2b42o2b6o$20b6o2b44o2b6o$19b6o2b46o2b6o$18b6ob50ob6o$16b7ob52ob7o
$15b7ob54ob7o$15b6ob56ob6o$14b6ob58ob6o$13b6ob60ob6o$12b6ob62ob6o$11b
6ob64ob6o$10b6ob66ob6o$9b6ob68ob6o$9b82o$8b84o$7b5ob74ob5o$7b4ob76ob4o
$6b4ob78ob4o$5b90o$5b43o4b43o$4b4ob34o14b34ob4o$4b37o18b37o$3b37o20b
37o$3b3ob32o22b32ob3o$3b34o26b34o$2b4ob29o28b29ob4o$2b33o30b33o$2b32o
32b32o$b33o32b33o$b32o34b32o$b31o36b31o$b31o36b31o$31o38b31o$31o38b31o
$31o38b31o$30o40b30o$30o40b30o$30o40b30o$30o40b30o$31o38b31o$31o38b31o
$31o38b31o$31o38b31o$3ob27o38b27ob3o$3ob28o36b28ob3o$b3ob27o36b27ob3o$
b3ob27o36b27ob3o$b2o3b27o34b27o3b2o$b3o2b28o32b28o2b3o$b3o3b27o32b27o
3b3o$2b2o3b28o30b28o3b2o$2b3o2b29o28b29o2b3o$2b3o3b29o26b29o3b3o$3b3o
2b30o24b30o2b3o$3b3o3b30o22b30o3b3o$4b3o2b32o18b32o2b3o$4b3o3b32o16b
32o3b3o$5b3o2b34o12b34o2b3o$5b3o3b78o3b3o$6b3o3b76o3b3o$6b4o2b76o2b4o$
7b4o2b74o2b4o$7b4o3b72o3b4o$8b4o2b72o2b4o$9b4o2b70o2b4o$9b5o2b68o2b5o$
10b5o2b66o2b5o$11b6ob64ob6o$12b6ob62ob6o$13b6ob60ob6o$13b7ob58ob7o$14b
7ob56ob7o$15b7ob54ob7o$16b7ob52ob7o$17b7ob50ob7o$18b7ob48ob7o$19b7ob
46ob7o$20b8ob42ob8o$22b7ob40ob7o$23b8ob36ob8o$24b8o2b32o2b8o$26b8o2b
28o2b8o$27b9o2b24o2b9o$29b10o2b18o2b10o$31b10o2b14o2b10o$33b34o$35b30o
$38b24o$41b18o$48b4o!

Code: Select all

x = 100, y = 100, rule = R45,C2,S2884-4922,B2500-4973|R45,C2,S0-8280,B
40b20o$36b9o10b9o$34b7o5b8o5b7o$32b6o6b12o6b6o$30b6o6b16o6b6o$28b6o5b
22o5b6o$27b5o5b26o5b5o$25b6o3b32o3b6o$24b5o4b34o4b5o$22b6o3b38o3b6o$
21b6o2b42o2b6o$20b6o2b44o2b6o$19b6o2b46o2b6o$18b6ob50ob6o$16b7ob52ob7o
$15b7ob54ob7o$15b6ob56ob6o$14b6ob58ob6o$13b6ob60ob6o$12b6ob62ob6o$11b
6ob64ob6o$10b6ob66ob6o$9b6ob68ob6o$9b82o$8b84o$7b5ob74ob5o$7b4ob76ob4o
$6b4ob78ob4o$5b90o$5b43o4b43o$4b4ob34o14b34ob4o$4b37o18b37o$3b37o20b
37o$3b3ob32o22b32ob3o$3b34o26b34o$2b4ob29o28b29ob4o$2b33o30b33o$2b32o
32b32o$b33o32b33o$b32o34b32o$b31o36b31o$b31o36b31o$31o38b31o$31o38b31o
$31o38b31o$30o40b30o$30o40b30o$30o40b30o$30o40b30o$31o38b31o$31o38b31o
$31o38b31o$31o38b31o$3ob27o38b27ob3o$3ob28o36b28ob3o$b3ob27o36b27ob3o$
b3ob27o36b27ob3o$b2o3b27o34b27o3b2o$b3o2b28o32b28o2b3o$b3o3b27o32b27o
3b3o$2b2o3b28o30b28o3b2o$2b3o2b29o28b29o2b3o$2b3o3b29o26b29o3b3o$3b3o
2b30o24b30o2b3o$3b3o3b30o22b30o3b3o$4b3o2b32o18b32o2b3o$4b3o3b32o16b
32o3b3o$5b3o2b34o12b34o2b3o$5b3o3b78o3b3o$6b3o3b76o3b3o$6b4o2b76o2b4o$
7b4o2b74o2b4o$7b4o3b72o3b4o$8b4o2b72o2b4o$9b4o2b70o2b4o$9b5o2b68o2b5o$
10b5o2b66o2b5o$11b6ob64ob6o$12b6ob62ob6o$13b6ob60ob6o$13b7ob58ob7o$14b
7ob56ob7o$15b7ob54ob7o$16b7ob52ob7o$17b7ob50ob7o$18b7ob48ob7o$19b7ob
46ob7o$20b8ob42ob8o$22b7ob40ob7o$23b8ob36ob8o$24b8o2b32o2b8o$26b8o2b
28o2b8o$27b9o2b24o2b9o$29b10o2b18o2b10o$31b10o2b14o2b10o$33b34o$35b30o
$38b24o$41b18o$48b4o!

Identify considers the bottom to be a still life all the time from what I've seen.

[rowett]

Identifying this pattern, which stops it at generation 4, gives a different result from autostart/stop and startfrom:

What's the difference?

A dying cell is absent to the left of the block.

When I run all three patterns Identify stops at generation 6, and not 4, and the output is identical.

[rowett]

Identify used on a spaceship which is alternated with a "do nothing" rule sometimes reports it as a still life in the general-range outer-totalistic rulespace

Fixed, thanks.

[rowett]

If the none rule's colors are overwritten, those colors are not actually shown in Help --> Info --> [Theme/Colours]:

Fixed, thanks.

[muzik]

... can the following triangular neighbourhood (possibly "LA" for Triangular All) also be added?

Only if I decide to add Triangular neighbourhood support to the HROT/LtL algo. The current tile-based Triangular algo can't support it since it's effectively range 3.

Can this be implemented now that general triangular outer-totalistic neighbourhoods are supported?

[muzik]

Pasting doesn't appear to work correctly for PCA cells. In the following example, try pasting an east cell into the north square. The expected result would be that they would combine to form a northeast cell, but instead the north cell is completely replaced with the east cell:

Code: Select all

x = 18, y = 17, rule = 2PCA4,0,2,4,12,8,5,9,7,1,6,10,11,3,13,14,15
7.A5.5A$8.A4.5A$B3.6A3.5A$8.A4.5A$7.A5.5A4$7.B3.A.A$4.B.B5.A$5.B5.A.A
2$3.5A2.5A$3.5A2.5A$3.2AC2A2.2AB2A$3.5A2.5A$3.5A2.5A!

I may have also encountered a bug with the undo system:
- Select All on the above pattern
- Clear the selection with the correct button
- Deselect the pattern
- Advance one generation
- Advance another generation
- Advance a third generation
- Stat pressing the undo button
After undoing several times, the original cells from the original pattern may reappear in a glitched state. If you attempt to select everything and then delete everything, the viewer states that the pattern is empty. These cells also don't seem to count towards the population counter in the T menu. Hitting play when the ghost pattern is present causes a strobing effect.

This also highlights the fact that the generations counter does not appear to tick upwards for PCA if no cells are present, which is inconsistent with other rules. It gets to 1 just fine, but the value just stops incrementing after that (the gen counter in the T menu does increase though):

Code: Select all

x = 18, y = 17, rule = 2PCA4,0,2,4,12,8,5,9,7,1,6,10,11,3,13,14,15
b!

Code: Select all

x = 18, y = 17, rule = B3/S23
b!

PCA also doesn't display the New Pattern message unlike other rule families.

Also, this period-384028 oscillator has a mod of 96007 (as the symmetric envelope and lower example patterns demonstrate), but Identify does not show this:

Code: Select all

x = 8, y = 15, rule = RotationsIII
4bo$o2bo$5bo$2bo2$2bo2$4bo7$7bo!
[[ ZOOM 16 ]]

Code: Select all

x = 8, y = 15, rule = RotationsIII
4bo$o2bo$5bo$2bo2$2bo2$4bo7$7bo!
[[ ZOOM 16 STARTFROM 384028 ]]

Code: Select all

x = 8, y = 15, rule = RotationsIII
4bo$o2bo$5bo$2bo2$2bo2$4bo7$7bo!
[[ ZOOM 16 STARTFROM 96007 ]]

Code: Select all

x = 8, y = 15, rule = RotationsIII
4bo$o2bo$5bo$2bo2$2bo2$4bo7$7bo!
[[ ZOOM 16 STARTFROM 192014 ]]

Code: Select all

x = 8, y = 15, rule = RotationsIII
4bo$o2bo$5bo$2bo2$2bo2$4bo7$7bo!
[[ ZOOM 16 STARTFROM 288021 ]]

And this doesn't register its mod of 7:

Code: Select all

x = 13, y = 3, rule = M0,0,0,15,0,15,0,0,0,0,15,0,15,0,0,15
$b12o$b12o

Is it intended that Time does not increase when startfrom or go to gen are used?

Code: Select all

x = 8, y = 15, rule = RotationsIII
4bo$o2bo$5bo$2bo2$2bo2$4bo7$7bo!
[[ ZOOM 16 STARTFROM 384028 SHOWGENSTATS THEME Generations ]]

[rowett]

Pasting doesn't appear to work correctly for PCA cells.

Fixed, thanks.

I may have also encountered a bug with the undo system

Fixed, thanks.

Also, this period-384028 oscillator has a mod of 96007 (as the symmetric envelope and lower example patterns demonstrate), but Identify does not show this...

And this doesn't register its mod of 7...

In both cases these are Margolus patterns. Because of the alternating grid the Margolus Identify only looks at every other generation, so odd Mods are not detected.

[muzik]

736 bug: while the grid button reacts as one would expect to changing the grid color via commands, it doesn't react to theme changes:

Code: Select all

x = 9, y = 5, rule = B3/S23
$bo3b3o$b3o2bo$2bo!
[[ COLOR GRID 255 255 0 ]]

Code: Select all

x = 9, y = 5, rule = B3/S23
$bo3b3o$b3o2bo$2bo!
[[ THEME MCell ]]

[muzik]

Is [R]Super intended to have a two-state random fill button? [R]History doesn't have such an option and I don't see how having it would be useful given that all other states are annotation states.

Code: Select all

x = 27, y = 15, rule = LifeHistory
2A$A$2.3A.3A.A3.3A.3A.3A$2.A3.A3.A3.A3.A4.A$2.3A.3A.A3.3A.A4.A$4.A.A
3.A3.A3.A4.A$2.3A.3A.3A.3A.3A2.A2$8.3A.A3.A$8.A.A.A3.A$8.3A.A3.A$8.A.
A.A3.A$8.A.A.3A.3A$26.A$25.2A!

Code: Select all

x = 27, y = 15, rule = LifeSuper
2A$A$2.3A.3A.A3.3A.3A.3A$2.A3.A3.A3.A3.A4.A$2.3A.3A.A3.3A.A4.A$4.A.A
3.A3.A3.A4.A$2.3A.3A.3A.3A.3A2.A2$8.3A.A3.A$8.A.A.A3.A$8.3A.A3.A$8.A.
A.A3.A$8.A.A.3A.3A$26.A$25.2A!

The "Invert" button also causes living cells to be replaced with state 24 and dead cells with 25 for RSuper, which is incorrect - it should have the same behaviour as RHistory.

Also, could RHistory's state 2 color be changed to match that of RSuper's for the sake of consistency?

Code: Select all

x = 14, y = 9, rule = LifeHistory
4A.4B.4C$4A.4B.4C$4A.4B.4C$4A.4B.4C2$4D.4E.4F$4D.4E.4F$4D.4E.4F$4D.4E
.4F!

Code: Select all

x = 14, y = 9, rule = LifeSuper
4A.4B.4C$4A.4B.4C$4A.4B.4C$4A.4B.4C2$4D.4E.4F$4D.4E.4F$4D.4E.4F$4D.4E
.4F!

Can the "select drawing state" bar found in Draw mode also be added to Select mode, such that the 2-state random fill state can be selected from there without having to go to Draw and then back to Select?

Cutting/copying and pasting don't seem to work at all for PCA anymore, at least on my end. Other rule families work fine.

[pzq_alex]

Also, could RHistory's state 2 (you mean 3) color be changed to match that of RSuper's for the sake of consistency?

Code: Select all

x = 14, y = 9, rule = LifeHistory
4A.4B.4C$4A.4B.4C$4A.4B.4C$4A.4B.4C2$4D.4E.4F$4D.4E.4F$4D.4E.4F$4D.4E
.4F!

Code: Select all

x = 14, y = 9, rule = LifeSuper
4A.4B.4C$4A.4B.4C$4A.4B.4C$4A.4B.4C2$4D.4E.4F$4D.4E.4F$4D.4E.4F$4D.4E
.4F!

That color would be very similar to that of state 13.

Code: Select all

x = 2, y = 1, rule = LifeSuper
CM!
[[ COLOR 3 255 255 255 ]]

[rowett]

736 bug: while the grid button reacts as one would expect to changing the grid color via commands, it doesn't react to theme changes:

Fixed, thanks.

[rowett]

Is [R]Super intended to have a two-state random fill button?

Yes and a multi-state random fill. [R]History only supports 2-state fill.

The "Invert" button also causes living cells to be replaced with state 24 and dead cells with 25 for RSuper

Fixed, thanks.

Also, could RHistory's state 2 color be changed to match that of RSuper's for the sake of consistency?

No they are deliberately different so you get a visual cue of which rule type is active.

Cutting/copying and pasting don't seem to work at all for PCA anymore, at least on my end. Other rule families work fine.

Fixed, thanks.

[muzik]

Triangular bounded grids seem to be flawed. The cell that gets zoomed in on should turn on in generation 32' but does not, breaking mirror symmetry as a result:

Code: Select all

x = 2, y = 2, rule = B12/SL:T30,30
2o$2o!
[[ STOP 32 T 16 X 0 Y 0 T 32 X -15 Y -15 ZOOM 16 ]]