Skip to main content

Friday Quiz problem 18 Mar 22 - how many beans make 5?

H
ere's today's question:
I played 40 games of backgammon and scored 25 points.  A win counts as one point, a draw counts as half a point, and a loss counts as zero points.  How many more games did I win than lose?


At first glance it looks as if you can 'formularise' this (ie w + d/2 + 0l = 25)  but you can't solve that, it seems as if there are many values that could work.

My title refers to an old kids' joke - "how many beans make 5?" The answer I knew was "two beans, a bean and a half, half a bean and a bean" (said quickly!) But other kids had their own version of this and you can have many combinations of beans and half-beans. 
 
The question is curiously-worded. "how many more times did I win than lose?"  

My starting point was that if you could see all the possible values of w, d and l  that total 25 points, the pattern would be obvious.

So the problem becomes one of printing out these values.

The easiest brute-force way is to nest 3 loops 0 - 40, and ignore unless the 3 add up to 40. But that's inefficient and inelegant.

We're going to win anywhere between 0 and 40 games:

10 FOR W = 0 TO 40

(I'm using BASIC, it's neat when it comes to nested loops and printing variables).

For each of those cases, the remainder (40-W) will be split between draws and losses. If you know the wins and draws, then the loses will be 40-(D+W). That's only two loops, with the inner one becoming smaller each time.

Then we're only interested in those combinations where the points add up to 25 (see line 40) 

10 FOR W = 0 TO 40                                                              
20 FOR D = 0 TO (40-W)                                                            
30 LET L = 40 - (D+W)                                                     
40 IF (W*2)+D=50 THEN PRINT W; D; L; (W-L)                                                    
50 NEXT:NEXT

(I've doubled the values in 40 so that we're dealing with integers. Using a floating-point value when you're testing equality is asking for trouble.)
That's still a lot of looping. But it's done in a couple of seconds.

Answer

Seeing the output from this program makes it obvious that it doesn't matter that we don't know the actual number of games won/lost/drawn, because the answer is always 10 for all possible values.

I had to look at the results with my human eyes to see the answer. The question asked about the difference between wins and loses. So perhaps 40 could also print that difference, to make it more obvious that it's always 10:

40 IF (W*2)+D=50 THEN PRINT W; D; L; (W-L) 

Efficiency

To make this more efficient, we can think about upper and lower limits. It's obvious now that if we win any more than 25 games, that makes more than 25 points, so that's our upper limit for W in line 10

There's a lower limit too - we can't make 25 points entirely from draws (half-points) because there aren't enough games. We can see from the result of the program that if we draw 30 (15 points) that's the maximum number of draws. Any more than that and it's not possible to make enough wins to make up the points.  But I'm not sure whether it's possible to calculate that, it only becomes clear when you see the values. 

So 

10 FOR W = 0 TO 25 gives us the same result and is much quicker. 

The question that remains is: is it possible to arrive at the answer - that wins are always 10 more than losses - using reason and without actually looking at the numbers and observing that fact?

Comments

Popular posts from this blog

RC2024/10 - my entry

A while ago I made this MIDI module for RC2014: It works but a better design would have its own serial chip and port decoding.  As it is, it provides the MIDI interface and a clock signal for the second SIO2 serial port. This means that it requires a little setting up and will only work for RC2014s with an SIO2 (and port B not already used). I think people might reasonably expect it to be plug-and-play and self-contained, ie do all the serial itself. My challenge to myself is to:  learn how to connect a serial chip (probably 68B50 ACIA) to receive the incoming MIDI and to serialise outgoing MIDI design the module, including the port decoding write a library so that it can easily be used on any RC2014. Potential applications include a MIDI sequencer and using incoming MIDI to trigger notes on the AY or SID sound chips. Entering the Retro Challenge 2024 (aka RC2024/10)  has given me an incentive to get on with this! I'm happy to see several more entries in the RC2014 category, includ

How to convert images for TMS9918A graphics on the RC2014

For me, graphics capability is essential for an 8-bit computer. My graphics chip of choice for the RC2014 is the very capable TMS9918A. It has 15 colours, sprites, several modes and a max resolution of 256x192. It makes arcade-style games possible, such as Tut-Tut above.  I enjoy simply displaying images and have a bunch on my CF card (my 'hard drive') and have written image viewer and slideshow apps to display them. Some useful links: Convert9918 Tutorial of Convert9918's settings Multipaint J B Langston's TMS9918A video module my own TMSEMU video module my respository of TMS9918A software, games and .s2/.sc3 images Image conversion I did dabble in writing my own utility to convert .png images but then settled on the Multipaint app which can open a png in a MSX 'screen 2', allow you to tidy it up with paint tools and save as a .sc2 file. (An sc2 file is little more than a video-memory dump and so it's easy to blast that back into vram to display the image.

IM53 8080 birthday cake

 Each year I've been trying to get more creative with ideas for Spencer's birthday cake. The plan this year was to incorporate LEDs in place of candles. I eventually settled on an Altair / IMSAI / PDP -style computer since those are the type of computers that inspired his RC2014. The IMSAI 8080 has the most colourful switches as well as a name that I could twist. The thought that it could show randomly flashing lights (as if the computer were running) and that it could also play a game of 'kill the bit' was very appealing. A plan formed to use a capacitive touch pad on the cake itself. The first job is to bake the fruitcake. I often use a 7" square tin and one of those cut in half and rearranged makes a cake of suitable proportions.  Even after taking a slice off the faces to make them nice and square, there are still some rounded corners, so after putting on the marzipan, I used more marzipan as a filler to flatten the whole thing. Even though I wanted to end up w