Skip to main content

Friday Quiz maths problem and Heap's algorithm

 T

oday's Friday Quiz maths problem is a corker:

916237458 is an example of a 9-digit number that contains all the digits 1-9 once.  It also has the digits 1 to 5 appearing in their natural order, whilst the digits 6 to 9 do not.  How many such numbers are there?

When the official answer came, a simple solution was given with the answer (I'll save that till later) which didn't make things clear to me.

But without seeing an easier way, my approach, as usual, was to find all the permutations of the 9 digits, and count the ones that meet the criteria. 

The *number* of ways you can arrange some objects is easy to calculate. But how to actually shuffle those around in memory so that you can test them?

Long story short, I devised my own way to shuffle the numbers around, which I thought would work and it nearly did. But not quite. I turned to the web and found Heap's algorithm, which is very similar to what I was trying to do, except that it does actually work. 

It's simple, and the Wikipedia page gives some example code which is recursive.

Here's my version of that in C (I made my array global, rather than passing pointers around)


In my program, printNumber() also performs the test. If that number passes the test, it increases the 'result' counter and also prints an asterisk. 


This runs in 2-3 seconds on my M1 Mac, and that's the correct answer. (the number of permutations of the 9 digits is 9! which is 362880)

This week I've had an Amiga out and among other things I've been revisiting C on that computer. I find it amazing that the C I use every day targeting modern computers and microcontrollers is exactly the same as it was 30 years ago. So my same source compiled and ran on the Amiga (you can see that I added my own bool and true/false definitions because I like writing them lowercase)

And after an hour and a half, here's the same answer:
Another remarkable thing is that a friend on Twitter suggested that quite a bit of that time was probably used printing the numbers to the screen, so I took the printf's out and recompiled, and the program ran in less than a minute!!
It's not meant to be exemplary code, and I didn't spend any time on optimisations. Feel free to do those things.  Also note the typedef and defines for lowercase bool, true and false in my earlier screenshot.

The answer is 2898, and the official explanation given by the quizmaster is (126*(24-1)). This baffled me at first, but my friend George has explained in this Twitter thread:

https://twitter.com/markgbeckett/status/1594685436622143488


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&