GridFire is a C++ library designed to perform general nuclear network evolution using the Reaclib library. It is part of the larger SERiF project within the 4D-STAR collaboration. GridFire is primarily focused on modeling the most relevant burning stages for stellar evolution modeling. Currently, there is limited support for inverse reactions. Therefore, GridFire has a limited set of tools to evolves a fusing plasma in NSE; however, this is not the primary focus of the library and has therefor not had significant development. For those interested in modeling super nova, neutron star mergers, or other high-energy astrophysical phenomena, we strongly recomment using SkyNet.
Design Philosophy and Workflow: GridFire is architected to balance physical fidelity, computational efficiency, and extensibility when simulating complex nuclear reaction networks. Users begin by defining a composition, which is used to construct a full GraphEngine representation of the reaction network. To manage the inherent stiffness and multiscale nature of these networks, GridFire employs a layered view strategy: partitioning algorithms isolate fast and slow processes, adaptive culling removes negligible reactions at runtime, and implicit solvers stably integrate the remaining stiff system. This modular pipeline allows researchers to tailor accuracy versus performance trade-offs, reuse common engine components, and extend screening or partitioning models without modifying core integration routines.
Funding
GridFire is a part of the 4D-STAR collaboration.
4D-STAR is funded by European Research Council (ERC) under the Horizon Europe programme (Synergy Grant agreement No. 101071505: 4D-STAR) Work for this project is funded by the European Union. Views and opinions expressed are however those of the author(s) only and do not necessarily reflect those of the European Union or the European Research Council.
Build and Installation Instructions
Prerequisites
- C++ compiler supporting C++23 standard
- Meson build system (>= 1.5.0)
- Python 3.10 or newer
- Python packages:
meson-python>=0.15.0 - Boost libraries (>= 1.75.0) installed system-wide
Note: Boost is the only external library dependency; no additional libraries are required beyond a C++ compiler, Meson, Python, and Boost.
Note: Windows is not supported at this time and there are no plans to support it in the future. Windows users are encouraged to use WSL2 or a Linux VM.
Dependency Installation on Common Platforms
- Ubuntu/Debian: sudo apt-get update && \sudo apt-get install -y build-essential meson python3 python3-pip libboost-all-dev
- Fedora/CentOS/RHEL: sudo dnf install -y gcc-c++ meson python3 python3-pip boost-devel
- macOS (Homebrew): brew update && \brew install boost meson python
Building the C++ Library
Installing the Library
Python Bindings and Installation
The Python interface is provided via meson-python and pybind11. To install the Python package:
Developer Workflow
- Clone the repository and install dependencies listed in
pyproject.toml. - Configure and build with Meson: meson setup buildmeson compile -C build
- Run the unit tests: meson test -C build
- Iterate on code, rebuild, and rerun tests.
Code Architecture and Logical Flow
GridFire is organized into a series of composable modules, each responsible for a specific aspect of nuclear reaction network modeling. The core components include:
- Engine Module: Core interfaces and implementations (e.g.,
GraphEngine) that evaluate reaction network rate equations and energy generation. - Screening Module: Implements nuclear reaction screening corrections (
WeakScreening,BareScreening, etc.) affecting reaction rates. - Reaction Module: Parses and manages Reaclib reaction rate data, providing temperature- and density-dependent rate evaluations.
- Partition Module: Implements partition functions (e.g.,
GroundStatePartitionFunction,RauscherThielemannPartitionFunction) to weight reaction rates based on nuclear properties. - Solver Module: Defines numerical integration strategies (e.g.,
DirectNetworkSolver) for solving the stiff ODE systems arising from reaction networks. - Python Interface: Exposes almost all C++ functionality to Python, allowing users to define compositions, configure engines, and run simulations directly from Python scripts.
Generally a user will start by selecting a base engine (currently we only offer GraphEngine), which constructs the full reaction network graph from a given composition. The user can then apply various engine views to adapt the network topology, such as partitioning fast and slow reactions, adaptively culling low-flow pathways, or priming the network with specific species. Finally, a numerical solver is selected to integrate the network over time, producing updated abundances and diagnostics.
GraphEngine Configuration Options
GraphEngine exposes runtime configuration methods to tailor network construction and rate evaluations:
- Constructor Parameters:
BuildDepthType(Full/Reduced/Minimal): controls network build depth, trading startup time for network completeness.partition::PartitionFunction: custom functor for network partitioning based onZ,A, andT9.
- setPrecomputation(bool precompute):
- Enable/disable caching of reaction rates and stoichiometric data at initialization.
- Effect: Reduces per-step overhead; increases memory and setup time.
- setScreeningModel(ScreeningType type):
- Choose plasma screening (models:
BARE,WEAK). - Effect: Alters rate enhancement under dense/low-T conditions, impacting stiffness.
- Choose plasma screening (models:
- setUseReverseReactions(bool useReverse):
- Toggle inclusion of reverse (detailed balance) reactions.
- Effect: Improves equilibrium fidelity; increases network size and stiffness.
Available Partition Functions
| Function Name | Identifier | Description |
|---|---|---|
GroundStatePartitionFunction | "GroundState" | Weights using nuclear ground-state spin factors. |
RauscherThielemannPartitionFunction | "RauscherThielemann" | Interpolates normalized g-factors per Rauscher & Thielemann. |
These functions implement:
Engine Views
The GridFire engine supports multiple engine view strategies to adapt or restrict network topology. Each view implements a specific algorithm:
| View Name | Purpose | Algorithm / Reference | When to Use |
|---|---|---|---|
| AdaptiveEngineView | Dynamically culls low-flow species and reactions during runtime | Iterative flux thresholding to remove reactions below a flow threshold | Large networks to reduce computational cost |
| DefinedEngineView | Restricts the network to a user-specified subset of species and reactions | Static network masking based on user-provided species/reaction lists | Targeted pathway studies or code-to-code comparisons |
| MultiscalePartitioningEngineView | Partitions the network into fast and slow subsets based on reaction timescales | Network partitioning following Hix & Thielemann Silicon Burning I & II (DOI:10.1086/177016,10.1086/306692) | Stiff, multi-scale networks requiring tailored integration |
| NetworkPrimingEngineView | Primes the network with an initial species or set of species for ignition studies | Single-species injection with transient flow analysis | Investigations of ignition triggers or initial seed sensitivities |
These engine views implement the common Engine interface and may be composed in any order to build complex network pipelines. New view types can be added by deriving from the EngineView base class, and linked into the composition chain without modifying core engine code.
Python Extensibility: Through the Python bindings, users can subclass engine view classes directly in Python, override methods like evaluate or generateStoichiometryMatrix, and pass instances back into C++ solvers. This enables rapid prototyping of custom view strategies without touching C++ sources.
Numerical Solver Strategies
GridFire defines a flexible solver architecture through the networkfire::solver::NetworkSolverStrategy interface, enabling multiple ODE integration algorithms to be used interchangeably with any engine that implements the Engine or DynamicEngine contract.
- NetworkSolverStrategy<EngineT>: Abstract strategy templated on an engine type. Requires implementation of: which integrates the network over one timestep and returns updated abundances, temperature, density, and diagnostics.NetOut evaluate(const NetIn& netIn);
DirectNetworkSolver (Implicit Rosenbrock Method)
- Integrator: Implicit Rosenbrock4 scheme (order 4) via Boost.Odeint’s
rosenbrock4<double>, optimized for stiff reaction networks with adaptive step size control using configurable absolute and relative tolerances. - Jacobian Assembly: Employs the
JacobianFunctorto assemble the Jacobian matrix (∂f/∂Y) at each step, enabling stable implicit integration. - RHS Evaluation: Continues to use the
RHSManagerto compute and cache derivative evaluations and specific energy rates, minimizing redundant computations. - Linear Algebra: Utilizes Boost.uBLAS for state vectors and dense Jacobian matrices, with sparse access patterns supported via coordinate lists of nonzero entries.
- Error Control and Logging: Absolute and relative tolerance parameters (
absTol,relTol) are read from configuration; Quill logger captures integration diagnostics and step statistics.
Algorithmic Workflow in DirectNetworkSolver
- Initialization: Convert input temperature to T9 units, retrieve tolerances, and initialize state vector
Yfrom equilibrated composition. - Integrator Setup: Construct the controlled Rosenbrock4 stepper and bind
RHSManagerandJacobianFunctor. - Adaptive Integration Loop:
- Perform
integrate_adaptiveadvancing untiltMax, catching anyStaleEngineTriggerto repartition the network and update composition. - On each substep, observe states and log via
RHSManager::observe.
- Perform
- Finalization: Assemble final mass fractions, compute accumulated energy, and populate
NetOutwith updated composition and diagnostics.
Future Solver Implementations
- Operator Splitting Solvers: Strategies to decouple thermodynamics, screening, and reaction substeps for performance on stiff, multi-scale networks.
- GPU-Accelerated Solvers: Planned use of CUDA/OpenCL backends for large-scale network integration.
These strategies can be developed by inheriting from NetworkSolverStrategy and registering against the same engine types without modifying existing engine code.
Usage Examples
C++ Example: GraphEngine Initialization
C++ Example: Adaptive Network View
Python Example
More detailed python usage can be found here
Common Workflow Example
A representative workflow often composes multiple engine views to balance accuracy, stability, and performance when integrating stiff nuclear networks:
Workflow Components and Effects:
- GraphEngine constructs the full reaction network, capturing all species and reactions.
- MultiscalePartitioningEngineView segregates reactions by characteristic timescales (Hix & Thielemann), reducing the effective stiffness by treating fast processes separately.
- AdaptiveEngineView prunes low-flux species/reactions at runtime, decreasing dimensionality and improving computational efficiency.
- DirectNetworkSolver employs an implicit Rosenbrock method to stably integrate the remaining stiff system with adaptive step control.
This layered approach enhances stability for stiff networks while maintaining accuracy and performance.
Related Projects
GridFire integrates with and builds upon several key 4D-STAR libraries:
- fourdst: hub module managing versioning of
libcomposition,libconfig,liblogging, andlibconstants - libcomposition (docs): Composition management toolkit.
- libconfig: Configuration file parsing utilities.
- liblogging: Flexible logging framework.
- libconstants: Physical constants
