1. Computers
  2. Display Drivers
  3. Graphics Cards
  4. Memory
  5. Motherboards
  6. Processors
  7. Software
  8. Storage
  9. Operating Systems


Facebook RSS Twitter Twitter Google Plus


Phoronix Test Suite

OpenBenchmarking.org

Touring The Chernobyl Nuclear Accident Site In 2010

Michael Larabel

Published on 7 April 2010
Written by Michael Larabel
Page 2 of 9 - 85 Comments

Testing of this nuclear safety feature in April of 1986 turned into this deadly disaster as established procedures were not followed and in the minutes leading up to the accident, emergency warnings were ignored and mistakes were made. There also proved to be several flaws within the design of the Soviet RBMK nuclear reactor and in its construction. In the early hours on the 26th of April, the experiment of testing the steam turbines to produce electricity for the reactor's water pumps began while the diesel generators began ramping up their electricity production. Where the test went wrong was when the water flow rate dropped due to the turbines losing momentum, steam voids formed within the nuclear core that caused the water coolant system to not work as effectively, which in turn drove up the power output from the nuclear reactor. As the power output increased, more heat was generated that caused more water to turn into steam and this was a cascading effect as the reactor continued outputting more power due to the rising temperature.

The rise in temperature and power was attempted to be offset by cooling down the nuclear rods via inserting them into the core, but due to technical problems, the nuclear fuel rods could not be fully inserted in time. The temperature / power output jumped greatly before the first explosion occurred due to the steam build-up as the top of the reactor blew off. Fires began on other buildings at the Chernobyl Nuclear Plant from burning graphite and other radioactive material that was shot from Reactor #4. There are many details of this accident not fully known due to, among other reasons, many of the key plant employees having died from the radiation. In the end, the Chernobyl nuclear accident is attributed to testing out a nuclear safety feature that exploited many mistakes from human error to design/construction flaws with the RBMK reactor. Worth noting is that none of the reactors at Chernobyl had a containment building, which is effectively an airtight shield made of steel and concrete that covers the nuclear reactor and presents radiation from escaping into the atmosphere. Such containments are standard in nuclear power plants found in the United States and other parts of the world, especially after the devastating nuclear accident at Chernobyl. If such a containment been in place on these reactors, the disaster should not have been nearly as devastating.

In regards to the severity of this nuclear accident, this is the only nuclear power plant disaster to ever be declared a level seven event on the International Nuclear Event Scale. A level seven nuclear event is the most severe as rated by the International Atomic Energy Agency (IAEA) with an event of this magnitude causing widespread health and environmental effects far beyond just the vicinity of the nuclear accident. For comparison, the commonly known Three Mile Island nuclear accident in Pennsylvania and the Windscale Fire in the United Kingdom were each rated only a level five event on this Richter-like scale of nuclear tragedies. There was only ever a single nuclear accident that was declared a level six event -- the second worse nuclear disaster in history -- by the IAEA and that too took place in the former Soviet Union more than 50 years ago. As another scale for comparison, the Chernobyl nuclear accident led to more than one hundred times the nuclear fallout of what was experienced during the atomic bombings of Hiroshima and Nagasaki during World War II.

Latest Linux Hardware Reviews
  1. CompuLab Intense-PC2: An Excellent, Fanless, Mini PC Powered By Intel's i7 Haswell
  2. From The Atom 330 To Haswell ULT: Intel Linux Performance Benchmarks
  3. AMD Radeon R9 285 Tonga Performance On Linux
  4. Apotop Wi-Copy
Latest Linux Articles
  1. AMD Moves Forward With Unified Linux Driver Strategy, New Kernel Driver
  2. MSI: Update Your BIOS From The Linux Desktop
  3. NVIDIA vs. AMD 2D Linux Drivers: Catalyst Is Getting Quite Good At 2D
  4. 15-Way GPU Comparison With Mesa 10.3 + Linux 3.17
Latest Linux News
  1. Linux 3.18-rc1 Released One Week Early With Many Changes
  2. The VC4 Gallium3D Driver Is Still Moving Along For The Raspberry Pi
  3. Direct3D 9 Support Might Land Within Mainline Mesa 3D Drivers
  4. OpenGL Preview Benchmarks For NVIDIA's GeForce GTX 970
  5. HOPE: The Ease Of Python With The Speed Of C++
  6. Vitesse: Using LLVM To Speed Up Databases
  7. AMD Is Restructuring Again, Losing 7% Of Employees
  8. Linux Testing Of The NVIDIA GeForce GTX 970
  9. Qt 5.4 Now In Beta With Web, Bluetooth LE, Graphics Improvements
  10. AMD's Radeon R9 285 On Linux Offers Good OpenCL Performance
Latest Forum Discussions
  1. NVIDIA Presents Its Driver Plans To Support Mir/Wayland & KMS On Linux
  2. AMD Is Restructuring Again, Losing 7% Of Employees
  3. Bye bye BSD, Hello Linux: A Sys Admin's Story
  4. Open-Source AMD Fusion E-350 Support Takes A Dive
  5. Upgrade to Kaveri, very slow VDPAU performance
  6. ChromeOS Drops Support For EXT2/EXT3/EXT4 File-Systems
  7. Lennart Poettering On The Open-Source Community: A Sick Place To Be In
  8. The Slides Announcing The New "AMDGPU" Kernel Driver