Originally posted by SophyI meant it would be too easy to pick apart your spelling and grammar. The fastest stalemate appears to belong to well-known puzzle composer Sam Loyd:
Then, can you show it to me ?
1.e3 a5 2.Qh5 Ra6 3.Qxa5 h5 4.Qxc7 Rah6 5.h4 f6 6.Qxd7+ Kf7 7.Qxb7 Qd3 8.Qxb8 Qh7 9.Qxc8 Kg6 10.Qe6
Apparently Frederick Rhine had to have a kick at the can too:
1.d4 c5 2.dxc5 f6 3.Qxd7+ Kf7 4.Qxd8 Bf5 5.Qxb8 h5 6.Qxa8 Rh6 7.Qxb7 a6 8.Qxa6 Bh7 9.h4 Kg6 10.Qe6
Originally posted by afxNot so easy to do that, even for silicon.
Lloyd showed us this beautiful stalemate in 10..
But nobody proofed, that this is really the fastest one.
Did anyone //proof//, that there is no stalemate in 9?
Even with the silicon friend?
18 ply of brute-force calculation takes a looooong time still. [Plus you need a custom-written program just for the task.]
Originally posted by SwissGambitI did not say, that it is easy!
Not so easy to do that, even for silicon.
18 ply of brute-force calculation takes a looooong time still. [Plus you need a custom-written program just for the task.]
Brute force is obviously the wrong way.
But think of a retro game, b.f. would be no solution, either!
You have here a very complicated retro, even the end position
is not fixed, just the 18 ply and the stalemate.
The "custom written program" is not the problem. Firstly, in principle
you need one for every retro game.
Secondly, I could use the one I have written already ;-)
Originally posted by afxI'm not sure about your use of terminology.
I did not say, that it is easy!
Brute force is obviously the wrong way.
But think of a retro game, b.f. would be no solution, either!
You have here a very complicated retro, even the end position
is not fixed, just the 18 ply and the stalemate.
The "custom written program" is not the problem. Firstly, in principle
you need one for every retro game.
Secondly, I could use the one I have written already ;-)
If, by 'retro game', you mean 'proof game', then there are already programs that will solve most of those. And you wouldn't need multiple programs for it.
I would call this a 'construction task'. There are few programs that actually compose retro problems, and that's what you'd need to write [maybe your program indeed does this; again, I'm not quite sure what some of your terms mean].