Electron Dance
26Jul/11Off

The Fukushima Syndrome, 2

This is the tenth article in the Where We Came From series.

Last week: Attempting to learn more about the ongoing crisis at the Fukushima Daiichi reactor, I study a complex simulation program that was released on the Atari 400/800 computer in 1981, SCRAM by Chris Crawford. I've read the manual and bought the T-shirt. Now it's time to show this reactor what I'm made of.

Atoms, apparently.

It's probably just me, but I like to visualise the process of nuclear fission as atomic sex. All it takes is just one neutron to penetrate the heart of an atom, to fertilise it. The fertilised atom divides into two and, in this orgasm of reproduction, fires more neutrons into the atomic void. These neutrons find other atoms to fertilise... and the reactor core becomes a vast, self-sustaining sex orgy.

But what happens if the orgy gets out of control? How do you stop nuclear reproduction? Obvious. Nuclear condoms.

Enrico Fermi was well aware of the problem when he and his associates were building the first nuclear reactor on a University of Chicago squash court in 1942. They used neutron-absorbing control rods to manage the reaction. Withdrawing the rods from the core would allow a self-sustaining nuclear reaction to take place and re-inserting them back in would subdue it. As this was the first reactor, the test of theory, control was their primary concern.

One story goes that the rods were held up by a rope and a codeword to order the rope be cut was “SCRAM” which either stood for “Safety Control Rod Ax Man” or “Start Cutting Right Away, Man”. Another story is that the emergency shutdown button was marked “SCRAM” because the team would have to scram out of there if the button was actually needed. Whilst the origin of the term “scram” in the nuclear context is unclear, its use is ubiquitous.

At Fukushima Daiichi, the reactors were scrammed as soon as the earthquake hit. This is standard procedure. An hour later, a tsunami battered the plant and disabled the backup power generators - sending the reactors hurtling towards meltdown.

Why?

A Reactor Operator's Diary

As explained last week, SCRAM is a hardcore simulation with limited visual feedback. It's a game that takes its subject matter seriously and is impossible to figure out without the manual. Rather than try to explain in text how SCRAM functions, I put together a video instead (featuring original music composed by regular commentmeister Sid Menon, a.k.a. BeamSplashX).

What follows is the diary of my progress through the risk levels. I only considered a risk level "completed" if I hit the corresponding energy production target in the manual and achieved cold shutdown.

Risk 1: 1000 MWH

Meltdown! First quake, temperature shoots up in the primary loop so I assume it must be one of the primary loop pumps. Fixed. Second quake, saw the same thing, made the same conclusion and wrong-o. Waste most of my workers fixing the perfectly good components. Turns out to be a broken pump in the tertiary loop. Third quake leads me on a similar wild goose chase. After my fifth quake I have only five workers remaining, and the temperature is rising. Meltdown occurs with around 814 MWH generated.

Successful on the second attempt, so at least I'm learning.

Risk 2: 900 MWH

Game aspect becomes more prominent but am I learning anything about Fukushima? All the new reactor knowledge in my head was acquired via the manual and not the game itself.

But I've learnt another lesson. In our CSI times, we've become entrenched in a make-believe of computer systems that tell us answers and spell out the truth. Reality is not quite like that. I like the idea of having to work out where the problem is myself.

Not sure of the purpose of the auxiliary feedwater tank attached to the middle loop, so unlikely I am playing the way Crawford intended.

Seems like games on risk levels 1 and 2 take around 20-25 minutes and it gets dull waiting for something to happen. But I reach the production target of 900MWH and achieve cold shutdown first time.

Risk 3: 800 MWH

Getting better at this. A drop in temperature at a loop inflow is a key signal for pump failure – as coolant isn't flowing as fast, heat backs up at the top of the loop and, just for a moment, drops at the bottom. But composite problems are a nightmare. The signals are confused when you have multiple component problems, gets frustrating when you can't work out what's going on without guesswork.

After reaching target, I bring the control rods in only to get hit by a cluster of quakes. Think I’m going to lose... but cold shutdown is achieved just in the nick of time.

"SCRAM: A Nuclear Power Plant Simulation" box art

Risk 4: 700 MWH

The tedium between quakes now becomes tension. I worry whether I can fix a broken component in time before the next quake hits.

I reach 292 MWH and have 45 workers left. When I reach 418 MWH, failure to find which valve is broken leads to wasted workers, 25 left. Have a bout of “steam voiding” so to cool the core I push the control rods in; the power output falls. I literally despite a fall in power output because the longer you play, the more quakes you are exposed to.

I eventually run out of workers around 550 MWH and then lots of quakes follow. It's clear I'm not going to make it and I wonder how much of this is luck. I restart.

I take action to make SCRAM an easier ride and begin to game the simulation.

First: I use quake-free mode Risk 0 to pump the pressure up a bit and ensure the turbine is generating 999 MW before I increase the risk level. Although the energy score is reset when you change level, the current production rate of the reactor is preserved.

Second: I decide not to fix every component problem until I need to, because quakes don't wait for me to track them down. Until now I've been doing experiments to find out which component was broken and this tinkering destabilises the reactor state – this means if a quake hits, it's difficult to see what new dynamic has arrived.

On my second attempt, as I approach 700MWH I get hit with multiple pump problems. 645MWH, 20 Workers left. The shutdown phase is really tricky, not just because it is so slow but also as the system is in temperature freefall, reading pump problems is virtually impossible.

But cold shutdown is achieved, 726 MWH and 15 workers left.

Risk 5: 600 MWH

Success! 628 MWH, 25 workers left. When temperatures start rising I try to fix within seconds. A drop in power output is more fatal to your long-term game health than anything else, as it substantially elongates your game, ratcheting up the quake risk. And I ram the control condoms into the reactor as soon as I get near the target. I become efficient at my job.

Risk 6: 500 MWH

Takes two attempts to succeed. 522 MWH, 25 workers left.

Risk 7: 400 MWH

Here is where I skewer any pretence of simulation. You can turn the auxiliary pumps on which will have no effect on the reactor, provided you leave the auxiliary valves closed. Once pumps are activated, they become potential targets for each quake so I'm using the game's strange logic of “one quake, one break” to deflect damage away from components that are vital for success. This is truly a strategy that would work in real life.

Cold shutdown achieved with 414 MWH produced, 35 workers left.

Risk 8: 300 MWH

I make 321 MWH but cannot survive the onslaught of quakes that befall me during reactor scram. Unable to identify what's broken during the shutdown, I run out of workers with random guesses.

I realise I've had enough and decide to end my experiment.

Fail Safe

The game itself didn't teach me anything – it was the manual that did all the work. The game often overwhelms the player with problems and, on the higher risk levels, I never got the sense I was resolving them with anything less than luck. It's not particularly fun, it doesn't educate through its mechanics and it feels unfair. I would've liked more emphasis on black box problem-solving in a real-world context and less on anxiety.

SCRAM meltdown

Crawford came to similar conclusions in his book, Chris Crawford on Game Design:

“All in all, Scram was a stupid game devoid of entertainment value. … I could hide behind the fact that software in those days was mostly bad. … If I had it all to do over again, I would start my design process by asking myself, "What is fun and interesting about nuclear power plants?" The answer, of course, would be "Not much," and I would walk away from the idea of building such a game.”

So is SCRAM just an oddity from an era when game design was crawling out of the swamp? Is it the kind of experimental work we wouldn't see now? Hmm...

If you're looking for evidence that the 80s were the only decade where true gaming experimentation occurred, you are not going to find it here.

Twilight's Last Gleaming

So SCRAM never told me why Fukushima Daiichi experienced core meltdown. Why was it important for the generators in Fukushima to keep running if the control rods were inserted? Even in the game, if your pumps break, the control rods are not sufficient to shut down the plant. I had to fall back on the internet for the answer.

A reactor core also produces what is known as decay heat because it is radioactive. A concentration of decay heat alone will be enough to bring about a meltdown and so cooling is essential. You can't just shut it off because the nature of the very material itself is unstable. So a key to safe reactor design is being able to keep the coolant circulating in even the most extreme scenarios.

If Fukushima Daiichi had better defences against the tsunami, we wouldn't be talking about a 20km exclusion zone right now. But it's important to note there's another Fukushima nuclear plant, Fukushima Daini, which was also overwhelmed by the tsunami. It achieved cold shutdown four days after the earthquake and is not in danger of meltdown.

Tsunami overrunning Fukushima Daini nuclear power plant

Tsunami overrunning Fukushima Daini nuclear power plant

It's true that the Japanese nuclear reactor industry has been bizarrely complacent about safety – there have been many concerns and incidents over the years. But there's also something to be said about the Swiss cheese model of system accidents. In a complex system, it is difficult to identify exactly how disaster could strike. Hindsight and experience are much better at suggesting improvements to a system than thought experimenting our way to the perfect design. We learn through error.

But with nuclear power, accidents have the potential for large-scale environmental damage. Charles Perrow, who devised “normal accident theory” even went so far as to say “some technologies, such as nuclear power, should simply be abandoned because they are not worth the risk.”

Movie poster for "The China Syndrome"

Anti-nuclear hysteria has inculcated a nuclear industry that is hyper-defensive and dwells in a state of minimal transparency. After the first explosion at Fukushima Daiichi the media talked up the danger of explosions for days, suggesting that Japan was teetering on the edge of a new Chernobyl. This hype obscured the real story of a tsunami-devastated coast, of death beyond comprehension. Nuclear power comes in for a lot of criticism but in the wake of a media frenzy like we have just seen, it is not out of place to ask whether nuclear power gets a raw deal.

But the nuclear industry does itself no favours. The latest bad news came from Reuters:

The workers who stayed on to try to stabilise the plant in the darkest hours after March 11 were lauded as the "Fukushima 50" for their selflessness. But behind the heroism is a legacy of Japanese nuclear workers facing hazards with little oversight, according to interviews with more than two dozen current and former nuclear workers, doctors and others.

Since the start of the nuclear boom in the 1970s, Japan's utilities have relied on temporary workers for maintenance and plant repair jobs, the experts said. They were often paid in cash with little training and no follow-up health screening.

I just wish the trials and tribulations of nuclear power were as simple those an Atari gamer faced in the compact, sterile microcosm of SCRAM: A Nuclear Power Plant Simulation.

Share This
Subscribe for Updates

Posted by HM

Electron Dance Highlights

Comments (16) Trackbacks (2)
  1. Joel, I shared this with my former research group at Stanford (How They Got Game). Turns out my friend/colleague Eric Kaltman briefly mentioned this same game in a blog post a while back:
    http://www.stanford.edu/group/htgg/cgi-bin/drupal/?q=node/479

    But only you were hardcore enough to go and make a video tutorial. I love it! Major props :)

    btw you should totally send this to Chris Crawford.

  2. I did actually come across that and it was almost – almost – cited here to point out it wasn’t the first reactor sim to come out, beaten to the punch by Three Mile Island on the Apple II.

    You know, I fear Chris will tell me I’m playing game ALL WRONG. At least this way, no one reading Electron Dance will even think about reproducing my SCRAM play and question my strategy. But I love the ABC interview he did in the first video above, I think it’s wonderfully representative of the time. It looks so low-key and understated compared to where we are now.

  3. I must say, I am astounded that anybody would take any time with that 30-year-old software. Yes, it is very primitive. I am less surprised that you had some problems understanding the model — I suppose that reflects my usual overly optimistic assumptions about the clarity of my software. I am a teacher at heart, and I designed Scram primarily as an educational game.

    The game is easy to figure out when you are dealing with just a single failure, but if you’re slow to respond, and a second earthquake strikes before you fix it, then it becomes quite difficult to deduce the failed component. It’s really just a matter of looking how far downstream the big temperature differences extend; the failed component is either a valve or a pump in the furthest-downstream overheating loop.

    You’ll be chagrined to learn that I am now working on a new version of my 1990 educational simulation, Balance of the Planet. It’s much, much hairier than Scram, loaded with all sorts of information, and covers environmental issues pretty thoroughly. Want to know what a steam condenser is? That’s in the backup material, all of which is in a hypertext document built right into the simulation. What about sulfur dioxide? We got that, too. Industrial production, acid rain, GM crops, malnutrition — we got all the top items from the environmental hit parade! I guarantee, NOBODY will play this for fun — but anybody who wants to learn about environmental issues will find this the most enjoyable way to understand the complex dynamics of the problem.

  4. Thanks for the big-up, Joel! This version is a big improvement, though you didn’t say “ass” in this one (just to let everyone else know what they’re missing).

    I think SCRAM would make for an enjoyably apocalyptic screensaver these days, if nothing else. How about it, Chris? Either that or a GRITTY REBOOT that teaches children about nuke-beasts, which are the actual cause of problems in a nuclear powerplant, taken care of with extreme violence.

  5. Fantastic stuff. I love how you approached this, Joel. It’s actually one of the better game diaries I’ve seen!

    @Chris: That sounds fascinating. I’m not sure for how long I would play it, but I would give it a try in a heartbeat and hope to not get distracted by shiny for long enough to become immersed.

  6. @Chris, I am remiss in not expanding on this but when you’re allowed to focus on a single problem the game is really interesting, encouraging you to play with valves and pumps trying to track down a problem. The issue is that you have to wait minutes before getting another quake on the low risk levels (I maxed the CPU in the Atari emulator to get through the dead periods) and on the later ones, they come thick and fast preventing you from experimenting. Looking at it now, I think I would’ve loved a sort of Scram “puzzle mode” – where I have one component break and need to resolve it, rather than up against a random clock. A focus on the experimenting than a race against time.

    I guessed I should’ve been able to read the temperatures better to identify exactly which pump had failed but that particular knowledge didn’t seem to emerge naturally through my play. Thus it became quite tricky as I headed into the higher risk levels.

    For readers who don’t know, “Balance of the Planet” is Chris’ game that did the whole Fate of the World thing *20 years* before Fate of the World (disclaimer: not played, was not a PC user at the time of its release). It doesn’t appear anyone else picked up the environmental simulator baton in the intervening years. I think there’s a bigger market for this kind of software now, as people are hungry for more serious experiences. So it’s interesting that Chris is returning to it now – he has an ongoing developer diary I just found, which has impressive discussions on how to come up with equations to model deaths from malnutrition.

    What I’ve read of the diary makes it sound like a brand new ground-up build, Chris, and not developed off Storytron…?

    @BeamSplashX: No problemo, señor! To clarify for others, Sid is referring to a version 1 of the gameplay video which was drier – I used acronyms like RCS and HCI – and contained the full Scram Risk 6 game (the video stretched to around 15-20 mins long). I would have done a version 3 if I’d had the time. I’m never happy.

    @Shaun: Thanks! I wasn’t sure if anyone would actually follow this because, well, it’s all temperatures and pressures innit?

  7. Yes, this is not based on the Storytron technology. The original Storytron effort was a commercial failure, so I have backed up and am reconsidering a number of elements in it. I have come up with an idea that might revive it, but felt that it would be a good thing to earn some money before continuing. I’m hoping to get back to Storytron late this year.

  8. I’m glad you waited until total catastrophe before throwing me and Gregg to the radioactive fires.

    Amazing video and analysis. I never played SCRAM, but now I must. I can see so many applications for games like this – fun, complex, hard to master, but teaching. Great work HM!

  9. @Chris, quite sad to hear that about Storytron but interested to see the next iteration as well as Balance of the Planet. Please accept my belated thanks for De Re Atari, which was my personal bible for many years.

    @Steerpike, I’m heartened you sat through the entire video to discover the Easter Egg reference to Tap! I’ll embed a Da Vinci style ARG in the next video and expect the internet to crack it.

  10. Scram actually sounds like my job, with valves being replaced by people, and natural catastrophes being replaced by client demands. Would be interested in Balance of the Planet. Obviously I will just read about it and um and ah, then go back to what I know best.

  11. BC, you’ll probably use the excuse “I’m waiting for the console release.”

  12. @Chris, I’d love to see the source code of SCRAM released under a free license. I personnally would look at it, and maybe with the help of the community, we could give the game a second life…

  13. Martin, I’m not sure who owns SCRAM in this post-Atari future. The brand and all its “properties” still exist (witness “revivals” of Yars’ Revenge and Star Raiders) but as for the original code it may be a grubby grey area.

    On the other hand, I hit the BREAK key in the middle of SCRAM and was able to type LIST. Because SCRAM is written in BASIC with some supporting machine code routines.

    So if you have a copy of SCRAM, you should be able to analyse the code if you’re really interested.

  14. Additional… from the looks of it, it’s highly optimised for BASIC performance (e.g. using named variables in place of floating point constants). So it’s not going to be that easy a read…

  15. My current project building a modern version of Balance of the Planet is an experiment. If it works out commercially, then I intend to rebuild all of the stuff I did in modern form. However, I see no need to do all the coding myself. I’m thinking that perhaps I should recruit some eager young game designers fresh out of school and have them do the coding. This would give them some experience and something to put on their resumes. Besides, the kids coming out of schools these days face a horrific job market.

  16. @Chris,

    Hi.

    I’m interested in these projects you mention.
    I’d like to discuss with you further the possibility of some possible investment/staffing (I manage software development projects in Asia).

    If that is of value, please drop me an email…

    First time visitor to this site, love the writing style and content.
    Subscribing to the RSS.

    Got here via wikipedia small reactor research, which led to Chernobyl-disaster 3hour side-track.
    Which led to thoughts on gaming and finally here.
    I now have about 7 new tabs open from stuff in this page alone.
    Sick in bed, making for a great afternoon of reading.
    Thanks…

    -Will