Wimbledon 2019: IBM’s Slammtracker AI Technology Heralds The Demise Of The Human Player

Whilst we patiently wait for the day that Womble-shaped robots replace human tennis players at Wimbledon, we can admire the IBM powered AI technology that the organisers of the Wimbledon tennis tournament use to enhance the experience for TV and phone viewers.

As can be expected, the technology tracks the ball, analyses player gestures, crowd cheers/booing but can’t yet discern the more subtle player behaviour such as serving an ace or the classic John McEnroe ‘smash your racket on the ground’ stunt. Currently a large number of expert human side kicks are required for recording these facets and manually uploading them into the huge Watson driven analytics system.

Phone apps are possibly the best places to see the results of the IBM Slammtracker system and are perfect for the casual tennis train spotter. It would be interesting to see the intrinsic AI bias at work – whether it can compensate for the greater intensity of the cheer for the more popular celebrities rather than the skill, or fluke shot, of the rank outsider. We also wonder if it will be misogynistic – will it focus on men rather than women in the mixed doubles or the other way round? Will it be racist? Also, when will the umpires be replaced with 100% AI?

Finally, whilst we at Hackaday appreciate the value of sport and exercise and the technology behind the apps, many of us have no time to mindlessly watch a ball go backwards and forwards across our screens, even if it is accompanied by satisfying grunts and the occasional racket-to-ground smash. We’d much rather entertain ourselves with the idea of building the robots that will surely one day make watching human tennis players a thing of the past.

The OS/2 Operating System Didn’t Die… It Went Underground

One problem with building things using state-of-the-art techniques is that sometimes those that look like they will be “the next big thing” turn out to be dead ends. Next thing you know, that hot new part or piece of software is hard to get or unmaintained. This is especially true if you are building something with a long life span. A case in point is the New York City subway system. Back in the 1990s the transit authority decided to adopt IBM’s new OS/2 operating system. Why not? It was robust and we used to always say “no one ever got fired for buying IBM.”

There was one problem. OS/2 was completely eclipsed by other operating systems, notably Windows and — mostly — has sunk from the public view. [Andrew Egan’s] post covers just how the conversion to a card-based system pushed OS/2 underground all over the Big Apple, and it is an interesting read.

Continue reading “The OS/2 Operating System Didn’t Die… It Went Underground”

So, You Want To Buy A Mainframe

The computers we are used to working with are more likely to be at the smaller end of the computational spectrum. Sometimes they are very small indeed, such as tiny microcontrollers with only a few GPIOs. Others are single board machines such as a Raspberry Pi or an Arduino, and often a desktop or laptop PC. Of course, while these can be very capable machines, they don’t cut the mustard in the upper echelons of corporate computing. There the mainframe still rules, sitting in air-conditioned machine rooms and providing some of the glue that cements our economy together.

Most of us will never own a mainframe, even if sometimes we marvel at people who rescue ancient ones for museums. But it’s not impossible to run one yourself even if it isn’t cheap, and  [Christian Svensson] has written a guide for the potential purchaser of a more recent IBM model.

This is a fascinating piece as an uninformed spectator because it reveals something about the marketing of these machines. A fridge-sized rack may contain much more hardware than expected because all machines ship with high specifications installed but not enabled by licensing software. In some IBM machines this software comes on an attached laptop which goes missing when the mainframe is decommissioned, we’re told without this essential component the machine is junk. The practicalities are also considered, such things as whether the appropriate interface modules are present, or how to assess how much RAM has been installed. Powering the beast is less of a problem than you might expect as they ship with PSUs able to take a wide variety of DC or AC sources.

Once upon a time the chance to own one of the earlier DEC VAX minicomputers came the way of your scribe, the passing up on which has ever since been the source of alternate regret and thankfulness at a lucky escape. The ownership of second-hand Big Iron is not for everyone, but it’s nevertheless interesting to learn about it from those who have taken the plunge. There’s a tale unfolding about the ownership of a much older IBM room-sized computer at the moment.

IBM mainframes header image: Agiorgio [CC BY-SA 4.0]

How Hard Can It Be To Buy A Computer In Germany And Get It Back Home To The UK?

Some of the best adventures in the world of hardware hacking start in the pub. For three volunteers at the National Museum Of Computing in the UK, [Adam Bradley], [Chris Blackburn], and [Peter Vaughan], theirs started over a pint with an eBay listing for an old computer in Germany. No problem you might think, we’re well used to international parcel shipping. This computer wasn’t a crusty old Commodore 64 though, instead it was a room-sized IBM System/360 Model 20 from the 1960s, complete with the full array of peripherals and what seemed to be a lot of documentation and software media. It would need a Mercedes Sprinter, a large van, to shift it, but that seemed feasible. With a bit of frantic bidding they secured the auction, and set off for Germany to view their purchase.

Arriving at the machine’s location they found a little bit more than they had expected. In an abandoned building on a side street in Nuremburg there was an intact machine room full of the IBM computer cabinets over a false floor with all the machine cabling in place, and the only usable access was through a street door which hadn’t been opened in decades and which was obstructed by the false floor itself. To cap it all they found they’d bought not one but two System/360s, and also unexpectedly a 1970s System/370 Model 125. Clearly this was more than a job for a quick in-and-out with a Sprinter.

What followed became a lengthy saga of repeated trips, van hire, constructing ramps, and moving heavy computer parts to a hastily rented storage unit. Decabling a computer of this size is no easy task at the best of times, and these cables had spent many decades in a neglected machine room. It’s a fascinating read, and a very well-documented one with plenty of photos. The machines now sit in their storage units awaiting a return to the UK, and the trio are soliciting any help they can find to make that happen. So if you happen to own a European haulage company with spare capacity on your Germany — UK route or if you can help them in any way, donate or get in touch with them. We think this project has much more to offer, so we’ll be following their progress with interest.

These three intrepid computer hunters were brought together at The National Museum Of Computing at Bletchley, UK. If you find yourself within range it is an essential place to visit, we did so in 2016.

Quantum Computing With QISKit

We all know that quantum computing is coming, but it is hard to know how to get started with it. [Mtreinish] suggests Qiskit — an Apache Licensed SDK for developing quantum applications. He has a presentation he gave in Singapore that you can see below, and a notebook you can go through on GitHub. If you are impatient, you can even run the notebook online through Google.

The tools can work against several backends including a simulator or the real hardware available from IBM. The official site has a different notebook you can use as a tutorial. Interestingly, the foundation of all Qiskit programs is “Terra” (the Earth) and permeating all Qiskit elements is Aer or air. There are also fire and water elements. At the bottom of the official notebook, you’ll find a lot of community notebooks that go deeper into specific topics.

Continue reading “Quantum Computing With QISKit”

Bell Labs, Skunk Works, And The Crowd Sourcing Of Innovation

I’ve noticed that we hear a lot less from corporate research labs than we used to. They still exist, though. Sure, Bell Labs is owned by Nokia and there is still some hot research at IBM even though they quit publication of the fabled IBM Technical Disclosure Bulletin in 1998. But today innovation is more likely to come from a small company attracting venture capital than from an established company investing in research. Why is that? And should it be that way?

The Way We Were

There was a time when every big company had a significant research and development arm. Perhaps the most famous of these was Bell Labs. Although some inventions are inevitably disputed, Bell Labs can claim radio astronomy, the transistor, the laser, Unix, C, and C++ among other innovations. They also scored a total of nine Nobel prizes.

Bell Labs had one big advantage: for many years it was part of a highly profitable monopoly, so perhaps the drive to make money right away was less than at other labs. Also, I think, times were different and businesses often had the ability to look past the next quarter.

Continue reading “Bell Labs, Skunk Works, And The Crowd Sourcing Of Innovation”

Blowing The Dust Off Of An IBM AS/400 Server

If you’ve never seen an IBM AS/400 machine, don’t feel bad. Most people haven’t. Introduced in 1988 as a mid-range server line, it used a unique object-based operating system and was geared specifically towards business and enterprise customers. Unless you’re a particularly big fan of COBOL you probably won’t have much use for one today, but that doesn’t mean they aren’t worth playing around with if the opportunity presents itself.

So when a local IT company went belly up and was selling their old hardware, including a late 90’s era IBM AS/400e Series, [Rik te Winkel] jumped at the chance to take this unique piece of computing history home. He knew it was something of a risk, as maintenance and repair tasks for these machines were intended to be done by IBM certified technicians rather than the DIYer, leaving little in the way of documentation or even replacement parts. But in the end it worked out, and best of all, he documented the successful process of dragging this 90’s behemoth into the blinding light of the twenty-first century for all the world to see.

After getting the machine home and sitting through its thirty minute boot process, [Rik] was relieved to see the code 01 B N pop on the server’s display. This meant the system passed all the internal checks and was ready to go, he just had to figure out how to talk to the thing. Built to be a pure server, the machine didn’t offer any video output so he’d have to log into it over the network.

[Rik] noted that there was no new DHCP entry in his router for the server, but of course that was hardly surprising as the machine would have certainly had a static IP when it was in use. So he shut the server down, plugged it directly into his laptop’s Ethernet port, and watched the output of Wireshark as it went through its arduous boot sequence. Eventually he started to pick up packets coming from the IP address 10.10.10.9, and he had his target.

There are a few clients out there that allow you to remotely log into an AS/400, so he downloaded one and pointed it to the server’s IP. He was surprised to see the operating system was apparently in Dutch, but at least he was in. He tried a few common usernames and passwords, helped along by the fact that this OS from a somewhat more innocent era will actually tell you if you have the username right or wrong, and eventually managed to hack the Gibson with the classic admin/admin combo.

So he was in, but now what? [Rik] decided that he couldn’t truly call this machine bested until he could pull up the Hackaday Retro Edition, so he started work on writing a program to let him pull down the page directly on the AS/400 in IBM’s proprietary Report Program Generator (RPG) programming language. You know, as one does. He didn’t quite feel up to writing a whole HTML parser, but he got as far as generating a HTTP GET request, downloading the page’s source, and opening it up as a local file. That’s good enough for us.

Our very own [Al Williams] documented his adventures poking around an Internet-connected AS/400 machine, which might serve as a helpful primer if you ever find one of these delightfully oddball computers kicking around the local recycling center.