Code: Select all
x = 20, y = 20, rule = B3/S23
7bob5obob3o$2b2o2b2o2b3o2b5o$b2obo6bob3o$bob2obobo2bo$2b3o6bo$6b3o3b3o
$bobobobo3bob2o$2o3b2obo2bobo$3bobobo5bo$o8b2o2bo$2o7bo$5ob2o$2o3bo$ob
o2b5o$2bo2b2o$3o$bo$2o$2o$2o!
Code: Select all
x = 20, y = 20, rule = B3/S23
7bob5obob3o$2b2o2b2o2b3o2b5o$b2obo6bob3o$bob2obobo2bo$2b3o6bo$6b3o3b3o
$bobobobo3bob2o$2o3b2obo2bobo$3bobobo5bo$o8b2o2bo$2o7bo$5ob2o$2o3bo$ob
o2b5o$2bo2b2o$3o$bo$2o$2o$2o!
Code: Select all
x = 17, y = 10, rule = B3/S23
b2ob2obo5b2o$11b4obo$2bob3o2bo2b3o$bo3b2o4b2o$o2bo2bob2o3b4o$bob2obo5b
o2b2o$2b2o4bobo2b3o$bo3b5ob2obobo$2bo5bob2o$4bob2o2bobobo!
Code: Select all
x = 18, y = 17, rule = B3/S23
bo3bo6bo3bo$bo4bo4bo4bo$2bo3bo4bo3bo$3b4o4b4o$5bo6bo$3b3o6b3o$bob3o6b
3obo$o2bo4b2o4bo2bo$b2o5b2o5b2o$b2o12b2o$2bo12bo$2b3o8b3o2$3bo2bo4bo2b
o$4b10o$5b3o2b3o$8b2o!
Roughly how long did this search take to complete?Kazyan wrote:I've just completed a gfind search for 3c/8 orthogonal with bilateral symmetry at width 22. Negative result.
I broke it up enough that I can't give a firm estimate, but looking at the dump file dates, it's between 2 and 2.5 weeks of CPU time.velcrorex wrote:Roughly how long did this search take to complete?Kazyan wrote:I've just completed a gfind search for 3c/8 orthogonal with bilateral symmetry at width 22. Negative result.
It's Paul Tooke's gfind. I'd gotten annoyed with losing a bunch of search time when my OS froze or the power cut out.Scorbie wrote:Umm... Is there a way to generate and reload dumpfiles in an unmodified gfind? Or is it Paul Tooke's version of gfind?
A knightship can be oriented in two ways: the "long end" can extend in either the 1-cell or 2-cell direction of travel. Which case do you mean here? Or does your search cover both cases? Also, does your program extend the pattern in only one generation, or does it consider the pattern over its full period?moebius wrote:In the search for a period 6 knightship I can report failure at widths 11, 12, 13, and 14.... I am two weeks into the search for a width 15 period 6 knightship
Paul Tooke made some modifications to gfind which, among many things, enable searching for knightships (see here.) I believe I've searched up to width 14 for period 6 knightships. I estimated using gfind to search width 15 would take on the order of a year (or more.) I never tried the search. So, your estimate of time to complete the search with your program sounds encouraging to me.moebius wrote:In the search for a period 6 knightship I can report failure at widths 11, 12, 13, and 14. These searches failed to extend at approximately rows 24, 26, 28, and 30. The maximum extension pattern was approximately the same in each case. This is not encouraging.
I am two weeks into the search for a width 15 period 6 knightship, and it will either fail in about another two weeks or show signs of life and take months to complete. We will see what happens.
Code: Select all
x = 77, y = 29, rule = B3/S23
2b2o3bobo3b2o$2bobob2ob2obobo$2bo3bo3bo3bo$2bo2bo5bo2bo$3bobo5bobo$30b
3o11b3o$3bobo5bobo17bobo9bobo$2bo2bo5bo2bo17bo11bo$3o11b3o14bo13bo$31b
3o9b3o$obo11bobo13b2ob4o3b4ob2o15b6ob6o$2bo2b2o3b2o2bo20bo5bo20bo4bobo
4bo$bo13bo19b2o3b2o22bob2ob2obo$bo3bobobobo3bo17bo9bo21bo5bo$4bo2bobo
2bo20bo9bo20bobo3bobo$4b2obobob2o19b2o3bobo3b2o16b7ob7o$5b3ob3o20b2obo
bobobob2o17bo4bobo4bo$bo13bo17bo3bobo3bo20b2o5b2o$2bobo7bobo18b2o7b2o
20bo7bo$3b2o7b2o23bobo25bo5bo$3bob2o3b2obo21b2o3b2o21b2o7b2o$2b2obobob
obob2o48b2o7b2o$3bo3bobo3bo21bo5bo20b3ob2ob2ob3o$5bobobobo19b2obobo3bo
bob2o$3bobobobobobo20bobo3bobo17b2ob2obo3bob2ob2o$3bobobobobobo20b3o3b
3o18bob4o3b4obo$5bobobobo54bo3bo$4bo2bobo2bo19b2obo5bob2o17bob2o5b2obo
$5b2o3b2o21b2o7b2o19b2o7b2o!
Does that mean c/8 orths don't exist within 17 width?Kazyan wrote:Completed a gfind search for 1c/8 orthogonal, width 17, bilateral symmetry with gutter. Negative result. It took about 244 hours of CPU time.
No width-17 bilaterally-symmetric c/8 orthogonal ships with an empty column down the center exist.David wrote:Does that mean c/8 orths don't exist within 17 width?
Code: Select all
x = 15, y = 37, rule = B3/S23
7bo$5b5o$5bo4b2o$3bo3b3obo$3bo3b2obo$2bo3bo$2b2obo$2b4o2bo$4bo$2b4o3b
2o$2b3o2bob2o$6b2obobo$6b3o2b2o$b3o6b3o$2b2o5b2o2$7b3o2b2o$9bob3o$4b3o
3b3o$4bo6bo$3bo3b3ob2o$b2obo5b2obo$4bob3obo$o5bo2bo$4bob2o4bo$2bobo5b
2o$2bo5b2o$2bo$2bo3bobo$o3bo2b2o$o2b2o2b2o$3b3o$2ob2ob2o$2obo4b4o$bobo
b2o3b2o$2bo4bo5b2o$2b2o4bob2o!
Code: Select all
x = 25, y = 12, rule = B3/S23
2b2obo3b4o$bo2b3ob2ob5o$o3b2o2b2obo2bobo$o$o3bo5bo3bo$5bo4bo$2b2o10b2o
2b2o$5b2o6b2ob2o2bo2bo$5bobo10b5obo$12bo4b2o5bo$12bobobo$13bo!
moebius wrote:Width 15 period 6 knightship (2,1)/6 -- No ships found
Hmm... Could you tell me why? I don't have that intuition.moebius wrote: but means to me that unless incredible luck occurs no period 6 knightships exist at widths less than 17 or 18.
Wow! That does seem new! Congrats! And this tells me i) Nobody searched this with gfind or ii) We have a new fast program!moebius wrote:Width 13 period 5 diagonal (1,1)/5 -- Ship found
I believe this ship is new and at a 63 pip minimum count it would be the second smallest c/5 diagonal ship.Code: Select all
x = 25, y = 12, rule = B3/S23 2b2obo3b4o$bo2b3ob2ob5o$o3b2o2b2obo2bobo$o$o3bo5bo3bo$5bo4bo$2b2o10b2o 2b2o$5b2o6b2ob2o2bo2bo$5bobo10b5obo$12bo4b2o5bo$12bobobo$13bo!
Aha! Good to know Thanks!moebius wrote: I have run many searches over the years and I have noted that for almost any search as I increase the width the final partials get very long (5 to 10 times the width) at the widths just below where ships start being found.
No wonder you got something new and exciting. It sure is worth that 400 hours.moebius wrote:The c/5 diagonal search at width 13 ran 400 hours before it found that ship.
Code: Select all
x = 17, y = 10, rule = B3/S23
b2ob2obo5b2o$11b4obo$2bob3o2bo2b3o$bo3b2o4b2o$o2bo2bob2o3b4o$bob2obo5b
o2b2o$2b2o4bobo2b3o$bo3b5ob2obobo$2bo5bob2o$4bob2o2bobobo!
4 days and 4 hours, if that's what you're asking. And we're talking about non-stop here...Saka wrote:How much is 100 hours?
Ok, then I have been searching for a 2c/9 with wls for about a 5 days, so 125 hours of cpu, and it's still halfway! Also, what is the smallest width for c/8 diagonal? Also, how do you get gfind to search for "specific" speeds? I can only enter the period of the spaceship and then let gfind scroll through the translations (I do not know how to make gfind search specifically for 2c/5, but I can enter o5v and wait until it finishes c/5 and starts 2c/5)towerator wrote:4 days and 4 hours, if that's what you're asking. And we're talking about non-stop here...Saka wrote:How much is 100 hours?
Code: Select all
x = 17, y = 10, rule = B3/S23
b2ob2obo5b2o$11b4obo$2bob3o2bo2b3o$bo3b2o4b2o$o2bo2bob2o3b4o$bob2obo5b
o2b2o$2b2o4bobo2b3o$bo3b5ob2obobo$2bo5bob2o$4bob2o2bobobo!
Are you currently running searches with the other symmetries, because Codeholic's table of Known spaceships by width has some fairly small numbers on the row for (1,0)c/8. I just ran width 13 (l112) for odd bilateral symmetry which took less than 12 hours. I expect the l128 search will take a similar time to the one above. I'm currently running 'gfind o8n1vl112' just to have a look at the even symmetry partials as well. If no one else is running them yet, I'll run the l128 searches over the next week or two.Kazyan wrote:Completed a gfind search for 1c/8 orthogonal, width 17, bilateral symmetry with gutter. Negative result. It took about 244 hours of CPU time.
Interesting partials, though:
Code: Select all
<snip>
Code: Select all
x = 112, y = 20, rule = B3/S23
2bo3bo3bo40bob2obob2obo39bo2b2ob2o2bo$51bo3bobo3bo42b2ob2o$2b2obobob2o
40bo3bobo3bo$bobobobobobo43bobo43bob2o3b2obo$2ob2o3b2ob2o39bo2bobo2bo
40bo2bo3bo2bo$b3obobob3o41b2o3b2o43b2o3b2o$b5ob5o$4b2ob2o45bo3bo45bo3b
o$2bob5obo42bobobobo43bobobobo$2b2o5b2o44bobo47bobo$4bo3bo46bobo47bobo
$4b2ob2o43bo2bobo2bo41bo2bobo2bo$o4bobo4bo38bobobobobobo39bobobobobobo
$bo2b2ob2o2bo40b3o3b3o41b3o3b3o$2b2o5b2o2$6bo46bo5bo43bo5bo$5bobo44bob
o3bobo41bobo3bobo$5bobo44bobo3bobo41bobo3bobo$6bo46bo5bo43bo5bo!