RSICC Home Page

RSICC CODE PACKAGE CCC-783



For the current version of RASCAL 4.3.1 please visit https://ramp.nrc-gateway.gov/codes/rascal


  1. NAME AND TITLE

    RASCAL 4.3: Radiological Assessment Systems for Consequence AnaLysis.


  2. CONTRIBUTORS

    Athey Consulting, Charles Town, West Virginia,

    Ramsdell Environmental Consulting, Redmond, Washington, Pacific Northwest National Laboratory, Richland, Washington,

    U.S. Nuclear Regulatory Commission, Washington, DC.


  3. CODING LANGUAGE AND COMPUTER

    Visual Basic and Visual Fortran; PC running Windows OS (XP, 7, 8) (C00783PCX8602).


  4. NATURE OF PROBLEM SOLVED

    RASCAL Version 4.3 is the latest in the series of the Radiological Assessment System for Consequence AnaLysis codes. It evaluates releases from nuclear power plants, spent fuel storage pools and casks, fuel cycle facilities, and radioactive material handling facilities. Developed for the U.S. Nuclear Regulatory Commission, RASCAL is designed to be used in the independent assessment of dose projections during response to radiological emergencies. The system supplements assessments based on plant conditions. RASCAL will be used by response personnel to conduct an independent evaluation of dose and consequence projections and for training and drills. The model was developed to allow consideration of the dominant aspects of source term, transport, dose, and consequences. Source term calculations in RASCAL estimate the amount of radioactive (or hazardous) material released based on a wide variety of potential radiological accident scenarios. The source term calculations performed that pertain to fuel-cycle facility and materials accidents can generally be categorized as (1) fuel-cycle facility/UF accidents, (2) uranium fires and explosions, (3) criticality accidents, and (4) isotopic releases (e.g., transportation, materials).

    Major changes and improvements in RASCAL 4.3 are listed below.

  5. METHOD OF SOLUTION

    RASCAL is a set of tools for emergency response applications. There are four primary tools and three support tools. Two of the primary tools make dose calculations, and the other two display information related to radionuclides and their decay.

    The most used tool is STDose. It has modules that calculate the release of material to the atmosphere from several types of nuclear facilities, including nuclear power plants, fuel cycle facilities, and industrial facilities that use radioactive material. Material released to the atmosphere is transported, dispersed, and deposited using Gaussian models. A straight-line Gaussian model is used for near-field calculations, and a Lagrangian Gaussian puff model is used for far-field calculations. Deposition is calculated using a deposition velocity approach in which spatially and temporally varying deposition velocities are estimated using a resistance analogy. Iodine is treated as consisting of three species, iodine associated with particles, reactive iodine gas (e.g. I2), and non-reactive gas (e.g.CH3I). Doses may be calculated using either ICRP-26/30 or ICRP 60/72 dose conversion factors. Submersion doses are calculated using both finite plume and semi-infinite plume models. Calculated doses are compared with various protective action criteria as appropriate.

    The other dose calculation tool is Field Measurement to Dose (FMDose). It calculates dose for the first year after the event, the second year after the event, and 50 years after an event from field measurements of deposited radionuclides. The tool calculates groundshine, submersion, and inhalation doses at the measurement point. All dose calculations include decay and ingrowth of daughters. Groundshine doses include the effects of weathering, and submersion and inhalation doses include both weathering and re-suspension.

    The support tools are used in conjunction with STDose. The first of these tools is used to create a file that describes the recent operational history of a power reactor. The file is used if an option to create custom core and spent fuel inventories is selected in STDose. The second tool is used to merge source term files from two or more reactors in the event of a multiple reactor event. The tool may also be used to create a source term file for use with other codes. The third support tool is used to set up a utility program that can download meteorological data (observations and forecasts) from the internet.


  6. RESTRICTIONS OR LIMITATIONS

    RASCAL is a set of tools for emergency response applications. As a result, it bases its estimates of material released on limited information that should be available at the time of the event. The atmospheric transport, dispersion, and deposition of the released material are calculated using available meteorological information, which may be limited. The consequence assessments are based on simple models. Each of these components has inherent uncertainties. RASCAL does not model the uncertainties or estimate confidence intervals for its consequence estimates. It is the responsibility of the consequence assessor to understand the limitations of the models implemented in RASCAL and determine whether or not RASCAL output is reasonable.


  7. TYPICAL RUNNING TIME

    RASCAL is designed to permit a complete consequence assessment and evaluation of results within 15 minutes.

    Data entry times for RASCAL depend on the complexity of the problem being addressed. Data for simple problems can be entered in less than a minute. Data entry for more complex problems can generally be accomplished in less than five minutes. Run times depend on the computer and duration of the period being modeled. The run time for a 24-hour release takes less than 30 seconds on a computer with an Intel i7 CPU with Windows 8. Running the same problem on a computer with an Intel i5 CPU and Windows 7 takes about 35 seconds.


  8. COMPUTER HARDWARE REQUIREMENTS

    RASCAL runs on computers using the Windows operating system (XP, 7, or 8).


  9. COMPUTER SOFTWARE REQUIREMENTS

    RASCAL 4.3 is a Windows-based application. Executables included in the package were created using Microsoft Visual Basic 6, Microsoft VB.NET, and Intel Visual Fortran compilers. No source files are distributed. The software was tested under Windows 8, Windows 7, and XP service pack 3. Some modules require Microsoft.NET Framework 4.


  10. REFERENCES

      1. Included Documentation

        RASCAL Installation and Notes (informal document) 2013.

      2. Background Documentation

    J. V. Ramsdell, Jr., G. F. Athey, S. A. McGuire, and L. K. Brandon, “RASCAL 4: Description of Models and Methods,” NUREG-1940 (December 2012).

    G. F. Athey, L. K Brandon, and J. V. Ramsdell, Jr., “Draft RASCAL 4.3 Workbook,” (September 2013).


  11. CONTENTS OF CODE PACKAGE

    Included in this package are the Windows executable, data, help files, and an install procedure. Source files are not included in this release.


  12. DATE OF ABSTRACT

March 1993, May 1995, August 1997, November 1998, July 2001, June 2002, July 2007, February 2008, May 2008,

January 2009, August 2011, September 2012, September 2013.


KEYWORDS: EMERGENCY RESPONSE; CONSEQUENCE ASSESSMENT; DOSE CALCULATION; NUCLEAR POWER PLANT; FUEL CYCLE FACILITY; GAUSSIAN PLUME MODEL; INTERNAL DOSE; MICROCOMPUTER; RADIONUCLIDE TRANSPORT; RADIOACTIVITY RELEASE; RADIOLOGICAL SAFETY; REACTOR ACCIDENT