x = 151, y = 228, rule = LifeHistory
simsim314 wrote:Another question that bothers me, is there a good collection of recipes for glider shoot from slow salv[o]? everything I could find is of construction nature - block moves etc.
oblique wrote:I'm not quite getting the search space you are describing here. Do you mean: all gliders in one recipe must have the same color? Like in skiping every other "lane"? What are the other parameters of the search?
x = 17, y = 23, rule = B3/S23
#C 8-glider m-12,-10:E-9 E-13 E-13 O-13 E-9 E-5 O-9 O-5
x = 235, y = 238, rule = B3/S23
simsim314 wrote:Here is a recipe for a 3 collinear glider pairs for "slow" shoot. I also "proved" just by brute force that two collinear glider pairs always leave some debris.
simsim314 wrote:Let's do some thinking: assuming we'll find some compact "two-glider input" duplicator with simple interpreter (one comes to my mind is just two silvers with two semi Snarks, allowing any distance we choose).
simsim314 wrote:Also as a thought it might be possible to create some part of the new copy using direct shoots from the salvo itself, which might make it even faster than current Geminoid. Of course tweaking the Geometry is necessary, placing most of the "mass" of the new copy in the "shoot range" of the salvo.
dvgrn wrote:Did you look at all seven possible sets of opposing glider lanes?
x = 401, y = 398, rule = LifeHistory
dvgrn wrote:...using tandem gliders
dvgrn wrote:Herschel transceivers are not much bigger than Silver reflectors
dvgrn wrote: Some variant of this idea might even set a new record for the smallest Life universal constructor
dvgrn wrote:Some variant of this idea might even set a new record for the smallest Life universal constructor, which is currently somewhere around 44.5 still lifes in about a 200x200 bounding box.
#C 124x133 39sL replicator unit, possibly?
x = 257, y = 267, rule = B3/S23
simsim314 wrote:dvgrn wrote:...using tandem gliders
I guess you mean few glider tracks?dvgrn wrote:Herschel transceivers are not much bigger than Silver reflectors
Hmm...do you mean there is a faster way to convert glider into Hershel?
dvgrn wrote:I just had a new idea that needs investigating..
x = 1997, y = 2008, rule = LifeHistory
x = 4215, y = 4321, rule = LifeHistory
simsim314 wrote:I've "proved" universality of this constructor. Using trial and error I've found the bounds of both white and black glider shoots. Using a little bit modified recipes for arm movements it's easy to see that the bounds of the UC shoots are much wider than the trace of the lowest and the highest gliders in the recipes. To shoot a different color glider, one should move the block by (2,1) and use the same recipe.
x = 1830, y = 1850, rule = LifeHistory
simsim314 wrote:EDIT3: While I was thinking of it, due to the fact the current shooting range is actually considerably bigger than the optimized recipes range (which probably could be even more optimized as well), maybe it's possible to squeeze some extra still life and box-size optimization, cutting somewhere in the Hershel conduit...
simsim314 wrote:...I'm conducting some experiment with small width salvos. I noticed that the current recipes didn't consider "glider range" as optimization parameter... I'm currently investigating what is the smallest salvo width for "Universality". But Before that, I just want to have a "thin" recipe collection.
simsim314 wrote:I think it's more theoretical question, what is the smallest UC possible? Even if really ineffective. This question also has few meanings: is only Spartan components are permissible? or any still life? For computers guns and such there is no reason not to use the most advanced technology available, but for replicators it's better to use the Spartan toolkit.
simsim314 wrote:The other question which is more "practical" is: what is the smallest "Full Range" opposite collision UC. For this one I really need the Herschel covered.
dvgrn wrote: sort the block-move table by glider range. See attached.
x = 426, y = 182, rule = LifeHistory
dvgrn wrote:it's perfectly okay to include non-Spartan components if they really improve functionality tremendously
simsim314 wrote:Now it would be nice to build something with it... just as an experiment.
simsim314 wrote:By the way do you have some "conventions" for salvo recipes? I saw that you have script for some "code", but I couldn't understand it, just saw it worked. I could do some "reverse engineering", just find gliders, recognize their locations. But if there is something out of the box, simple enough, I could definitely use it.
EDIT: I've found this one http://conwaylife.com/forums/viewtopic.php?p=8186#p8186 and it's definitely was understandable. The only question is what if I want to create some "pattern" is there a recipes for still life creation as well?
EDIT2: I've found this one http://conwaylife.com/forums/viewtopic.php?p=9590#p9590 but it's definetly a partial info, that does not include the location of each still life that was created.
simsim314 wrote:I think we need some standard notions for still life, their orientation and locations (like we have for gliders). I guess you have some "standard" as a working prototype that you used in the Geminoid project, but I can't find any mention of it.
simsim314 wrote:So first of all I've found a way to diagonally move traffic light with 2-3 glider shoots, and 4 range by your notation (I didn't get how you calculate range, for me it's just natural to use glider level of freedom. So having only 3 levels of freedom or making a mark of 6 "blue horizontal cells" in LifeHistory), I managed to create all necessary movements.
simsim314 wrote:Now the tricky part is to find thin glider shooters.
simsim314 wrote:Another though[t]: if we will use this arm-less approach for UC's, and use two units so we have 90 degree instead of slow salvo, I don't think we have good recipes for the parts that "outside the bounds" except of slow salvo (X2 because we have two units). It's probable that placing "outside the bounds" can be optimized with "90 degree" two glider shoot. Kinda "90 degree-two-glider based slow salvo".
x = 250, y = 269, rule = B3/S23
dvgrn wrote:Do you have a name for your new 180-degree-gliders design
dvgrn wrote:but not the kind of script that anyone else would have an easy time learning how to use!
dvgrn wrote:Those recipes all include the new location of the target block
dvgrn wrote: I should really have a similar stamp collection for all the other Spartan objects -- just haven't gotten around to it yet.
dvgrn wrote: that can start from an RLE pattern, or perhaps an ordered list of small objects, and reliably create a slow-salvo recipe that can build the full pattern
dvgrn wrote:..."Blockic compiler" stage...
simsim314 wrote:dvgrn wrote:I should really have a similar stamp collection for all the other Spartan objects -- just haven't gotten around to it yet.
You said you have a db of all those recipes, you just don't have time to compile a query? Or is it all somewhat more "messy"?
dvgrn wrote: Then again, one of Paul Chapman's early searches found a universal toolkit with slow glider pairs following each other on a single lane...
dvgrn wrote:. I'm betting that width 4 will be enough
dvgrn wrote:is there an equivalent set of BLACK and WHITE glider outputs at some odd offset?
dvgrn wrote:It will take a bit longer to come up with a good "stamp collection"
dvgrn wrote:Here's a sample 45sL replicator
x = 363, y = 316, rule = LifeHistory
simsim314 wrote:dvgrn wrote:It will take a bit longer to come up with a good "stamp collection"
...I wanted to use the same idea, to take recipes from Gemini two arm construction. It's also not as trivial as it seems, Gemini uses pretty advanced placing patterns that go to the edge very efficiently.
#C recent version of calcyman's SSL.mc, including tub-with-tail eaters
x = 4101, y = 373, rule = LifeHistory
simsim314 wrote:Well if I understand you correctly, BLACK and WHITE recipes are totally different, it's just pure chance they both ended in the same lanes. So no, there is no "odd" offset for timing. But maybe I misunderstood your question...
dvgrn wrote:I don't know whether to keep the attempts at armless R.U.s that turn out to have same-color outputs
simsim314 wrote:Also if we on it: do we have "biased recipes", that have preference for "some color". I mean if the recipe has option to use both white and black with same success it will always use white/black?
x = 239, y = 238, rule = LifeHistory
x = 265, y = 287, rule = LifeHistory
x = 774, y = 776, rule = LifeHistory
x = 783, y = 788, rule = LifeHistory
Users browsing this forum: No registered users and 2 guests