Posts Tagged ‘1950s’

Meditations

Narratives of Manhattan Project secrecy

Friday, March 29th, 2013

Secrecy suffused every aspect of the Manhattan Project; it was always in the background, as a context. But it’s also a topic in and of itself — people love to talk about the secrecy of the work, and they’ve loved to talk about it since the Project was made public. In the 1940s there was something of a small industry of articles, books, and clichés regarding how secret the atomic bomb was kept. Of course, the irony is… it wasn’t really kept all that well, if you consider “keeping the secret” to involve “not letting the Soviet Union know pretty much everything about the atomic bomb.” (Which was, according to General Groves, one of the goals.)

It’s easy to get sucked into the mystique of secrecy. One way I’ve found that is useful to help people think critically about secrecy (including myself) is to focus on the narratives of secrecy. That is, instead of talking about secrecy itself, look instead at how people talk about secrecy, how they frame it, how it plays a role in stories they tell about the Manhattan Project.

One of many early articles in the genre of Manhattan Project secrecy: "How We Kept the Atomic Bomb Secret," from the Saturday Evening Post, November 1945.

One of many early articles in the genre of Manhattan Project secrecy: “How We Kept the Atomic Bomb Secret,” from the Saturday Evening Post, November 1945.

My first example of this is the most obvious one, because it is the official one. We might call this one the narrative of the “best-kept secret,” because this is how the Army originally advertised it. Basically, the “best-kept secret” narrative is about how the Manhattan Project was sooo super-secret, that nobody found out about it, despite its ridiculous size and expense. The Army emphasized this very early on, and, in fact, Groves got into some trouble because there were so many stories about how great their secrecy was, revealing too much about the “sources and methods” of counterintelligence work.

The truth is, even without the knowledge of the spying (which they didn’t have in 1945), this narrative is somewhat false even on its own terms. There were leaks about the Manhattan Project (and atomic bombs and energy in general) printed in major press outlets in the United States and abroad. It was considered an “open secret” among Washington politicos and journalists that the Army was working on a new super-weapon that involved atomic energy just prior to its use. Now, it certainly could have been worse, but it’s not clear whether the Army (or the Office of Censorship) had much control over that.

Panel from FEYNMAN by Jim Ottaviani and Leland Myrick.

Panel from FEYNMAN by Jim Ottaviani and Leland Myrick.

We might contrast that with the sort of narrative of secrecy that comes up with regards to many participants’ tales of being at places like Los Alamos. Richard Feynman’s narrative of secrecy is one of absurd secrecy — of ridiculous adherence to stupid rules. In Feynman’s narratives, secrecy is a form of idiotic bureaucracy, imposed by rigid, lesser minds. It’s the sort of thing that a trickster spirit like Feynman can’t resist teasing, whether he’s cracking safes, teasing guards about holes in the fence, or finding elaborate ways to irritate the local censor in his correspondence with his wife. All participants’ narratives are not necessarily absurd, but they are almost always about the totalitarian nature of secrecy. I don’t mean “fascist/communist” here — I mean the original sense of the word, which is to say, the Manhattan Project secrecy regime was one that infused every aspect of human life for those who lived under it. It was not simply a workplace procedure, because there was no real division between work and life at the Manhattan Project sites. (Even recreational sports were considered an essential part of the Oak Ridge secrecy regime, for example.)

So we might isolate two separate narratives here — “secrecy is ridiculous” and “secrecy is totalitarian” — with an understanding that no single narrative is necessarily exclusive of being combined with others.1

"Beyond loyalty, the harsh requirements of security": Time magazine's stark coverage of the 1954 security hearing of J. Robert Oppenheimer.

“Beyond loyalty, the harsh requirements of security”: Time magazine’s stark coverage of the 1954 security hearing of J. Robert Oppenheimer.

But the Feynman approach looks perhaps unreasonably jolly when we contrast it to the narrative of J. Robert Oppenheimer and his students, for whom secrecy became something more sinister: an excuse to blacklist, a means of punishment. Oppenheimer did fine during the Manhattan Project, but the legacy of secrecy caught up with him in his 1954 security hearing, which effectively ended his government career. For his students and friends, the outcomes were often as bad if not worse. His brother, Frank, for example, found himself essentially blacklisted from all research, even from the opportunity to leave the country and start over. (It had a happy ending, of course, because without being blacklisted, he might never have founded the Exploratorium, but let’s just ignore that for a moment.)

For a lot of the scientists involved in the Manhattan Project, secrecy ended up putting their careers on the line, sometimes even their lives on the line. In response to (fairly ungrounded) suspicions about Oppenheimer’s student Rossi Lomanitz, for example, Groves actually removed his draft deferment and had him sent into the dangerous Pacific Theatre. This narrative of secrecy is what we might classically call the “tragic” narrative of secrecy — it involves a fall from grace. It emphasizes the rather sinister undertones and consequences of secrecy regimes, especially during the period of McCarthyism.

The original "best-kept secret" story, released on August 9, 1945 (the day of the Nagasaki bombing).

The original “best-kept secret” story, released on August 9, 1945 (the day of the Nagasaki bombing).

So what other narratives are there? Here is a short list, in no particular order, that I compiled for a talk I gave at a workshop some weeks ago. I don’t claim it to be exhaustive, or definitive. Arguably some of these are somewhat redundant, as well. But I found compiling it a useful way for me to think myself around these narratives, and how many there were:

  • Secrecy is essential”: early accounts, “best-kept secret” stories
  • Secrecy is totalitarian”: secret site participants’ accounts
  • Secrecy is absurd”: e.g. Feynman’s safes and fences
    • Common hybrid: “Secrecy is absurdly totalitarian
  • Secrecy is counterproductive”: arguments by Leo Szilard et al., that secrecy slowed them down (related to the “absurd” narrative)
  • Secrecy is ineffective”: the post-Fuchs understanding — there were lots of spies
  • Secrecy is undemocratic”: secrecy reduces democratic participation in important decisions, like the decision to use the bomb; fairly important to revisionist accounts
  • Secrecy is tragic”: ruinous effects of McCarthyism and spy fears on the lives of many scientists
  • “Secrecy is corrupt: late/post-Cold War, environmental and health concerns

It’s notable that almost all of these are negative narratives. I don’t think that’s just bias on my part — positive stories about secrecy fit into only a handful of genres, whereas there are so many different ways that secrecy is talked about as negative. Something to dwell on.

What does talking about these sorts of things get us? Being aware that there are multiple “stock” narratives helps us be more conscious about the narratives we talk about and tap into. You can’t really get out of talking through narratives if you have an interest in being readable, but you can be conscious about your deployment of them. For me, making sense of secrecy in an intellectual, analytical fashion requires being able to see when people are invoking one narrative or another. And it keeps us from falling into traps. The “absurd” narrative is fun, for example, but characterizing the Manhattan Project experience of secrecy makes too much light of the real consequences of it.

As an historian, what I’m really trying to do here is develop a new narrative of secrecy — that of the meta-narrative, One Narrative to Rule Them All, the narrative that tells the story of how the other narratives came about (a history of narratives, if you will). Part of talking about secrecy historically is looking at how narratives are created, how they are made plausible, how they circulate, and where they come from. Because these things don’t just appear out of “nowhere”: for each of these narratives, there is deep history, and often a specific, singular origin instance. (For some, it is pretty clear: Klaus Fuchs really makes the “ineffective” narrative spring to live; Leo Szilard and the Scientists’ Movement push very hard for the “counterproductive” narrative in late 1945; the “best-kept secret” approach was a deliberate public relations push by the government.)

As a citizen more broadly, though, being conscious about narratives is important for parsing out present day issues as well. How may of these narratives have been invoked by all sides in the discussions of WikiLeaks, for example? How do these narratives shape public perceptions of issues revolving around secrecy, and public trust? Realizing that there are distinct narratives of secrecy is only the first step.

Notes
  1. Both of these might classically be considered “comic” narratives of secrecy, under a strict narratological definition. But I’m not really a huge fan of strict narratological definitions in this context — they are too broad. []
Meditations | Redactions

Death of a patent clerk

Friday, March 15th, 2013

This post is a bit longer than most, but the story is a bit more involved than most. It’s got a little bit of everything — if by “everything” one means atomic patents and mysterious deaths.

Four of my favorite atomic patents — the nuclear reactor, the Calutron, the triggered spark gap, and the barometric fuse

Manhattan Project inventions: Patents 2,708,656, 2,709,222, 3,956,658, and 3,358,605.

During the Manhattan Project, one of the odder activities that was undertaken — approved directly by Roosevelt and Churchill — was to try and file secret patent applications for every single invention that was developed while trying to build the atomic bomb. I have written about this at length in various places and won’t repeat all of that here. Basically, the people working on the bomb project weren’t sure of what would happen after the war, and so were trying to make sure they had iron-clad legal control over the bomb, and the secret patent applications were a way to guarantee government control of nuclear technology with regards to private contractors, private scientists, and universities.

The person who was in charge of all of this work was Captain Robert A. Lavender, USN (Ret.). Lavender was the chief patent officer of the Office for Scientific Research and Development (OSRD), which headed up the civilian functions of the bomb project. Lavender was basically a Navy lawyer who knew intellectual property law inside and out. His job, basically, was to make sure that all of those secret patent applications were properly filed. He knew his stuff and he got it done. By the time the Atomic Energy Commission took over the job, Lavender’s office had docketed reports on over 5,600 different inventions relating to the atomic bomb, with some 2,100 separate patent applications ready to be filed — in secret.

Now, one of the ironies of the Manhattan Project patent program is that it pretty much operated in an opposite way than the rest of the bomb work. The bomb program was defined by its secrecy. You didn’t use the names of real things, you used code-names (“oralloy,” “copper,” “the Gadget”). You didn’t centralize information, you compartmentalized it. You worried about what you needed now, not what you needed in the future. And the patent program was the opposite: you used the real names, with centralized information, because it was about protecting the bomb — legally — for the indefinite future. So from a certain standpoint, the Manhattan Project patent division housed more technical secrets in one place than any other part of the bomb program.

Invention by Oppenheimer, patent by Lavender.

Invention by Oppenheimer, patent by Lavender.

Lavender didn’t do this alone, of course. He had a staff, and each Project site had dozens of lawyers attending technical meetings, looking for inventions, forcing the poor, harried scientists to fill out invention reports. It’s a really amusing idea if you think about it, juxtaposing that familiar narrative of the racing Los Alamos scientists with the dull banality of the legal aspects of patent applications. The local patent officer at Los Alamos, for example, recommended that they allow a “competent disinterested individual” attend the “Trinity” test so they could write a report that would testify to the “reduction to practice” of the first atomic bomb. Talk about the least interesting reason to be at “Trinity” on July 16, 1945.

The second in command at Lavender’s office was Captain Paul P. Stoutenburgh. Stoutenburgh was born in Norwalk, Ohio, on September 25, 1901. He received B.A. from Johns Hopkins in 1923, was married in 1926, and received a law degree from George Washington University in 1928. Stoutenburgh was had worked as an attorney for the Justice Department, in the claims division, and had joined the Army only in July 1945. He was discharged from the Army in February 1946 as a Lieutenant Colonel, and he thereafter resigned from the Justice Department and returned to work for the Office for Scientific Research and Development as a civilian.

When I was researching the atomic patent program, I came across Stoutenburgh’s name occasionally, but it didn’t stand out. His memos to Lavender or others weren’t anything unusual or special — just a guy doing his job. Sometimes he wrote things in Lavender’s name, the way that subordinates often do. I wasn’t drawn to him in any particular way.

But as part of my research into Lavender, I started running his name through various newspaper archives, looking for obituaries, articles, later jobs, and so on. And when I did, suddenly Stoutenburgh showed up, in a horrific way:

1946 - Dead Atom Bomb Expert Carried From Home

On the morning of Saturday April 1, 1946, a friend of Stoutenburgh’s daughter, became alarmed when she did not show up for a roller skating date and no one would answer the phone at the Stoutenburgh residence. They contacted Mrs. Stoutenberg’s brother, and another friend, and together they went to Stoutenberg’s Northwest Washington, DC, home. Finding the Stoutenberg car in the garage, they assumed the worst, and contacted the Sixth Precinct police. Three officers arrived and broke into the house through a back window.

Inside was a scene of horror. Paul Stoutenburgh was wearing his pajamas and a smoking jacket, and was sprawled across his daughter’s bed on his back, with his feet on the floor. Near his hand was a .25-caliber pistol. In his right temple, a bullet wound. He was 44.

His wife, Anna, was face-down, near the door in the same room. She wore a black housecoat. She had a bullet wound in the back of her head, exiting through the skull. She was also 44.

His daughter, Mary Alice, was found unconscious, breathing heavily on the other side of the bed, in her pajamas. She had a bullet wound in her right temple. She was taken to Walter Reed Hospital, without much of hope of survival. She died a week later, without reviving. She was 12.


What happened? According to Stoutenburgh’s former Justice Department colleagues, he had visited them the week before and told them that he’d be returning to the claims division soon. According to Stoutenburgh’s neighbors, he had developed a “‘phobia’ over atomic bomb secrets, which he believed were leaking out despite his repeated recommendations to the War and Navy Departments,” as the Washington Post put it at the time. “Atomic sescrets worried him,” they wrote under his photo — mangling the epitaph.

The War Department, for their part, told the press that “Stoutenburgh had nothing to do with the development of the atomic bomb itself,” and left it at that. Well, yes and no, as we’ve seen. He didn’t build the bomb, but he did help patent it — every part of it.

1946 - Washington Post - Stoutenburgh detail

The newspaper stories implied that Stoutenburgh succumbed to paranoia: he imagined secrets were getting out, and couldn’t take it anymore. The coroner ruled it “homicide-suicide.” The phenomena of male familial murder-suicide is not a new one. These things happen with disturbing frequency. Apparently Stoutenburgh had tried to commit suicide a month previous, and failed.

He was a troubled man in a troubling time. The spring of 1946 was the period of the first real atomic spy scare — the Gouzenko affair. In terms of actual data given away, it was a minor thing; it involved a Canadian spy ring, and General Groves had compartmentalized the Canadians out of pretty much everything he cared about.1 It was nothing like a Klaus Fuchs situation.

But in the spring of 1946 it was a big deal, both because it was the first such spy scare, and because Groves leaked the news about the espionage to the press that February. Why? Because he wanted Congress to be scared of the Russians, so they would add scarier secrecy provisions to the draft version of the Atomic Energy Act they were considering. And it worked — the changes to the law made in the spring of 1946 are responsible for the problematic “Restricted Data” clause and all of its issues.

1946 - Stoutenburgh newspaper stories

Given the context, it’s not surprising that Stoutenburgh’s death briefly made the front pages of several national newspapers. Each played up the “secrets” angle, though the stories themselves make it clear that they are about a man driven mad by fear of secrets getting out, not actual cases of secrets getting out. Therein is the question: Did secrets kill the Stoutenburgh family, or did “secrets” kill them? Was it the thing itself, or just a fear about the thing itself? Or neither?


It doesn’t strike me implausible as that someone who was on the periphery of real policy, but with an acquaintance with secrets, might, in the spring of 1946, get concerned with the loss of secrets, especially if one implies some sort of latent mental illness. But I’m an historian, not a psychologist, so I am not really treading into those waters. Still, I’ve tried to follow this up a bit, and the trail wasn’t very rich for the most part. Stoutenburgh once had an FBI file, but it doesn’t exist anymore.

2007 - Stoutenburgh FBI FOIA response

Specifically, the FBI told me that:

Records which may be responsive to your Freedom of Information-Privacy Acts (FOIPA) request were destroyed on October 1, 2001. Since this material could not be reviewed, it is not known if it actually pertains to your subject.

Now this sounds Kafkaesque, if not a wee bit conspiratorial, but I’ve been assured this is pretty standard boilerplate for a pretty common issue. Somewhere in the FBI’s record database it basically says, “we had a file with this guy’s name on it, but we destroyed it.” Ergo, they don’t really know what was in it anymore. Not so helpful.2

The Washington, DC, Police Department destroyed the records awhile back because of age. The DC Coroner’s Office, likewise. The case had been closed, ruled murder-suicide, so there was no need to keep the files. Army Intelligence had nothing on Stoutenburgh, a FOIA to the National Archives turned up nothing.

But I did find a few little other tidbits in the archives. Because it wasn’t just present-day people who worried about conspiracies — there were Stoutenburgh conspiracy theories back in the day, they just didn’t end up in the newspapers.

The first little nibble comes from the papers of James Burnham. Burnham’s work is pretty well-known — in a nutshell, he was a former Marxist who became an anti-Communist neo-conservative political pundit during the Cold War. You know the type. He wrote a lot, and wrote for the National Review, among other publications. Apparently he also collected rumors about dead patent clerks.

Burnham - Stoutenburg case, 1951

On a memo from December 1951, now in his papers at the Hoover Institution Archives, Burnham wrote that he had been called by someone he listed only as “BL.” I’ve no clue who it is meant to correspond to, but presumably it is someone who worked with Burnham regularly.  Here’s what Burnham wrote:

L stated that a fantastic and sensational story had been brought to him. He felt it essential to try to check any point we could, in order to see whether it has a presumption of truth. Involved is a man named L.t Col. STOUTENBURGH. It is stated that on 31 March 1946 STOUTENBURGH was found shot dead by a bullet in his home in Washington, D.C. His wife and daughter were also shot, presumably also dead. Apparently they were murdered, although the facts were never established. STOUTENBURGH is said to have had a secret job in connection with the atomic bomb, perhaps in something involving British-Canadian-United States liaison.

Apparently a certain E.M. Lee, living in Silver Spring, Maryland, worked with Stoutenburgh at some point. Burnham was told by “BL” that he should call Lee and tell him he was a friend of Bill Offenhauser, of Telenews in New York, and get more information. A few weeks later, Burnham called Edward M. Lee, whose number he got from a telephone directory. He spoke to Lee, who confirmed he was a friend of Offenhauser. Burnham wrote of it:

I then brought up the STOUTENBURGH case. For a minute or two, LEE shied away from the matter, and said nothing to indicate that he knew what I was talking about. Then, he stated that he had not been personally acquainted with STOUTENBURGH but had had certain relations with him. He said that STOUTENBURGH was working in the Patent Office of the ATOMIC ENERGY COMMISSION (he then corrected himself and said that at that time it was called the Manhattan Project). He (LEE) had been transferred to the Navy, and had certain “business” with STOUTENBURGH, which was transacted by telephone. He said that half a dozen or more times he had telephoned STOUTENBURGH at the latter’s office. He stated that he knew nothing further about him, and nothing about the deaths except of what he had read in the papers. (It was my impression that LEE probably knows a good deal more about STOUTENBURGH that he indicated in his telephone conversation, and that he has thought a good deal about the case.)

Burnham’s other research involved pulling up the various newspaper articles about the Stoutenburgh case. But there the trail ends. It doesn’t add up to a whole lot — even the initial lead was just a suspicion, not anything hard.


The other piece was a memo I found in the archives of the Congressional Joint Committee on Atomic Energy. In late August 1953, a certain Calvin Bertolotte of New York City got in touch with a Congressman, desiring to talk with someone about “a theory had had which might explain the operations of the Soviet espionage in connection with the atomic program.” He was put in touch with the staff of the Joint Committee, who liked to investigate this sort of thing. Bertolotte was “an employee of the Telefact Foundation engaged in research in information control and world strategy.” He told the Committee staff that he had been a friend or colleague of Sidney Young White, a physicist in New York City.

1953 - JCAE Stoutenberg detail

According to Bertolotte, White had related to him “on several occasions” the story of Stoutenburgh’s death. As the staff noted in their later write-up of their interview, “Bertolotte implied that both he and White imputed espionage significance to the story.”

Basically, Bertolotte and White’s objections to the official story were as follows, with my thoughts in parentheses:

  • Stoutenburgh actually did important secret work at the patent office and “had access to vital information.” (True)
  • White claimed to have determined that Stoutenburgh only had a .45-calibre weapon, not the .25-calibre one that he was reported to have used. (How would White have known what guns Stoutenburgh could have owned?)
  • White knew Stoutenburgh was a poor shot, so how had he hit his wife and child when at least the former was fleeing? (I don’t think you have to be that good a shot at that close a range.)
  • White “determined” (doesn’t say how) that Stoutenburgh had mentioned “either to his brother or his brother-in-law” that papers had gone missing from his desk for short periods of time, and would then be returned. (Vaguely sourced.)

Bertolotte thought the FBI ought to get involved, but didn’t want to betray White’s trust, so he gave it to the Joint Committee staff instead. (Um.) The Joint Committee staff asked whether they could relay the information to the FBI for him; Bertolotte asked to check with White first, then later got in touch and said he preferred they not give it to the FBI. The Committee staff member writing this up said that “unless advised to the contrary,” he was going to send all of this to the FBI anyway “despite Bertolotte’s objection.” I have no record as to whether he did this or not.


Where does that leave us? At a minimum, I think, we can agree with the general notion that secrecy engenders this kind of speculation. Monsters manifest within a vacuum of information, and at its peripheries. If this didn’t have any connection to “secrets,” would it stand out above the many other similar tragedies that happen each year? Obviously I wouldn’t be sending out Freedom of Information Act requests left and right if he didn’t have an atomic connection, either.

On the other hand, the fact that someone who had been so close to various secrets died under mysterious circumstances, and seems to have left no trace of any kind of official investigation, is suspicious. If you even sneezed near Los Alamos during World War II, the Manhattan Project security people would have opened a file on you. Why wasn’t there more poking around? (As for me, I poke around in these things compulsively — it’s sort of my job. I am always happy to check into unusual or unlikely stories, though I always try to do so with a skeptical mindset.)

Maybe there was, and it turned up nothing interesting, hence the destruction of the records. But I’ve got to say, the FBI sure kept around records of a lot of less-interesting cases than this one. And we do know that secrets were leaking out of the Manhattan Project during this time, after all. Stoutenburgh might not have known anything “solid” about that, but the fact that there was quite a lot of Soviet spying going on does perhaps raise our estimations of his suspicions.

Stoutenburgh signature from the Manhattan Project files

On the other hand, the idea that, say, the KGB would have killed Stoutenburgh and his family just seems unlikely. Really not their style. In general, killing someone and their whole family is not the quietest way to make accusations of spying go away. Of course, it might still be murder, but if it was, I wouldn’t really suspect the Soviets. If this were a James Ellroy novel, there’d be a murderer, but it wouldn’t really be about the atomic secrets — that would just be the hook that brings the ambitious young detective onto the case in the first place, an opening into a far seedier story. But this isn’t a James Ellroy novel. It’s real life, where banal answers are usually the correct ones.

My eventual conclusion, is that this just another sad story in a world of sad stories. It’s a story, at most, that is about the conspiracy fears that cluster around “secrets” — and the conspiracy fears that follow those conspiracy fears around, decades into the future. In this case, one almost hopes there was something more sinister to it, because it would keep it from seeming so pointlessly tragic. But pointlessly tragic is probably just what it was.

Notes
  1. Groves let a number of French and Canadian scientists work on a reactor and plutonium separation in Montreal, but it was a strictly one-way information flow. They did good work there, but they didn’t benefit from the support of the rest of the Allied effort. []
  2. Of course, the mere mention of the year 2001 is going to set off further conspiracy blinkers, but it’s hard to see any connection there. []
Redactions

The “Secret” song

Monday, February 25th, 2013

I spent some of the last week in the National Security Archive, a private archive hosted by George Washington University, looking at the papers of Chuck Hansen (1947-2003). Hansen was one of the great nuclear researchers, meticulously compiling thousands upon thousands of nuclear documents by means of archival visits, Freedom of Information Act requests, and crawling of the public literature. His books, U.S. Nuclear Weapons (1988) and Swords of Armageddon (1995), were the final products of this trawling. They weren’t scintillating reads, but they’re chock full of interesting technical details derived from his voluminous archives.

Hansen papers, Box 18

How many boxes do you have lying around with “NUCLEAR WEAPONS SECRETS” written on the side of them? Answer truthfully.

I found a lot of useful files for a number of projects I’m working on (including the oft-mentioned book), but I also found a few highly amusing things as well. Chief among these is a song composed by someone at the Operation Upshot-Knothole nuclear test series, held at the Nevada Test Site in 1953. What’s really remarkable about it is that it appears to use the classified names of the actual nuclear devices, earning it a nice “SECRET” rating. How many “SECRET” songs do you know?1

It follows a little poem about setting up the tests which is not quite as good, except for the final stanzas:

As someone says, without aplomb
“We just can’t seem to find the bomb.”
So D (for day)
Looks pretty gray
For something’s surely gone agley
No bomb? Oh well
And what the hell?
We’ll try again some other day.

Below is a transcription; the original can be viewed here. The names of the devices have been blacked out in the original, but through referencing Hansen’s published work (he ferreted them out from here and there), his speculations in the margins (some of which must be right, some of which must be wrong), along with some of the internal indications (e.g. puns, character spaces), I think I’ve worked out what they are meant to be:

There were ten little gadgets, sitting in a line
[XR-3] was X-quisite and then there were nine.

There were nine little gadgets, the tower held the weight,
[ZOMBIE] had a kick to it, and then there were eight.

There were eight little gadgets (oh, NPG2 is heaven?)
They couldn’t hide the [HYDRIDE-1,] and then there were seven.

There were seven little gadgets, brought out for kicks,
[DIXY]3 was deuti-full4, and then there were six.

There were six little gadgets, pretty much alive,
[BUZZARD]5 said “let’s carrion”, and then there were five.

There were five little gadgets, they couldn’t find no more,
[HYDRIDE-2]6 kicked up its heels, and then there were four.

There were four little gadgets, observers came to see,
One was [SIMULTANEITY,] and then there were three.

There were three little gadgets, [HAMLET] got his due,
The time was not so out of joint, and then there were two.

There were two little Gadgets, [ENCORE]7 said this is fun,
The military got Effects, and then there was one.

There was one little gadget, that lonesome little Gun,8
They shot the hell right out of it
And
        then
                 there
                         was
                                NONE.

Someone else (not Hansen) has hand-written “Climax!” at the bottom of the page, here — indicating, perhaps, that the original poem was written before the final, late addition to the Upshot-Knothole schedule was added. The eleventh shot, approved at the very last minute as a special addition to the series was shot CLIMAX.9

Shot HARRY (HAMLET) of Operation Upshot-Knothole.

Shot HARRY (HAMLET) of Operation Upshot-Knothole.

The whole thing looks a little more ominous, though, when you know that Upshot-Knothole had some fairly negative public health effects. The ninth shot, HARRY (the “HAMLET” device, above) was extremely dirty — a lot of fallout resulted and contaminated nearby St. George, Utah. As Richard Hewlett and Jack Holl put it:

Postponed for three days because of unfavorable weather, Harry was fired under what seernecl to be perfect conditions. But a wind shift and a slight increase in wind velocity spread fallout in a pattern about fifty miles square over populated areas east of the proving ground. For the second time in a month roadblocks were set up on major highways to monitor motor vehicles. At 9:10 a.m., about four hours after the shot had been fired, readings as high us 0.32 roentgens per hour were being recorded at the roadblocks. At that time Edward S. Weiss, the Public Health Service officer stationed in St. George, called the sheriff’s oflice and radio station to warn people in the area to take cover. Local schools kept children indoors during the morning recess, and the washing of contaminated cars in St. George was suspended. By 9:40 a.m. most of the population in St. George was under cover, and the community came to a standstill. … From measurements at St. George the test group later estimated that the maximum amount of external exposure that could have been received at St. George was 6.0 roentgens and 5.0 roentgens at Cedar City.10

That’s probably not enough to kill you by itself, to be sure, but it’s still some thousands of times higher than the average background radiation, higher than the maximum “safe” dose that had previously been established for the entire test series, and just one of the many tests that rained fallout on the people in those towns. It may, even, have been responsible for killing John Wayne and much of the cast of The Conqueror, too. (I’m usually dubious about attributing individual deaths to such exposures — the probabilistic nature of such cancers makes it very hard to attribute them on an individual level, as opposed to an epidemiological level — though the rates for the cast, and the types of cancers involved, are particularly disturbing.)

The people running the test shot were hardly ignorant of such possibilities. Consider the first lines of the “poem” that preceded the “song”:

We’ll all be safe
As Rad can be
For milliroentgens frighten me

And if a meter
Starts its clickin’
We will run to beat the dickens

So it’s all fun and games… unless the winds shift.

Notes
  1. Citation: Poem and song about Operation Upshot-Knothole (ca. May 1953), copy in the Chuck Hansen papers, National Security Archive, George Washington University, Box 18, “1953,” folder 1. []
  2. NPG = Nevada Proving Ground = Nevada Test Site. []
  3. This might not be right. The spacing is four letters; nothing obviously fits. It can’t be “RUTH” because that’s one of the HYDRIDEs. “DIXIE” is the official name of the test, though one can imagine the scribe got the spelling wrong. The device name for DIXIE was apparently “DEUTERIUM,” which goes with the sentence. []
  4. Amusingly, this is the only part of the song that made it into Hansen’s published work. Footnote 534 of Volume II of Swords of Armageddon reads: “An untitled, undated classified poem issued sometime soon after the end of UPSHOT-KNOTHOLE states that the fourth shot ‘was deuti-full.’ The device may have used a solid or crystalline lithium deuteride boosting charge.” []
  5. Hansen thought this might be HYDRIDE-2, because it is the next in order. But “let’s carrion” must be a reference to BUZZARD, no? Plus it fits perfectly with the spacing. []
  6. Might also be “DEUTERIUM,” the device name for the DIXIE shot. []
  7. Well, this is and isn’t right. The space here is only four letters. But the ninth device was dubbed “EFFECTS” and was test “ENCORE” so it’s got to be something about that. Maybe it was spelled eccentrically, like NCOR? Or something like XR-3. []
  8. This is, of course, the famous GRABLE atomic cannon shot. Apparently the censor did not know that GUN was its device name, and it was not redacted. []
  9. The eleventh was needed because an earlier shot failed to reach its full yield. The device in question, COBRA, was the primary for at least one of the devices in the CASTLE series and its exact yield needed to be known ahead of time. Eisenhower was very irritated by the last-minute addition and approved it only because it meant they could cancel another test series, DOMINO, that had been planned for later in the year. []
  10. Richard G. Hewlett and Jack M. Holl, Atoms for Peace and War, 1953-1961: Eisenhower and the Atomic Energy Commission (University of California Press, 1989), 154. []
Visions

More nuclear symbolism

Tuesday, January 22nd, 2013

Two small graphical things I wanted to share that came from feedback on a few recent posts.

The first is an explanation, of sorts, of the United Kingdom Atomic Energy Authority’s very unusual emblem:

UKAEA Coat of Arms

I had ragged on the AEA’s design as being particularly stodgy, but I’ve been corrected. It’s just unduly weighed down by obscure symbolism, as a commentator pointed out. It was, apparently, designed by the Royal College of Arms with the following visual references:

  • The central shield is black denoting the core of a graphite reactor, with inserted rods of silver uranium.
  • The inverted triangle shows gold and scarlet bolts of heat and power.
  • The energy released by splitting the atom is controlled by a pair of red pantheons, which are ferocious heraldic beasts. They are firmly held to the ground by thick golden chains to ensure the energy is firmly controlled.
  • The pantheons have 13 six-pointed stars and two seven-pointed stars, totalling 92. These represent the 92 natural elements found in creation and also the atomic number of uranium.
  • The five spikes on the collars signify the atomic number of boron, which was used to shutdown the early reactors.
  • There are numerous representations of 8 for the atomic number of oxygen, 2 for helium and 1 for hydrogen – suggesting water. The whole gives insights into the four medieval elements of earth, air, fire and water.
  • The sun represents the power of fusion, and the small shield with the black bird (a martlet) is the Coat of Arms of Lord Rutherford. He is recognised as the founder of nuclear physics.
  • The steel helmet signifies the arms of a corporate body.
  • The whole is placed on the earth on which flowers and plants are flourishing normally. [???]
  • The motto “E minimis – maxima” means; ‘from the smallest, the greatest‘.

I thought that was interesting enough to share. Any resemblance between the “pantheons” and mutated horse-dogs is apparently entirely coincidental. And despite the barren, Moon-like appearance of the “earth,” it is apparently “flourishing normally.” Actually, the above image, painted on the doors of the Dounreay Prototype Fast Reactor, is slightly different than the other image of the emblem I had posted, which does have a more flourishing-looking ground cover, as well as a knight’s head.

All of this is a stark contrast from the US Atomic Energy Commission’s emblem, whose symbolism seems to have been, “it’s an atom, stupid.” I hereby promote the AEA’s emblem from “most boring” to “not as boring as I thought,” which leaves the current Department of Energy seal as the “most boring.”

Secondly, I have another cryptic drawing referencing the history of the hydrogen bomb, again by George Gamow. This one has been reproduced here and there, but a friend of mine came across an original version in the Gamow papers at the Library of Congress awhile back, and sent me his photographs of it and its captions. The drawing follows:

H-bomb history drawing, by George Gamow

The attached caption (written, as always, in Gamow’s amusing handwriting and bad English) was as follows:

A drowing made by G. Gamow (with photographic inserts) which was handing [hanging?] in his office in the Los Alamos Scientific Laboratory during the dispute about the political necessity of developing an H-bomb and during the early stages of its developement after President Truman sayd: “Yes, go ahead.”

Top left is Comarade Stalin carrying the A-bomb made in the USSR.

Top right is Dr. Robert Oppenheimer who was objecting against H-bomb project on the basis that it is extremely difficult (actually it took less than two years) and will induce USSR to do the same (actually Russians worked on H-bomb when this discussion was taking place).

The coffin with the Harvard University coat of arms belong to Professor Dr. James B. Connant who said that: “H-bomb will be built only over his dead body.”

On the bench below are Dr’s Stan Ulam, Edward Teller, and George Gamow, demonstrating their proposals for making H-bomb. The simbolism of these deviced cannot be explained because AEC classified them as “SECRET”. 

The “simbolism” is fairly cryptic. The caption dates it around February 1950, so that might make it even harder to make sense of, as we’re talking about fairly early days when it comes to the final H-bomb design, but I’m not sure how reliable I find that dating. (The H-bomb debate was in late 1949-early 1950, though the caption was obviously written at a much later time.)

Looking for some insight into the technical discussions that were happening at this time, I took a gander at Anne Fitzpatrick’s quite detailed thesis on the early history of the H-bomb, “Igniting the Light Elements: The Los ALamos Thermonuclear Weapons Project, 1942-1952,” (Virginia Polytechnic Institute and State University, 1999), which was issued as LA-13577-T. Fitzpatrick’s work is notable as one of the few H-bomb histories that have been written by a non-participant but also with access to classified information. (The whole thing was, of course, screened for security, and she notes in a few places where she was asked to label things merely as “special” to make them more vague.)

Fitzpatrick notes that Gamow spent a sabbatical year at Los Alamos in 1949-1950, to help with work on the H-bomb, which matches up with his caption above. While there, he seems to have produced a bevy of H-bomb-themed drawings, of which she reproduces three. One shows the complexity of the energy flow problem in a Super, another portrays the hydride bomb (“Elmer”) as “unattractive and clumsy” in comparison with a lower-yield water penetrating fission bomb (“Elsie”/”L.C.”), and the another portrayed Ulam and Teller themselves as the ultimate Super design:

Gamow's Can't Lose Model for the Super

But back to the original, “simbolic” Gamow image. Ulam’s spittoon almost surely references the fact that you’re using forces at a (relative) distance to compress the secondary, right? Whether one does that by hydrodynamic lensing (Ulam’s original proposal) or radiation implosion (the later Teller-Ulam design) doesn’t seem to be distinguishable. On the other hand, Ulam didn’t propose that until 1951, so this might be something else entirely. Fitzpatrick’s thesis doesn’t spell out any additional Ulam proposals that I saw.

Teller’s is much more cryptic. Looking at Fitzpatrick’s thesis, she says that at this time, Teller was championing a device dubbed “Little Edward.” (Oh myyyy.) This was, she says, “a giant, high-yield multi-crit gun device proposed by Teller that was supposed to produce x-radiation to ignite the D-T mixture in the Super.” Could that be the string of beads with the giant Omega in the middle of it? It sounds like an ungainly device, and indeed, it was eventually dropped as being very wasteful and without much guarantee that it would do anything better than other designs on the table.

And lastly, there’s Gamow’s. According to Fitzpatrick, Gamow’s design was known as the “Cat’s Tail.” She says that it was “a variation on the large fission detonator purported to ignite the Super… Gamow theorized that the Cat’s Tail needed less T[ritium] than had been assumed in the ENIAC Super problems, but could not guarantee this.” Since, as far as I know, Gamow’s designs have never been discussed openly (and were not successful), it’s pretty difficult to try and correlate such an image to an actual bomb design.

Presumably there were no cat-driven hydrogen bombs, though having owned a cat, I can see that one might be seriously tempted to exploit some of their malicious energy in this way. I welcome any and all additional interpretations.

Visions

The story behind the IAEA’s atomic logo

Friday, January 11th, 2013

Since my post last week was such a bummer, I thought I’d do something a little more fun and trivial today.

The International Atomic Energy Agency (IAEA) has, without much competition, the coolest logo of any part of the UN.1 Heck, I’ll go so far as to say that they have the coolest logo of any atomic-energy organization in history. I mean, check this thing out:

IAEA flag

It’s not only an atom, it’s an atom with style. It’s got a classic late-1950s/early-1960s asymmetrical, jaunty swagger. Those electrons are swinging, baby! This is an atom for love, not war, if you dig what I’m saying. An atom that knows how to have fun, even when it’s doing serious business, like investigating your nuclear program. The James Bond of atoms.

The staid seal of the US Atomic Energy Commission cannot really compete for hipness, though it gets major nostalgia points and I love it dearly. The emblem of the Atomic Energy Organization of Iran is arguably the only real runner-up — check out that minimalism! Most worldwide atomic energy organizations/commissions have variously tacky rip-offs of the original AEC logo. The UK’s Atomic Energy Authority gets props for having the least cool emblem of any atomic energy agency, and also the least obviously atomic (the little sun at the top, and the Latin, somewhat give it away). On the other hand, it’s the only one that looks like it would be perfectly at home inside a Lewis Carroll book.

For awhile, I’ve been kind of obsessed with finding out who drew this thing. It looks remarkably similar to the aesthetic adopted by the Swiss designer Erik Nitsche, who did a lot of other groovy atomic posters for General Dynamics. This poster of Nitsche’s from 1955 has similarly jaunty orbitals, though I don’t think they’re meant to be electrons:

But upon further investigation, I’ve not found any evidence that Nitsche was involved, sadly. In fact, all signs point to an anonymous staffer in the US State Department, but the story is a bit more fun than just that.

The IAEA was founded  in 1957 as the UN organization that would try to enact the “Atoms for Peace” plans of the Eisenhower administration. It wasn’t yet the nuclear watchdog organization; that came later, with the Nuclear Non-Proliferation Treaty. Its first head was W. Sterling Cole, a former US Congressman who had been a member of the Joint Committee on Atomic Energy. From pretty much the very beginning, the IAEA started using a little atomic logo on its letterhead:

IAEA letterhead, July 1957

The first instance of this I’ve found is the above, dated July 1957 (though the document was published in August), which is the same time as the IAEA came into being, more or less. By October 1957 they were using a white-on-black approach but it was basically the same thing. An internal IAEA history chalks its creation up to someone within the US State Department or the US Atomic Energy Commission — which is another way of saying, they have no real idea, except that it seems to have come from America. Fair enough, I suppose, though looking at what the Atomic Energy Commission’s own stab at an “Atoms for Peace” logo, I find it really unlikely that they had anything to do with it:

It’s a pretty different aesthetic: that staid AEC atom (perfectly symmetrical), plus a dog’s breakfast of other generic symbols (microscope! medicine! a gear! wheat!). It’s a lousy emblem — it’s messy, it’s generic, and it has finicky details that wouldn’t reproduce well at a small size, which means that it always looks too big.

Anyway, the first IAEA logo, as you can see, was a somewhat informal thing — it’s not as stylized, and its lines aren’t very confident, but the essence of the final emblem is there, hidden within it. It doesn’t have little dots for electrons, and the asymmetry looks only somewhat intentional. They used this up until 1958 without anybody raising any fuss, and without formally adopting it.

But at some point in 1958, someone with just enough education to be dangerous noticed that their little peaceful atom had three electrons. What element has three electrons, typically? Lithium. What’s lithium most associated with, in the area of atomic energy? Hydrogen bombs. Lithium deuteride is the main fusion fuel in hydrogen bombs. When the lithium nucleus absorbs a neutron, it turns into tritium and helium. Tritium and deuterium readily fuse. It’s a nice little reaction — if you’re a weapon designer. If you’re an “Atoms for Peace” agency, it’s a little more problematic. So someone — again, nobody seems to know who — flipped about this. An easy fix was proposed: add another electron! Then it’s no longer lithium… it’s beryllium. Let’s all collectively ignore the fact that beryllium is also used in nuclear weapons, and is also fiendishly toxic, to boot. If they’d just added one more orbital, it would have made boron, which is a neutron absorber that keeps you from getting irradiated — a little more on target, but nobody asked me.

You can see the extra orbital somewhat crudely added to the original emblem in this backdrop at the Second Annual General Conference of the IAEA, from 1958:

They’ve also added little dots for the electrons, too. The version above is somewhat wildly, problematically asymmetrical — the orbitals don’t intersect well in the upper-left corner at all.

Once they started messing with it, though, things got a little out of control. Why stop with just another electron? Now here’s the part where I can clearly see an American governmental influence… they started mucking it up. To quote from that IAEA internal history I referenced before:

Once the process of altering the emblem had started, further suggestions were made and soon a design evolved in which the central circle had been expanded into a global map of the world and five of the eight loops formed by the ellipses contained respectively: a dove of peace with an olive branch; a factory with smoking chimneys and surcharged with a train of three gear wheels; a microscope; two spears of grain; and finally a caduceus, to symbolise respectively the peaceful, industrial, research, agricultural and medicinal uses of atomic energy.2

If that isn’t the most god-awful design-by-committee creation, what is? Another fun fact: they made it gold.

I’d love to show you a version of that one, but I can’t find a copy of it. It sounds wonderfully awful. The helpful folks at the IAEA archive have been unable to track down a drawing of it — at least, within as much energy as they are willing to expend on such a folly, which is understandably limited. I’ve gone over every image I could find from the time period looking for a picture of it. No dice. But, just to have some fun, here is a “creative interpretation” of the above, which I have myself drawn up for you:

IAEA 1958 logo (artist's interpretation)

Ah, but they didn’t stop there. Cole, the IAEA Director General, apparently enjoyed this enough that he had the new emblem printed in gold on a blue flag, and put it up above the United Nations flag outside of the Third General Conference of the IAEA in 1959.

Apparently in UN-world, this was seen as a major scandal. A representative of the UN Secretary General, Dag Hammarskjöld, saw it, flipped out, and had it immediately removed. And it was never seen again. 

Shortly after this flap, it was decided that perhaps they ought to have a formal procedure before creating their emblem. They rolled back all of the modifications except the extra orbital, and cleaned up the layout a bit, and added a set of olive leaves to match the UN flag. On April 1, 1960, this finalized emblem was adopted by the IAEA Board of Governors, in a document that the IAEA archives folks were willing to dig up for me and post online:

INFCIRC/19 - The Agency's Emblem and Seal

As with all things, we’re left with the final product and generally no indication that there was a process to get to it. But, as with all things, there is a process: there is a history. Emblems don’t just pop out of nowhere fully formed, just as institutions, organizations, and policies always have to follow a messy path when coming into existence. The emblem, aside from being a piece of natty graphic design, is one of those typical organizational by-products. Somebody started drawing it, not knowing what it was, and they’ll continue drawing it forever just because… with a slight detour to make it especially ugly after having found a conceptual problem in their original, ad hoc, implementation.

Anyone who has dabbled in graphic design will also recognize this process. You start with half an idea, one imbued with a germ of goodness inside it, somewhere. You try to elaborate on the idea, inevitably making things worse temporarily  Finally, scaling things back, you return to the original, and find that beautiful thing that was hiding in it all along, just out of sight. The snazzy, modern emblem wasn’t achieved on the first go round — it had to pass through design hell before its potential for good could really emerge.

Notes
  1. Technically the IAEA is autonomous from the UN though under its aegis. []
  2. Paul C. Szasz, “The Law and Practices of the International Atomic Energy Agency,” [IAEA] Legal Series No. 7 (Vienna: International Atomic Energy Agency, 1970), 1001-1002. []