ConwayLife.com

Posted: **April 25th, 2021, 7:39 am**

lemon41625 wrote: July 23rd, 2020, 8:30 pm R2 Cross INT

x = 53, y = 95, rule = B/S012345678History
.3C3.2C4.3C3.3C3.C.C3.3C3.3C3.3C3.3C$.C.C4.C6.C5.C3.C.C3.C5.C7.C3.C.C
$.C.C4.C4.3C3.3C3.3C3.3C3.3C5.C3.3C$.C.C4.C4.C7.C5.C5.C3.C.C5.C3.C.C$
.3C3.3C3.3C3.3C5.C3.3C3.3C5.C3.3C2$2.D5.D5.D5.D5.D5.C5.C5.C5.C$2.D5.C
5.C5.C5.C5.D5.D5.D5.C$2D.2D.2D.2D.2D.CD.2D.CD.DC.CD.2C.DC.2C.DC.2C.2C
.2C.2C$2.D5.D5.D5.C5.C5.D5.C5.C5.C$2.D5.D5.D5.D5.D5.C5.C5.C5.C2$8.C5.
D5.C5.D5.D5.C5.D$8.D5.C5.C5.C5.D5.D5.C$6.2D.2D.2D.2D.2D.CD.DC.CD.2C.D
C.2C.2C.2C.2C$8.D5.C5.D5.D5.C5.D5.C$8.D5.D5.D5.C5.C5.C5.C2$14.C5.D5.D
5.C5.D$14.C5.C5.C5.D5.D$12.2D.2D.2D.CD.2C.CD.2C.DC.2C.2C$14.D5.D5.D5.
C5.C$14.D5.C5.D5.D5.C2$14.D5.D5.C5.C5.C$14.C5.C5.C5.D5.D$12.2D.DC.CD.
2D.DC.CD.DC.2C.2C.CD$14.D5.C5.D5.D5.C$14.D5.D5.D5.C5.C2$14.D5.C5.D5.D
5.C$14.C5.C5.C5.D5.D$12.2D.2D.2D.2D.CD.CD.2C.2C.2C.2C$14.D5.C5.D5.D5.
C$14.C5.D5.C5.C5.D2$14.C5.D5.D5.C5.D$14.D5.C5.C5.D5.C$12.2D.DC.CD.2D.
CD.2C.DC.2C.2C.CD$14.D5.D5.D5.C5.C$14.D5.C5.D5.D5.C2$14.C5.D5.C5.C5.D
$14.D5.C5.C5.D5.C$12.2D.2D.CD.DC.CD.CD.DC.CD.2C.2C$14.D5.D5.D5.C5.C$14.
C5.D5.D5.C5.D2$20.C5.C5.D$20.C5.C5.D$18.CD.2D.2D.2C.DC.2C$20.D5.D5.C$
20.D5.D5.C2$20.C5.D5.D$20.D5.C5.C$18.CD.DC.CD.DC.DC.CD$20.D5.C5.C$20.
D5.D5.C2$26.C$26.C$24.2D.2D$26.C$26.C2$26.C$26.C$24.CD.2D$26.C$26.D2$
26.C$26.C$24.CD.DC$26.D$26.D2$26.D$26.C$24.CD.DC$26.D$26.C2$26.C$26.C
$24.CD.2D$26.D$26.C2$26.C$26.D$24.CD.DC$26.D$26.C!

Use letters acehijnopqrtuvw

Seems this transition and its inverse was left out:

Code: Select all

x = 5, y = 5, rule = bs012345678History
2.C$2.C$2D.2D$2.D$2.C!

The sixth and thirteenth knight 4 cases also seem to be duplicates.

I've noticed that the latest build 606 changes the LifeHistory colors, but this wasn't announced in the changelog - is this an intentional change?

Posted: **April 25th, 2021, 7:57 am**

muzik wrote: April 25th, 2021, 7:39 am I've noticed that the latest build 606 changes the LifeHistory colors, but this wasn't announced in the changelog - is this an intentional change?

No. Fixed, thanks.

Posted: **April 25th, 2021, 10:21 am**

A few other nitpicky desktop things:
- The rounded black box effect thing I mentioned earlier actually intrudes on the inside of the viewer slightly, causing the edges of buttons to be cut off as a result.
- The "Click to control" text only disappear when the mouse is released, which doesn't make sense since the first pressing of a click allows control as is shown by being able to use sliders with the text still active.
- Greyed-out sliders, such as the three settings sliders when hexagonal/triangular cells are enabled, still change the cursor accordingly despite being non-interactive.

Posted: **April 25th, 2021, 12:28 pm**

muzik wrote: April 20th, 2021, 8:22 am I may have finally stumbled upon a way to activate the random occurrences of Slo Mo Blue Box syndrome with the popup viewer. While the results are nowhere near consistent, with a bit of luck and the appropiate hardware (dvgrn might be able to reproduce this) it should take less than a minute for it to happen.

I've put in an experimental fix for the SMBB syndrome. I'm fairly sure the blue box will disappear but I've no idea if that will change performance. Please let me know. Without an iPad I'm throwing darts blindfold at the problem.

Posted: **April 25th, 2021, 1:05 pm**

rowett wrote: April 25th, 2021, 12:28 pm
muzik wrote: April 20th, 2021, 8:22 am I may have finally stumbled upon a way to activate the random occurrences of Slo Mo Blue Box syndrome with the popup viewer. While the results are nowhere near consistent, with a bit of luck and the appropiate hardware (dvgrn might be able to reproduce this) it should take less than a minute for it to happen.
I've put in an experimental fix for the SMBB syndrome. I'm fairly sure the blue box will disappear but I've no idea if that will change performance. Please let me know. Without an iPad I'm throwing darts blindfold at the problem.

Fantastically, the "tap on popup region before it shows up" no longer seems to cause it to show up at all.

Using the copy function, which would also previously guarantee its appearence with Sync on, no longer triggers it either (although it still doesn't actually copy the pattern to the clipboard).

Posted: **April 25th, 2021, 8:15 pm**

On the usual platform it seems as though expanding thumbnail viewers that had previously been opened and then closed becomes impossible:

viewtopic.php?f=3&t=1622&start=150#p29766

The post also contains a script error - was the map command removed?

Posted: **April 25th, 2021, 8:35 pm**

rowett wrote: January 30th, 2020, 1:45 pm
muzik wrote: January 30th, 2020, 12:25 pm Not sure exactly what you mean...

The TriLife implementation has roughly the same symmetries as natively supported golly hexagonal rules, unlike with lifeviewer's, so there might need to be a bit of weird rotation done to make patterns work.
I guess what I'm saying is it's not a priority to me so I'm not going to work it out but if some kind soul wants to detail the conversion steps then I'll probably implement it.

This might work, but could probably be optimised:

Code: Select all

x = 59, y = 11, rule = TriLife-B45S34
2$26.A.A12.A.A10.A.A$2.2A8.A.A7.ABA2.BAB6.ABA2.BAB5.3A2.3A$CABC4.C.A.
B.C8.BAB3.BA5.BAB3.BA5.3A3.2A$BC.BA3.B.C3.B.A!

0. Read the pattern, and verify that it uses the TriLife format by starting with TriLife
1. Stretch the pattern out so that every second column is state 0
2. Move all state 2 cells one cell to the right, and for all state 3 cells, change them to state 1 and add a state 2 cell to their right
3. Shift each row to the left one more cell than the row above it
4. Convert all cells to state 1
5. Convert the rulestring accordingly (abc to XYZ if present)

Posted: **April 25th, 2021, 10:26 pm**

rowett wrote: April 25th, 2021, 12:28 pm
muzik wrote: April 20th, 2021, 8:22 am I may have finally stumbled upon a way to activate the random occurrences of Slo Mo Blue Box syndrome with the popup viewer. While the results are nowhere near consistent, with a bit of luck and the appropiate hardware (dvgrn might be able to reproduce this) it should take less than a minute for it to happen.
I've put in an experimental fix for the SMBB syndrome. I'm fairly sure the blue box will disappear but I've no idea if that will change performance. Please let me know. Without an iPad I'm throwing darts blindfold at the problem.

Unfortunately I do seem to be experiencing brand-new unexplainable, inconsistent slowdowns characteristic of what would happen if the blue box was there. They don't seem to be triggered by what would trigger the old blue box though, so I have no idea what to go off of.

Posted: **April 26th, 2021, 12:20 am**

muzik wrote: April 25th, 2021, 8:15 pm On the usual platform it seems as though expanding thumbnail viewers that had previously been opened and then closed becomes impossible:

viewtopic.php?f=3&t=1622&start=150#p29766

It works for me on the iPhone.

muzik wrote: April 25th, 2021, 8:15 pm The post also contains a script error - was the map command removed?

Yes it was deprecated.

Posted: **April 26th, 2021, 1:57 am**

Are arrow keys meant to move selected regions in the opposite direction?

Posted: **April 26th, 2021, 11:41 am**

muzik wrote: April 26th, 2021, 1:57 am Are arrow keys meant to move selected regions in the opposite direction?

They pan.

Posted: **April 26th, 2021, 8:18 pm**

KILLGLIDERS doesn't seem functional for super:

Code: Select all

x = 3, y = 3, rule = B3/S23
o$obo$2o!
[[ KILLGLIDERS ]]

Code: Select all

x = 3, y = 3, rule = B3/S23History
o$obo$2o!
[[ KILLGLIDERS ]]

Code: Select all

x = 3, y = 3, rule = B3/S23Super
o$obo$2o!
[[ KILLGLIDERS ]]

I should also mention that for History, generic dead cells replace marked cells in these cases, and rewinding doesn't reset the cells to their initial states either:

Code: Select all

x = 11, y = 3, rule = LifeHistory
C7.E$C.C5.E.E$2C6.2E!
[[ KILLGLIDERS ]]

Would history processing for state 1 and 2 in LifeSuper be possible?

And one last thing: I'm not sure if invert functionality is supported for [R]History but the invert function in select replaces red cells with state 0, where i'd expect state 3 (and states 3/5 to 4).

Code: Select all

x = 2, y = 2, rule = LifeHistory
2D$2D!

---

Just to complicate things a bit more, there are oscillators that could be considered FlipXorY or RotCWorCCW:

Code: Select all

x = 4, y = 4, rule = R2,C0,S1,B3,NB
bo$o$3bo$2bo!

Posted: **April 27th, 2021, 10:04 am**

It seems the blue box behaviour is back in the latest build.

Posted: **April 27th, 2021, 10:38 am**

muzik wrote: April 27th, 2021, 10:04 am It seems the blue box behaviour is back in the latest build.

Yes I'm still working on it which is why I haven't published any information about it yet.

Posted: **April 27th, 2021, 11:22 am**

Would it be possible to implement multiple alternating rules? 2 isn't always enough.

Posted: **April 28th, 2021, 12:41 am**

Some very low-priority rulespace suggestions, in no particular order:

- Cyclic cellular automata: One of the few rulespaces MCell supports natively that LifeViewer still doesn't. Analogously to deriving HROT from LtL, it might be possible to modify the rulestring to make the "threshold" be generalised to any desired values, rather than just a specified minimum (and we can probably benefit from the up to 500 range and more supported neighbourhoods at the same time). Old MCell specification here: http://psoup.math.wisc.edu/mcell/rullex_cycl.html

- Rock Paper Scissors cellular automata: A lesser known class of CA, these commonly exhibit the spiral behaviour commonly seen in cyclic CA. Not sure if these would work for even state counts. Info on them can be found here https://softologyblog.wordpress.com/201 ... -automata/ although I'm not sure how rulestrings would be formatted.

- Parity rulespace: By default, Golly has the FredkinModN script packaged alongside its list of other rule generators. While the script obviously works, it has its flaws: higher state counts end up taking absolutely ages to create ruletables for, neighbourhoods such as Moore also take far more time to generate a rule for than an equivalent von Neumann rule, and Golly's handling of triangular rules, alongside taking an absolutely stupid amount of time to generate rules for (generating the 3-state case for it took literally 100 whole hours and I don't even know it if works properly), limits our modulo to way under 256 due to all different possible sets of two triangles requiring a single dedicated state each.

On a similar note, while the new HROT specification for Golly and LifeViewer allows for Fredkin replicator rules to be simulated for higher ranges, due to half of each of the possible birth and survival conditions having to be specified, with nine being adjacent to allow for compression via dashes, the rulestrings get very unwieldy very quickly. Both the ruletable generation and rulestring length problems could be solved by making parity rules their own rulespace with the following rulestring format:

R[range],C[states],M[whether the center should be preserved; 0 for rules like B1357/S1357 and 1 for rules like B1357/S02468],N[neighbourhood]

Examples:
R2,C2,M0,NM

Code: Select all

x = 1, y = 1, rule = R2,C0,S1,3,5,7,9,11,13,15,17,19,21,23,B1,3,5,7,9,11,13,15,17,19,21,23
o!
[[ AUTOFIT ]]

R1,C3,M0,NM

Code: Select all

x = 1, y = 1, rule = Fredkin_mod3_Moore
A!
[[ AUTOFIT ]]

R1,C3,M0,NH

Code: Select all

x = 1, y = 1, rule = Fredkin_mod3_hexagonal
A!
[[ AUTOFIT ]]

R1,C7,M0,NN

Code: Select all

x = 1, y = 1, rule = Fredkin_mod7_vonNeumann
A!
[[ AUTOFIT ]]

R1,C2,M1,NN

Code: Select all

x = 1, y = 1, rule = B13/S024V
A!
[[ AUTOFIT ]]

R1,C2,M0,NL

Code: Select all

x = 1, y = 1, rule = B13579Y/S13579YL
o!
[[ AUTOFIT ]]

Posted: **April 28th, 2021, 1:36 am**

Code: Select all

x = 35, y = 20, rule = R10,C0,S230-392,B200-398,NL
11b13o$8b19o$7b23o$4b27o$3b29o$2b31o$b16ob16o$bob11o7b14o$b11o11b12o$
12o11b12o$12o11b12o$b11o11b12o$bob11o7b14o$b16ob16o$2b31o$3b29o$4b27o$
7b23o$8b19o$11b13o!
[[ AUTOSTART STOP 50 ]]

Select All seems to count history states for HROT rules for some reason.

Posted: **April 28th, 2021, 8:26 am**

Is there a way to support multiple alternating rules?

Posted: **April 28th, 2021, 9:34 am**

muzik wrote: April 26th, 2021, 8:18 pm KILLGLIDERS doesn't seem functional for super.

True, it's on the backlog.

muzik wrote: April 26th, 2021, 8:18 pm I should also mention that for History, generic dead cells replace marked cells in these cases, and rewinding doesn't reset the cells to their initial states either.

[R]History extra states don't yet work properly with the snapshot function. It's a long standing bug I haven't prioritized for a fix yet.

muzik wrote: April 26th, 2021, 8:18 pm Would history processing for state 1 and 2 in LifeSuper be possible?

Yes, it's possible. I took a brief look a while back and need to spend more time on an efficient solution. So it's on the backlog.

muzik wrote: April 26th, 2021, 8:18 pm And one last thing: I'm not sure if invert functionality is supported for [R]History but the invert function in select replaces red cells with state 0,
where i'd expect state 3 (and states 3/5 to 4).

There's nothing currently specific for [R]History (or [R]Super). Invert is just inverting the states. I'll add something to the backlog to make it more intelligent for those families.

muzik wrote: April 26th, 2021, 8:18 pm Just to complicate things a bit more, there are oscillators that could be considered FlipXorY or RotCWorCCW.

Good news!

Posted: **April 28th, 2021, 9:35 am**

wwei47 wrote: April 27th, 2021, 11:22 am Would it be possible to implement multiple alternating rules? 2 isn't always enough.

Yes it's possible. I'll put it on the backlog.

Posted: **April 29th, 2021, 4:17 am**

Could the T menu be made to display two values for the generation count?:

- The current generation count, which displays the same value represented in the T button itself
- The amount of generations elapsed, which is always positive, and increments regardless of whether reverse playback is active or not

Posted: **April 29th, 2021, 5:08 am**

A couple of sightings and questions regarding notated [R] support:

- LifeViewer appears to have two distinct types of MarkOff cell in [R]History - one that can be drawn with, and a "hidden" second version which cannot. The former corresponds to Mark1, and the hidden to Mark2. Births into the Mark2 version will always result in Mark2 cells being born, which is inconsistent with Golly's implementation. Is this intended? This has been the case for a long time now so I'd assume so, but I can't be certain.

Code: Select all

x = 23, y = 17, rule = LifeHistory
14.C5.A$14.C.C3.A.A$14.2C4.2A5$7.D5.E$7.D.D3.E.E$7.2D4.2E5$D5.D$D.D3.
D.D$2D4.2D!
[[ STOP 28 ]]

- The default [R]Super color is slightly different from the default [R]History color:

Code: Select all

x = 3, y = 3, rule = LifeHistory
3A$A.A$3A!

Code: Select all

x = 3, y = 3, rule = LifeSuper
3A$A.A$3A!

- The names of states in [R]Super appear to be different from those in [R]History. Are there any reasons for this (I'd assume backwards compatibility, although in that case wouldn't History's be renamed and the old names kept as alternates)?

- [R]Super's default colors also differ significantly from the ones specified in Golly - specifically states 1 and 2, which were made to look as close to the Blues theme as possible for the original ruletable (whose specification carried on into Golly).

- And is there any reason why [R]Super doesn't support Themes, for the colors of the first two states?

Posted: **April 29th, 2021, 12:06 pm**

muzik wrote: April 29th, 2021, 5:08 am - LifeViewer appears to have two distinct types of MarkOff cell in [R]History - one that can be drawn with, and a "hidden" second version which cannot. The former corresponds to Mark1, and the hidden to Mark2. Births into the Mark2 version will always result in Mark2 cells being born, which is inconsistent with Golly's implementation. Is this intended? This has been the case for a long time now so I'd assume so, but I can't be certain.

Yeah, it's intended.

Posted: **April 29th, 2021, 1:41 pm**

Using the state picker will shift the state numbers displayed to include the picked state, but this is not reflected by the slider.

Code: Select all

x = 1, y = 1, rule = scrapped-annotation-rule
pF!

Posted: **May 2nd, 2021, 12:13 am**

It doesn't seem possible to specify state colors using @NAMES specified state names:

Code: Select all

x = 11, y = 11, rule = WireWorld
3.5C$2.C2.C2.C$.C3.C3.C$C2.3CAB2.C$C2.C3.B2.C$4C3.4C$C2.C3.C2.C$C2.5C
2.C$.C3.C3.C$2.C2.C2.C$3.5C!
[[ COLOR copper wire 0 255 0 ]]

Code: Select all

x = 11, y = 11, rule = WireWorld
3.5C$2.C2.C2.C$.C3.C3.C$C2.3CAB2.C$C2.C3.B2.C$4C3.4C$C2.C3.C2.C$C2.5C
2.C$.C3.C3.C$2.C2.C2.C$3.5C!
[[ COLOR "copper wire" 0 255 0 ]]

ConwayLife.com

Pattern viewer for forum threads

Re: Pattern viewer for forum threads

Re: Pattern viewer for forum threads

Re: Pattern viewer for forum threads

Re: Pattern viewer for forum threads

Re: Pattern viewer for forum threads

Re: Pattern viewer for forum threads

Re: Pattern viewer for forum threads

Re: Pattern viewer for forum threads

Re: Pattern viewer for forum threads

Re: Pattern viewer for forum threads

Re: Pattern viewer for forum threads

Re: Pattern viewer for forum threads

Re: Pattern viewer for forum threads

Re: Pattern viewer for forum threads

Re: Pattern viewer for forum threads

Re: Pattern viewer for forum threads

Re: Pattern viewer for forum threads

Re: Pattern viewer for forum threads

Re: Pattern viewer for forum threads

Re: Pattern viewer for forum threads

Re: Pattern viewer for forum threads

Re: Pattern viewer for forum threads

Re: Pattern viewer for forum threads

Re: Pattern viewer for forum threads

Re: Pattern viewer for forum threads