Roadmap

This is the official planning page for the ARMI framework.

v0.5.0

Success! Released on 2024-12-14.

v0.5.1

March, 2025

This will be a quick turn-around release for internal things, like software qualification.

Must Have

• Open-Source ARMI Requirements
• Add CI for ARMI System Tests
• Move Global Nuclides out of the global scope (5-10 days)

Should Have

• Finally change Database3 to Database
• Reduce the trickiness of ArmiObject.setNumberDensities() by moving it to Component (1-3 days)
• Update docs to Python 3.13 (1-3 days)

Nice-to Have

• Remove the Operator from the Reactor (1-3 days)

v0.6.0

2025, October-ish timeline

Must Have

• Remove references to geom files in the code (2-4 days)
• numMoves is different between cases depending on numProcessors
• Pin pitch in HexBlocks can be inconsistent with grid definitions
• TBD

Should Have

• AM242 specification issue (1-3 days)
• Database cannot recall user materials
• TBD

Nice-to Have

• Organize the armi/tests/ directory and armi/testing/ module
• TBD

v1.0.0

No firm timeline.

This is the big one. This release is meant to be the line in the sand where ARMI's API is made stable. And ARMI will be feature-rich without including the science or engineering calculations within ARMI.

Features

• Allow ARMI DBs to be opened without the App that created them
• Composites should be able to have children that are Composites
• Find and eliminate all hex assembly assumptions
• Materials redesign
• Meaningful assem Sort Order
• Matrix input on BP

Architecture

• Move Global Nuclides out of the global scope (1-10 days)
• Finish removing large and important things from the global scope
• Remove XML geom files completely
• Redesign of migration scripts
• De-homogenization of Number Densities
• Defining Custom material properties in the blueprints

Quality Assurance

• Remove ARMI's unit tests from the API, and create armi.testing
• Choose a type system: type hints, or NumPy docs or other
• Remove use of NumPy defunct jagged arrays and thus support Python 3.12
• Finally change Database3 to Database

User Interface

• Improved user experience with preparing input files and analyzing output files
  • Possibly along the lines of NEAMS Workbench or something web-based

Plugin Ecosystem

• Finish the ARMI OpenMC plugin
• ARMI input model for the BEAVRS benchmark
• ARMI plugin for INL's Deep Lynx