Pattern viewer for forum threads
 gameoflifeboy
 Posts: 474
 Joined: January 15th, 2015, 2:08 am
Re: Pattern viewer for forum threads
Re: Pattern viewer for forum threads
If you mean this then it's not planned. I'm currently working on Golly.gameoflifeboy wrote:When, if ever, will the features of the viewer on the forum (the new themes, support for nontotalistic and multistate rules and bounded grids, a universe larger than 512 by 512, and ability to zoom out farther than one cell per pixel) or most of the new shortcuts be implemented into the original LifeViewer?

 Posts: 3138
 Joined: June 19th, 2015, 8:50 pm
 Location: In the kingdom of Sultan Hamengkubuwono X
Re: Pattern viewer for forum threads
Code: Select all
x = 17, y = 10, rule = B3/S23
b2ob2obo5b2o$11b4obo$2bob3o2bo2b3o$bo3b2o4b2o$o2bo2bob2o3b4o$bob2obo5b
o2b2o$2b2o4bobo2b3o$bo3b5ob2obobo$2bo5bob2o$4bob2o2bobobo!
Re: Pattern viewer for forum threads
It sets the seed used by the pseudorandom number generator. Typically used if you need a repeatable sequence of pseudorandom numbers.Saka wrote:What does the RANDOMSEED command do?
It's currently not very useful in LifeViewer since there aren't many script commands that use pseudorandom numbers. However this may change in the future.
Re: LifeViewer bug
This has been implemented and will be in the next released build. Test case is here.rowett wrote:Nontotalistic rules with B0 are not supported yet.PHPBB12345 wrote:Code: Select all
x = 3, y = 6, rule = B01c2c35i/S23 bo$bo$3o$obo$obo$o!
Re: Pattern viewer for forum threads
Please note: you will need to refresh your browser to use the new build
Enhancements since the last released build:
 nontotalistic rule B0 support  test
Code: Select all
x = 104, y = 79, rule = B012ai3ciy4aceqryz5cenqr6n/S1e2aik3acjkq4jnqrtwy5cjnr6e
49bobo$48b2ob2o2$48b2ob2o$49bobo$56b2o21bobo$55b4o18bobob2o$56bob2o7bo
bob3o3b5o$55bo2bob2o4b3o2b7obob2o5b2o4bo$15bo36bo2bobo2bobobob2obob5o
2bobob2o2b6o$14bob2o39bo3b6ob8obo2b2o2bobo2bob4o$15bobo6b3o29bobob17ob
4o3b2ob4o$15b3o5bob3o8bo18b3o4b23o3bob6o$15b4o3bo3b2o5b2o14bo4bobo3bo
4b20o2b2o2b3obo$18bo4bo2b3o6bob2o9bob5ob3obob2ob21obo2b6o$17bobob2o4b
2ob4o3bo2bo6bob3obo2bo5bo2b20ob2o2bob4o$17b2o9b2obob2obo2b2ob2ob5obob
6o3b24o6bob2ob2o$16b7obobob2o2b2obo4b3ob4obobob5obo2b2obobob13ob2o8bo$
16bobo8b5obo6bob4ob2ob2ob3ob5ob4obo4b3obobo14bo$13bob2ob2obo2b4ob2o9b
5o2b2obob5o2bob4o3bo3b2o2b3o15bo$11b3obo3bo4b3ob3o11b6o3bob5obob3o10bo
bo$16b2ob2ob2obob2o2bo9bob9o2b5o14b3o$12b2ob2o3bo3b2o3bo12bob16o12b2ob
o$12bob2o2bob3o19bob12obo$13b2ob2obobo17bo3b7o4bo3bo$11bob2obo22b2o3b
5obob3obo46bo$11bo2b2o24bob6ob2o3bo46b2o$10bobobobo23bobob5obobobo6bo
40b2o$10b3ob3o20bo5bob4o2b4o6b2o39bo$10b3ob3o17b3o5bo2b5obo22bo10b4o
12b2o$7bob7obo16b2obo3b2ob2o2bob2obo33b2o$8b11o14bob2o7b4ob2o14bobo3b
3o11bo4bo$3bobob11o12bo2bob2o9b5obo19bobo15b2o$b18o9b2obob2obo11bobob
2o11bobo21b2obob2o$6ob14o7bobobob3o12b4o12bobo23b6o$5obob13o7b7obo12b
3o36bob6o$b5o2b9ob5o3b3o3b4o14bo14bobo16b2o3b8o$2b3o4b10ob2o5b3o2b2o
51b11o$7bo2b5o2bobobobobob5o53b11o$5b3ob5o4bobo2bobo2bob3o53b9o$7b2obo
bobo4bob2obob3obobobo34bo2bo11bo2b8o$14bo4b5ob4obobo38bo13b11o$18b3o3b
ob4o39b4ob2o8b13o$16b2ob3o3b5obo39b2obo7b16o$14b2obob4o3b4ob3o37b2ob2o
7b16o$14b9ob7o2bo36bo2bob2o8b13o$12bob8obob4o6b2o33bo2b2obo8b14o$14b4o
b4o3b2obo5bobobobo20bobo2bobob3ob2o8b14o$12b2ob2ob2o2b3ob4ob2o8b2o19bo
3b9ob2obo4b16o$15b2o3b3o2b5o7bob2obobo16bob13obobob2ob2ob14o$16bo5b2ob
7obo7bo17b25o2b15o$11bo3b3o2b12o8bob2obo14b23ob4ob11o$8b4o2bob5o3bob8o
10bo12b25o2bo3bob11o$6bob2o5bo2b4o2bobo3bo10bo2bo10bo2b22obob6ob2obobo
b5o$7b2ob2ob2obobo7bo18b2obob2ob3ob19obob2o7b3o3b9o$8b2o4bob2ob3o19bob
2o2b4ob7o2b12o3b3o7b3o4b3ob6o$8bobob7o11bo12b2o2b6o3bo4bob11ob2o10bo5b
ob2o3b2o$9bob13o16b2ob13obobo3b6o5bob2o10b2obo6b3o$9b11ob4o15b6o2b12o
4bo2b2o2b2ob2o13bobobobob5o$9b12o17b2o3b3o4b5o4bob4ob2obob3o13b3o7b4o$
11b10obo16b4ob3ob2ob4o3b2ob2o2bobob5obo22b4o$8bobo2b6ob3o16b7o3b2ob3ob
3ob3ob2obo3b4o12b2o8b4o$7b4o2b5ob3o16b8ob2o4bob5o2bobo3bo2bo2bo10bobo
10b2o$13bobob3o18b6o2b4o4bo3bo3b2o6b2o$8bo4b2o2b3o17b10obo5b2ob2obobo
5b3o$20bo16b5obobob2o8b2ob2o5b2o$19bo17b4obo2bobo9bo3bo2b2o3bo$19bo16b
2ob2obobobo9bo3bo4b2o2bo$39b2obobo13bo5bo4b2o$56bo2bo5bobo2b2o$43bo15b
o8b5o$56bo9b4obo$67b4o$67b3o$67bo$65bobo$38b2o26b2obo$37bo30bo$38bo30b
o!  native MAP rules (also implemented in Golly 2.9b2)  test
 Totalistic and isotropic nontotalistic rules are only a small subset of all possible rules for a 2state Moore neighborhood. The Moore neighborhood has 9 cells which gives 512 (2^9) possible combinations of cells. For each of these combinations you define whether the output cell is dead or alive, giving a string of 512 binary digits, each being 0 (dead) or 1 (alive).
Code: Select all
0 1 2 3 4 5 > 4' 6 7 8
 The first few entries for Conway's Life (B3/S23) in this format are as follows:
Code: Select all
Cell 0 1 2 3 4 5 6 7 8 > 4' 0 0 0 0 0 0 0 0 0 0 > 0 1 0 0 0 0 0 0 0 0 1 > 0 2 0 0 0 0 0 0 0 1 0 > 0 3 0 0 0 0 0 0 0 1 1 > 0 4 0 0 0 0 0 0 1 0 0 > 0 5 0 0 0 0 0 0 1 0 1 > 0 6 0 0 0 0 0 0 1 1 0 > 0 7 0 0 0 0 0 0 1 1 1 > 1 B3 8 0 0 0 0 0 1 0 0 0 > 0 9 0 0 0 0 0 1 0 0 1 > 0 10 0 0 0 0 0 1 0 1 0 > 0 11 0 0 0 0 0 1 0 1 1 > 1 B3 ... 19 0 0 0 0 1 0 0 1 1 > 1 S2 ... 511 1 1 1 1 1 1 1 1 1 > 0
 This creates a string of 512 binary digits:
Code: Select all
00000001000100000001...0
 This binary string is then base64 encoded for brevity giving a string of 86 characters:
Code: Select all
ARYXfhZofugWaH7oaIDogBZofuhogOiAaIDogIAAgAAWaH7oaIDogGiA6ICAAIAAaIDogIAAgACAAIAAAAAAAA
 By prefixing this string with "MAP" the syntax of the rule becomes:
Code: Select all
rule = MAP<base64_string>
 So, Conway's Life (B3/S23) encoded as a MAP rule is:
Code: Select all
rule = MAPARYXfhZofugWaH7oaIDogBZofuhogOiAaIDogIAAgAAWaH7oaIDogGiA6ICAAIAAaIDogIAAgACAAIAAAAAAAA
 Given each MAP rule has 512 bits this leads to 2^512 (roughly 1.34x10^154) unique rules. Totalistic rules are a subset of isotropic nontotalistic rules which are a subset of MAP rules.
 MAP rules can also be used with Generations in which case the syntax is:
Code: Select all
rule = MAP<base64_string>/<n_states>
 Totalistic and isotropic nontotalistic rules are only a small subset of all possible rules for a 2state Moore neighborhood. The Moore neighborhood has 9 cells which gives 512 (2^9) possible combinations of cells. For each of these combinations you define whether the output cell is dead or alive, giving a string of 512 binary digits, each being 0 (dead) or 1 (alive).
 population graph  test
 LifeViewer can now display a live graph of population, births and deaths as an overlay over the pattern
 hotkey "y" toggles the graph display
 hotkey shift and "y" to toggle graph lines or points
 hotkeys "7" and "9" to increase or decrease graph opacity
 hotkey shift and "o" now opens population graph snapshot in a separate window
 new graph script commands
 [[ GRAPH ]] enables population graph display on pattern load
 [[ GRAPHPOINTS ]] draw the graph with points rather than lines
 [[ GRAPHOPACITY <0.0..1.0)> ]] set graph background opacity
 graph colors can be customized
 [[ COLOR GRAPHBG R G B ]] to set background color
 [[ COLOR GRAPHAXIS R G B ]] to set axis color
 [[ COLOR GRAPHALIVE R G B ]] to set alive color
 [[ COLOR GRAPHBIRTH R G B ]] to set birth color
 [[ COLOR GRAPHDEATH R G B ]] to set death color
 graph settings and colors are shown in the help information
Code: Select all
#C [[ AUTOSTART STOP 600 AUTOFIT ]]
#C [[ GRAPH ]]
x = 2, y = 2, rule = Faders
2A$A!
 LifeViewer can now display a live graph of population, births and deaths as an overlay over the pattern
 autofit
 new script command [[ STATE1FIT ]] that forces autofit only to use state 1 for [R]History patterns
 hotkey shift and "s" to toggle
 new script command [[ STATE1FIT ]] that forces autofit only to use state 1 for [R]History patterns
 aliases
 added "Just Friends" to the nontotalistic aliases
 UI
 added a close button to the navigation menu for the popup Viewer
 [[ TRACK ]], [[ TRACKBOX ]] and [[ TRACKLOOP ]] now scroll more smoothly at low GPS
 error display wasn't hiding UI controls correctly
 accurate "Life ended at" generation when using STEP > 1
 Faders and Sticks aliases were incorrect  test
 patterns were not correctly centered when bounded grid had a zero dimension  test
 fixed an issue when just [[ COLOR BACKGROUND ]] and [[ COLOR ALIVE ]] were defined which caused an invalid [[ COLOR DEADRAMP ]]
 tooltips in multiitem controls now work after item clicked
 deprecated [[ FILL ]], [[ MAP ]] and [[ MAPODD ]] script commands
Comments, feedback, suggestions and bug reports welcome!
Re: Pattern viewer for forum threads
Re: Pattern viewer for forum threads
Since MAP rules really are the complete set of nontotalistic rules, maybe it would be clearer to sayrowett wrote:[*]Given each MAP rule has 512 bits this leads to 2^512 (roughly 1.34x10^154) unique rules. Totalistic rules are a subset of nontotalistic rules which are a subset of MAP rules.
Totalistic rules are a subset of isotropic nontotalistic rules which are a subset of MAP rules.
Put another way, the set of MAP rules is made up of the set of isotropic nontotalistic rules (where pattern behavior doesn't change under rotation or reflection) plus the much larger set of anisotropic nontotalistic rules (where symmetry is broken).
There are good reasons why people have focused almost exclusively on isotropic rules so far  it seems like a very strange idea to have spaceships that work in only one direction, like the lightspeed diagonal singlecell travelers below. Do such things even count as spaceships? Or I suppose some spaceships, oscillators, etc., might work in 2/3/4/5/6/7 of the eight possible orientations.
Code: Select all
x = 37, y = 13, rule = MAPQAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
o9bo9bo9bo$bo9bo9bo$2bo9bo$3bo$4bo15bo$5bo13bo$6bo11bo5bo$7bo9bo5bo$8b
o7bo5bo4bo$9bo5bo5bo4bo$o13bo5bo4bo4bo$13bo15bo$33bo2$5bo8bo$4b3o$3b5o
$4b3o12b2o$5bo13b2o$27b3o$o9bo16b3o$27b3o!
#C [[ AUTOSTART GRID GPS 1 TRACK 1 1 ]]
An odd thought is that every distinct 86characterlong string with spaces removed (or replaced by forward slashes)  quote from Shakespeare, quote from John Conway, whatever  is a different nontotalistic rule.
And capitalization matters  allcaps and lowercase versions would be significantly different rules, though CamelCase will at least somewhat resemble its lowercase version.
Unfortunately, I suspect that just about every such rule, quoting anyone other than a character in a certain Edvard Munch painting, will end up being boringly chaotically explosive. It will be hard to tell one chaotic region apart from another  though the behavior at the boundaries will certainly be very different:
Code: Select all
x = 1, y = 1, rule = MAPHeresyLadleFurryStarryToilingUdderWartsWelcherAlterGirdleDeferentFormOnceInnerRegional
o!
#C [[ AUTOSTART AUTOFIT ]]
Code: Select all
x = 1, y = 1, rule = MAP40+40andsevenyearsagoourfathersbroughtforthonthiscontinentanewnationconceivedinliberty
o!
#C [[ AUTOSTART AUTOFIT ]]
Code: Select all
x = 1, y = 1, rule = MAP40+40AndSevenYearsAgoOurFathersBroughtForthOnThisContinentANewNationConceivedInLiberty
o!
#C [[ AUTOSTART AUTOFIT ]]
Code: Select all
x = 1, y = 1, rule = MAPcorn/sieved/inebriety/tanned/addict/hated/tutor/preposition/dot/omen/or/crated/inkwell
o!
#C [[ AUTOSTART AUTOFIT ]]
Code: Select all
x = 1, y = 1, rule = MAPCORN/SIEVED/INEBRIETY/TANNED/ADDICT/HATED/TUTOR/PREPOSITION/DOT/OMEN/OR/CRATED/INKWELL
o!
#C [[ AUTOSTART AUTOFIT ]]
Re: Pattern viewer for forum threads
Thanks for the correction  I've modified the post above!dvgrn wrote:Totalistic rules are a subset of isotropic nontotalistic rules which are a subset of MAP rules.

 Posts: 3138
 Joined: June 19th, 2015, 8:50 pm
 Location: In the kingdom of Sultan Hamengkubuwono X
Re: Pattern viewer for forum threads
Code: Select all
x = 1, y = 1, rule =
MAPARYXfhZofugWaH7oaIDogBZofuhogOiAaIDogIAAgAAWaH7oaIDogGiA6ICAAIAAaIDogIAAgACAAIAAAAAAAA
bo$o$3o!
Code: Select all
x = 1, y = 1, rule = MAPcorn/sieved/inebriety/tanned/addict/hated/tutor/preposition/dot/omen/or/crated/inkwell
o!
#C [[ AUTOSTART AUTOFIT ]]
Code: Select all
x = 1, y = 1, rule =
MAPcorn/sieved/inebriety/tanned/addict/hated/tutor/preposition/dot/omen/or/crated/inkwell
o!
#C [[ AUTOSTART AUTOFIT ]]
Code: Select all
x = 17, y = 10, rule = B3/S23
b2ob2obo5b2o$11b4obo$2bob3o2bo2b3o$bo3b2o4b2o$o2bo2bob2o3b4o$bob2obo5b
o2b2o$2b2o4bobo2b3o$bo3b5ob2obobo$2bo5bob2o$4bob2o2bobobo!
Re: Pattern viewer for forum threads
The "rule = MAP..." needs to be all on one line, yours has a return character after the "rule = " part:Saka wrote:The map doesn't work for me?Code: Select all
x = 1, y = 1, rule = MAPARYXfhZofugWaH7oaIDogBZofuhogOiAaIDogIAAgAAWaH7oaIDogGiA6ICAAIAAaIDogIAAgACAAIAAAAAAAA bo$o$3o!
Code: Select all
x = 1, y = 1, rule = MAPARYXfhZofugWaH7oaIDogBZofuhogOiAaIDogIAAgAAWaH7oaIDogGiA6ICAAIAAaIDogIAAgACAAIAAAAAAAA
bo$o$3o!
Re: Pattern viewer for forum threads
Very obscure reference, just something I have memorized, a good source of randomlooking words. Google "crated inkwell" or "Ladle Rat Rotten Hut" if interested.Saka wrote:WHAT??
MAPcorn/sieved/inebriety/tanned/addict/hated/tutor/preposition/dot/omen/or/crated/inkwell
Re: Pattern viewer for forum threads
Code: Select all
x = 1, y = 1, rule = MAPUCQkTIILAEAiBWoPBXAIqGgWAIhqgCSTWEkAARYVtgoCNSYHAoAARBQMQhEqhQIxRCyCFAQQQMCBCK4log5Zww
o!
[[ AUTOSTART AUTOFIT THEME 9 ]]
Code: Select all
x = 2, y = 1, rule = MAPAOgg4gQjkipZDBEQwoRLIEFFBMJyY8M4wZRAZCCCCwQWGBSFxAAAJuCKeSAII0RAJRiFSQiwCRAISIWRICAMBQ
oo!
[[ AUTOSTART AUTOFIT THEME 2 ]]
Code: Select all
x = 7, y = 3, rule = MAPAQydAEBuUCZLAJY2A6CIwgQM+NAFAYOpALiBAoIQtJiCcQOEQA4bAIImeyAAEQCggFgc0FCSABiRAgAUgEoBgQ
2o2b3o$3b03b$b05b!
[[ AUTOSTART TRACK 1 1 X 215 Y 215 ZOOM 1 THEME 4 ]]
Re: Pattern viewer for forum threads
Please note: you will need to refresh your browser to use the new build
Enhancements since the last released build:
 added script command [[ NOGRAPH ]] which disables the population graph
 gives a slight performance increase when generation statistics are not displayed
 better error reporting for invalid MAP rules  test
 fixed an issue with MAP rules and bounded grids  test
 fit zoom and thumbnail mode now work together
 graphs now display properly in thumbnail mode  test
 graph colors were incorrect on some browsers
 AUTOSTART no longer runs patterns with invalid rules
 statistics generation was not being reset when new pattern loaded in existing Viewer
 fixed an issue with canonical representation of nontotalistic rules
Re: Pattern viewer for forum threads
Re: Pattern viewer for forum threads
There's just one letter change from A to C in the 77th position, right? Which is the 74th position after we remove "MAP", which is really position #73 since the initial "A" is position #0,_zM wrote:Can someone tell me what the difference between Life(MAPARYXfhZofugWaH7oaIDogBZofuhogOiAaIDogIAAgAAWaH7oaIDogGiA6ICAAIAAaIDogIAAgACAAIAAAAAAAA) and MAPARYXfhZofugWaH7oaIDogBZofuhogOiAaIDogIAAgAAWaH7oaIDogGiA6ICAAIAAaIDogIAAgCCAAIAAAAAAAA means in terms of transition(s)?
A = 000000, C = 000010, so that's adding a condition for a cell to turn ON, at neighborhood number 73*6+4 = 442. (The +4 is just because neighborhood numbering also starts with #0, so the "1" in the binary expansion of base64 "C" is in position #4.)
442 in binary is 110111010, which by LifeViewer's ruleinteger numbering means this neighborhood:
Code: Select all
1 1 0
1 1 1
0 1 0
Code: Select all
x = 8, y = 8, rule = MAPARYXfhZofugWaH7oaIDogBZofuhogOiAaIDogIAAgAAWaH7oaIDogGiA6ICAAIAAaIDogIAAgCCAAIAAAAAAAA
bo4bo$3o2b3o$b2o2b2o3$b2o2b2o$3o2b3o$bo4bo!
#C [[ STOP 1 ]]
As a shortcut, if there's only a singlebit difference like this, you can often do something like run a pi heptomino and notice where the explosion first becomes asymmetrical  in this case, at T=18 (extra ON cell in the right wing):
Code: Select all
x = 3, y = 3, rule = MAPARYXfhZofugWaH7oaIDogBZofuhogOiAaIDogIAAgAAWaH7oaIDogGiA6ICAAIAAaIDogIAAgCCAAIAAAAAAAA
obo$obo$3o!
#C [[ STOP 18 ]]
Re: Pattern viewer for forum threads
Thanks!dvgrn wrote:There's just one letter change from A to C in the 77th position, right? Which is the 74th position after we remove "MAP", which is really position #73 since the initial "A" is position #0,_zM wrote:Can someone tell me what the difference between Life(MAPARYXfhZofugWaH7oaIDogBZofuhogOiAaIDogIAAgAAWaH7oaIDogGiA6ICAAIAAaIDogIAAgACAAIAAAAAAAA) and MAPARYXfhZofugWaH7oaIDogBZofuhogOiAaIDogIAAgAAWaH7oaIDogGiA6ICAAIAAaIDogIAAgCCAAIAAAAAAAA means in terms of transition(s)?
A = 000000, C = 000010, so that's adding a condition for a cell to turn ON, at neighborhood number 73*6+4 = 442. (The +4 is just because neighborhood numbering also starts with #0, so the "1" in the binary expansion of base64 "C" is in position #4.)
441 in binary is 110111010, which by LifeViewer's ruleinteger numbering means this neighborhood:
So I'd expect that in the following test pattern, just the lower right one of the four 7bit groups below would have its central cell turned ON after one tick:Code: Select all
1 1 0 1 1 1 0 1 0
... Success!Code: Select all
x = 8, y = 8, rule = MAPARYXfhZofugWaH7oaIDogBZofuhogOiAaIDogIAAgAAWaH7oaIDogGiA6ICAAIAAaIDogIAAgCCAAIAAAAAAAA bo4bo$3o2b3o$b2o2b2o3$b2o2b2o$3o2b3o$bo4bo! #C [[ STOP 1 ]]
As a shortcut, if there's only a singlebit difference like this, you can often do something like run a pi heptomino and notice where the explosion first becomes asymmetrical  in this case, at T=18 (extra ON cell in the right wing):
Code: Select all
x = 3, y = 3, rule = MAPARYXfhZofugWaH7oaIDogBZofuhogOiAaIDogIAAgAAWaH7oaIDogGiA6ICAAIAAaIDogIAAgCCAAIAAAAAAAA obo$obo$3o! #C [[ STOP 18 ]]
Re: Pattern viewer for forum threads
Code: Select all
x = 9, y = 10, rule = B3/S23:T10+2,10
o$o8$8bo!
Code: Select all
x = 10, y = 9, rule = B3/S23:T10,10+2
2o8$9bo!
Re: Pattern viewer for forum threads
Code: Select all
x = 9, y = 133, rule = 23/34/256
6.yO$2yO5.yM$6.2yNyL$2.yIyJ2.yNyJ$.yGyK2yOyJyK2yI$yF2yHyK2yMyKyJ$.yDyH
2yKyDyC$2yCyEyD2yIyEyA$.yDyE2yGyE2yBxX$2.xUxV2yEyBxV$.xSxW2yCxVxW2xU$
xR2xTxW2yAxWxV$.xPxT2xWxPxO$2xOxQxP2xUxQxM$.xPxQ2xSxQ2xNxL$2.xIxJ2xQxN
xJ$.xGxK2xOxJxK2xI$xF2xHxK2xMxKxJ$.xDxH2xKxDxC$2xCxExD2xIxExA$.xDxE2xG
xE2xBwX$2.wUwV2xExBwV$.wSwW2xCwVwW2wU$wR2wTwW2xAwWwV$.wPwT2wWwPwO$2wO
wQwP2wUwQwM$.wPwQ2wSwQ2wNwL$2.wIwJ2wQwNwJ$.wGwK2wOwJwK2wI$wF2wHwK2wMwK
wJ$.wDwH2wKwDwC$2wCwEwD2wIwEwA$.wDwE2wGwE2wBvX$2.vUvV2wEwBvV$.vSvW2wC
vVvW2vU$vR2vTvW2wAvWvV$.vPvT2vWvPvO$2vOvQvP2vUvQvM$.vPvQ2vSvQ2vNvL$2.
vIvJ2vQvNvJ$.vGvK2vOvJvK2vI$vF2vHvK2vMvKvJ$.vDvH2vKvDvC$2vCvEvD2vIvEvA
$.vDvE2vGvE2vBuX$2.uUuV2vEvBuV$.uSuW2vCuVuW2uU$uR2uTuW2vAuWuV$.uPuT2uW
uPuO$2uOuQuP2uUuQuM$.uPuQ2uSuQ2uNuL$2.uIuJ2uQuNuJ$.uGuK2uOuJuK2uI$uF
2uHuK2uMuKuJ$.uDuH2uKuDuC$2uCuEuD2uIuEuA$.uDuE2uGuE2uBtX$2.tUtV2uEuBtV
$.tStW2uCtVtW2tU$tR2tTtW2uAtWtV$.tPtT2tWtPtO$2tOtQtP2tUtQtM$.tPtQ2tStQ
2tNtL$2.tItJ2tQtNtJ$.tGtK2tOtJtK2tI$tF2tHtK2tMtKtJ$.tDtH2tKtDtC$2tCtE
tD2tItEtA$.tDtE2tGtE2tBsX$2.sUsV2tEtBsV$.sSsW2tCsVsW2sU$sR2sTsW2tAsWsV
$.sPsT2sWsPsO$2sOsQsP2sUsQsM$.sPsQ2sSsQ2sNsL$2.sIsJ2sQsNsJ$.sGsK2sOsJ
sK2sI$sF2sHsK2sMsKsJ$.sDsH2sKsDsC$2sCsEsD2sIsEsA$.sDsE2sGsE2sBrX$2.rU
rV2sEsBrV$.rSrW2sCrVrW2rU$rR2rTrW2sArWrV$.rPrT2rWrPrO$2rOrQrP2rUrQrM$
.rPrQ2rSrQ2rNrL$2.rIrJ2rQrNrJ$.rGrK2rOrJrK2rI$rF2rHrK2rMrKrJ$.rDrH2rK
rDrC$2rCrErD2rIrErA$.rDrE2rGrE2rBqX$2.qUqV2rErBqV$.qSqW2rCqVqW2qU$qR
2qTqW2rAqWqV$.qPqT2qWqPqO$2qOqQqP2qUqQqM$.qPqQ2qSqQ2qNqL$2.qIqJ2qQqNqJ
$.qGqK2qOqJqK2qI$qF2qHqK2qMqKqJ$.qDqH2qKqDqC$2qCqEqD2qIqEqA$.qDqE2qGqE
2qBpX$2.pUpV2qEqBpV$.pSpW2qCpVpW2pU$pR2pTpW2qApWpV$.pPpT2pWpPpO$2pOpQ
pP2pUpQpM$.pPpQ2pSpQ2pNpL$2.pIpJ2pQpNpJ$.pGpK2pOpJpK2pI$pF2pHpK2pMpKpJ
$.pDpH2pKpDpC$2pCpEpD2pIpEpA$.pDpE2pGpE2pBX$2.UV2pEpBV$.SW2pCVW2U$R2T
W2pAWV$.PT2WPO$2OQP2UQM$.PQ2SQ2NL$2.IJ2QNJ$.GK2OJK2I$F2HK2MKJ$.DH2KDC
$2CED2IEA$.DE2GE2BA$2.2A2EBA$2.A2C2A$3.3A$4.A!
 gmc_nxtman
 Posts: 1148
 Joined: May 26th, 2015, 7:20 pm
Re: Pattern viewer for forum threads
It's simply because autofit only tracks cells in state1.drc wrote:Another simple glitch, try running AutoFit on this pattern posted by 83bismuth38:Code: Select all
x = 9, y = 133, rule = 23/34/256 6.yO$2yO5.yM$6.2yNyL$2.yIyJ2.yNyJ$.yGyK2yOyJyK2yI$yF2yHyK2yMyKyJ$.yDyH 2yKyDyC$2yCyEyD2yIyEyA$.yDyE2yGyE2yBxX$2.xUxV2yEyBxV$.xSxW2yCxVxW2xU$ xR2xTxW2yAxWxV$.xPxT2xWxPxO$2xOxQxP2xUxQxM$.xPxQ2xSxQ2xNxL$2.xIxJ2xQxN xJ$.xGxK2xOxJxK2xI$xF2xHxK2xMxKxJ$.xDxH2xKxDxC$2xCxExD2xIxExA$.xDxE2xG xE2xBwX$2.wUwV2xExBwV$.wSwW2xCwVwW2wU$wR2wTwW2xAwWwV$.wPwT2wWwPwO$2wO wQwP2wUwQwM$.wPwQ2wSwQ2wNwL$2.wIwJ2wQwNwJ$.wGwK2wOwJwK2wI$wF2wHwK2wMwK wJ$.wDwH2wKwDwC$2wCwEwD2wIwEwA$.wDwE2wGwE2wBvX$2.vUvV2wEwBvV$.vSvW2wC vVvW2vU$vR2vTvW2wAvWvV$.vPvT2vWvPvO$2vOvQvP2vUvQvM$.vPvQ2vSvQ2vNvL$2. vIvJ2vQvNvJ$.vGvK2vOvJvK2vI$vF2vHvK2vMvKvJ$.vDvH2vKvDvC$2vCvEvD2vIvEvA $.vDvE2vGvE2vBuX$2.uUuV2vEvBuV$.uSuW2vCuVuW2uU$uR2uTuW2vAuWuV$.uPuT2uW uPuO$2uOuQuP2uUuQuM$.uPuQ2uSuQ2uNuL$2.uIuJ2uQuNuJ$.uGuK2uOuJuK2uI$uF 2uHuK2uMuKuJ$.uDuH2uKuDuC$2uCuEuD2uIuEuA$.uDuE2uGuE2uBtX$2.tUtV2uEuBtV $.tStW2uCtVtW2tU$tR2tTtW2uAtWtV$.tPtT2tWtPtO$2tOtQtP2tUtQtM$.tPtQ2tStQ 2tNtL$2.tItJ2tQtNtJ$.tGtK2tOtJtK2tI$tF2tHtK2tMtKtJ$.tDtH2tKtDtC$2tCtE tD2tItEtA$.tDtE2tGtE2tBsX$2.sUsV2tEtBsV$.sSsW2tCsVsW2sU$sR2sTsW2tAsWsV $.sPsT2sWsPsO$2sOsQsP2sUsQsM$.sPsQ2sSsQ2sNsL$2.sIsJ2sQsNsJ$.sGsK2sOsJ sK2sI$sF2sHsK2sMsKsJ$.sDsH2sKsDsC$2sCsEsD2sIsEsA$.sDsE2sGsE2sBrX$2.rU rV2sEsBrV$.rSrW2sCrVrW2rU$rR2rTrW2sArWrV$.rPrT2rWrPrO$2rOrQrP2rUrQrM$ .rPrQ2rSrQ2rNrL$2.rIrJ2rQrNrJ$.rGrK2rOrJrK2rI$rF2rHrK2rMrKrJ$.rDrH2rK rDrC$2rCrErD2rIrErA$.rDrE2rGrE2rBqX$2.qUqV2rErBqV$.qSqW2rCqVqW2qU$qR 2qTqW2rAqWqV$.qPqT2qWqPqO$2qOqQqP2qUqQqM$.qPqQ2qSqQ2qNqL$2.qIqJ2qQqNqJ $.qGqK2qOqJqK2qI$qF2qHqK2qMqKqJ$.qDqH2qKqDqC$2qCqEqD2qIqEqA$.qDqE2qGqE 2qBpX$2.pUpV2qEqBpV$.pSpW2qCpVpW2pU$pR2pTpW2qApWpV$.pPpT2pWpPpO$2pOpQ pP2pUpQpM$.pPpQ2pSpQ2pNpL$2.pIpJ2pQpNpJ$.pGpK2pOpJpK2pI$pF2pHpK2pMpKpJ $.pDpH2pKpDpC$2pCpEpD2pIpEpA$.pDpE2pGpE2pBX$2.UV2pEpBV$.SW2pCVW2U$R2T W2pAWV$.PT2WPO$2OQP2UQM$.PQ2SQ2NL$2.IJ2QNJ$.GK2OJK2I$F2HK2MKJ$.DH2KDC $2CED2IEA$.DE2GE2BA$2.2A2EBA$2.A2C2A$3.3A$4.A!
Re: Pattern viewer for forum threads
Thanks for reporting, I'll take a look.wildmyron wrote:There is apparently a subtle bug in how LifeViewer handles toroidal boundary conditions with shifts along the yaxis.
Re: Pattern viewer for forum threads
Correct, standard AUTOFIT only tracks cells in state 1. However you can modify this with the HISTORYFIT script command or by pressing 'H' (shift and 'h') to toggle normal/history mode.gmc_nxtman wrote:It's simply because autofit only tracks cells in state1.drc wrote:Another simple glitch, try running AutoFit on this pattern
In HISTORYFIT mode LifeViewer will include any cell that was ever alive in the AUTOFIT calculation.
Re: Pattern viewer for forum threads
This has been fixed and will be in the next release build. Test case is here.rowett wrote:Thanks for reporting, I'll take a look.wildmyron wrote:There is apparently a subtle bug in how LifeViewer handles toroidal boundary conditions with shifts along the yaxis.
Re: Pattern viewer for forum threads
Thank you.rowett wrote:This has been fixed and will be in the next release build. Test case is here.rowett wrote:Thanks for reporting, I'll take a look.wildmyron wrote:There is apparently a subtle bug in how LifeViewer handles toroidal boundary conditions with shifts along the yaxis.

 Posts: 652
 Joined: June 14th, 2014, 5:03 pm
Re: Pattern viewer for forum threads
I think what gmc_nxtman wants is a way to track all nonstate0 cells.rowett wrote:Correct, standard AUTOFIT only tracks cells in state 1. However you can modify this with the HISTORYFIT script command or by pressing 'H' (shift and 'h') to toggle normal/history mode.gmc_nxtman wrote:It's simply because autofit only tracks cells in state1.drc wrote:Another simple glitch, try running AutoFit on this pattern
In HISTORYFIT mode LifeViewer will include any cell that was ever alive in the AUTOFIT calculation.