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

ZX81 reversible internal 16k upgrade

T his post is an upvote for Tynemouth Software's  ZX81 reversible Internal 16K RAM upgrade . Their instructions are easy enough for even me to follow and don't involve cutting tracks. This is the ZX81 I've had out on display and used whenever I wanted to. It's an issue 1 and was probably a kit judging by some very untidy assembly. It has a ZX8-CCB  composite video mod and an external keyboard fitted. On board it has two 1k x 4-bit chips.  The ZX81 originally came with 1k on board. Thanks to a trick with compressing the display in ram, that was enough to type and run a small program but you soon felt the limitations. Back in the early 80s, the solution was a 16k ram pack which plugged into the back[1] and this is the way I've been using this particular machine. These ram packs are notorious for 'ram pack wobble'. Even if fastened into place, you can still randomly find your work disappearing. This is a very reliable solution using a more modern 32k chip (half

Driving NeoPixels with Z80

I 've long been thinking about a version two   RC2014 LED matrix module . I've had a matrix with a MAX 7219 on a module. It's a nice enhancement. But there's only so much you can do with a single-colour LED array right? Wouldn't it be cool to have RGB LEDs?  At Liverpool MakeFest I saw a wall-sized ping-pong ball NeoPixel display and picked up some NeoPixels with the intention of making one. Possibly driven by my RC2014.  I enjoy learning about protocols and have had some SPI devices working with the RC2014 - bit-banging SPI works really well because it doesn't care about timing. NeoPixels really do care about timing though. From Adafruit's web page about their 8x8  NeoPixel matrix: If there's one thing I want to get across in this blog post, it's don't just accept what you're told . Question everything. Learn about what's going on and find out why you're being told something isn't possible. Get creative with workarounds. I'

Making new ROMs for the Vic20 / Vicky Twenty

M y Vicky Twenty is very nearly complete.  As things stand, the board and every single component is new*. The processor and VIAs are newly-manufactured (W65C02 and W65C22).  Obviously the Vic1 chip isn't manufactured today, but there is 'new old' stock about. I have been able to buy a Vic 1, date code 1987 (which seems very late). It obviously hasn't been in a computer before, passes the acetone test and works. The same goes for two of the ROMs - character and BASIC. But I haven't been able to buy a new-old Kernal ROM (901486-07). I am able to borrow one - all of the boards I have, have this particular ROM socketed. I don't know whether all of this indicates that the Kernal has proved less reliable than the other two. I recently bought a TL866 for another project. Of all the retro-computing hardware things I've had to learn to do, making ROMs has been one of the simplest. So far, everything has been very easy and worked first time.  I'm not sure that it&