skip to main content
OSTI.GOV title logo U.S. Department of Energy
Office of Scientific and Technical Information

Title: Framework for Research in Nuclear Science and Engineering v. 0.3.0

Abstract

FRENSIE (the Framework for Research in Nuclear Science and Engineering) is a Monte Carlo code for solving linear particle transport problems with neutron, photon, and electron particles.

Authors:
 [1]
  1. Sandia National Laboratories
Publication Date:
Research Org.:
Sandia National Lab. (SNL-NM), Albuquerque, NM (United States)
Sponsoring Org.:
USDOE
OSTI Identifier:
1331006
Report Number(s):
FRENSIE; 005014MLTPL00
SCR #2123
DOE Contract Number:
AC04-94AL85000
Resource Type:
Software
Software Revision:
00
Software Package Number:
005014
Software CPU:
MLTPL
Open Source:
Yes
Source Code Available:
Yes
Other Software Info:
A previous version of FRENSIE was license under BSD-3 and put under copyright by the FRENSIE development team at UW-Madison. It was released to Sandia with the hope that the enhancements made at Sandia would eventually be incorporated back into the main code.
Related Software:
MOAB, CGM (optional), Cubit (optional), Trilinos, Boost
Country of Publication:
United States

Citation Formats

Kersting, Luke J. Framework for Research in Nuclear Science and Engineering v. 0.3.0. Computer software. https://www.osti.gov//servlets/purl/1331006. Vers. 00. USDOE. 8 Aug. 2016. Web.
Kersting, Luke J. (2016, August 8). Framework for Research in Nuclear Science and Engineering v. 0.3.0 (Version 00) [Computer software]. https://www.osti.gov//servlets/purl/1331006.
Kersting, Luke J. Framework for Research in Nuclear Science and Engineering v. 0.3.0. Computer software. Version 00. August 8, 2016. https://www.osti.gov//servlets/purl/1331006.
@misc{osti_1331006,
title = {Framework for Research in Nuclear Science and Engineering v. 0.3.0, Version 00},
author = {Kersting, Luke J},
abstractNote = {FRENSIE (the Framework for Research in Nuclear Science and Engineering) is a Monte Carlo code for solving linear particle transport problems with neutron, photon, and electron particles.},
url = {https://www.osti.gov//servlets/purl/1331006},
doi = {},
year = 2016,
month = 8,
note =
}

Software:
To order this software, request consultation services, or receive further information, please fill out the following request.

Save / Share:
  • Software lifecycles are becoming an increasingly important issue for computational science and engineering (CSE) software. The process by which a piece of CSE software begins life as a set of research requirements and then matures into a trusted high-quality capability is both commonplace and extremely challenging. Although an implicit lifecycle is obviously being used in any effort, the challenges of this process - respecting the competing needs of research vs. production - cannot be overstated. Here we describe a proposal for a well-defined software lifecycle process based on modern Lean/Agile software engineering principles. What we propose is appropriate for manymore » CSE software projects that are initially heavily focused on research but also are expected to eventually produce usable high-quality capabilities. The model is related to TriBITS, a build, integration and testing system, which serves as a strong foundation for this lifecycle model, and aspects of this lifecycle model are ingrained in the TriBITS system. Here, we advocate three to four phases or maturity levels that address the appropriate handling of many issues associated with the transition from research to production software. The goals of this lifecycle model are to better communicate maturity levels with customers and to help to identify and promote Software Engineering (SE) practices that will help to improve productivity and produce better software. An important collection of software in this domain is Trilinos, which is used as the motivation and the initial target for this lifecycle model. However, many other related and similar CSE (and non-CSE) software projects can also make good use of this lifecycle model, especially those that use the TriBITS system. Indeed this lifecycle process, if followed, will enable large-scale sustainable integration of many complex CSE software efforts across several institutions.« less
  • Software lifecycles are becoming an increasingly important issue for computational science & engineering (CSE) software. The process by which a piece of CSE software begins life as a set of research requirements and then matures into a trusted high-quality capability is both commonplace and extremely challenging. Although an implicit lifecycle is obviously being used in any effort, the challenges of this process--respecting the competing needs of research vs. production--cannot be overstated. Here we describe a proposal for a well-defined software lifecycle process based on modern Lean/Agile software engineering principles. What we propose is appropriate for many CSE software projects thatmore » are initially heavily focused on research but also are expected to eventually produce usable high-quality capabilities. The model is related to TriBITS, a build, integration and testing system, which serves as a strong foundation for this lifecycle model, and aspects of this lifecycle model are ingrained in the TriBITS system. Indeed this lifecycle process, if followed, will enable large-scale sustainable integration of many complex CSE software efforts across several institutions.« less
  • No abstract prepared.

To initiate an order for this software, request consultation services, or receive further information, fill out the request form below. You may also reach us by email at: .

OSTI staff will begin to process an order for scientific and technical software once the payment and signed site license agreement are received. If the forms are not in order, OSTI will contact you. No further action will be taken until all required information and/or payment is received. Orders are usually processed within three to five business days.

Software Request

(required)
(required)
(required)
(required)
(required)
(required)
(required)
(required)