Version History

Abbreviated Release Notes

Version 2.5

Build Date: 2003-Feb-03

Revisions were implemented to make update RT3D with MT3DMS bug fixes through MT3DMS 4.00.

  1. Replacement of the MIC subroutine in "gcg30d.f" with that from MT3DMS 4.00 to address the out-of-bounds error that occurred when using the implicit solver with the modified incomplete Cholesky preconditioner (fix noted for MT3DMS 3.00.B).
  2. Replacement of the CFACE subroutine in "adv30d.f" with that from MT3DMS 4.00 to address the TVD bug (fix noted for MT3DMS 4.00).
  3. In "fmi30d.f," fixed the comparison of a variable to both upper and lowercase "Y" characters.
  4. In "btnrtv25.f," altered an ELSEIF comparison for TSMULT to use a tolerance rather than be a direct comparison of two floating point numbers.
  5. A bug in calculating maximum time increment that meets stability criterion for solving the explicit finite-difference dispersion equation was fixed in MT3DMS (MT3DMS 3.50.A) and RT3D has been updated accordingly.
  6. In the generalized conjugate gradient solver package, a user-defined value was (inappropriately) used to evaluate whether it is necessary to proceed with the iterative solution. Now the criterion is hard coded as 1.0e-6.
  7. Made the evaluation of THKMIN consistent with MT3DMS 4.00. The maximum value for THKMIN in RT3D (10%) is higher than MT3DMS (5%).

Build Date: 2002-Oct 18

  • Revisions were made to btnrtv25.f and ssmrtv25.f to fix 3 errors (incorrect source decay functionality for FD and TVD advection solvers, reading the decay constants for a single species simulation incorrectly, and invalid initialization of Typess(-2) [a cosmetic issue]).

Build Date: 2002-Jan 17

Version 2.0 (2000-Jun 04)

  • This version had limited distribution as a part of a GMS release.

Version 1.0 (1998-Nov 02)

  • Initial version.

Synopsis of the RT3D Development History

RT3D was originally developed based on an interest in modelling bioremediation reactions for accelerated in-situ bioremediation and monitored natural attenuation scenarios. Dr. Clement (lead author of RT3D) and Dr. Chunmiao Zheng (lead author of MT3D) collaborated in a back-and-forth fashion such that the first publicly available version of RT3D was built off the advection, dispersion, and source/sink framework of MT3D. The key features of RT3D were the multi-species and advanced reaction capabilities. Subsequently, MT3DMS was released by Dr. Zheng, in part, to parallel the multi-species features of RT3D. While some third parties have described RT3D as an "add-on" to MT3D, the RT3D development team prefers to describe RT3D as a sister code to MT3DMS. RT3D and MT3DMS share core functionality, but they differ significantly in their reaction capabilities; each is a standalone solute transport software.

Since RT3D and MT3DMS have been available to the public, others have used these codes as a starting point to add supplemental functionality, resulting in a number of solute transport codes in the MT3DMS family. Daughter codes have been developed to include variable-density flow, geochemical reactions, biological reactions, and time-varying porosity. The modeler should understand the diversity of features and limitations available in the MT3DMS family of solute transport codes and, as with consideration of analytical versus numerical models, select the simplest tool that meets the needs of the site under consideration.

Development and the initial release of RT3D were done by the RT3D development team at PNNL. Dr. Clement has since taken a post at Auburn University as a professor in the Civil Engineering Department, expanding the geographic diversity of the RT3D development team.

Funding support for the development of RT3D has come primarily from the U.S. Department of Energy under multiple programs (including the Remediation Technologies Development Forum and the Monitored Natural Attenuation/Enhanced Attenuation for Chlorinated Solvents Technology Alternative Project).

Export Control Categorization

The RT3D software has been classified as export control classification number EAR99 by the U.S. Department of Commerce, Bureau of Industry and Security. This software may be exported without a license (i.e., "NLR") provided that the recipient meets all regulations governing export. To meet the export administration regulations, no recipient may 1) be a national of or located within designated (i.e., embargoed/terrorist) countries, 2) appear on the Denied Persons List, 3) appear on the Unverified List, 4) appear on the Entity List, 5) appear on the Specially Designated Nationals List, or 6) appear on the Debarred List. All lists are published by the Bureau of Industry and Security and can be accessed at http://www.bis.doc.gov/complianceandenforcement/liststocheck.htm.

This software is exported from the U.S. in accordance with the Export Administration Regulations. Diversion contrary to U.S. law is prohibited; that is, the software may not be further distributed to third or subsequent parties who are ineligible to receive exports based on the Export Administration Regulations and the associated Bureau of Industry and Security lists.