ConwayLife.com

Posted: **March 10th, 2015, 9:37 pm**

I'm currently looking for a heisenburp involving a block (or other common still life) being the subject of the heisenburp, another common still life, and two gliders traveling in the same direction. The end result should be a glider traveling in the opposite direction only if the heisenburped SL is there (or not), and nothing in the case of the other SL presence parity. Said glider should be clear of that SL diagonally, as there will be a string of such SLs. (A small bit of debris is allowable, as another glider could be sent which kickbacks the original result glider, or gets rid of the debris, but I would prefer it if there were no debris left in either case.) Here's a failed example:

Code: Select all

x = 51, y = 28, rule = LifeHistory
26.A22.A$25.A.A20.A.A$16.2C7.A.A11.2D7.A.A$16.2C8.A12.2D8.A9$13.2A21.
2A$12.A.A20.A.A$14.A22.A11$3A20.3A$2.A22.A$.A22.A!

Anything that would work here?

Posted: **March 10th, 2015, 10:09 pm**

Can you post an RLE?
I'm Life History challenged.
triller

Posted: **March 11th, 2015, 4:22 am**

Would you please clarify some restrictions? Is 2 still-lifes the maximum? Is it a strict restriction, that all still-lifes should be common? Does "produces nothing" mean that it eats the input gliders, or it could be that it lets them through? Is it a strict requirement, that there might be only two input gliders, no more, no less? Must they be on the same lane, or it's arbitrary? The distance between them is arbitrary, I assume?

Posted: **March 11th, 2015, 10:10 am**

triller wrote:Can you post an RLE? I'm Life History challenged.

Wait a minute. As of a couple of years ago, hadn't you started to be able to see things in color...?

LifeHistory is only a very thin disguise for RLE, though scripts are also available if you have Python installed (click the download link to "LifeHistory archive", which contains a Scripts subfolder).

Failing that, here are the results of a search-and-replace done in a text editor. Replace A->o, B->., C->o, D->., etc., and the pattern will magically turn into working (if not exactly optimal) RLE:

Code: Select all

x = 77, y = 74, rule = B3/S23

52.o.o$41.o8.o$55.o$41.o$55.o$41.o11.o2$41.o9.o2$41.o8.o.o.2o6$52.o

22.o$51.o.o20.o.o$42.2o7.o.o11.2.7.o.o$42.2o8.o12.2.8.o4$24.o$23.o.o

2$22.o3.o2$22.o.o.o12.2o21.2o$38.o.o20.o.o$22.o3.o13.o22.o2$22.o3.o5$

13.o.o$13.o3.o2$13.o3.o$26.3o20.3o$13.o.o12.o22.o$17.o9.o22.o$13.o$

17.o$13.o.o8$16.o2$8.o5.o2$8.o3.o2$8.o.o2$8.o.o.o.o4$2.o.o$o4.o2$o2$o

2$o4.o$2.o.o!

#C [[ ZOOM 5 ]]

@Extrementhusiast: I think there are a couple of little-known 1D and 2D stable memory experiments from years ago, that might possibly fit what you're looking for... Actually there may be something even simpler, but I can't tell: couldn't quite decode whether "that SL" was "the heisenburped SL" or "the other SL"

I've added some labels above as a crutch for my mental limitations. Do I have this right?

Glider A hits SL#2 to produce an active reaction.
Active reaction touches location of SL#1, producing either
- empty space if SL#1 not present, or
- return glider C if SL#1 is present.
Gliders A, B, and C should be on lanes that don't interfere with other SL#1s on the same diagonal.
Glider C's lane can overlap SL#2.
Double-checking: SL#2 does not have to remain after the reaction. Ideally only SL#1 (if present) will remain.

So... is the above pattern a failure only because it leaves behind a beehive in the absence of SL#1?

Posted: **March 11th, 2015, 10:20 am**

dvgrn wrote:@Extrementhusiast: I think there are a couple of little-known 1D and 2D stable memory experiments from years ago, that might possibly fit what you're looking for... Actually there may be something even simpler, but I can't tell: couldn't quite decode whether "that SL" was "the heisenburped SL" or "the other SL"

I've added some labels above as a crutch for my mental limitations. Do I have this right?
Glider A hits SL#2 to produce an active reaction.

Active reaction touches location of SL#1, producing either
empty space if SL#1 not present, or

return glider C if SL#1 is present.

Gliders A, B, and C should be on lanes that don't interfere with other SL#1s on the same diagonal.

Glider C's lane can overlap SL#2.

Double-checking: SL#2 does not have to remain after the reaction. Ideally only SL#1 (if present) will remain.
So... is the above pattern a failure only because it leaves behind a beehive in the absence of SL#1?

Yes, all that is accurate. However, I am also allowing the possibility for glider C to be present if SL#1 is not there, and for glider C not to be present when SL#1 is there.

Posted: **March 11th, 2015, 12:23 pm**

Extrementhusiast wrote:Yes, all that is accurate. However, I am also allowing the possibility for glider C to be present if SL#1 is not there, and for glider C not to be present when SL#1 is there.

The first run through my very old email (pre-Gmail, for me anyway -- January 2004) turned up some ideas, but no exact matches. Paul Chapman and I were calling this kind of reaction a "non-destructive read", or "ND-read", at the time:

Code: Select all

#C duplicate a block if it exists on a diagonal tape
x = 78, y = 38, rule = B3/S23
2o38b2o$2o38b2o8$9b2o38b2o$9b2o38b2o$17b2o38b2o$17b2o2b2o34b2o2b2o$21b
obo37bobo$21bo39bo4$18b2o$18b2o8$27b2o38b2o$27b2o38b2o8$36b2o38b2o$36b
2o38b2o!

There are ways of adding a glider B to create two different objects depending on the presence of the block, but I don't see a simple solution for a clean return glider C. Maybe a three-glider salvo would do it. Or if SL#2 is allowed to be a three-block constellation, I can patch together something that works -- and the two gliders don't even have to be synchronized:

EDIT: Found an easy improvement to a 2sL constellation, again with two independent gliders. The 3-block one is off-viewer now, over on the right. Might need an automated search to get a single SL#2 that works.

Code: Select all

x = 300, y = 56, rule = B3/S23

7$15b2o68b2o$15b2o68b2o92b2o19b2o27b2o19b2o$179b2o19b2o27b2o19b2o$204b

2o48b2o$41bo69bo92b2o48b2o$26b2o12bobo53b2o12bobo$21b2o3b2o12b2o49b2o

3b2o12b2o78b2o48b2o$21b2o68b2o92b2o3b2o43b2o3b2o$185b2o48b2o4$27b2o$

27b2o162b2o$191b2o4$33b2o68b2o$33b2o68b2o92b2o48b2o$197b2o48b2o4$39b2o

68b2o$39b2o68b2o92b2o48b2o$50b2o68b2o81b2o48b2o$50bobo67bobo91b2o48b2o

$50bo69bo93bobo47bobo$214bo49bo4$64b2o68b2o$64bobo67bobo92b2o48b2o$64b

o69bo94bobo47bobo$229bo49bo!

#C [[ THUMBNAIL HEIGHT 300 AUTOSTART GPS 20 LOOP 200 X -60 Y 8 ZOOM 5.6 ]]

Posted: **March 11th, 2015, 7:45 pm**

dvgrn wrote:
triller wrote:Can you post an RLE? I'm Life History challenged.
Wait a minute. As of a couple of years ago, hadn't you started to be able to see things in color...?

Got lazy after a recent crash and have reverted (for now) to Golly 1.3, which was included on the most recent backup I'd bothered to make. Should do that more often (backup that is). Of all my flaws, procrastination is probably the one I most excel at.

triller

Posted: **March 12th, 2015, 7:04 am**

Here is a block heisenburp reaction I was found.

Code: Select all

x = 192, y = 43, rule = LifeHistory

50.2C100.2D$50.2C100.2D14$28.2A42.2A56.2A42.2A$27.ABA4.2A30.2A4.ABA

54.ABA4.2A30.2A4.ABA$26.3BA4.2A30.2A4.A3B52.3BA4.2A30.2A4.A3B$25.4B

44.4B50.4B44.4B$24.4B46.4B48.4B46.4B$23.4B48.4B46.4B48.4B$22.4B50.3B

2A43.4B50.3B2A$21.4B52.2BABA41.4B52.2BABA$20.4B54.BA3B39.4B54.BA3B$

19.4B56.5B37.4B56.5B$18.4B58.5B35.4B58.5B$17.4B60.5B33.4B60.5B$16.4B

62.5B31.4B62.5B$15.4B64.5B29.4B64.5B$14.4B66.5B27.4B66.5B$13.4B68.5B

25.4B68.5B$12.4B58.2A10.4B24.4B58.2A10.4B$11.4B35.2A21.2A2B10.3B23.4B

35.2A21.2A2B10.3B$10.4B36.2A22.BA2B10.2B22.4B36.2A22.BA2B10.2B$9.4B

62.4B10.B21.4B62.4B10.B$7.2A3B64.4B29.2A3B64.4B$6.ABA2B66.4B27.ABA2B

66.4B$5.3BAB68.4B25.3BAB68.4B$4.5B70.4B23.5B70.4B$3.5B72.4B21.5B72.4B

$2.5B74.4B19.5B74.4B$.5B76.4B17.5B76.4B$5B78.4B15.5B78.4B!

I already tried to find this reaction to make 2D Stable Block Memory. viewtopic.php?f=2&t=542 But, It need two directions of glider stream.

ConwayLife.com

Searching for a block heisenburp

Searching for a block heisenburp

Re: Searching for a block heisenburp

Re: Searching for a block heisenburp

Re: Searching for a block heisenburp

Re: Searching for a block heisenburp

Re: Searching for a block heisenburp

Re: Searching for a block heisenburp

Re: Searching for a block heisenburp