My first encounter with computers

For me it would be being introduced to an ICL 4130 (formerly an Elliot Computing 4130) mainframe and the use of punch card decks. I was instructed on how to program the computer using the computer language Algol-60 and I had to write the code on sheets that were then punched by punch card operators. Somewhere, I have a booklet which describes the machine … somewhere!

Anyway, by the time I’d got started on my computing life the 4130 was getting a bit long in the tooth and the form for Universities in those days (remember everything was centrally funded by the Universities Grant and Research Grant Committees of the Education Department then) was to get a visit from the Computer Board – a group of the wise and worldly (it must have been, I went on to serve on its successor body much later on – the Joint Information Systems Committee) who would adjudicate whether an institution needed a new computer or, if it was between its regular visits, whether the Computer Centre needed new peripherals such as disk drives, printers or plotters. As a research student (at UCW Aberystwyth) I, along with my other researchers were fully prepped to be able to say the right thing just in case one of these visiting folk asked a question. What fun! The preparation must have paid off because we got a new machine.

The ICL 4130 was replaced by an ICL 1900 series machine running George 3 – a proper operating system [I think a second machine was purchased later on and they were linked so that one could handle batch punch card jobs and the other handled teletype terminals and possibly output]. Of course this was the time when Computer Operators were needed and they ran jobs (including back-ups) overnight and had to be in attendance to change magnetic tapes, and handle printed output – a lot of which was created by me!

I was teaching myself multi-variate statistics, mainly based on linear and multiple regression models, but also principal components and factor analysis and using standard programs which I modified in part to my research subject because I needed mapped output, on a line-printer! The main program I worked with however was written (in Fortran IV) by David Wishart from St Andrews for Cluster Analysis, so I learnt to program in Fortran and this soon replaced Algol-60 as my preferred programming language. This program and its adaptation to spatial analysis (in which I followed the work of a fellow researcher called Stan Openshaw who was using the technique in human geography to group together similar grid cells from maps) was to take up a huge part of the next 10 years of my life as I worked hard to avoid actually going out to do any field work on my research topic “Contemporary Erosion in mid-Wales”. Most of my jobs were by now being run by remote job entry at the Manchester Regional Computing Centre as the size of my data set was too large to run in the UCW Aberystwyth Computer Centre.

It was an exciting time to be a geographer and books and monographs were being published on quantitative geography amongst which were ones in the Institute of British Geographers CATMOG series, still in my possession, by a certain John Silk. A lovely coincidence that brings John and myself together and allows us to reminisce on the early 1970’s and “the quantitative revolution” as it was called by some!

Through the 1970’s I returned every summer holiday to Aber, and camped at the top of Penglais Hill to get time on the mainframe. In between these visits I would sit at a teletype at Doncaster College of Education, where I was now a Lecturer in Physical Geography, and submit jobs to the IBM 360 mainframe at what was then Sheffield Polytechnic. It had to be said that by 1978-9 my main interest (apart from the family that was now arriving on the scene) was in computing, not geography, and so when a friend asked me to put my knowledge to work in programming some engineering design problems, I accepted the challenge, set up my own consultancy (with my HoD’s approval) and started programming an Olivetti P6060 desktop computer using Basic. Having it at home to do the work allowed my eldest daughter (44 yesterday) to have a go at programming …

So now the link to geography had begun to be broken. This was severed by Shirley Williams decision in 1978 to close the Teacher Training part of the College where I worked. I bravely, one of my colleagues thought foolishly given that we had by now three young children, decided to opt for voluntary redundancy on the basis of being given a year’s fully-paid retraining. I went to Bradford University and did a one-year MSc in Computer Science giving me letters after my name to go with my 10+ years programming experience. Here I was introduced to the DEC PDP-11/60 mini-computer – a lovely machine running Unix, which was a lovely operating system which I continue to use in it’s Linux incarnation, to this day. I wrote my thesis on building a disk operating system (Modus) for a PDP-8 using a high-level structured programming language (Wirth’s Modula) on the PDP-11. I could now program in Algol-60, Basic, Fortran iV, Fortran 66, Cobol, PDP Assembler, Pascal and Modula.

It was the latter language (the first concurrent programming language and the precursor of first Modula-2 and then Ada) that enabled me to get a job as a Systems Programmer / Computer Lecturer at South Glamorgan Institute of HE at Llandaff. I was returning to Cardiff and HE. Not a very bold move and “only for 4 years max” (which is what I said to Jenny). That was not to be! At SGIHE/CIHE/UWIC I oversaw the introduction of a mini-computer service based initially on a Prime 550, then Prime 750 and so on, initially writing the systems programs for its operating system – Primos in Fortran, PL/P and SP/L, and then becoming Head of the Computer Centre where I dabbled in producing the first website for the institute, which has since been a continuing interest for me.

Here are a few pictures of the Computer Centre at UWIC taken before I left for UWCM at UHW (The Heath) …

The Operator’s Consoles for each system are on the left, the tape rack for the day’s tape back-ups are in the background, a terminal room with micro-computers was alongside the Computer Centre …

The original Line printer (orange) was till in service, the Prime 750 is in the background …

I’d become a manager, and the rest is another story, which I’ll record another day!

At home we’d purchased one of the first BBC-B Computers – the first of a long series of domestic computers which again is another story, which I’ll record another day!

David Harrison, June 2020

 

Covid-19 Tracing app

What is Contact Tracing, and how does an app help?

This video from The Guardian is an excellent review of how Contact Tracing works in both a traditional and technology-enable world. You should watch it.

Contact Tracing Infographic

An Infographic that explains how Contact Tracing works

Approaches to creating a Contact Tracing app

Google and Apple have combined to work out a solution that works across iOS/Android devices. Here's a document that explains how what they have done would work …

 

But there are Privacy concerns as this BBC article (with video) explains.  Regardless of those concerns the app is being trialled in the Isle of Wight. It’s useful to know the difference between the approach being used by the NHS and the Google-Apple approach, this article explains those differences.

However there are potentially difficulties …

France (how unexpected) have threatened Google-Apple over the fact they won’t work with France’s standalone approach (a similar approach to the UK); and it has been suggested that failure to adopt a common approach could threaten international travel – as “health passports” will be impossible to implement.

Then there are technical difficulties as iOS and Android devices work in different ways (not unsurprisingly) causing success of the Google-Apple approach to be dependent on a very high adoption amongst Android users.

The new NHS contact-tracing app could be used to send malicious alerts causing people to isolate unnecessarily, The Independent has been told. The app, which is being trialled in the Isle of Wight, tells users if someone they have been in close proximity with may be suffering from coronavirus, meaning they could be exposed. But because users can set off the warnings themselves by reporting symptoms – rather than positive Covid-19 test results – it could be used to send out false alerts. Dr Michael Veale, a lecturer in digital rights at University College London, said Britain’s tracing app had no measures in place to stop individuals “maliciously triggering notifications” using its normal functionality.

Then, on the technical front, some notes from Phil Edwards’ friend

On the Apple-Google Indirect approach

“Their approach seems pretty solid. I think they’re basically exposing some features that previously weren’t available to app developers. Both seem pretty determined to limit the potential for it to be exploited by governments; I think they announced yesterday/the day before that any apps using their system can’t also access location data.

Contact tracing is totally doable without central databases. I can see why a government might want to own data themselves, but there are big downsides (especially security when building in such a rush).”

On the NHSx Direct approach

“The implementation of this contact tracing app really hits that sweet spot between ‘Are they incompetent?’ and ‘Do they have ulterior motives?’ I’d advise against installing it but I doubt it’s going to work properly anyway in its current implementation because of various oddities around how Bluetooth LE works. This isn’t a great article but covers some of it.”

A better comment from Hacker News covers it clearer:

“‘Bluetooth LE has four main states: scanning, advertising, peripheral connection, and central connection. In order to exchange the data that the app needs it needs one device in the peripheral connection mode and the other in the central connection mode. This means one device must have previously been advertising and the other scanning. The two important states are advertising and scanning.Android devices can advertise in the background but they can’t scan reliably, they can do this for a short period of time enforced by the Android time limits on apps running in the background and possibly manufacturer specific power savings measures. These limits are not well documented and cause issues on any device using Bluetooth.iOS devices can’t advertise in the background, however they do advertise an Apple specific advertisement which can’t be controlled by the app but can still be connected to. iOS devices also can’t reliably scan in the background however they can scan more reliably for iBeacons (special adverts) [1]Combined this makes it difficult to work well in the background, Android devices can’t reliably connect to any device, iOS devices can’t connect to each other but iOS devices may be able to connect to Android devices.'”

Finally, a potential for Fraud

Plus fraudsters have not been slow to latch-on to the possibility of piggy-backing on the NHS app as this article in The Guardian show (thanks Phil for the link).

Other references:

The NHS Covid-19 website