In August 1996, SUMMARIZE was revised to Version 2.15 and was validated on a DEC Alpha 2100 with OpenVMS 6.1 [5, 6].  Test Cases 2, 3, 5, 6, and 7 for the validation of SUMMARIZE 2.15 were identical to test cases for the validation of SUMMARIZE 2.10.  The acceptance criteria for these test cases were satisfied by DOE when they demonstrated that the output from SUMMARIZE 2.15 was identical to the output of the SUMMARIZE 2.10 validation tests.  Test Cases 1 and 4 were modified to test code functionality that changed from Version 2.10 to Version 2.15.  In these test cases, the acceptance criteria were satisfied by analysis of the output of SUMMARIZE 2.15.

In July 1997, SUMMARIZE was revised to Version 2.20 and was validated on a DEC Alpha 2100 with OpenVMS 6.1 [1, 2].  The validation test included the seven test cases defined for Version 2.15, and an additional Test Case 8.  Test Case 8 was added to verify the correction of an error found in Version 2.15.  Acceptance criteria for Test Cases 1 - 7 were satisfied by comparing output of SUMMARIZE 2.20 to the output of SUMMARIZE 2.15, while the acceptance criteria for Test Case 8 were satisfied by analysis of the output of SUMMARIZE 2.20.
SUMMARIZE 2.20 has one current Software Problem Report [6].  The subroutine SURFER_PRINT_TWO_D_GRID prints data to a file that can be read by the SURFER plotting program.  This subroutine contains an error that causes the data to be printed incorrectly.  The error was determined by DOE (and checked by EPA) to be of no consequence, since the SURFER output capability is not used by WIPP PA.  SUMMARIZE has not been revised to correct the error.  Test Case 3 produces SURFER-formatted output as part of the test case.  Hence, DOE expected to find numerical differences in the output of Test Case 3.

In order to test new operating systems that were added in 2002 - 2003 (Section 1), regression test results from SUMMARIZE 2.20 run on the ES40 using OpenVMS 7.3-1 were compared to results from the validation tests of SUMMARIZE 2.20 run on a DEC Alpha 2100 using OpenVMS 6.1.  In June 2003, the Agency completed a report documenting the Agency's approval of SUMMARIZE 2.20 on those operating systems [7].  In January 2003, two new hardware systems were added to conduct PAs for the WIPP; a Compaq ES45 and a Compaq Alpha 8400, both running OpenVMS 7.3-1 [8, 9].  In September 2004, the Agency concluded that SUMMARIZE 2.2 met the acceptance criteria specified in the VVP [1], and was considered as validated on the COMPAQ ES45 and 8400 platforms using OpenVMS 7.3-1 [10].  SUMMARIZE 2.2 was used to support the 2004 CRA.

In the 2004 CRA review of the SUMMARIZE code, EPA and DOE both found errors in how the code selected input data and cumulated results when generating output summary.  These errors were traced back to errors in the SUMMARIZE input files and not the code itself.  The errors were corrected for use with Version 3.00 of the SUMMARIZE code and verified by EPA [28].

Version 3.00 of the code was subsequently validated to run on the COMPAQ ES40 with OpenVMS 7.3-1 [12].  Following the validation of the code on the ES40 it was regression tested to run on the ES45 [13, 15].

In 2005, two Software Problem Reports were completed that identified two issues with SUMMARIZE 3.0 [18, 19].  SPR 05-002 discussed an underflow problem when interpolating very small numbers.  The error only occurs when the absolute difference between the two values to be interpolated is less than 0.29E-39 [18].  SPR 05-003 discussed a problem in the untested feature TIMES=All.  When TIMES=ALL requested in the *TIMES environment, an extra record is appended to the expected output records.  This extra record contains meaningless values [19].

In 2005, a Change Control Form was completed that indicates SUMMARIZE 3.0 will be updated to SUMMARIZE 3.01 after the problems are resolved [20].  The problem identified in SPR 05-002 was corrected by converting the single-precision CAMDAT input values to double-precision and doing all real arithmetic in double-precision.  SUMMARIZE 3.00 uses the CAMSUPES_LIB method of dynamic allocation.  Where appropriate, SUMMARIZE 3.01 arrays will be declared and allocated with Fortran 90 constructs.  To rectify the problem identified in SPR 05-003, the extra record appended to the output will not appear with SUMMARIZE 3.01 [19].

Following the provisions of the Change Control Form, a new ID [21] and VVP/VD [22] were developed for SUMMARIZE 3.01.  As indicated in the VVP/VD, SUMMARIZE Version 3.01 is a modification of SUMMARIZE Version 3.00, and code has been converted to double precision to prevent problems interpolating very small numbers.  The error that occurred when requesting all CAMDAT times has been fixed and a new test case, Test Case 14, verifies that the problems addressed in the Change Control Form [20] have been corrected.  For this test case, the tester must examine the output data file for content.
A Software Problem Report 06-001 (2005) indicated that SUMMARIZE 3.01 could incorrectly determine that the attribute requested in the Input control file does not exist for the element block and abort [23].  The problem is caused by an error in the DBEL2BLK routine that should return the element block for a given element.  SUMMARIZE could also incorrectly determine that the attribute does exist for the element block, but this could only occur if the input control file was incorrect.  Since the problem causes SUMMARIZE to abort, the problem will not have an effect on calculation results.
In 2006, SNL procured four Compaq ES47 machines to add to the computing resources of two Compaq ES40 and two Compaq ES45 machines [26].  In addition to the hardware upgrades, the operating system OpenVMS 7.3-1 was upgraded to OpenVMS 8.2 [26].  Because of these changes in the operating system and the addition of a new computing platform, regression testing was conducted for SUMMARIZE 3.01 to ensure that it continued to function correctly [28].

In 2013, SNL migrated WIPP PA software from the VMS Alpha platform on a cluster of Compaq computers with OpenVMS 8.2 operating system to the Solaris Blade platform on Sun hardware with Intel based processors with SunOS 5.11 operating system [29, 31].  Results on VMS were transferred to the Solaris, converted to Solaris platform format as needed, and compared to the Solaris results using the UNIX diff command and plotted for visual comparison as needed [30].

SNL notes in the installation and checkout procedure that: "AP 162 states that numeric differences are expected, due to the change to double precision floating point variables in the code and differences in the two platforms. Some of the SUMMARIZE tests show a large number of numeric differences. AP 162 states that relative percent differences (RPD) of 1E-4 or less are insignificant" [30].

The discussion below documents the 2012 test methodology, regression test results, and the Agency's conclusions with respect to SUMMARIZE 3.02 running on the Solaris Blade with SunOS 5.11 [30].

Test Methodology

The test set for SUMMARIZE Version 3.00, as documented in the VVP/VD [12], consisted of 12 test cases; Test Cases 1, 2, and 4 through 13.  (Test Case 3 was removed from the test set.)  In the revised VVP/VD for SUMMARIZE 3.01, these 12 test cases are regression-tested by running SUMMARIZE Version 3.01 on the Compaq ES40 with OpenVMS V7.3-1 and comparing its output with the output from the validation of SUMMARIZE Version 3.00 [27], which was also run on the Compaq ES40 with OpenVMS V7.3-1.

SUMMARIZE needs the following input files: an input control file and a set of CAMDAT data files.  The SUMMARIZE input control file must always be modified slightly for each test case because it contains the name of the output data file, which includes the program class.  The differences between the SUMMARIZE Version 3.01 and Version 3.00 input control files are listed with the VMS DIFFERENCE utility in the VVP/VD [22].  The CAMDAT data files were the same files used in the previous validation of SUMMARIZE Version 3.00.

A successful SUMMARIZE execution generates one or more ASCII output data files and a log file.  The log file is not part of the code's functionality and is usually not examined or compared. Each output data file is compared to the corresponding file from the previous validation of SUMMARIZE Version 3.00 using the VMS DIFFERENCE utility.  DOE did not expect any differences for test cases that do not interpolate values, i.e., those test cases that request the "nearest" time step value or request only attribute or property values, which have no associated time.  However, the DOE notes that the conversion to double precision may cause numerical differences in interpolated values.  These differences make use of the VMS DIFFERENCE utility impractical.  Therefore, the DOE developed two short FORTRAN test programs to help verify that these differences are due to the conversion from single to double precision.  COMPARE_SUM compares the Version 3.01 and Version 3.00 output files line-by-line and identifies values that have a significant relative difference.  INTERP_CDB reads values for selected global variables for all times from the input CAMDAT file, and performs the interpolation at specified times in double and single precision.

Test Cases 12 and 13 check error conditions that are designed to cause SUMMARIZE to abort.  If SUMMARIZE aborts, no output data file is generated; the log file indicates that SUMMARIZE detected the error condition and aborted.  For these two test cases, DOE compares the log file to the corresponding file from the previous validation of SUMMARIZE Version 3.00 using the VMS DIFFERENCE utility.

A new test case, Test Case 14, verifies that the problems addressed in the CCF [20] have been corrected.  For this test case, the tester must examine the output data file for content.

All test cases are run using the WIPP PA run control system.  The script and script input files reside in class QB0301 of library EVAL in the SCMS.  All other files related to validation testing of SUMMARIZE Version 3.01 reside in class QB0301 of library SUM in the SCMS.  All test inputs are fetched at run time by the scripts, and test outputs/results and run logs are automatically stored by the scripts in class QB0301 of library SUM in the SCMS.  A log file that indicates the input/output files is generated by each test case execution.

Once the tests described above were completed and favorable comparisons were obtained between the results from SUMMARIZE Version 3.00 and Version 3.01 both running on the Compaq ES40 with OpenVMS V7.3-1, additional regression testing was performed.  This testing involved comparing the regression testing results for the 13 test cases described in the VVP/VD for SUMMARIZE 3.01 and run on the ES40, ES45 and the ES47 with OpenVMS 8.2 to the results from the validation tests of SUMMARIZE 3.01 run on the ES40 with OpenVMS 7.3-1.

In 2012, SNL regression tested SUMMARIZE 3.02 for use on the Solaris Blade with SunOS 5.11 against results on the Compaq ES47 with Open VMS 8.2.   The regression test included thirteen test cases; Test Cases 1, 2, and 4 through 14 (Test Case 3 was previously removed) examined numerous functions of the code [30].

SNL developed a python utility code, Regr_Sum.py, to compare results line-by-line, calculate the RPD, and report lines with differences greater than the RPD threshold.  SNL states that, "Any differences with an RPD greater than 1 E-4 must be explained" ([30] page 8). SNL compared results greater than the RPD to expected values to verify that the values have a reasonable justification [30].

Test Results

Test Case 1 show no numeric difference and acceptable textural differences ([30] Section 5.0).  Test Cases 4, 14, and 6 through 11 show acceptable textural differences (e.g., spacing, version number, filenames, etc.) and numeric differences below the RPD threshold.

Test Cases 2 and 5 have significant differences.  SNL notes differences in Sections 5.2 and 5.5 of the installation and checkout procedure [30] are: "... primarily due to the change in the seconds-to-year conversion factor...".  SNL did additional examination and explained the difference in Appendix C [30].

Test Cases 12 and 13 verify error handling for the code ([30 Sections 5.12 and 5.13) and showed acceptable differences.

The Agency's Conclusions

The Agency closely examined the regression testing of SUMMARIZE 3.02 and found that SNL's review and explanation of differences is adequate. The Agency concludes that SUMMARIZE 3.02 meets the acceptance criteria in the RD/VVP and is validated for WIPP PA use on the Solaris Blade with SunOS 5.11.
References

 WIPP PA (Performance Assessment) 1997.  "Requirements Document & Verification and Validation Plan for SUMMARIZE Version 2.20."  Sandia National Laboratories.  Sandia WIPP Central Files WPO #46449.
 WIPP PA 1996.  "Requirements Document & Verification and Validation Plan for SUMMARIZE Version 2.10."  Sandia National Laboratories.  Sandia WIPP Central Files WPO #37458.
 WIPP PA 1996.  "Validation Document for SUMMARIZE Version 2.10."  Sandia National Laboratories.  Sandia WIPP Central Files WPO #37461.
 WIPP PA (Performance Assessment) 1996.  "Requirements Document & Verification and Validation Plan for SUMMARIZE Version 2.15."  Sandia National Laboratories.  Sandia WIPP Central Files WPO #40252.
 WIPP PA 1996.  "Validation Document for SUMMARIZE Version 2.15."  Sandia National Laboratories.  Sandia WIPP Central Files WPO #40254.
 WIPP PA 1997.  "Software Problem Report 97-016 for SUMMARIZE Version 2.10, 2.15, 2.20."  Sandia National Laboratories.  Sandia WIPP Central Files WPO #246511.
 EPA 2003.  "Review of WIPP Performance Assessment Computer Code Migration, June 10, 2003."  Environmental Protection Agency.
 WIPP PA.  "Analysis Report for the ES45 Regression Test, March 6, 2003."  Sandia National Laboratories.  Sandia WIPP Central Files.  ERMS #530290.
 WIPP PA.  "Analysis Report for the 8400 Regression Test," Sandia National Laboratories.  Sandia WIPP Central Files.  ERMS #527280.
 USEPA  -  "Review of WIPP Performance Assessment Computer Code Migration Activities  - Version 2."  September 2004.
 WIPP PA 2005.  "Change Control Form for SUMMARIZE, Version 2.20 Sandia National Laboratories."  ERMS #540117.
 WIPP PA 2005.  "Verification and Validation Plan/Validation Document for SUMMARIZE Version 3.0."  Sandia National Laboratories.  Sandia WIPP Central Files.
 WIPP PA 2005.  "Installation and Checkout for SUMMARIZE Version 3.0 Regression Testing for the Compaq ES45 Platform."  Sandia National Laboratories.
 WIPP PA (Performance Assessment) 2005.  "Verification of the SUMMARIZE Interface in the CRA-2004 Performance Assessment Baseline Calculation."  Sandia National Laboratories.  Sandia WIPP Central Files 540977.
 Dunagan, S. 2004.  Explanation of how SUMMARIZE and CCDFGF are checked/verified/tested for capturing the correct CDB data streams in the WIPP CRA-2004 Performance Assessment.  Technical Memorandum ERMS #536767, Sandia National Laboratories, Carlsbad, New Mexico.
 Piper, L. 2004.  4[th] Response Submittal to EPA.  U.S. Department of Energy, Carlsbad, New Mexico.
 WIPP PA (Performance Assessment) 2005.  "Requirements and Design Document for SUMMARIZE Version 3.0."  Sandia National Laboratories.  Sandia WIPP Central Files WPO #540107.
 WIPP PA 2005.  "Software Problem Report 05-002 for SUMMARIZE 3.0."  Sandia National Laboratories.  Sandia WIPP Central Files ERMS #519714.
 WIPP PA 2005.  "Software Problem Report 05-003 for SUMMARIZE 3.0."  Sandia National Laboratories.  Sandia WIPP Central Files ERMS #519714.
 WIPP PA 2005.  "Change Control Form for SUMMARIZE, Version 3.0."  Sandia National Laboratories."  ERMS #541842.
 WIPP PA 2005.  "Implementation Document for SUMMARIZE 3.01."  Sandia National Laboratories.  Sandia WIPP Central Files WPO #542062.
 WIPP PA 2006.  "Verification and Validation Plan/Validation Document for SUMMARIZE 3.01."  Sandia National Laboratories.  Sandia WIPP Central Files WPO #542063.
 WIPP PA 2005.  "Software Problem Report 06-001 for SUMMARIZE 3.00 and 3.01."  Sandia National Laboratories.  Sandia WIPP Central Files ERMS #542399.
 USEPA  -  "Technical Support Document for Section 194.23:  Models and Computer Codes-PABC Codes Changes Review."  March 2006.  Docket No. A-98-49/II-B1-8.
 EPA 2004.  "Review of WIPP Performance Assessment Computer Code Migration, March 31, 2004."  Environmental Protection Agency.
 WIPP PA  -  2006.  "Installation of OpenVMS Version 8.2-1 on the WIPP Alpha Cluster and Regression Testing, dated March 16, 2006."  Sandia National Laboratories.  Sandia WIPP Central Files WPO #542680.
 WIPP PA  -  "Regression Testing Report of SUMMARIZE 3.01 on the Compaq ES40, ES45, and ES47 Platforms Using OpenVMS 8.2 dated May 31, 2006."  Sandia National Laboratories.  Sandia WIPP Central Files.  ERMS #543462.
 EPA 2006.  Technical Support Document for Section 194.23:  Review of WIPP Recertification Performance Assessment Computer Codes  -  CRA Code Review Docket No. A-98-49 II-B1-7.
 WIPP PA  -  "Summary Report on the Migration of the WIPP PA Codes From VMS to Solaris, AP-162 dated December 23, 2013." Sandia National Laboratories.  Sandia WIPP Central Files ERMS #561457.
 WIPP PA  -  "Installation and Checkout for SUMMARIZE Version 3.02 Regression Testing for the Solaris Blade dated December 11, 2012." Sandia National Laboratories. Sandia WIPP Central Files ERMS #557814.
 WIPP PA - "AP-162 Analysis Plan for Migration of the Performance Assessment Codes to the Sun Solaris Blade Server Running with Intel Processors, Revision 0 dated June 12, 2012." Sandia National Laboratories. Sandia WIPP Central Files ERMS #557765.

LIBRARIES

**SNL states in the Solaris migration plan ([15] AP-162, page 7), "Libraries do not require separate validation because their subroutines are validated when the code into which they are linked is validated."  EPA examined this comment and agrees with its concept.  Programmers develop object libraries to store common routines or subroutines that are used by multiple programs.  These routines are usually database access, input/output, or memory access, etc. subroutines used frequently by numerous programs.  Library routines are linked (combined) when the main computer code, such as BRAGFLO or CCDFGF, are created (complied).  The Agency concludes that SNL's position is appropriate and closely examined these issues when examining the qualification of the main programs during our review.  EPA found that all main line codes preformed adequately. The Agency left this section of the report unchanged to preserve historical review information.

This section presents the regression testing for the libraries, specifically the CAMCON_LIB Version 2.20, CAMDAT_LIB Version 1.25, CAMSUPES_LIB 2.22 and SDBREAD_LIB 2.11.

CAMCON_LIB

This section presents the regression test results for the CAMCON_LIB software library.  CAMCON_LIB is a collection of routines that perform Quality Assurance, File processing, Free-Field Input processing, String processing, and Finite Element Index processing.  The data manipulations to be performed are expressed as algebraic equations involving the existing and/or newly created data.
<IP_ADDRESS>	Introduction

CAMCON_LIB 2.16 was used in the CCA [1].  CAMCON_LIB 2.16 was validated in January 1996 on a DEC Alpha 2100 with OpenVMS 6.1 by demonstrating that the results of seven Test Cases (1 through 7) met the acceptance criteria defined in the RD/VVP for CAMCON_LIB 2.16 (document Version 1.00) [3].  As a consequence of the upgrade to OpenVMS 7.3-1, CAMCON_LIB was re-compiled on the ES40 to create Version 2.20 [2].  No changes were made to the CAMCON_LIB source code.  The Implementation Document for CAMCON_LIB 2.20 documents the build of CAMCON_LIB 2.20 [6].
In January 1999 source code changes were made to CAMCON_LIB and the code was revised to Version 2.18.  CAMCON_LIB 2.18 was validated on a DEC Alpha 2100 with OpenVMS 7.1
[4, 5].  Test Cases 1 - 7 for the validation of CAMCON_LIB 2.18 were identical to test cases for the validation of CAMCON_LIB 2.16.  The acceptance criteria for these test cases were satisfied by showing that the output from CAMCON_LIB 2.18 was identical to the output of the CAMCON_LIB 2.16 validation tests.

In order to test new operating systems that were added in 2002 - 2003 (Section 1), regression test results from CAMCON_LIB 2.2 run on the ES40 with OpenVMS 7.3-1 were compared to results from the validation tests of CAMCON_LIB 2.20 run on a DEC Alpha 2100 with OpenVMS 6.1. In June 2003, the EPA completed a report documenting the Agency's conclusions with respect to the migration and verification of CAMCON_LIB 2.20 on those operating systems [7].  In January 2003, two new hardware systems were added to conduct PAs for the WIPP; a Compaq ES45 and a Compaq Alpha 8400, which are both running OpenVMS 7.3-1 [8, 9].  In March 2004, the Agency completed a report documenting the Agency's approval of CAMCON_LIB 2.20 on the Compaq Alpha ES45 and 8400 with OpenVMS 7.3-1 [10]. CAMCON_LIB 2.20 was used to support the 2004 CRA.

In 2006, an error was found in CAMCON_LIB 2.20 and is described in the Software Problem Report as, "If the routine STRCMPRS is called with a string that contains an internal blank, but does not have a blank at the end of the string, the routine will go into an endless loop.  For example, CALL STRCMPRS (STR,L), where STR is dimensioned CHARACTER*14 STR and set to STR= Initial Cavity" [11].  The SPR also notes that, "Since this problem causes the calling code to go into an endless loop, it could not have occurred in any analyses so far, and has thus had no impact."

A Change Control Form was also completed in 2006 that indicates the error in the STRCMPRS routine (string compression) will be corrected, and the test driver will be changed to allow more flexibility in naming the test output files [12].  Calls will be added to the test driver for this code to test the correction to the STRCMPRS routine and to test the QABANNER capability to display a short version of the QA banner.  These changes to CAMCON_LIB 2.20 were completed and the version was changed to CAMCON_LIB 2.21.

In 2006, SNL procured four Compaq ES47 machines to add to the computing resources of two Compaq ES40 and two Compaq ES45 machines [13].  In addition to the hardware upgrades, the operating system OpenVMS 7.3-1 has been upgraded to OpenVMS 8.2 [13].  Because of these changes in the operating system and the addition of a new computing platform, regression testing has been conducted for CAMCON_LIB 2.21 to ensure that it continues to function correctly.

The discussion below documents the test methodology, regression test results, and the Agency's conclusions with respect to CAMCON_LIB 2.21 running on the Compaq ES40, ES45, and ES47 machines with OpenVMS 8.2.

<IP_ADDRESS>	Test Methodology

The tests for this library comprised the seven test cases described in the Requirements Document & Verification and Validation Plan for CAMCON_LIB Version 2.16 (RD/VVP) [3].  Regression testing results from CAMCON_LIB 2.21 run on the ES47 with OpenVMS 8.2 were compared to results from the validation tests of CAMCON_ LIB 2.21 run on the ES40 with OpenVMS 7.3-1; Regression testing results from CAMCON_ LIB 2.21 run on the ES40 and ES45 with OpenVMS 8.2 were compared to the regression testing results from CAMCON_LIB 2.21 run on the ES47 with OpenVMS 8.2 [14].

The regression test methodology uses the VMS DIFFERENCE command to compare output from CAMCON_LIB 2.21 on the COMPAQ ES47 with OpenVMS 8.2 to the output from validation tests of CAMCON_LIB 2.21 on the COMPAQ ES40 with OpenVMS 7.3-1, and output from CAMCON_LIB 2.21 on the COMPAQ ES40 and ES45 with OpenVMS 8.2 to output from CAMCON_LIB 2.21 on the COMPAQ ES47 with OpenVMS 8.2.  The VMS DIFFERENCE command compares two files and identifies records that are different in the two files.

<IP_ADDRESS>	Test Results

The results of the tests referenced above are that only very minor differences (e.g., spacing, version number) were found for the seven test cases.  The comparison found that all differences in the output are limited to code run date and time, platform names, system version numbers, the directory, and file names.
<IP_ADDRESS>	The Agency's Conclusions

The Agency found that all differences in output are acceptable; namely, that the differences are limited to code run date and time, platform names, system version numbers, the directory, and file names.  The comparison found no differences in the numerical output of CAMCON_LIB 2.21.  The Agency concludes that CAMCON_LIB 2.21 meets the acceptance criteria in the RD/VVP and is validated for WIPP PA use on the ES40, ES45, and ES47 with OpenVMS 8.2.

<IP_ADDRESS>	References

 Analysis Plan (AP-042) 1998.  "Regression for the Upgrade to OpenVMS Version 7.1 on the WIPP COMPAC Alpha Cluster."  Sandia National Laboratories.
 Analysis Plan (AP-065) 2000.  "Regression for the Upgrade to OpenVMS Version 7.2 on the WIPP DEC Alpha Cluster."  Sandia National Laboratories.
 WIPP PA (Performance Assessment) 1995.  "Requirements Document & Verification and Validation Plan for CAMCON_LIB Version 2.16" (document Version 1.00).  Sandia National Laboratories.  Sandia WIPP Central Files WPO #27736.
 WIPP PA (Performance Assessment) 1999.  "Change Control Form for CAMCON_LIB, Version 2.18."  Sandia National Laboratories.  Sandia WIPP Central Files WPO #51637.
 WIPP PA (Performance Assessment) 1999.  "Regression testing of CAMCON_LIB Version 2.18."  Sandia National Laboratories.  Sandia WIPP Central Files WPO #51629.
 WIPP PA (Performance Assessment) 1995.  "Implementation Document for CAMCON_LIB Version 2.20" (document Version 1.04).  Sandia National Laboratories.  Sandia WIPP Central Files WPO #525736.
 EPA 2003.  "Review of WIPP Performance Assessment Computer Code Migration, June 10, 2003."  Environmental Protection Agency.
 WIPP PA  -  "Analysis Report for the ES45 Regression Test, March 6, 2003."  Sandia National Laboratories.  Sandia WIPP Central Files.  ERMS #530290.
 WIPP PA  -  "Analysis Report for the 8400 Regression Test," Sandia National Laboratories.  Sandia WIPP Central Files.  ERMS #527280.
 EPA 2004.  "Review of WIPP Performance Assessment Computer Code Migration, March 31, 2004."  Environmental Protection Agency.
 WIPP PA 2006.  "Software Problem Report 06-001 for CAMCON_LIB 2.20."  Sandia National Laboratories.  Sandia WIPP Central Files ERMS #542992.
 WIPP PA 2006.  "Change Control Form for CAMCON_LIB 2.20 [proposed 2.21] Sandia National Laboratories."  ERMS #542994.
 WIPP PA  -  2006.  "Installation of OpenVMS Version 8.2-1 on the WIPP Alpha Cluster and Regression Testing, dated March 16, 2006."  Sandia National Laboratories.  Sandia WIPP Central Files WPO #542680.
 WIPP PA  -  "Regression Testing Report of CAMCON_LIB 2.21 on the Compaq ES40, ES45, and ES47 Platforms dated May 15, 2006."  Sandia National Laboratories.  Sandia WIPP Central Files.  ERMS #543447.
 WIPP PA - "AP-162 Analysis Plan for Migration of the Performance Assessment Codes to the Sun Solaris Blade Server Running with Intel Processors, Revision 0 dated June 12, 2012." Sandia National Laboratories. Sandia WIPP Central Files ERMS #557765.

CAMDAT_LIB

This section presents the regression test results for the CAMDAT_LIB software library.  CAMDAT_LIB is a collection of routines that read from and write to a computational database (CAMDAT) file for use by WIPP PA computer codes.  The data manipulations to be performed are expressed as algebraic equations involving the existing and/or newly created data.

<IP_ADDRESS>	Introduction

CAMDAT_LIB 1.22 was used in the CCA.  CAMDAT_LIB 1.22 was validated in January 1996 on a DEC Alpha 2100 with OpenVMS 6.1 by demonstrating that the results of seven Test Cases (1 through 7) met the acceptance criteria defined in the RD/VVP for CAMDAT_LIB 1.22 [1, 2, 4].  As a consequence of the upgrade to OpenVMS 7.3-1, CAMDAT_LIB was re-compiled on the ES40 to create Version 1.25.  No changes were made to the CAMDAT_LIB source code.  The Implementation Document for CAMDAT_LIB 1.25 documents the build of CAMDAT_LIB 1.25 [3].

In order to test new operating systems that were added in 2002 - 2003 (Section 1), regression test results from CAMDAT_LIB 1.25 run on the ES40 with OpenVMS 7.3-1 were compared to results from the validation tests of CAMDAT_LIB 1.25 run on a DEC Alpha 2100 with OpenVMS 6.1 [5].  In June 2003, the EPA completed a report documenting the Agency's conclusions with respect to the migration and verification of CAMDAT_LIB 1.25 on those operating systems [6].  In January 2003, two new hardware systems were added to conduct PAs for the WIPP; a Compaq ES45 and a Compaq Alpha 8400, which are both running OpenVMS 7.3-1 [7, 8].  In March 2004, the Agency completed a report documenting the Agency's approval of CAMDAT_LIB 1.25 on the Compaq Alpha ES45 and 8400 with OpenVMS 7.3-1 [9].  CAMDAT_LIB 1.25 was used to support the 2004 CRA.

In 2006, SNL procured four Compaq ES47 machines to add to the computing resources of two Compaq ES40 and two Compaq ES45 machines [10].  In addition to the hardware upgrades, the operating system OpenVMS 7.3-1 has been upgraded to OpenVMS 8.2 [10].  Because of these changes in the operating system and the addition of a new computing platform, regression testing has been conducted for CAMDAT_LIB 1.25 to ensure that it continues to function correctly.

The discussion below documents the test methodology, regression test results, and the Agency's conclusions with respect to CAMDAT_LIB 1.25 running on the Compaq ES40, ES45, and ES47 machines with OpenVMS 8.2.

<IP_ADDRESS>	Test Methodology

The tests for this library comprised the seven test cases described in the Requirements Document & Verification and Validation Plan for CAMDAT_LIB Version 1.22 (RD/VVP) [1].  Regression test results from CAMDAT_LIB 1.25 run on the Compaq ES40 with OpenVMS 7.3-1 used the VMS DIFFERENCE command to compare results from the validation tests of CAMDAT_LIB 1.25 run on the Compaq ES40, ES45, and the ES47 with OpenVMS 8.2 [11].
<IP_ADDRESS>	Test Results

The results of the tests referenced above are that only very minor differences (e.g., spacing, version number) were found for the seven test cases.  The comparison found that all differences in the output are limited to code run date and time, platform names, system version numbers, the directory, and file names.

<IP_ADDRESS>	The Agency's Conclusions

The Agency found that all differences in output are acceptable; namely, that the differences are limited to code run date and time, platform names, system version numbers, the directory, and file names.  The comparison found no differences in the numerical output of CAMDAT_LIB 1.25.  The Agency concludes that CAMDAT_LIB 1.25 meets the acceptance criteria in the RD/VVP and is validated for WIPP PA use on the ES40, ES45, and ES47 with OpenVMS 8.2.

<IP_ADDRESS>	References

 WIPP PA (Performance Assessment) 1995.  "Requirements Document & Verification and Validation Plan for CAMDAT_LIB Version 1.22" (document Version 1.00).  Sandia National Laboratories.  Sandia WIPP Central Files WPO #28109.
 WIPP PA (Performance Assessment) 1995.  "Validation Document for CAMDAT_LIB Version 1.22" (document Version 1.00).  Sandia National Laboratories.  Sandia WIPP Central Files WPO #28112.
 WIPP PA (Performance Assessment) 1995.  "Implementation Document for CAMDAT_LIB Version 1.25" (document Version 1.25).  Sandia National Laboratories.  Sandia WIPP Central Files WPO #525734.
 WIPP PA (Performance Assessment) 1996.  "Validation Document for CAMDAT_LIB Version 1.22" (document Version 1.10).  Sandia National Laboratories.  Sandia WIPP Central Files WPO #37497.
 WIPP PA (Performance Assessment) 2003.  "Analysis Report for the OpenVMS 7.3-1 Regression Test."  Sandia National Laboratories.  Sandia WIPP Central Files ERMS #525277.
 EPA 2003.  "Review of WIPP Performance Assessment Computer Code Migration, June 10, 2003."  Environmental Protection Agency.
 WIPP PA  -  "Analysis Report for the ES45 Regression Test, March 6, 2003."  Sandia National Laboratories.  Sandia WIPP Central Files.  ERMS #530290.
 WIPP PA  -  "Analysis Report for the 8400 Regression Test."  Sandia National Laboratories.  Sandia WIPP Central Files.  ERMS #527280.
 EPA 2004.  "Review of WIPP Performance Assessment Computer Code Migration, March 31, 2004."  Environmental Protection Agency.
 WIPP PA  -  2006.  "Installation of OpenVMS Version 8.2-1 on the WIPP Alpha Cluster and Regression Testing, dated March 16, 2006."  Sandia National Laboratories.  Sandia WIPP Central Files WPO #542680.
 WIPP PA  -  "Regression Testing Report of CAMDAT_LIB 1.25 on the Compaq ES40, ES45, and ES47 Platforms Using OpenVMS 8.2 dated May 31, 2006."  Sandia National Laboratories.  Sandia WIPP Central Files.  ERMS #543448.

CAMSUPES_LIB

This section presents the regression test results for the CAMSUPES_LIB software library.  The CAMSUPES_LIB library is a collection of routines that perform system-dependent functions and allocate memory for arrays at run time for FORTRAN-77 programs.  The system dependent functions provide a uniform interface to necessary operating system functions that are not included in the ANSI FORTRAN-77 standard.  The purpose of the memory management routines is to allow an applications programmer to write standard, readable FORTRAN-77 code making efficient use of memory resources.

<IP_ADDRESS>	Introduction

CAMSUPES_LIB 2.18 was used to support the CCA [1, 4].  CAMSUPES_LIB 2.18 was validated in January 1996 on a DEC Alpha 2100 with OpenVMS 6.1 by demonstrating that the results of two Test Cases (1 and 2) met the acceptance criteria defined in the RD/VVP for CAMSUPES_LIB 2.18 [6].  As a consequence of the upgrade to OpenVMS 7.3-1, CAMSUPES_LIB was re-compiled on the ES40 to create Version 2.22 [2].  No changes were made to the CAMSUPES_LIB source code.  The Implementation Document (ID) for CAMSUPES_LIB 2.22 documents the build of CAMSUPES_LIB 2.22 [5].

In order to test new operating systems that were added in 2002 - 2003 (Section 1), regression test results from CAMSUPES_LIB 2.22 run on the ES40 with OpenVMS 7.3-1 were compared to results from the validation tests of CAMSUPES_LIB 2.22 run on a DEC Alpha 2100 with OpenVMS 6.1.  In June 2003, the EPA completed a report documenting the Agency's conclusions with respect to the migration and verification of CAMSUPES_LIB 2.22 on those operating systems [7].  In January 2003, two new hardware systems were added to conduct PAs for the WIPP; a Compaq ES45 and a Compaq Alpha 8400, which are both running OpenVMS 7.3-1 [8, 9].  In March 2004, the Agency completed a report documenting the Agency's approval of STEPWISE 2.21 on the Compaq Alpha ES45 and 8400 which were both running OpenVMS 7.3-1 [10].  CAMSUPES_LIB 2.2 was used to support the 2004 CRA.

In 2006, SNL procured four Compaq ES47 machines to add to the computing resources of two Compaq ES40 and two Compaq ES45 machines [11].  In addition to the hardware upgrades, the operating system OpenVMS 7.3-1 has been upgraded to OpenVMS 8.2 [11].  Because of these changes in the operating system and the addition of a new computing platform, regression testing has been conducted for CAMSUPES_LIB 2.22 to ensure that it continues to function correctly.
The discussion below documents the test methodology, regression test results, and the Agency's conclusions with respect to CAMSUPES_LIB 2.22 running on the Compaq ES40, ES45, and ES47 machines with OpenVMS 8.2.

<IP_ADDRESS>	Test Methodology

The tests for this software library comprised the two test cases described in the Verification and Validation Plan for CAMSUPES_LIB Version 2.20 (document Version 1.01) (VVP) [3].  Regression test results from STEPWISE 2.21 run on the Compaq ES40 with OpenVMS 7.3-1 used the VMS DIFFERENCE command to compare results from the validation tests of CAMSUPES_LIB 2.22 run on the Compaq ES40, ES45, and the ES47 with OpenVMS 8.2 [12].

<IP_ADDRESS>	Test Results

The results of the tests referenced above are that only very minor differences (e.g., spacing, version number) were found for the two test cases.  The comparison found that all differences in the output are limited to code run date and time, platform names, system version numbers, the directory, and file names.

<IP_ADDRESS>	The Agency's Conclusions

The Agency found that all differences in output are acceptable; namely, that the differences are limited to code run date and time, platform names, system version numbers, the directory, and file names.  The comparison found no differences in the numerical output of CAMSUPES_LIB 2.22.  The Agency concludes that CAMSUPES_LIB 2.22 meets the acceptance criteria in the RD/VVP and is validated for WIPP PA use on the ES40, ES45, and ES47 with OpenVMS 8.2.

<IP_ADDRESS>	References

 Analysis Plan (AP-042) 1998.  "Regression for the Upgrade to OpenVMS Version 7.1 on the WIPP COMPAC Alpha Cluster."  Sandia National Laboratories.
 Analysis Plan (AP-065) 2000.  "Regression for the Upgrade to OpenVMS Version 7.2 on the WIPP DEC Alpha Cluster."  Sandia National Laboratories.
 WIPP PA (Performance Assessment) 1995.  "Verification and Validation Plan for CAMSUPES_LIB Version 2.20" (document Version 1.01).  Sandia National Laboratories.   Sandia WIPP Central Files WPO #51633.
 WIPP PA (Performance Assessment) 1995.  "Validation Document for CAMSUPES_LIB Version 2.18" (document Version 1.02).  Sandia National Laboratories.  Sandia WIPP Central Files WPO #51634.
 WIPP PA (Performance Assessment) 1995.  "Implementation Document for CAMSUPES_LIB Version 2.22" (document Version 1.04).  Sandia National Laboratories.  Sandia WIPP Central Files WPO #525738.
 WIPP PA (Performance Assessment) 1995.  "Requirements Document and Verification and Validation Plan for CAMSUPES_LIB Version 2.18" (document Version 1.00).  Sandia National Laboratories.  Sandia WIPP Central Files WPO #27744.
 EPA 2003.  "Review of WIPP Performance Assessment Computer Code Migration, June 10, 2003."  Environmental Protection Agency.
 WIPP PA  -  "Analysis Report for the ES45 Regression Test, March 6, 2003."  Sandia National Laboratories.  Sandia WIPP Central Files.  ERMS #530290.
 WIPP PA  -  "Analysis Report for the 8400 Regression Test."  Sandia National Laboratories.  Sandia WIPP Central Files.  ERMS #527280.
 EPA 2004.  "Review of WIPP Performance Assessment Computer Code Migration, March 31, 2004."  Environmental Protection Agency.
 WIPP PA  -  2006.  "Installation of OpenVMS Version 8.2-1 on the WIPP Alpha Cluster and Regression Testing, dated March 16, 2006."  Sandia National Laboratories.  Sandia WIPP Central Files WPO #542680.
 WIPP PA  -  "Regression Testing Report of CAMSUPES_LIB 2.22 on the Compaq ES40, ES45, and ES47 Platforms Using OpenVMS 8.2 dated May 18, 2006."  Sandia National Laboratories.  Sandia WIPP Central Files.  ERMS #543449.

PLT_LIB

This section presents the regression test results for the PLT_LIB software library.  PLT_LIB is a general device-independent plotting package that performs basic graphics operations.

<IP_ADDRESS>	Introduction

PLT_LIB 1.02 was used to support the CCA.  The Implementation Document (ID) for PLT_LIB documents the build of PLT_LIB 1.02 [1].  PLT_LIB 1.02 was validated in January 1996 on a DEC Alpha 2100 with OpenVMS 6.1 by demonstrating that the results of three Test Cases met the acceptance criteria defined in the VVP for PLT_LIB 1.02 [2].  As a consequence of the upgrade to OpenVMS 7.3-1, PLT_LIB was re-compiled on the ES40 to create Version 2.04.  No changes were made to the PLT_LIB source code.

In order to test new operating systems that were added in 2002 - 2003 (Section 1), regression test results from PLT_LIB 1.02 run on the ES40 with OpenVMS 7.3-1 were compared to results from the validation tests of PLT_LIB 2.04 run on a DEC Alpha 2100 with OpenVMS 6.1 [3].  In January 2003, regression testing of PLT_LIB 2.04 was completed on the Compaq ES45 and a Compaq Alpha 8400, which were both running OpenVMS 7.3-1 [4, 5].  PLT_LIB 2.04 was used to support the 2004 CRA.

In 2006, an error was found in PLT_LIB 2.04 and is described in the Software Problem Report as "The plot file name appears on the Title line near the top of the plot file.  When the Title line is longer than 80 characters (i.e., when the file name with directory is long), two blank lines are written before the Title lines.  The blank lines do not cause a problem when plotting the Postscript or Adobe plot files.  This problem affects all plot codes that link to PLT_LIB" [6].  The SPR also notes that, "It has no effect on the analysis."

A Change Control Form was also completed in 2006 indicating that, "this library will be recompiled on OpenVMS 8.2, so that it will be compatible with codes that are compiled on the new system and link in the library.  The library will be tested on all machines in the Alpha cluster, including the new ES47.  A correction will be made to PLT_LIB to fix a bug that causes two blank lines to be output to the plot file if the plot name is too long.  Note that PLT_LIB Version 2.05 was built, but will not be qualified" [7].  The revised version of PLT_LIB is 2.06.

In 2006, SNL procured four Compaq ES47 machines to add to the computing resources of two Compaq ES40 and two Compaq ES45 machines [8].  In addition to the hardware upgrades, the operating system OpenVMS 7.3-1 has been upgraded to OpenVMS 8.2 [8].  Because of these changes in the operating system and the addition of a new computing platform, regression testing has been conducted for PLT_LIB 2.06 to ensure that it continues to function correctly.

The discussion below documents the test methodology, regression test results, and the Agency's conclusions with respect to PLT_LIB 2.06 running on the Compaq ES40, ES45, and ES47 machines with OpenVMS 8.2.

<IP_ADDRESS>	Test Methodology

The tests for this software library comprised the three test cases described in the Validation Document for PLT_LIB 2.04 (VD) [2].  Because PLT_LIB is a library, not a code, it is the object library (.OLB), rather than an executable (.EXE), that is of interest.  However, an executable is generated for the driver program that tests the library functionality.  Regression testing results from PLT_LIB 2.06 run on the ES47 with OpenVMS 8.2 were compared to results from the validation tests of PLT_LIB 2.04 run on the ES40 with OpenVMS 7.3-1; and regression testing results from PLT_LIB 2.06 run on the ES40 and ES45 with OpenVMS 8.2 were compared to the regression testing results from PLT_LIB 2.06 run on the ES47 with OpenVMS 8.2 [9].

<IP_ADDRESS>	Test Results

The results of the tests referenced above are that only very minor differences (e.g., spacing, version number) were found for the three test cases.  The comparison found that all differences in the output are limited to code run date and time, platform names, system version numbers, the directory, and file names.

<IP_ADDRESS>	The Agency's Conclusions

The Agency found that all differences in output are acceptable; namely, that the differences are limited to code run date and time, platform names, system version numbers, the directory, and file names.  The comparison found no differences in the numerical output of PLT_LIB 2.06.  The Agency concludes that PLT_LIB 2.06 meets the acceptance criteria in the VD and is validated for WIPP PA use on the ES40, ES45, and ES47 with OpenVMS 8.2.

<IP_ADDRESS>	References

 WIPP PA (Performance Assessment) 1995.  "Implementation Document for PLT_LIB 2.06 Version 1.06" (document Version 1.04).  Sandia National Laboratories.  Sandia WIPP Central Files WPO #543405.
 WIPP PA (Performance Assessment) 1995.  "Validation Document for PLT_LIB Version 1.02" (document Version 1.02).  Sandia National Laboratories.  Sandia WIPP Central Files WPO #45406.
 Analysis Plan (AP-042) 1998.  "Regression for the Upgrade to OpenVMS Version 7.1 on the WIPP COMPAC Alpha Cluster."  Sandia National Laboratories.
 WIPP PA  -  "Analysis Report for the ES45 Regression Test, March 6, 2003."  Sandia National Laboratories.  Sandia WIPP Central Files.  ERMS #530290.
 WIPP PA  -  "Analysis Report for the 8400 Regression Test."  Sandia National Laboratories.  Sandia WIPP Central Files.  ERMS #527280.
 WIPP PA 2006.  "Software Problem Report 06-001 for PLT_LIB 2.04."  Sandia National Laboratories.  Sandia WIPP Central Files ERMS #542992.
 WIPP PA 2006.  "Change Control Form for PLT_LIB 2.04 [proposed 2.06] Sandia National Laboratories."  ERMS #543391.
 WIPP PA 2006.  "Installation of OpenVMS Version 8.2-1 on the WIPP Alpha Cluster and Regression Testing, dated March 16, 2006."  Sandia National Laboratories.  Sandia WIPP Central Files WPO #542680.
 WIPP PA  -  "Regression Testing Report of PLT_LIB 2.06 on the Compaq ES40, ES45, and ES47 Platforms Using OpenVMS 8.2 dated June 6, 2006."  Sandia National Laboratories.  Sandia WIPP Central Files.  ERMS #543599.

SDBREAD_ LIB

This section presents the test results for the SDBREAD_LIB software library.  The SDBREAD_LIB library is a collection of routines that allow the calling program to retrieve parameter information from the parameter database (PAPDB).

<IP_ADDRESS>	Introduction

SDBREAD_LIB 3.10 was used to support the CCA.  SDBREAD_LIB 3.10 was validated in January 1996 on a DEC Alpha 2100 with OpenVMS 6.1 by demonstrating that the results of five Test Cases met the acceptance criteria defined in the VVP for SDBREAD_LIB 3.10 [1].

As a consequence of the upgrade to OpenVMS 7.3-1, SDBREAD_LIB 3.10 was re-compiled on the ES40 to create Version 3.11 [2].  No changes were made to the SDBREAD_LIB 3.10 source code.  In order to test new operating systems that were added in 2002 - 2003 (Section 1), regression test results from SDBREAD_LIB 3.10 run on the ES40 with OpenVMS 7.3-1 were compared to results from the validation tests of SDBREAD_LIB 3.11 run on a DEC Alpha 2100 with OpenVMS 6.1 [3].  In January 2003, regression testing of SDBREAD_LIB 3.11 was completed on the Compaq ES45 and a Compaq Alpha 8400, which were both running OpenVMS 7.3-1 [4, 5].  SDBREAD_LIB 3.11 was used to support the 2004 CRA.

A Change Control Form was also completed in 2006 that details the revision from Version 3.11 to 3.12 and indicates that "this library will be recompiled on OpenVMS 8.2, so that it will be compatible with codes that are compiled on the new system and link in the library.  The library will be tested on all machines in the Alpha cluster, including the new ES47" [6].  The Implementation Document (ID) for SDBREAD_LIB documents the build of SDBREAD_LIB 3.12 [7].

In 2006, SNL procured four Compaq ES47 machines to add to the computing resources of two Compaq ES40 and two Compaq ES45 machines [8].  In addition to the hardware upgrades, the operating system OpenVMS 7.3-1 was upgraded to OpenVMS 8.2 [8].  Because of these changes in the operating system and the addition of a new computing platform, regression testing was conducted for SDBREAD_LIB 3.12 to ensure that it continues to function correctly.

In 2011 and 2012, SNL moved the WIPP PA parameter database from the SQLServer to MySQL, therefore SDBREAD_LIB 3.12 was updated to SDBREAD_LIB 4.00 to allow PA codes to access the new database functions [10].  SDBREAD_LIB 4.00 was used during the 2014 CRA calculations.

The discussion below documents the test methodology, regression test results, and the Agency's conclusions with respect to SDBREAD_LIB 4.00 running on the Compaq ES45, and ES47 machines with OpenVMS 8.2.

<IP_ADDRESS>	Test Methodology

The tests for this software library comprised the five test cases described in the Verification and Validation Plan & Validation Document (VVP/VD) for SDBREAD _LIB Version 3.10 [1], which is still in effect for Version 3.12.  Because SDBREAD _LIB is a library, not a code, it is the object library (.OLB), rather than an executable (.EXE), that is of interest.  However, an executable is generated for the driver program that tests the library functionality.

Regression testing results from SDBREAD_LIB 3.12 run on the ES47 with OpenVMS 8.2 were compared to results from the validation tests of SDBREAD_LIB 3.11 run on the ES40 with OpenVMS 7.3-1; regression testing results from SDBREAD _LIB 3.12 run on the ES40 and ES45 with OpenVMS 8.2 were compared to the regression testing results from SDBREAD_LIB 3.12 run on the ES47 with OpenVMS 8.2 [9].

To qualify SDBREAD_LIB 4.00, SNL developed two new test cases, Test Cases 11 and 12 to qualify access to the new MySQL parameter database, PAPDB Version 2.00 [10].  These test cases evaluate database open, access to parameter values, track access activities and database closer of the new database.  Database access results are recorded in output files and then manually compared to the MySQL database values to confirm proper performance of SDBREAD_LIB 4.0 routines [10].

<IP_ADDRESS>	Test Results

Evaluation of test cases #11 and #12 verify that SDBREAD_LIB 4.00 routines successfully satisfy the acceptance criteria and access the PAPDB 2.0 parameter database properly ([10] Section 7.0).

<IP_ADDRESS>	The Agency's Conclusions

The Agency's review found that SDBREAD_LIB 4.00 satisfies the acceptance criteria and performs the functional requirements [10].    The Agency concludes that SDBREAD_LIB 4.00 meets the acceptance criteria in the VD and is validated for WIPP PA use on the ES45, and ES47 with OpenVMS 8.2.

<IP_ADDRESS>	References

 WIPP PA (Performance Assessment) 1995.  "Verification Validation Plan for SDBREAD_LIB 3.10."  Sandia National Laboratories.
 Sandia WIPP Central Files WPO #519728.  WIPP PA 2002.  "Change Control Form for SDBREAD_LIB 3.10 [proposed 3.11] Sandia National Laboratories."  ERMS #524653.
 Analysis Plan (AP-042) 2002.  "Regression for the Upgrade to OpenVMS Version 7.1 on the WIPP COMPAC Alpha Cluster."  Sandia National Laboratories.
 WIPP PA  -  "Analysis Report for the ES45 Regression Test, March 6, 2003."  Sandia National Laboratories.  Sandia WIPP Central Files.  ERMS #530290.
 WIPP PA  -  "Analysis Report for the 8400 Regression Test," Sandia National Laboratories.  Sandia WIPP Central Files.  ERMS #527280.
 Sandia WIPP Central Files WPO #519728.  WIPP PA 2006.  "Change Control Form for SDBREAD_LIB 3.11 [proposed 3.12] Sandia National Laboratories."  ERMS #542998.
 WIPP PA (Performance Assessment) 2006.  "Implementation Document for SDBREAD_LIB 3.12."  Sandia National Laboratories.  Sandia WIPP Central Files WPO #543027.
 WIPP PA 2006.  "Installation of OpenVMS Version 8.2-1 on the WIPP Alpha Cluster and Regression Testing, dated March 16, 2006."  Sandia National Laboratories.  Sandia WIPP Central Files WPO #542680.
 WIPP PA  -  "Regression Testing Report of SDBREAD_LIB 3.12 on the Compaq ES40, ES45, and ES47 Platforms Using OpenVMS 8.2 dated June 6, 2006."  Sandia National Laboratories.  Sandia WIPP Central Files.  ERMS #543599.
 WIPP PA  -  "Verification and Validation Plan/Validation Document for SDBREAD_LIB 4.00, dated March 12, 2012." Sandia National Laboratories. Sandia WIPP Central Files. ERMS #556461.

Codes Used to Support the Inventory Report

ORIGEN2

<IP_ADDRESS>	Introduction

The ORIGEN2, Version 2.2 software is an isotope generation and depletion code that uses the matrix exponential solution method.  The software was developed and distributed by the Radiation Safety Information Computational Center (RSICC) at the Oak Ridge National Laboratory [1].  The software was adopted into the Los Alamos National Laboratory  -  Carlsbad Operation (LANL-CO) Software Quality Assurance program to decay and report the inventory of radionuclides on a transuranic (TRU) waste stream basis to a common base year within the Comprehensive Inventory Database (CID).  The CID (Section 5.31.3) stores and controls access to TRU waste inventory data required for the WIPP PA calculations.

ORIGEN2, Version 2.2 is a versatile computer code system for calculating the buildup, decay, and processing of radioactive materials [1].  It is written in the FORTRAN programming language.  The software was originally developed on a large IBM mainframe computer.  However, developments and enhancements have subsequently been made on a Pentium PC running Microsoft(R) Windows 2000.  The software may be executed on any Intel Pentium or equivalent processor PC machine capable of running Microsoft(R) Windows.

The original ORIGEN computer code was developed in the early 1970s [2].  ORIGEN2, released in 1980, incorporated updates of the reactor models, cross sections, fission product yields, decay data, and decay photon data, as well as the source code.  ORIGEN2, Version 2.1 was released in August, 1991, replacing ORIGEN2.  In June 1996, the source code was not modified, but the code was recompiled with the Lahey F77-EM/32 V5.10 compiler to replace the Lahey F77 V4.00 compiled executables, which were distributed with the release of ORIGEN2, Version 2.1.  This was done because the Lahey F77 V4.00 executables were incompatible with Microsoft(R) Windows 95.  The Lahey F77-EM/32 V5.10 executables could be run in a DOS window of Microsoft(R) Windows 95 or greater.  In a May 1998 update, the installation procedure was simplified and files in the sample problems directories were reorganized so that the PC output generated at the ORNL could be distributed in a separate subdirectory for each test case.  Due to calculation discrepancy in the mass of fission products, ORIGEN2, Version 2.1 was replaced by Version 2.2 in June 2002.

The LANL-CO TRU Waste Inventory program qualified ORIGEN2, Version 2.2 software under the SNL-CPG software quality assurance program for the initial 2004 CRA of the WIPP.  As presented in Section 1.0, SNL-CPG uses NP19-1, Software Requirements to quality all their production software.

The following software qualification documents have been developed by LANL as part of DOE's life-cycle management process for software used to support the PA (see Section 2.1).

Requirements Document for ORIGEN 2, Version 2.2.

Design and Implementation Document for ORIGEN2, Version 2.2.

User's Manual for ORIGEN2, Version 2.2

ORIGEN2, Version 2.2 Verification and Validation Plan and Validation
 Document

Software Installation and Checkout Forms (various)

ORIGEN2, Version 2.2 is installed on a production machine platform by executing the compressed Microsoft(R) Windows file, C371DOS3.EXE, on the distribution compact disk (CD) creating a subdirectory C:\origen22.  ORIGEN2, Version 2.2 software has not been modified in any fashion for use by the LANL-CO TRU Waste Inventory Program.

The Microsoft(R) Windows executables were created at the RSICC at ORNL on a Pentium IV in a DOS window of Microsoft(R) Windows 2000 with the Lahey/Fujitsu FORTRAN 95 Compiler Release 5.50d compiler.  According to the Users Manual for ORIGEN2, Version 2.2 [3] the compilation generated warning messages but no fatal errors.  DOE also tested the executables under Microsoft(R) Windows 95.

The official version of ORIGEN2, Version 2.2 source code is listed in Appendix 1 of the Design and Implementation Document (DI) [4].  Appendix 2 in the DI is the ORIGEN2, Version 2.2 variable dimension data file that defines the problem size of the main routine.  Appendix 3 of the DI contains the relevant data library file (DECAY.LIB) supplied with the ORIGEN2, Version 2.2 distribution CD.

The Requirements Document for ORIGEN2, Version 2.2 (RD), identifies the requirements that ORIGEN2, Version 2.2 must satisfy under four categories [2]: 1) functional requirements, (2) external interface requirements, (3) design constraints, and (4) attributes.  Table 5.36-1 presents a summary of the specific requirements and the implementation methods to meet the RD.

Table 5.36-1.  Software Requirements and Implementation Methods

                            Functional Requirements
                         Design/Implementation Method
                                      F1
The software output must provide the version of the software being used.
ORIGEN2, Version 2.2 writes the version of the software to the output file(s).
                                      F2
The software output must provide the date and the time that the software is executed.
ORIGEN2, Version 2.2 writes the date and time the software was executed in the output file(s).
                                      F3
The software input must allow the user to specify a unique case title that is then printed to the output file.
ORIGEN2, Version 2.2 allows the user to enter a unique case title which is subsequently written to the output file(s).
                                      F4
The software data libraries must include all the radionuclides required to be tracked for the WIPP PA.  If the data libraries are missing any of the required radionuclides, the software must provide the ability to extend, update, and correct the libraries.
The decay data library listing (Appendix 3) lists all radionuclides that ORIGEN2, Version 2.2 tracks and will be verified against PA data needs.  The library is in an American Standard Code for Information Interchange (ASCII) test file, which allows it to be modified.
                                      F5
The software must have the ability to indicate that there were errors and the nature of the error in the execution of any case.
ORIGEN2, Version 2.2 has the ability to generate error messages and describes the associated nature of the error upon execution.
                                      F6
The software must employ a matrix exponential method to solve a large system of coupled, linear, first-order ordinary differential equations with constant coefficients to simulate the decay and buildup of radionuclides. ORIGEN-S functional requirement modified to state that, "The software must perform accurate radionuclide decay and buildup calculations" [10].
ORIGEN2, Version 2.2 is based on the matrix exponential method to solve a large system of coupled, linear, first-order ordinary differential equations with constant coefficients to simulate accurate decay and buildup of radionuclides.
              External Interface Requirements  -  User Interface
                         Design/Implementation Method
                                      E1
                                     (SI1)
The software input and output files must be in standard ASCII text file format with data in the format required by and generated by executing ORIGEN2, respectively. E1 same as SI1 [10].
ORIGEN2, Version 2.2 input and output files are in ASCII text file format.
                                     (SI2)
The software must provide an application program interface (API) which allows calling applications to execute a radioactive decay scenario. The results of the execution should be provided in an ASCII test-based file which may be passed by the calling application. New requirement and replaces TransOrigen software.
SCALE6/ORIGEN-S contains an API that allows an external program to execute ORIGEN-S and outputs the results to the calling program in ASCII format ([10] Section 3.2.).
                  Design Constraints  -  Hardware Limitations
                         Design/Implementation Method
                                      D1
The software must have the ability to be executed on an Intel Pentium or equivalent processor PC machine capable of running Microsoft(R) Windows 95 or greater.
ORIGEN2, Version 2.2 is designed to be operated within a DOS operating environment, which is included in Microsoft(R) Windows 95 or greater.
                            Attributes  -  Security
                         Design/Implementation Method
                                      S1
The software will only be available for execution to ORIGEN2, Version 2.2 licensed user's within the TRU Waste Inventory Program and will reside on Intel Pentium processor machines or equivalent running Microsoft(R) Windows 95 or greater.  Physical access to the software will be restricted to the Software Sponsor, the user(s) and the Software Configuration Management Coordinator (SCMC).
The Software Sponsor will designate user(s) of the software.  ORIGEN2, Version 2.2 will be installed on ORIGEN2, Version 2.2 licensed user's Intel Pentium processor machines running Microsoft(R) Windows 95 or greater.  Physical access to the software will be restricted to the Software Sponsor, the user(s) and the SCMC.
                        Attributes  -  Maintainability
                         Design/Implementation Method
                                      A1
The requirements related to maintainability that will be followed are set forth in LCO-QP19-1, Software Quality Assurance, and LCO-QPD-02, LANL-CO Software Quality Assurance Plan.
Maintainability of ORIGEN2, Version 2.2 will be implemented by following the requirements of LCO-QP19-1 and LCO-QPD-02.
                 Transferability and Conversion (Portability)
                         Design/Implementation Method
                                      P1
ORIGEN2, Version 2.2 must be installed on approved licensed user's machines where the workstation configuration standard must be Microsoft(R) Windows XP.
ORIGEN2, Version 2.2 will only be installed on approved user's machines where the workstation configuration standard is Microsoft(R) Windows XP or greater.
Note: Requirements in ( ) are additions or modifications related to the ORIGEN-S software requirements [10].

The Verification and Validation Plan and Validation Document (VVP/VD) describes only the decay and buildup features to be provided by the ORIGEN2, Version 2.2 software and does not verify and validate the reactor simulation of the software [5].

While the ORIGEN2, Version 2.2 software has many capabilities, the qualification for use in the WIPP LANL-CO TRU Waste Inventory Program is limited to radionuclide buildup and decay calculations.  DOE's qualification does not encompass any other code functionalities and any other use of ORIGEN2, Version 2.2.

The software is only used to calculate the inventory of radionuclides on a waste stream basis decayed to common base years, as defined by SNL [6].

In 2011, Los Alamos National Laboratory (LANL) qualified the SCALE6/ORIGEN-S code for use in WIPP PA inventory calculations.  EPA reviewed LANL's qualification in 2014 as part of its 2014 CRA review. LANL migrated to ORIGEN-S because ORIGEN2 was no longer supported by the Radiation Safety Information Computational Center (RSICC) at Oak Ridge National Laboratory (ORNL) ([8] Section 1). The matrix exponential expansion model of the ORIGEN code is unaltered in ORIGEN-S [8], therefore the program description provided above is still valid.

As noted by LANL, "All features of ORIGEN are retained, expanded, or supplemented within the ORIGEN-S module." The main difference between ORIGEN-S and ORIGEN2 is that the decay library, "... has been updated, contains current half-life data and associated radionuclide branching function" [8]. These changes for some radionuclide decay time periods my cause results to exceed acceptance criteria which will require additional review and explanation.

Tables 5.31-1 and 5.31-2 are modified to document changes in software requirements [10] and requirements tested [8]. The test methodology, results and Agency findings pertaining to the qualification of SCALE6/ORIGEN-S are discussed below.

<IP_ADDRESS>	Test Methodology

A number of the requirements that the ORIGEN2, Version 2.2 software must satisfy are qualitative in nature.  The qualitative requirements are validated through manual inspection of the test case output files in accordance with the acceptance criteria established for each test case in Section 4.0 of the VVP/VD [5].  The principal type of calculation performed by the ORIGEN2, Version 2.2 software relevant to the CID involves decaying radionuclides of TRU waste streams based on a reference assay year to common base years.  These quantitative calculations are accomplished within the ORIGEN2, Version 2.2 software through various numerical methods, with the key being the matrix exponential solution method.  The quantitative requirement for the ORIGEN2, Version 2.2 software to perform decay and buildup calculations was validated by comparison of the ORIGEN2, Version 2.2 results with those by the MicroShield(R) Version 6.02 software.  Quantitative comparisons of the results calculated by the software packages were accomplished by using Windows Microsoft Excel spreadsheets to check whether the acceptance criteria have been satisfied.

The primary methods of software test result validation utilized by LANL were by a combination of manual inspection of the output files and comparison of the test case results to those calculated by an independently developed and validated decay and buildup software.

MicroShield Version 6.02

MicroShield Version 6.02 is Windows-based software developed and maintained by Grove Engineering (Framatome ANP, Inc., d.b.a. Grove Engineering).  MicroShield Version 6.02 is used to analyze shielding and estimate exposure from gamma radiation.  Several of the specific uses of this type of analysis include designing shields and containers, assessing radiation exposure to people and equipment, selecting temporary shielding for maintenance tasks, inferring source strength for waste characterization and disposal from external gamma radiation measurements, minimizing exposure to people, and teaching principles of radiation and shielding.

MicroShield Version 6.02 verification and validation was conducted in conformance with Grove Engineering's Quality Assurance Program implementing the requirements of 10 CFR 50 Appendix B, as delineated in the MicroShield Quality Assurance Plan.  The Plan also implements ASME NQA 2a-1990, Part 2.7, Quality Assurance Requirements of Computer Software for Nuclear Facility Applications.

Microsoft Excel and Access Applications

Two Microsoft Excel applications were used for the ORIGEN verification and validation activities.  The first application, TransOrigen.xls, is a pre- and post-processor Excel workbook application for the ORIGEN2, Version 2.2 software.  The application provides an interface to process TRU waste stream data using the ORIGEN2, Version 2.2 software by facilitating the creation of input files, running the software, and post-processing the output files.  Documentation of the structure, functionality, and operations of the TransOrigen workbook application is provided in Section 3.0 of the VVP/VD [5].  The TransOrigen application also utilizes a Microsoft Access database file, TransOrigen.mdb, in its data transfer between the applications.  The second Excel application, GN_MS_Difference.xls, involves an Excel workbook developed to facilitate quantitative comparison of the results calculated by the ORIGEN2, Version 2.2 and the MicroShield Version 6.02 software for Test Cases 1 through 3 of the VVP/VD [5].  It consists of:

 The ORIGEN2, Version 2.2 decayed activity concentrations in units of Ci/m[3]
 The MicroShield Version 6.02 decayed activity concentrations in units of Ci/m[3]
 The absolute difference between the ORIGEN2, Version 2.2 and MicroShield Version 6.02 calculated activity concentrations in units of Ci/m[3]
 The relative percent difference (RPD) between ORIGEN2, Version 2.2 and MicroShield Version 6.02 calculated activity concentrations in units of Ci/m[3]

The inventory of radionuclides must be tracked for WIPP PA calculations and for determining the waste unit factor on a waste stream basis and/or on a WIPP-scale basis [6].  The key PA radionuclides are listed in Table 2-1 of the VVP/VD [5] with the corresponding six-digit numerical representation used by the ORIGEN2, Version 2.2 software.

Test Cases

Testing of ORIGEN2, Version 2.2 software was performed on a PC platform utilizing an Intel(R) Pentium(R) M Processor 2.26 GHz/2.21 GHz with Microsoft Windows XP Professional, Version 2002 SP2 as the operating system.  Computer programs Microsoft Office Excel 2003 SP2 and Microsoft Office Access 2003 SP2 were also utilized.

The VVP/VD documents eight test cases. Test Cases 1 through 3 test the ability of the software to perform decay and buildup calculations for 12 radionuclides in the TRU waste over the range of decay times required by the TRU Waste Inventory Program.  Test Cases 4 through 6 test the ability of the ORIGEN2, Version 2.2 software to produce identical results across various PC platforms (Intel Pentium processor machines or equivalent running Windows 95 or greater).  These test cases require the thermal reactor simulation of the ORIGEN2, Version 2.2 software (i.e., O2_THERM.EXE), which was used for Test Cases 1 through 3. Test Case 7 tests the ability of the ORIGEN2, Version 2.2 software to indicate errors. Test Case 8 tests the ability of ORIGEN2, Version 2.2 software to include all the radionuclides required to be tracked for WIPP. Descriptions of the test cases are provided in Sections 4.1 through 4.8 of the VVP/VD.  Table 5.36-2 provides a summary of the requirements coverage by test case.

In 2011, LANL qualified ORIGEN-S Version 2.2 using the techniques described above, which include manual inspection of the output files and comparison of test results to those calculated independently (regression testing).  In this case ORIGEN-S results are compared to ORIGEN2 results calculated on the same computer platform (Intel(R) Pentium(R) III Xenon Processor @ 2.60 GHz) [8].  Modifications to the software requirements and test cases coverage are listed in Table 5.36-2.  LANL used Windows Microsoft Excel spreadsheets to compare ORIGEN-S and ORIGEN2 Version 2.2 results.

Qualification of ORIGEN-S Version 2.2 consists of seven test cases (Test Case 8 was removed because Test Cases 1 through 4 test the F4 requirement in Table 5.36-2):

Test Cases			Scope (as described in the VVP/VD) [8]

       1  		Ensure ORIGEN-S module contains all of the WIPP PA radionuclides.
  2 and 3	Verify that ORIGEN-S correctly decays PA radionuclides CH and RH activities for 100, 1000, and 10,000 years.
      4		Decays sum of CH and RH (total) activities for 169 radionuclides correctly for                  	100, 1,000 and 10,000 years.
  5 and 6 	Verify proper operation of ORIGEN-ARP and PlotOPUS. LANL results are                 		compared to RSICC results.
      7		Verify ORIGEN-S reports errors properly.

LANL also notes, "In cases where the acceptance criteria are exceeded, an explanation and justification will be provided."

Table 5.36-2.	ORIGEN2 Version 2.2 Requirements Coverage by Test Case

                                  Requirement
                                   Test Case
                                      No.
                                  Description
                                       1
                                       2
                                       3
                                       4
                                       5
                                       6
                                       7
                                       8
                                      F1
The software output must provide the version of the software being used.
                                       X
                                       X
                                       X
                                       X
                                       X
                                       X
                                       *

                                      F2
The software output must provide the date and the time that the software is executed.
                                       X
                                       X
                                       X
                                       X
                                       X
                                       X
                                       *

                                      F3
The software input must allow the user to specify a unique case title that is then printed to the output file.
                                       X
                                       X
                                       X
                                       *
                                       *
                                       *
                                       *

                                      F4
The software data libraries must include all the radionuclides required to be tracked for the WIPP PA.  If the data libraries are missing any of the required radionuclides, the software must provide the ability to extend, update, and correct the libraries.
                                       *
                                       *
                                       *
                                       *

                                       X
                                      F5
The software must have the ability to indicate that there were errors and the nature of the error in the execution of any case.

                                       X

                                      F6
The software must employ a matrix exponential method to solve a large system of coupled, linear, first-order ordinary differential equations with constant coefficients to simulate the decay and buildup of radionuclides.  ORIGEN-S functional requirement modified to state that, "The software must perform accurate radionuclide decay and buildup calculations" [10].
                                       X
                                       X
                                       X
                                       *

                                      E1
                                     (SI1)
The software input and output files must be in standard ASCII text file format with data in the format required by and generated by executing ORIGEN2, Version 2.2, respectively.
                                       X
                                       X
                                       X
                                       X
                                       X
                                       X
                                       *

                                     (SI2)
The software must provide an application program interface (API) which allows calling applications to execute a radioactive decay scenario. The results of the execution should be provided in an ASCII text-based output file which may be passed by the calling application.
                                       *
                                       *
                                       *
                                       *

                                       *

                                     (D1)
The software must have the ability to be executed on an Intel Pentium or equivalent processor PC machine capable of running Microsoft(R) Windows XP.
                                       *
                                       *
                                       *
                                       *
                                       *
                                       *
                                       *

Note: Requirements in ( ) or with * are additions or modifications related to the ORIGEN-S software requirements [8].  Test Case 8 removed because Test Cases 1 through 4 test the F4 requirement.

<IP_ADDRESS>	Test Results

The purpose of Test Cases 1 through 3 is to decay 1 Ci/m[3] of each of 12 radionuclides with the highest concentrations in TRU waste over 3 time periods (i.e., 37, 50, and 100 years).  This same initial starting concentration was specified as input to the MicroShield Version 6.02 code.  The calculations obtained by running both ORIGEN2 Version 2.2 and MicroShield Version 6.02 code results were subsequently compared.

The stated intent of Tests 1 through 3 is to test the ability of the software to perform decay and buildup calculations for 12 radionuclides of TRU waste over the range of decay times required by the TRU Waste Inventory Program.  It is unclear why the comparison is not performed over a longer simulation time.  For instance, the verification of TransOrigin discussed in Section 5.36.2 included times of 100, 350, 1,000, 5,000 and 10,000 years.

The predicted discrepancy between ORIGEN and MicroShield at 37 years for Sr-90 was 1.6%; at 50 years, this error increased to 4.26%, and at 100 years, it decreased to 2.15%.  Although the differences were within the acceptance criteria of 5%, the relatively short timeframes do not allow an evaluation of how the errors may propagate over the time period of interest.  This concern was raised by the Agency to the DOE on June 10[th], 2010.  In response to the EPA's concern, DOE provided the following response:

      In light of the recent technical comment from the EPA regarding ORIGEN2, version 2.2 qualification under LANL-CO Software QA program, and the lack of a 10,000 year decay test, we investigated the LANL-CO ORIGEN2 Verification & Validation Plan and Validation Document (VVP/VD) tests to understand the problem better.

      First, we know that EPA recertified the WIPP in 2006.  Under the CRA (1), ORIGEN2, version 2.2 was used to decay the radionuclide inventory.  At that time, it was tracked under the software QA program at SNL-CPG.  SNL-CPG had qualified it after publishing a VVP/VD document of their own (ERMS #535718).  So, we thought it worth comparing the SNL-CPG VVP/VD test cases with those listed in LANL-CO's VVP/VD.  We know that we generally modeled our own VVP/VD from SNL's when we published ours in 2006.

      We found that five test cases are exactly as prescribed by SNL-CPG with no differences in output other than date/time stamping.  In addition to these, three test cases are very similar in their methodology, but use different input parameters and thus have different output.  One additional test case, though, was not performed by LANL-CO (this happens to be the one lacking test that EPA is calling into question).  LANL-CO never ran a specified test which decayed a radionuclide for 10,000 years and compared its results to those from another software package.  SNL-CPG's test case #7 prescribed the decay of 4,076 Ci of Pu-238 for 10,000 years, and compared the results from ORIGEN2 to those of their PANEL code.  Only long-lived (half-lives > 22 years) daughters were compared in the results.

      Upon further investigation, however, we found that two of our test cases (#4 and #6, which involved executing sample problems that came packaged with the ORIGEN2, version 2.2 code) did in fact decay radionuclide data for a range of terms from 0.1 years up to 1,000,000 years, including a 10,000 year term.  When we ran these tests, our results matched exactly those documented with the published sample problems packaged with the ORIGEN2, version 2.2 code.

      But in order to address EPA's concern, we decided to execute SNL-CPG's test case #7 on our ORIGEN2, version 2.2 production platform here at LANL-CO.  The results we obtained are exactly equal to those documented in SNL-CPG's VVP/VD.  Attached is the results of the comparison that was performed.

In response to DOE's explanation, the Agency reviewed the code comparison that DOE provided, as well as relevant sections in SNL's Verification and Validation Plan and Validation Document for ORIGEN2 Version 2.2 [7].  The LANL results for Test Case 7 do match exactly those results obtained by SNL for the same test problem.  Furthermore, the error falls below the acceptance criteria of 5%.

In the 2011, qualification of ORIGEN-S Version 2.2, Test Cases 1, 2 and 3 showed similar results.  For these tests cases, differences in results were relatively minor and caused by the half-life differences in the new ORIGEN-S program library. EPA agrees with LANL's explanation.  Test Case 4 showed a maximum of 0.247% difference between ORIGEN-S and ORIGEN2 results, which is reasonable.

Test Case 5 used RSICC Sample Problem 2 to validate that ORIGEN-S properly executes ORIGEN-ARP on LANL computers. Test case five results were identical to RSICC results.  Test Case 6 was used to validate the PlotOPUS plotting utilities.  Test Case 6 produced results that exactly mimic those generated by RSICC.  Test Case 7 verified ORIGEN-S' error handling capability.  ORIGEN-S reported errors and showed the nature of the errors properly.

<IP_ADDRESS>	The Agency's Conclusions

Based upon a review of the verification activities, the Agency concludes that ORIGEN-S Version 2.2 meets the acceptance criteria and is validated for decay and buildup calculations for the WIPP PA and the annual inventory calculations on LANL computers (Intel(R) Pentium(R) computers with Microsoft Windows Operating System and software).

<IP_ADDRESS>	References

 ORNL 2002.  RSICC Computer Code Collection: ORIGEN2.2, Isotope Generation and Depletion Code Matrix Exponential Method.  CCC-371, Oak Ridge National Laboratory, Oak Ridge, Tennessee.
 LANL 2007.  Requirements Document for ORIGEN 2, Version 2.2.  INV-OGN-01 Los Alamos National Laboratory  -  Carlsbad Operations, Carlsbad, New Mexico.
 LANL 2007.  MicroShield 6 User's Manual.  LCO-MIC-03, Los Alamos National Laboratory  - Carlsbad Operations, Carlsbad, New Mexico.
 LANL 2007.  Design and Implementation Document for ORIGEN2, Version 2.2.  INV-OGN-02, Los Alamos National Laboratory  -  Carlsbad Operations, Carlsbad, New Mexico.
 LANL 2007.  ORIGEN2, Version 2.2 Verification and Validation Plan and Validation Document  -  WIPP PA.  INV-OGN-04.  Los Alamos National Laboratory  -  Carlsbad Operations, Carlsbad, New Mexico.
 Dunagan, S.  2007.  "Sandia's WIPP Inventory Data Needs for Performance Assessment."  Letter to R. Patterson (CBFO), June 18, 2007.  Sandia National Laboratories, Carlsbad, New Mexico.
 SNL 2004.  ORIGEN2, Version 2.2 Verification and Validation Plan and Validation Document  -  WIPP PA.  Sandia National Laboratories  -  Carlsbad Programs Group, Carlsbad, New Mexico.
 WIPP PA  -  "ORIGEN-S Verification and Validation Plan and Validation Document, Revision 0", INV-OGS-03, dated June 3, 2011. Los Alamos National Laboratory  -  Carlsbad, New Mexico.
 WIPP PA  -  "ORIGEN-S, User' Manual, Revision 3", INV-OGS-02, dated June 7, 2011. Los Alamos National Laboratory  -  Carlsbad, New Mexico.
 WIPP PA  -  ORIGEN-S Requirements Document, Revision 1, dated May 16, 2011. Los Alamos National Laboratory  -  Carlsbad, New Mexico.

TransOrigen

**NOTE: Functionality incorporated into CID database software.

  <IP_ADDRESS> Introduction

Please Note: In 2014, EPA reviewed LANL's ORIGEN (ORIGEN-S, newest version) and CID documentation related to the TransOrigen code.  LANL incorporated all of TransOrigen's functionality into the CID database software.  The new CID database software imports input files and exports ORIGEN-S results directly.  The Agency focused its 2014 review on the changes to the CID database and software.  The Agency left this section of the report unchanged to preserve historical review information.

TransOrigen is a Microsoft Excel-based automation tool used to efficiently execute the ORIGEN2, Version 2.2 software in a batch sequence (once per waste stream), and compile the output data from all executions into a single spreadsheet.  The input for the execution is exported from the Comprehensive Inventory Database (CID).  TransOrigen writes a series of ORIGEN input files containing the input data.  Following the execution of ORIGEN on each of the files, the output data are transferred into a single "results" sheet within TransOrigen.  The CID subsequently imports these results for reporting purposes.

LANL completed an Analysis Report [1] to document the validity of the unit conversion and data transfer between the CID v.1.00 S.1.00 data version D.7.00 [2], and ORIGEN2, Version 2.2 software (Section 5.31.1).  The CID was qualified for use as developed software under the LANL-CO Quality Assurance (QA) Program in December of 2006, in accordance with LANL-CO Software Quality Assurance Plan, Revision 1 [3] and Quality Assurance for Developed Software, Revision 0, LCO-QP19-1 [4].  ORIGEN2, Version 2.2 was qualified for use as adopted software under the LANL-CO QA Program in August of 2007, in accordance with LANL-CO Software Quality Assurance Plan, Revision 2 [5] and Software Quality Assurance, Revision 1 [6].

This unit conversion and data transfer activity is accomplished using a utility named "TransOrigen," a Microsoft Excel 2003 workbook file (TransOrigen.xls) designed to accommodate the batch unit conversion and transfer of isotopic data, decay corrected using the ORIGEN2, Version 2.2 software.  TransOrigen employs Excel macros and code modules, written in Visual Basic for Applications (VBA), to perform calculations and transfer data between tabular spreadsheets and ASCII text files, which are the basis for the ORIGEN2, Version 2.2 input and output files.  In addition, TransOrigen makes use of a Microsoft Access 2003 database (TransOrigen.mdb) table to boost processing performance.  Appendix I of the Analysis Report provides a detailed description and application of the use of the workbook [1].

The testing of TransOrigen was performed on a workstation with the following characteristics:

 LANL Property No. PN1146933
 Hardware:  Dell Optiplex GX270
 Intel Pentium(R) 4 CPU - 3.2 GHz
 GB RAM
 212 GB HD
 Operating System: Microsoft(R) Windows XP Professional
 Version 2002 Service Pack 3
 Software: Microsoft Office Excel 2003 SP3
 Microsoft Office Access 2003 SP3
 Comprehensive Inventory Database v.1.00 S.1.00, data version D.7.00 [7]
This activity is performed by the LANL-CO Transuranic (TRU) Waste Inventory Program, and provides SNL information on the waste stream decay of radiological data for the PA calculations.

The Analysis Report [1] was prepared as prescribed by the Analysis Plan for Transuranic Waste Inventory, INV-AP-01, Revision 3 [8], and is written in accordance with Analyses, Revision 3 [9].  The Analysis Report is also prepared in accordance with current revisions of the LANL-CO Software Quality Assurance Plan, Revision 3 [10] and Software Quality Assurance, Revision 1 [11].  The test methodology, results and Agency findings pertaining to the qualification of TransOrigin are discussed below.

  <IP_ADDRESS>	Test Methodology

The CID maintains radionuclide concentrations (in Ci/m[3]) on a waste stream basis.  The CID also contains the year, for each waste stream, in which the radionuclide information was analyzed.  SNL requires that the radionuclide activities be decay-corrected to seven different common base years for purposes of running the PA.  In order to accomplish this, the radionuclide concentrations must be exported from the CID to TransOrigen, decay-corrected by ORIGEN2, Version 2.2 to the specified common base year, and re-imported from TransOrigen, for reporting by the CID.  ORIGEN2, Version 2.2 can accept a radionuclide distribution (in grams) for a single waste stream at a time, prescribing a single decay period (in years) in the form of a *.inp input file. Therefore, TransOrigen is designed to automate the following:

 Unit conversion from Ci/m[3] to g/m[3] for each waste stream's radionuclides
 Generating an ORIGEN2, Version 2.2 input file (*.inp) for each waste stream containing the radionuclide parameters
 Processing multiple executions of ORIGEN2, Version 2.2 (one per waste stream) as a batch
 Importing resulting radionuclide data from the ORIGEN2, Version 2.2 output files (*.u11)
 Unit conversion from g/m[3] back to Ci/m[3] for each waste stream's radionuclides

TransOrigen converts Ci/m[3] to g/m[3], which are subsequently supplied to ORIGEN2, Version 2.2, as an input using the ORIGEN2, Version 2.2 numeric ID.  ORIGEN2 Version 2.2 is used to decay the radionuclides for the prescribed period.  TransOrigen then reads the output file and converts the decayed radionuclides back from g/m[3] to Ci/m[3], and compiles the results of each execution into a format that can be imported back into the CID.  In order to validate the unit conversion and transfer of data between the TransOrigen utility and ORIGEN2, Version 2.2, LANL performed a separate validation execution to demonstrate that the pre- and post-processing data transfers are functioning as intended.  The "20081112_Val" folder (included in the electronic media associated with this analysis) contains the files pertaining to this execution.  In order to demonstrate the TransOrigen utility functions properly, a set of input data were decayed by ORIGEN2, Version 2.2 for a decay period of 0 (zero) years.  This dataset is essentially the CID data version D.7.00 radionuclide data, with the exception that all generation years have been explicitly set to 2007, with decay thru the year 2007.  The intent of this execution is to compare the input dataset with the output dataset for equivalency.  Any discrepancies were to be documented and an explanation given.  The acceptance criteria for validation are that no radionuclide data are lost as a result of the pre- and post-processing transfer.  Exceptions to these criteria are if the data are intentionally removed (i.e., an input activity concentration of zero Ci/m[3]), and if the data is lost because of limitations related to the TransOrigen utility (i.e., gram parameters cannot be smaller than 1.00E-24 or larger than 1.00E+38).

LANL validated the execution of the TransOrigen by conducting a technical review of the analysis results.  As part of that analysis, an example waste stream (SR-W027-221H-HET-RH) was selected for detailed inspection for each of the seven decay runs.  The results of this inspection are described within the Analysis Report [1].  The input data for the calculations are given in Table 1 of that report [1].  Waste stream SR-W027-221H-HET-RH contains 11 radionuclides, which are Am-241, Np-237, Pu-238, Pu-239, Pu-240, Pu-241, Pu- 242, U-234, U-235, U-236, and U-238.  The radionuclide concentrations for the waste stream reside in the CID data version D.7.00 [7].

Seven decay calculations are performed separately and verified to ensure that the radionuclide concentrations are properly converted from TransOrigen to ORIGEN2, Version 2.2.  The decay calculations for the waste stream SR-W027-221H-HET-RH are as follows.

 Decay through year 2007 (baseline inventory date)
 Decay through year 2033 (WIPP closure)
 Decay through year 2133 (100 years from WIPP closure)
 Decay through year 2383 (350 years from WIPP closure)
 Decay through year 3033 (1,000 years from WIPP closure)
 Decay through year 7033 (5,000 years from WIPP closure)
 Decay through year 12033 (10,000 years from WIPP closure)

The first worksheet in the TransOrigen workbook, called "qryOrigenDump_Final," contains the input data.  The computational methodology (implemented in the TransOrigen.xls workbook) involved a 12-step process described in Section 3 of the Analysis Report [1].  Briefly, these steps involved inputting data into TransOrigen, the data is manipulated and results are extracted and extraneous numeric format is removed, duplicate input is removed, and the inputted data are translated to symbols and numeric format.

  <IP_ADDRESS>	Test Results

Overall results of the comparison show that there is no difference between the TransOrigen and the ORIGEN2, Version 2.2 output, except for the last significant figures, due to rounding and unit conversions between TransOrigen and ORIGEN2, Version 2.2.  Details of each comparison for the 11 radionuclides are shown in Figures 1 through 4 in Section 4 of the Analysis Report [1].

<IP_ADDRESS>	The Agency's Conclusions

Based upon a comparison of work sheets, input and output files, the Agency concludes that TransOrigin meets the acceptance criteria and is validated for WIPP PA use.
<IP_ADDRESS>	References

 LANL 2008.  TransOrigin Unit Conversion and Data Transfer for the 2007 TRU Waste Inventory.  Analysis Report.  INV-SAR-14.  Los Alamos National Laboratory  -  Carlsbad Operations.
 LANL 2008.  Software Quality Assurance Plan, Revision 3, LCO-QPD-02, Carlsbad, New Mexico.  Los Alamos National Laboratory  -  Carlsbad Operations (LANL  -  CO).
 LANL 2005.  Criteria for the Certification and Recertification of the Waste Isolation Pilot Plant's Compliance With the 40 CFR Part 191 Disposal Regulations, Final Rule, 40 CFR 194, Federal Register, February 9, 1996.  Los Alamos National Laboratory  -  Carlsbad Operations (LANL - CO).
 LANL 2005.  Software Quality Assurance Plan, Revision 1, LCO-QPD-02, Carlsbad, New Mexico.  Los Alamos National Laboratory  -  Carlsbad Operations (LANL - CO).
 LANL 2007.  Quality Assurance for Developed Software, Revision 0, LCO-QP19-1, Carlsbad, New Mexico.  Los Alamos National Laboratory  -  Carlsbad Operations (LANL - CO).
 LANL 2007.  LANL-CO Software Quality Assurance Plan, Revision 2, LCO-QPD-02, Carlsbad, New Mexico.  Los Alamos National Laboratory  -  Carlsbad Operations (LANL - CO).
 LANL 2008.  Comprehensive Inventory Database, v.1.00, S.1.00, data version D.7.00, Carlsbad, New Mexico.  Los Alamos National Laboratory  -  Carlsbad Operations (LANL - CO).
 LANL 2008.  Analysis Plan for Transuranic Waste Inventory, Revision 3, INV-AP-01, Carlsbad, New Mexico.  Los Alamos National Laboratory  -  Carlsbad Operations (LANL - CO).
 LANL 2008.  Analyses, Revision 3, LCO-QP9-1, Carlsbad, New Mexico.  Los Alamos National Laboratory  -  Carlsbad Operations (LANL - CO).
 LANL 2007.  Software Quality Assurance, Revision 3, LCO-QP19-1, Carlsbad, New Mexico.  Los Alamos National Laboratory  -  Carlsbad Operations (LANL - CO).
 LANL 2002.  Software Quality Assurance, Revision 1, LCO-QP19-1, Carlsbad, New Mexico.  Los Alamos National Laboratory  -  Carlsbad Operations (LANL - CO).

Comprehensive Inventory Database

  <IP_ADDRESS> Introduction

To support the CCA and 2004 CRA, the DOE compiled an inventory of the TRU waste that were expected to be shipped to and disposed of in the WIPP.  The documents that provide these waste projections are Transuranic Waste Baseline Inventory Report, Revision 2 [1]; Transuranic Waste Baseline Inventory Report, Revision 3 [2]; and Transuranic Waste Baseline Inventory Report  -  2004 [3].  The generation of TRU waste inventory reports after the 2004 CRA have been facilitated by utilizing the CID.  The CID is a database application that was created using Microsoft(R) Access Data Project(R) (ADP) technology and provides access to a database running on a Microsoft SQL Server(R) 2000 platform.

The CID uses waste stream information provided by the DOE TRU waste generator sites.  This waste stream information includes a waste stream profile that is assigned to a Final Waste Form by the DOE TRU waste sites.  The CID has replaced the Transuranic Waste Baseline Inventory Database (TWBID), Revision 2.1, as the central inventory information repository for tracking all existing and potential (TRU) waste for use in the CRA-2009 and future CRAs.

The CID is frequently updated and contains all radiological, physical, chemical, and volumetric information for TRU waste generated at DOE complex TRU waste sites that eventually may be shipped to the WIPP.  The information is updated by either electronically importing data or by manual entry.  The waste information is tracked at a waste stream level, rather than on a container-by-container basis.

The following software qualification documents were developed as part of DOE's life-cycle management process for the CID to support their PA (Section 1.0):

 Requirements Document (RD), Requirements Document for the Comprehensive Database [4]
 Verification and Validation Plan (VVP), Verification and Validation Plan for the Comprehensive Inventory Database [5]
 Design & Implementation Document (DID), Design & Implementation Document for the Comprehensive Inventory Database [6]
 User's Manual (UM), User's Manual for the Comprehensive Inventory Database [7]
 Validation Document (VD), Validation Document for the Comprehensive Inventory Database [8]
 Software Installation and Checkout Forms (various)

The CID is updated and collected from the generator sites and WIPP on an annual basis.  Inventory data are compiled, summarized, scaled, reported from the CID, and published within the Performance Assessment Inventory Report (PAIR).  The CID was qualified December 2006 under QA 19-1 procedures [9, 10].
From 2011 through 2013, LANL ran three qualification activities to verify that the CID database and software continued to perform inventory operations correctly [12, 15, 16]. EPA reviewed LANL's qualification of the CID database and software in 2014 as part of its 2014 CRA review. In 2011, LANL ran 75 test cases to qualify CID Version 2.00 on Windows computer hardware using Microsoft Office Access and Excel 2010 and Microsoft SQL Server 2008 database software. In 2012, eleven test cases were run on CID Version 2.01 to test changes due to database/software problems reported by users and change control proposals [15].  In 2013 sixteen test cases were run on CID Version 2.02 to also test database/software changes [16].
Various cases tested a number of requirements the CID database and software are expected to perform, as documented in the requirements document [11].  These requirements include data entry, data import, manual data lookup, ORIGEN-S interface, report generation and other inventory related activities [11].  Functionality of TransOrigen was moved to the CID software. These functions were tested by a number of test cases, such as TC-018 and TC-083 [16].
The approach used by LANL is similar to that described in this report as described in [12] Section 5.3 (page 12). Numerous test cases were developed to test more than 200 requirements specified for the CID database and software [11]. The test methodology, results and Agency findings pertaining to the qualification of the CID are discussed below.
  <IP_ADDRESS>	Test Methodology

Microsoft(R) Access Data Project(R) (ADP) was used to develop the CID.  This technology was based upon the following considerations:

 Distributed Architecture
 Increased Development Efficiency
 Scalability
 Security
 Performance

The CID server component is a database running on a Microsoft SQL Server 2000 platform.

The VVP [5] identifies the following requirements:

    Twenty-three (23) functional requirements pertaining to the waste streams (e.g., volume shipped, radionuclide composition, complexing agents, oxianions, etc.)
    Twenty-six (26) reporting requirements (e.g., projected waste generation, waste shipping progress, waste stream volumes by container type)
    Thirty-four (34) interface requirements (e.g., viewing, conflict detection)
    Six (6) nonfunctional requirements (e.g., portability and performance)

The VD [8] presents 34 test cases that are designed to test all of the functional requirements listed above.  Table 5.31-1 presents the workstation configurations used during Validation testing.

Table 5.31-3.	Workstation Configurations Used during Validation Testing

                                  Workstation
                                   CPU Speed
                                      RAM
                                    HD Size
                               Operating System
                                System Software
                            Screen Resolution Used
PN1098668

Dell Latitude Laptop

Property No. 1098668
996 MHz
524 Mb
30 Gb
MS Windows 2000 Professional SP4
MS Access 2003 SP2

MS Excel 2003 SP2

MDAC 2.8 SP1
1024x768 pixels
PN1163363

Dell Optiplex GX280

Property No. 1163363
3.8 GHz
2.0 Gb
150 GB
MS Windows XP Professional ver. 2002 SP2
MS Access 2003 SP2

MS Excel 2003 SP2

MDAC 2.8 SP1
1024x768 pixels
                                    Server
                                   CPU Speed
                                      RAM
                                    HD Size
                               Operating System
                                System Software

E-CO2

Dell PowerEdge 2600

Property No. 1145676
3.06 GHz
2.0 Gb
272 Gb
MS Windows Server 2003 Standard SP1
MS SQL Server 2000 Standard SP3

To perform the testing, a synthetic dataset was developed to provide a sample set of parameters to test the report generation function.  This synthetic dataset was installed as part of the first test case execution (i.e., Test Case TC-001) and designated the "CIDFull" database, which included the parameters necessary to test the reporting requirements.  Although this dataset was designed to include enough variations in parameters to adequately test the reports, it is not inclusive of every possible combination of parameters.  One simplification in the dataset is that the radionuclide concentrations are not decayed through time.  Although this assumption does not simulate actual conditions, the DOE believes (and the Agency agrees) that for the purposes of testing, it is acceptable.  The parameters that comprise the synthetic dataset are provided in Appendix B of the VD [8].  The data entry requirements that were not tested on the "CIDFull" dataset were tested in other individual test cases.

In 2006, all the test cases were executed by first running the first two test cases (i.e., TC-011 and TC-002).  These test cases include information provided in the form of screen shots, spreadsheets, and reports that illustrate the execution of different steps that are required for all of the test cases [8].  DOE notes that the results of these test cases provide the evidence that the database has met the requirements of the RD [4].  The results from all of the testing are presented in Appendix C of the VD [8].
In 2011, 2012, and 2013, LANL verified that CID Versions 2.00, 2.01 and 2.02 inventory database and software continued to perform inventory operations correctly [12, 15, 16]. LANL ran numerous test cases to qualify CID Version 2.00, 2.01 and 2.02 on Windows computer hardware using Microsoft Office Access and Excel 2010 and Microsoft SQL Server 2008 database software. The approach used by LANL is similar to that described above as explained in Section 5.3 of the VVP/VD [12]. Numerous test cases were developed to test the full range of requirements specified for the WIPP PA (such as decay times up to 10,000 years) for the CID database and software [11].
  <IP_ADDRESS>	Test Results

During the test execution, a number of issues were identified.  DOE determined some to be flaws in the test case steps, while others were deemed to be software-related issues requiring correction. These issues, along with an explanation or their respective dispositions, are listed in the table presented in Section 6 of the VD [8].

The Agency agrees with the DOE determination that only the issues related to the Hazardous Waste Numbers entry (TC-008) should be corrected in the CID software.  Therefore, corrections were made and Test Case TC-008 was retested to validate the functionality.  Corrections were made to the CID, and a new version was released (i.e., S.1.00 RC 2).  Since the software was corrected, both test cases TC-001 and TC-002 (installation of the software) were retested.  Test Case TC-008 was also retested using v.1.00 RC 2, and no issues were identified.

EPA closely examined the results of LANL's CID qualification activities and found that their work thoroughly tested the many requirements for the CID database and database software. As previously performed, some test cases were rerun to verify problems found during the first execution of these test and were properly corrected (for example, test cases TC-076, TC-080, TC-081 and TC-084) [16].

  <IP_ADDRESS>	The Agency's Conclusions

EPA found testing to be adequate based upon the complete range of requirements tested by LANL for the inventory database and software of the Comprehensive Inventory Database (CID Version 2.02). Therefore, the Agency concludes that the CID database and software meets the acceptance criteria and is validated for the WIPP PA and the annual inventory reports on LANL computers (Intel(R) Pentium(R) computers with Microsoft Windows Operating System and software).

  <IP_ADDRESS>	References

 U.S. Department of Energy, 1995, Waste Isolation Pilot Plant Transuranic Waste Baseline Inventory Report, Revision 1, CAO-94-1005, February 1995.
 DOE 1996.  Transuranic Waste Baseline Inventory Report.  Revision 3, June 1996, DOE/CAO-95-1121, U.S. Department of Energy, Carlsbad, New Mexico.
 DOE 2006.  Transuranic Waste Baseline Inventory Report  -  2004.  Revision 0, DOE/TRU-2006-3344, U.S. Department of Energy  -  Carlsbad Field Office, Carlsbad, New Mexico.
 LANL 2006.  Requirements Document (RD), INV-CID-01, Requirements Document for the Comprehensive Database.  Los Alamos National Laboratory  -  Carlsbad Operations, Carlsbad, New Mexico.
 LANL 2006.  Verification and Validation Plan (VVP), INV-CID-02, Verification and Validation Plan for the Comprehensive Inventory Database.  Los Alamos National Laboratory  -  Carlsbad Operations, Carlsbad, New Mexico.
 LANL 2006.  Design & Implementation Document (DD & ID or DID), INV-CID-03, Design & Implementation Document for the Comprehensive Inventory Database.  Los Alamos National Laboratory  -  Carlsbad Operations, Carlsbad, New Mexico.
 LANL 2006.  User's Manual (UM), INV-CID-04, User's Manual for the Comprehensive Inventory Database.  Los Alamos National Laboratory  -  Carlsbad Operations, Carlsbad, New Mexico.
 LANL 2006.  Validation Document (VD), INV-CID-05, Validation Document for the Comprehensive Inventory Database.  Los Alamos National Laboratory  -  Carlsbad Operations, Carlsbad, New Mexico.
 LANL 2007.  Software Quality Assurance, Revision 3, LCO-QP19-1, Carlsbad, New Mexico.  Los Alamos National Laboratory  -  Carlsbad Operations (LANL - CO).
 LANL 2002.  Software Quality Assurance, Revision 1, LCO-QP19-1, Carlsbad, New Mexico.  Los Alamos National Laboratory  -  Carlsbad Operations (LANL - CO).
  [11] LANL 2011. Requirements Document for the Comprehensive Inventory Database, Revision 5, INV-CID-01, dated July 18, 2011, Carlsbad, New Mexico. Los Alamos National Laboratory  -  Carlsbad Operations (LANL - CO).
  [12] LANL 2011, Verification & Validation Plan and Validation Document for the Comprehensive Inventory Database, Revision 2, INV-CID-02, dated July 28, 2011, Carlsbad, New Mexico. Los Alamos National Laboratory  -  Carlsbad Operations (LANL - CO).
  [13] LANL 2014, Design & Implementation Document for the Comprehensive Inventory Database. Revision 3, INV-CID-03, dated January 10, 2014, Carlsbad, New Mexico.  Los Alamos National Laboratory  -  Carlsbad Operations (LANL - CO).
  [14] LANL 2013, User's Manual for the Comprehensive Inventory Database, Revision 2, INV-CID-04, dated December 19, 2013, Carlsbad, New Mexico.  Los Alamos National Laboratory  -  Carlsbad Operations (LANL - CO).
  [15] LANL 2012, Validation Document for the Comprehensive Inventory Database version v.2.01 S.2.01, Revision 0, INV-CID-06, dated March 10, 2012, Carlsbad, New Mexico.  Los Alamos National Laboratory  -  Carlsbad Operations (LANL - CO).
  [16] LANL 2013, Validation Documentation for the Comprehensive Inventory Database version v.2.02 S.2.02, Revision 0, INV-CID-07, dated December 19, 2013, Carlsbad, New Mexico.  Los Alamos National Laboratory  -  Carlsbad Operations (LANL - CO).

Summary and Conclusions

In 2006, SNL procured four Compaq ES47 machines to add to the computing resources of two Compaq ES40 and two Compaq ES45 machines.  In addition to the hardware upgrades, the operating system OpenVMS 7.3-1 has been upgraded to OpenVMS 8.2.  The 31 computer codes and 5 libraries and 3 databases that were used to support the 2009 CRA and 2009 PABC calculations were on the Compaq ES40, ES45, and ES47 machines with OpenVMS 8.2 (Table 3.1-1).  After completing the Agency's review, the Agency concludes that the versions of the computer codes indicated in Table 3.1-1 are approved for use in compliance calculations for the WIPP PA on the Compaq ES40, ES45, and ES47 machines with OpenVMS 8.2.

In 2013, SNL qualified six of the WIPP PA codes for use in the 2014 recertification application (2014 CRA) on the Compaq ES45 and ES47 computers using OpenVMS 8.2.  SNL also migrated the entire WIPP PA to the Solaris Blade platform with SunOS 5.11.  SNL/DOE established a new PA baseline (PABC09) entirely on the Solaris Blade Platform using SunOS 5.11 and performed integration tests to verify that the Solaris PA system generates adequate PA results. EPA concludes from its review that the WIPP PA codes are approved for use in the 2014 CRA on the Compaq cluster with Open VMS 8.2. The Agency also approves the WIPP PA codes, except for EQ3/6, migration to the Solaris Blade platform with SunOS 5.11 for future compliance calculations and the PABC09 baseline entirely on the Solaris platform.