Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > sci.physics > #885010
| From | Physfitfreak <Physfitfreak@gmail.com> |
|---|---|
| Newsgroups | comp.os.linux.advocacy, sci.physics |
| Subject | Re: A Problem To Solve :-) |
| Date | 2024-02-04 19:53 -0600 |
| Message-ID | <uppf2e$1bq1i$1@solani.org> (permalink) |
| References | <uog01l$mi9n$1@solani.org> <17ac13c4ae353932$16712$1979536$802601b3@news.usenetexpress.com> <uohk04$ndab$2@solani.org> <up4385$11vs3$1@solani.org> <upl2ru$19kpu$1@solani.org> |
Cross-posted to 2 groups.
On 2/3/2024 4:00 AM, Physfitfreak wrote: > "In each of my parties, a session is always included in which a > chessboard is placed on the floor, with no chess pieces on it. There is > a contest, and the winner is blindfolded and given two random chess > pieces of same color - but not any pawns - out of my pocket, to place > somewhere on the chessboard by the winner, in two of the squares. Then > the blindfold is removed and the winner will look at the chessboard and > counts the number of different moves he can make with the chess pieces > from the squares that they are in. The winner will get as many gold > coins from me as that count is. If I know in advance which two pieces > will be given to the winner, I need to know how many gold coins I should > bring with me to the party, so I could never find myself with not enough > coins to give to the winner, and never carry with me even one gold coin > that would never be needed to be given to the winner. Find how many > coins I should bring with me to the party." Looks like for the sub-"code monkeys" a bit of more explanation is due. Holaku will give one gold coin for every different first move that the winner can make on the board. Example. If the two pieces happen to be two bishops, and if the blindfolded winner happened to place one at the first square on the left of the bottom row, and the other on the last square on the far right of the bottom row, then winner will get 14 gold coins.
Back to sci.physics | Previous | Next — Previous in thread | Next in thread | Find similar
Re: A Problem To Solve :-) Physfitfreak <Physfitfreak@gmail.com> - 2024-01-27 17:22 -0600
Re: A Problem To Solve :-) Farley Flud <ff@linux.rocks> - 2024-01-28 12:31 +0000
Re: A Problem To Solve :-) Physfitfreak <Physfitfreak@gmail.com> - 2024-01-28 16:44 -0600
Re: A Problem To Solve :-) Farley Flud <ff@linux.rocks> - 2024-01-29 08:28 +0000
Re: A Problem To Solve :-) Athel Cornish-Bowden <me@yahoo.com> - 2024-01-29 11:53 +0100
Re: A Problem To Solve :-) Physfitfreak <Physfitfreak@gmail.com> - 2024-02-02 23:56 -0600
Re: A Problem To Solve :-) Physfitfreak <Physfitfreak@gmail.com> - 2024-01-30 01:25 -0600
Re: A Problem To Solve :-) Physfitfreak <Physfitfreak@gmail.com> - 2024-01-31 18:18 -0600
Re: A Problem To Solve :-) Stéphane CARPENTIER <sc@fiat-linux.fr> - 2024-02-02 21:49 +0000
Re: A Problem To Solve :-) Physfitfreak <Physfitfreak@gmail.com> - 2024-02-03 04:00 -0600
Re: A Problem To Solve :-) Farley Flud <ff@linux.rocks> - 2024-02-03 16:19 +0000
Re: A Problem To Solve :-) Physfitfreak <Physfitfreak@gmail.com> - 2024-02-03 16:17 -0600
Re: A Problem To Solve :-) Stéphane CARPENTIER <sc@fiat-linux.fr> - 2024-02-04 14:24 +0000
Re: A Problem To Solve :-) Physfitfreak <Physfitfreak@gmail.com> - 2024-02-04 19:53 -0600
Re: A Problem To Solve :-) Physfitfreak <Physfitfreak@gmail.com> - 2024-02-05 01:51 -0600
Re: A Problem To Solve :-) Physfitfreak <Physfitfreak@gmail.com> - 2024-02-05 19:39 -0600
Re: A Problem To Solve :-) Farley Flud <ff@linux.rocks> - 2024-02-06 21:00 +0000
Re: A Problem To Solve :-) Physfitfreak <Physfitfreak@gmail.com> - 2024-02-06 15:43 -0600
Re: A Problem To Solve :-) Physfitfreak <Physfitfreak@gmail.com> - 2024-02-06 18:19 -0600
Re: A Problem To Solve :-) Physfitfreak <Physfitfreak@gmail.com> - 2024-02-09 10:58 -0600
Re: A Problem To Solve :-) Physfitfreak <Physfitfreak@gmail.com> - 2024-02-06 21:55 -0600
Re: A Problem To Solve :-) Physfitfreak <Physfitfreak@gmail.com> - 2024-02-06 22:06 -0600
Re: A Problem To Solve :-) Physfitfreak <Physfitfreak@gmail.com> - 2024-02-12 01:39 -0600
Re: A Problem To Solve :-) Physfitfreak <Physfitfreak@gmail.com> - 2024-02-14 12:50 -0600
Re: A Problem To Solve :-) Lester Thorpe <lt@gnu.rocks> - 2024-02-14 20:33 +0000
Re: A Problem To Solve :-) Athel Cornish-Bowden <me@yahoo.com> - 2024-02-15 11:11 +0100
Re: A Problem To Solve :-) Physfitfreak <Physfitfreak@gmail.com> - 2024-02-15 13:22 -0600
Re: A Problem To Solve :-) Physfitfreak <Physfitfreak@gmail.com> - 2024-02-18 01:51 -0600
Re: A Problem To Solve :-) Physfitfreak <Physfitfreak@gmail.com> - 2024-02-21 00:38 -0600
Re: A Problem To Solve :-) Physfitfreak <Physfitfreak@gmail.com> - 2024-02-27 16:13 -0600
Re: A Problem To Solve :-) Kuang Tze Kui <ugdiun@kgknudu.cn> - 2024-02-27 22:46 +0000
Re: A Problem To Solve :-) Arindam Banerjee <banerjeeadda1234@gmail.com> - 2024-02-09 09:47 -0800
Re: A Problem To Solve :-) Arindam Banerjee <banerjeeadda1234@gmail.com> - 2024-02-12 04:41 -0800
csiph-web