Version 1.0.0 (09/30/2024)
New Features
Code of Account Output Ordering
ACCERT now supports new options for organizing cost outputs. This feature provides flexibility depending on the project’s cost accounting framework, making it easier to generate outputs in the desired format. The output format can be selected from two different Code of Accounts (COA) frameworks:
- GNCOA (Generalized Nuclear Code of Accounts): This format is used for advanced nuclear reactor systems, intended to be forward-looking (i.e., applicable to cost estimates of future reactors
- EEDB COA (Energy Economic Database Cost Code of Accounts): This traditional format organizes costs based on the Energy Economic Database COA structure, commonly used in existing nuclear technologies.
Fusion Model Integration
ACCERT now includes support for fusion reactor models, allowing users to estimate and analyze costs for fusion-based nuclear reactors. The fusion algorithms have been moved into a dedicated Python file (FusionFunc.py), which enhances scalability and simplifies updates, as fusion cost elements differ from those used in other reactor models.
New Indirect Costs Tables (Beyond the 20s)
ACCERT now supports the calculation of indirect costs, extending beyond traditional direct cost estimations. This feature provides more comprehensive cost modeling for nuclear reactor projects, helping users estimate all relevant costs.
Improved Scalability and Maintainability
Several redundant tables and columns have been removed from the ACCERT database to simplify its structure. This results in a cleaner, more efficient database. Additionally, unnecessary stored procedures in MySQL database have been eliminated, further improving system performance.
Refactored Algorithm Storage
Fusion algorithms, previously stored in the database, have been moved to Python scripts for better maintainability and clarity. This separation makes updates easier, as users can modify fusion algorithms without needing to directly alter the database.
Enhanced Documentation
The documentation for ACCERT has been updated to reflect the new features. It now includes detailed instructions on how to use the new functionality, along with examples and explanations to help users understand how to leverage the new capabilities. All main functions of ACCERT and the helper functions have been documented in the online user guide as well. New reference tables have been added to the table references pages in the user guide.
Bug Fixes
Cross-Platform Compatibility
Fixed issues with unit tests that passed on macOS but failed on Linux. This ensures better consistency and functionality across different platforms.
Performance Enhancements
Stored Procedure Usage
ACCERT now exclusively uses stored procedures for database interactions instead of the execute method, leading to improved performance and more consistent operations.
Known Gaps
The Generalized Nuclear Code of Accounts in ACCERT now needs to specify detailed algorithms.
NE-COST might have the potential to be set as a submodule of ACCERT.