Pattern viewer for forum threads

[rowett]

... a rainbow appeared.

Code: Select all

x = 50, y = 50, rule = Conway's Life:T200
3o3bobo4bobo2bo3b2o2b2obobobob2o2b5ob5o$o2bo2b2ob4o2b4o3bobo2b3o5bo3b
ob2ob4obo$obo3b4obo3bo2bo2b5o2bob6o2b3o2b2ob3o$2o3bo2bob2ob4o2bo3b2o4b
2o6bob3o$o4bob4o2b7o3b2o3bo2b2obob2o3b4obobo$bobob3o3bo5b2ob3o2bobo3b
3o4b2ob2ob2o2bo$3bobo3bo3b3obo2bo2b4ob3obobo2b2ob3o4bo$2ob2o2b4o2b4o4b
o2bo3b3o2b4o5bo2bo2b2o$4bo2bobo2b4ob2o2b2o2bo6bobob3o4b2obobo$2o5b2o2b
2obobo2bob2o4bo2bo5b4obobobobo$2b3obobob2obobobo4bo3bobo3bo2bob2o4b5o
$3b2o3bo2b5o2bo2b2o4b4o2b2o3b2obo2b3obo$3ob5ob3obo4b4ob3obo3b2o2bob2o
8bo$o2b3o2b2ob2obob6obobo3b3o5b2obo2bobob2o$2b2o5bo4b4o4b2ob12ob5o3bo
bo$b2o2bo4bo2bo3bobob7o2b8obob2o$2ob2ob12o4b2o3bo3b6o2b3o4b2obo$2bo2b
o3b6obob2ob3o3b3o4bobo3bo3b2o2b2o$o2b2ob3o3bob2o10b5o7b5o3bobo$ob2o3b
4o2b4o7b3o2b2obo4b4o2b2o3bo$2bob2ob3o7b3o3b2ob3o2b4obobob2o2b4obo$bob
obobob2ob3obobobo2b2ob3o3b3o2bo3b3o3bobo$5bo5bo4bo2b2obo4bo2bo2b2ob2o
b3o2b2obobo$4bobo2bob2ob4ob2obobo3b3o5bo2b2o2b2o2b2o$b2o2b2obo2bo3b2o
bo3bob3ob2o4b2o4bo2bo3b2o$5bobo4bobo3b3obo2bob2o2b2o3bob2ob2o6bo$bob2o
2bo2b2o2bo2b2o6bobo2bo3bob4ob2ob6o$2bo5bo3b2obo2b4o2bob3obob3o5b2obo2b
obo$o6bo5bo3bo2bob2o4bo3b7ob6ob2o$bobobo3bo2b2obo9bo3b2obo2b5o2b4obo$
bo3bob2obob4obob7o2b2o4b5o2bo2b2obobo$bo2b3o2b2o2bob2o2bob2o3bo6bo2bo
2b2obob2o3bo$4o2bob5ob3o4bo2bobo2bo2bo3b6o3b2o$bob3o2b2ob4o2bo3bob2ob
3ob2obob2obo4b5obo$2bo2bo4b5o7b3obobob3ob5o2b3o3b2o$b4o3b7o2b2o2b4o2b
4obo3bob2o2b2ob4o$b2o2b3obo2b5o3b3ob2o2bo2bo3bo3b2obo3b2o$4b2o4b2o6b3o
6b2o2bob2o6b4ob4o$2o4bo5bo2b3o2b2obo3bo2b3o2b5obo2b3o2bo$b3obob5o5bo4b
3obobo2bo3bob2ob4o2bob2o$b7o2bo5bo2bob3ob2o2bobo3b5ob2o2bo3bo$2bobo2b
ob2obob3o2bo4b3ob2o2bo2bobob2o2b4ob2o$obo3bo3bo3b3obo2b5ob3o2b5obobo2b
2obob2o$o2bob2obo4bo4b3o7b2ob2ob2o5bob3ob2o$2o2b4o2b2obobobob2o4bobob
2o3bo3b3obob2o2b2o$bo3b4obobobo3b5ob3ob2obo4b5o5b3o$o10bo2b2o3bob3obo
6b3obob2obo2bob2obo$o4b2o8b2o4b4obob2o2bobo4b2obobob2o$o2b4ob6o2bobob
3ob3o2b5obo4b2o3b2ob2o$obobob3ob3ob4o6b5o4b2o4bo4bobo2bo!
[[
ZOOM 8
AUTOSTART GPS 1
RLE enablesecretsnow bo$3o$bo!
RANDOMIZE RANDWIDTH 50 RANDHEIGHT 50
NOSTEPBACK SHADER Rainbow HARDRESET
LAYERS 5 DEPTH 0.1
]]

[rowett]

I'm confused about how to get a state to change to a different color if it's been alive for more than one generation. I tried using ALIVERAMP, but that makes it slowly change to a different color over time. I'd like any living cell which wasn't just born to immediately switch to a completely different color (from Red to Yellow, or something). How can I do this with scripts?

Also, I'm doing this for a 2-state automaton. This is what I attempted:

Code: Select all

#C [[ COLOR ALIVE Red ]] [[ COLOR ALIVERAMP Green ]] [[ COLOR DEAD Black ]]
x = 64, y = 64, rule = R2,C2,S2-3,B3,N@54422a:T100
!

but cells slowly go from red to green, instead of immediately.

This can now be done with the new [[ AGESTATES <0..63> ]] script command which defines how many generations an alive cell fades from the ALIVE colour to the ALIVERAMP colour. The default is 63 but if you want it to change immediately then use a value of 1.
Note you may need to hard refresh your browser to use the new build.

Code: Select all

#C [[ COLOR ALIVE Red COLOR ALIVERAMP Green COLOR DEAD Black ]]
#C [[ AGESTATES 1 ]]
x = 3, y = 3, rule = Life
o$
obo$
2o!

[bubblegum]

Triangular cells, like hexagonal cells, are slow. Hexagonal rules have the option to turn off hexagons, leading to a fair speed boost. Triangular rules…well, can LifeViewer have an option to turn off triangular cells too?

[rowett]

can LifeViewer have an option to turn off triangular cells too?

Yes, added in build 580. Toggle with hotkey /, or Settings->Display->Triangles. Override default (Triangles) with [[ SQUARECELLS ]] script command.

Thanks for the suggestion!

[bubblegum]

Running a pattern in a rule with a theme with history states and then turning Rainbow on can behave somewhat strangely sometimes. (Try it on the forums, and without waypoints.)

[rowett]

Running a pattern in a rule with a theme with history states and then turning Rainbow on can behave somewhat strangely sometimes. (Try it on the forums, and without waypoints.)

Please post a pattern here that demonstrates the issue.

[bubblegum]

Suggestion: Put the rule definition in the Change Rule dialog, currently a dynamically updating version is completely unavailable and having the alias in the dialog seems kind of unnecessary.

[muzik]

Could the "alive" parameter in the T menu be made to display counts per state, rather than "every cell which isn't 0"? Preferably with the same names as are displayed when selecting a state to draw with in the draw menu.

Code: Select all

x = 12, y = 10, rule = 12/34/3
3.2AB2A3.B$.B.BA4.B$B.AB5A.2B$.2A.BA4.A$3.BAB2AB.B$B.A.2B4AB$2AB2A.BA
B2.A$3.BABAB2AB$2.AB2.2B.BA$A.B2.A2.2B.A!

A generic "Transitions" counter for rules with 3 and more states, which counts all cell state changes that aren't 0 to not-0 or not-0 to 0, would also be appreciated (no need to list each type of transition individually since that would get way too big way too quickly)

[muzik]

Another suggestion: Identify to also print out the symmetry of the object in question (using the same symmetry names Catagolue would), only for square grid patters

[muzik]

It appears that using the cut option (and almost certaintly the copy option) will without fail bring up the Slow Mo Blue Box and slow down the viewer, alongside moving to the top of the page like I noticed a while ago.

[muzik]

Could the RANDOMIZE functionality be able to accept specific parameters to generate a random soup with a given symmetry (specifically those apgsearch can by default, as well as D8_2)?

[ColorfulGalaxy]

Bug: Venetian blinds freeze in strobing rule B03/S23
Also, in B0/S5, it oscillates, but "Identify" says it's a still life.

Code: Select all

x = 0, y = 0, rule = B3/S23:T8,8
8o$8o3$8o$8o!

Code: Select all

x = 0, y = 0, rule = B03/S23:T8,8
8o$8o3$8o$8o!

Code: Select all

x = 0, y = 0, rule = B03/S238:T8,8
8o$8o3$8o$8o!

Code: Select all

x = 0, y = 0, rule = B0/S5:T8,8
8o$8o3$8o$8o!
A still life that oscillates??????

[bubblegum]

Bug: Venetian blinds freeze in strobing rule B03/S23
Also, in B0/S5, it oscillates, but "Identify" says it's a still life.

B0 rules use emulation. Basically, B0/Smax rules invert themselves (so "dead" cells are alive and vice versa), while B0/S-max rules invert every other generation. This also means that "p2 oscillators" are still lives, "still lives" are p2 oscillators and everything has an even period (if it appears to have an odd period, the true period is doubled), explaining the "p3" you mentioned somewhere else.

[ColorfulGalaxy]

Bug: Venetian blinds freeze in strobing rule B03/S23
Also, in B0/S5, it oscillates, but "Identify" says it's a still life.

B0 rules use emulation. Basically, B0/Smax rules invert themselves (so "dead" cells are alive and vice versa), while B0/S-max rules invert every other generation. This also means that "p2 oscillators" are still lives, "still lives" are p2 oscillators and everything has an even period (if it appears to have an odd period, the true period is doubled), explaining the "p3" you mentioned somewhere else.

Also， if the script [[ STEP 2 ]] is added, the Venetian blinds will also freeze.

Code: Select all

x = 0, y = 0, rule = B3/S23:T8,8
8o$8o3$8o$8o!
[[ STEP 2 ]]

[bubblegum]

Also， if the script [[ STEP 2 ]] is added, the Venetian blinds will also freeze.

Why did you feel it was important to let me know this? This is intended behaviour.

[PHPBB12345]

Suggestion: Margolus rule with 3 states (include dead, alive, and stationary cell)
Example rules:
M[84020001000000088860004904400840290220082081006101010420410021000] = MargLogic
M[84C2A6E195D3B7F48A2C6E4891C5D84C81A239B82A81984162357426415421321] = MargLogicRev
M[12C4A9E865D3B7F4268CAE84C195D48C82A193B28A1898145236724614541232184C2A97165B3DEF4268CAE84C195D48C82A193B28A18981452367246145412321] = Critters with stable reflector
M[28A136B49CE57DF2468ACE14589CD48C12389AB28A189812345672461454123214158C6D2937AEBF2468ACE14589CD48C12389AB28A18981234567246145412321] = TMGas with boundary
M[21C856749AB3DEF2468ACE14589CD48C12389AB28A189812345672461454123214831A67295BCDEF2468ACE14589CD48C12389AB28A18981234567246145412321] = Dominotons

[Hunting]

will it be possible to add music to lifeviewer animations

also how to change theme at a certain point with cmds

[dvgrn]

also how to change theme at a certain point with cmds

Just put in the THEME command you want at the appropriate place in the T commands. I've edited in an example to the LeapLife animation starting at T=1750 -- you can see how it works there.

Notice that the way it works isn't quite what you might expect at first. Any T {whatever} command should be read something like:

"... from now until you get to T = {whatever}, do the following stuff..."

So a "T 1750" command followed by a THEME change will immediately change the theme at T=1750. Another THEME change at "T 2130" will immediately change it back -- it doesn't wait until the end of the time period in question.

[bubblegum]

Feature request: A command which will set a graph's default opacity (it's kind of annoying to have it start at 70% every time).

Also @rowett are you okay? You haven't been (multi-)posting lately, although I can see you're online and silently pushing updates to LifeViewer (and, of course, running ikpx2).

[rowett]

Feature request: A command which will set a graph's default opacity (it's kind of annoying to have it start at 70% every time).

You can specify it per pattern with: [[ GRAPHOPACITY <0.0..1.0> ]]

For a full list of supported commands use Help->Scripts or see LifeViewer#Scripts.

Also @rowett are you okay? You haven't been (multi-)posting lately, although I can see you're online and silently pushing updates to LifeViewer (and, of course, running ikpx2).

Yes I'm good thanks. Busy with work.

[muzik]

I've tried getting lifeviewer build 123 to run by using the same setup as would be used to run the current build of lifeviewer (renaming the js accordingly) but it just doesn't seem to work. Is this an issue with my execution or is the version itself at fault?

Build 231 also may or may not be mislabelled.

[rowett]

I've tried getting lifeviewer build 123 to run by using the same setup as would be used to run the current build of lifeviewer (renaming the js accordingly) but it just doesn't seem to work. Is this an issue with my execution or is the version itself at fault?

What LifeViewer expects from the HTML page changed in build 133 (not published) so the current method doesn't work for build 123. If you want to see build 123 working try this.

Build 231 also may or may not be mislabelled.

It was actually build 226 so I've renamed it. Enjoy LifeViewer archeology!

[muzik]

A couple more things:
- Build 482 seems to be slightly misnamed, so that may or may not warrant a correction.
- Also, what's with all the gaps in versions? A ton of the really old versions are missing, but there's also a few recent odd cases (builds 518 and 553) which are missing from the list as well. The changelog implies they should exist. Were these private development builds, builds hidden from the public due to major glitches, or just versions that are unfortunately now lost to time?

And a newly discovered bug: using the select function and dragging the cursor out of the viewer window with it active doesn't cancel the selection properly, and you need to click back in the window to conclude it.

[rowett]

Build 482 seems to be slightly misnamed, so that may or may not warrant a correction.

Fixed.

Also, what's with all the gaps in versions?

I only release when there's something worth releasing. Historically the release process was time consuming so I would only do it once in a while. Now it's trivial so I tend to do so more often.

And a newly discovered bug: using the select function and dragging the cursor out of the viewer window with it active doesn't cancel the selection properly, and you need to click back in the window to conclude it.

I'm quite happy with the current behaviour. It used to annoy me if I accidentally went slightly out of the window and it cancelled the selection.

[muzik]

Is build 333 also mislabelled?