CLOSE
Original image

Seawise Giant: You Can't Keep a Good Ship Down

Original image

We’ve all heard of the Titanic and the Exxon Valdez. The story of the tanker than was once known as the Seawise Giant is much less familiar, although it’s every bit as memorable. The largest ship ever built—she was nearly twice as long as the Titanic—actually sank, only to rise up from the ocean floor and sail again. This is the story of its odd life and multitude of names.

The tanker didn’t get off to the rosiest of starts. A Greek shipping magnate originally ordered the ship in 1979 when tanker construction was booming following a decade of unrest in the oil market. He ended up not being able to foot the bill when a Yokosuka, Japan, shipyard finished construction, though. The shipyard sold the tanker to Chinese shipping kingpin C.Y. Tung, who ordered a refitting of the tanker to make it the largest ship ever to sail. Tung then named the beast the Seawise Giant.

Just how big was the Seawise Giant?

Her rudder alone weighed 230 tons. She was over 1500 feet long and 226 feet wide. She was basically half again as long and half again as wide as an American aircraft carrier. She had a cargo capacity of 564,763 deadweight tons, which by that measure made her the largest ship on record. (The four French Batillus-class supertankers built during the 1970s had larger gross tonnage, but Seawise Giant had a larger fully loaded displacement.)

When she finally launched in 1981, the Seawise Giant began making relatively uneventful transport runs between the Middle East and the United States. Things bottomed out for the Seawise Giant in May 1988. The literal low point in the supertanker’s history came in 1988, when it became a casualty of the Iran-Iraq War. Iraqi planes attacked an Iranian oil platform in the Strait of Hormuz in the hopes of choking off a crucial part of Iran’s oil pipeline.

In addition to bombing the platform, the Iraqi jets opened fire on five oil tankers anchored in the area. The Spanish tanker Barcelona listed for a few days before sinking after a secondary explosion. The Seawise Giant weathered a similar onslaught of Exocet missiles and also sank. Suddenly, the world’s largest ship was the world’s largest shipwreck. The tanker’s owners wrote her off as a total loss.

Encore

Of course, it seemed like a waste to have such a gigantic ship just sitting and rotting on the sea floor. In 1989, after the Iran-Iraq War ended, a Norwegian consortium bought the Seawise Giant’s wreckage and had her pulled from the shallow water and transported to Singapore for significant repairs. The new owners renamed the tanker the Happy Giant because, hey, who wouldn’t be happy to get a second shot at life?

The sweeping repairs took two years, and at the end of the process Norwegian shipping mogul Jorgen Jahre bought the tanker for $39 million and again renamed her, this time to the Jahre Viking. For the next 13 years the Jahre Viking sailed under the Norwegian flag.

By 2004, it had started to become clear that while the gigantic tanker was certainly an engineering marvel, it wasn’t the most practical vessel for conveying oil in the modern economy. The economics of powering such a huge ship meant that some gargantuan tankers operated at a loss.

Furthermore, the Jahre Viking’s massive size meant that actually sailing the thing was a pain. It couldn’t navigate the English Channel thanks to its lack of maneuverability, and the tanker’s 81-foot draft meant that her crew had to remain vigilant about the very real risk of running aground in waters that were no problem for smaller ships. On top of that, while the tanker could get up to a speed of 16.5 knots in ideal conditions, it wasn’t great at slowing down; it took over five miles for the boat to stop when it was running at that speed.

The Jahre Viking may have outlived its usefulness as a tanker, but it wasn’t totally worthless. In 2004 First Olsen Tankers bought the ship and began converting her into a stationary storage tanker. After another name change to the Knock Nevis, the tanker ended up permanently moored in the Persian Gulf’s Al Shaheen Oil Field off the coast of Qatar as a floating storage and offloading vessel.

This Is the End

The Knock Nevis lasted about five years in this job before her owners decided that the behemoth no longer made sense as a storage vessel, either. It was time for her to meet the same fate as the four aforementioned Batillus class supertankers that rivaled her size. She headed to the scrapyard. The ship’s name was changed to Mont for a final voyage to India’s Alang-Sosiya ship-breaking yards in January 2010. Even dismantling the ship turned out to be an epic task; the Times of India reported that the project would take a year and require as many as 18,000 laborers. In the end, the Seawise Giant could survive a missile attack from Saddam Hussein’s air force, but she couldn’t withstand the pressure of a changing oil market.

Original image
iStock // Ekaterina Minaeva
technology
arrow
Man Buys Two Metric Tons of LEGO Bricks; Sorts Them Via Machine Learning
May 21, 2017
Original image
iStock // Ekaterina Minaeva

Jacques Mattheij made a small, but awesome, mistake. He went on eBay one evening and bid on a bunch of bulk LEGO brick auctions, then went to sleep. Upon waking, he discovered that he was the high bidder on many, and was now the proud owner of two tons of LEGO bricks. (This is about 4400 pounds.) He wrote, "[L]esson 1: if you win almost all bids you are bidding too high."

Mattheij had noticed that bulk, unsorted bricks sell for something like €10/kilogram, whereas sets are roughly €40/kg and rare parts go for up to €100/kg. Much of the value of the bricks is in their sorting. If he could reduce the entropy of these bins of unsorted bricks, he could make a tidy profit. While many people do this work by hand, the problem is enormous—just the kind of challenge for a computer. Mattheij writes:

There are 38000+ shapes and there are 100+ possible shades of color (you can roughly tell how old someone is by asking them what lego colors they remember from their youth).

In the following months, Mattheij built a proof-of-concept sorting system using, of course, LEGO. He broke the problem down into a series of sub-problems (including "feeding LEGO reliably from a hopper is surprisingly hard," one of those facts of nature that will stymie even the best system design). After tinkering with the prototype at length, he expanded the system to a surprisingly complex system of conveyer belts (powered by a home treadmill), various pieces of cabinetry, and "copious quantities of crazy glue."

Here's a video showing the current system running at low speed:

The key part of the system was running the bricks past a camera paired with a computer running a neural net-based image classifier. That allows the computer (when sufficiently trained on brick images) to recognize bricks and thus categorize them by color, shape, or other parameters. Remember that as bricks pass by, they can be in any orientation, can be dirty, can even be stuck to other pieces. So having a flexible software system is key to recognizing—in a fraction of a second—what a given brick is, in order to sort it out. When a match is found, a jet of compressed air pops the piece off the conveyer belt and into a waiting bin.

After much experimentation, Mattheij rewrote the software (several times in fact) to accomplish a variety of basic tasks. At its core, the system takes images from a webcam and feeds them to a neural network to do the classification. Of course, the neural net needs to be "trained" by showing it lots of images, and telling it what those images represent. Mattheij's breakthrough was allowing the machine to effectively train itself, with guidance: Running pieces through allows the system to take its own photos, make a guess, and build on that guess. As long as Mattheij corrects the incorrect guesses, he ends up with a decent (and self-reinforcing) corpus of training data. As the machine continues running, it can rack up more training, allowing it to recognize a broad variety of pieces on the fly.

Here's another video, focusing on how the pieces move on conveyer belts (running at slow speed so puny humans can follow). You can also see the air jets in action:

In an email interview, Mattheij told Mental Floss that the system currently sorts LEGO bricks into more than 50 categories. It can also be run in a color-sorting mode to bin the parts across 12 color groups. (Thus at present you'd likely do a two-pass sort on the bricks: once for shape, then a separate pass for color.) He continues to refine the system, with a focus on making its recognition abilities faster. At some point down the line, he plans to make the software portion open source. You're on your own as far as building conveyer belts, bins, and so forth.

Check out Mattheij's writeup in two parts for more information. It starts with an overview of the story, followed up with a deep dive on the software. He's also tweeting about the project (among other things). And if you look around a bit, you'll find bulk LEGO brick auctions online—it's definitely a thing!

Original image
Nick Briggs/Comic Relief
entertainment
arrow
What Happened to Jamie and Aurelia From Love Actually?
May 26, 2017
Original image
Nick Briggs/Comic Relief

Fans of the romantic-comedy Love Actually recently got a bonus reunion in the form of Red Nose Day Actually, a short charity special that gave audiences a peek at where their favorite characters ended up almost 15 years later.

One of the most improbable pairings from the original film was between Jamie (Colin Firth) and Aurelia (Lúcia Moniz), who fell in love despite almost no shared vocabulary. Jamie is English, and Aurelia is Portuguese, and they know just enough of each other’s native tongues for Jamie to propose and Aurelia to accept.

A decade and a half on, they have both improved their knowledge of each other’s languages—if not perfectly, in Jamie’s case. But apparently, their love is much stronger than his grasp on Portuguese grammar, because they’ve got three bilingual kids and another on the way. (And still enjoy having important romantic moments in the car.)

In 2015, Love Actually script editor Emma Freud revealed via Twitter what happened between Karen and Harry (Emma Thompson and Alan Rickman, who passed away last year). Most of the other couples get happy endings in the short—even if Hugh Grant's character hasn't gotten any better at dancing.

[h/t TV Guide]

SECTIONS
BIG QUESTIONS
BIG QUESTIONS
WEATHER WATCH
BE THE CHANGE
JOB SECRETS
QUIZZES
WORLD WAR 1
SMART SHOPPING
STONES, BONES, & WRECKS
#TBT
THE PRESIDENTS
WORDS
RETROBITUARIES