mini-ode
A minimalistic, multi-language library for solving Ordinary Differential Equations (ODEs). mini-ode is designed with a shared Rust core and a consistent interface for both Rust and Python users. It supports explicit, implicit, fixed step and adaptive step algorithms.
✨ Features
- Dual interface: call the same solvers from Rust or Python
- PyTorch-compatible: define the derivative function using PyTorch
- Multiple solver methods: includes explicit, implicit, and adaptive-step solvers
- Modular optimizers: implicit solvers allow flexible optimizer configuration
🧠 Supported Solvers
| Solver Class | Method | Suitable For | Implicit | Adaptive Step |
|---|---|---|---|---|
EulerMethodSolver |
Euler | Simple, fast, and educational use. | ❌ | ❌ |
RK4MethodSolver |
Runge-Kutta 4th Order (RK4) | General-purpose with fixed step size. | ❌ | ❌ |
ImplicitEulerMethodSolver |
Implicit Euler | Stiff or ill-conditioned problems. | ✅ | ❌ |
GLRK4MethodSolver |
Gauss-Legendre RK (Order 4) | High-accuracy, stiff problems. | ✅ | ❌ |
RKF45MethodSolver |
Runge-Kutta-Fehlberg 4(5) | Adaptive step size control. | ❌ | ✅ |
ROW1MethodSolver |
Rosenbrock-Wanner (Order 1) | Fast semi-implicit method for stiff systems. | semi | ❌ |
📦 Building the Library
mini-ode can be built against two different libtorch installations:
- a system-installed libtorch, or
- the libtorch bundled with a PyTorch installation.
It is important that the headers used at compile time and the shared libraries loaded at runtime come from the same installation.
Rust (system libtorch)
To build the Rust library against your system-installed libtorch:
cd mini-ode
cargo build --release
This is the recommended approach if you are developing a pure Rust application.
Python
To build the Python bindings using the PyTorch installation from your active Python environment:
cd mini-ode-python
LIBTORCH_USE_PYTORCH=1 maturin develop
This builds the Python bindings using maturin and installs the package locally. LIBTORCH_USE_PYTORCH=1 tells torch-sys to obtain the include directories and libraries from the currently active Python installation.
Building Rust code against a PyTorch installation
If you want to build the Rust version of mini-ode against the libtorch that ships with your Conda or virtual environment PyTorch installation, you must configure both the compiler and the runtime linker.
Using only
LIBTORCH_USE_PYTORCH=1 cargo build
is not enough.
While this causes torch-sys to compile against the headers from your Python installation, system will typically still load the system libtorch (for example /usr/lib/libtorch.so) at runtime. Simply activating a Conda environment does not guarantee that the Conda libtorch will be used. Mixing the compile-time headers from one PyTorch installation with the runtime libraries from another would lead to runtime failures.
Correct way to build and run:
export LIBTORCH_USE_PYTORCH=1
export LD_LIBRARY_PATH="$CONDA_PREFIX/lib/python*/site-packages/torch/lib:$LD_LIBRARY_PATH"
cargo build
cargo run
This ensures that both the compiler and the runtime use the same libtorch installation.
Tip
If your Rust code is loaded as a Python extension, importing
torchbefore importing your extension ensures that Python has already loaded the correct libtorch libraries.
🐍 Python Usage Overview
To use mini-ode from Python:
- Define the derivative function
f(x: torch.Tensor, y: torch.Tensor) -> torch.Tensor:xis a scalar tensor (rank 0, shape()).yis a 1D tensor (rank 1, shape(n,)wherenis the dimension of the state vector).- The function must return a 1D tensor of the same shape as
y(i.e.,(n,)).
- Trace the function using
torch.jit.traceto convert it to TorchScript. Provide example inputs matching the shapes (e.g.,torch.tensor(0.)forxandtorch.tensor([0.] * n)fory). - Create a solver instance, configuring parameters like step size or optimizer as needed.
- Call
solver.solve(traced_f, x_span, y0):x_span: A tuple(start, end)for the integration interval.y0: Initial state as a 1D tensor (shape(n,)).- Returns:
(xs, ys)wherexsis a 1D tensor of x-values (shape(num_points,)), andysis a 2D tensor of y-values (shape(num_points, n)).- For fixed-step solvers,
xsis evenly spaced (e.g., viatorch.linspace). - For adaptive-step solvers,
xshas a variable number of points based on error control.
- For fixed-step solvers,
Example usage flow (not full code):
import torch
import mini_ode
# 1. Define derivative function using PyTorch
def f(x: torch.Tensor, y: torch.Tensor):
return y.flip(0) - torch.tensor([0, 1]) * (y.flip(0) ** 3)
# 2. Trace the function to TorchScript
traced_f = torch.jit.trace(f, (torch.tensor(0.), torch.tensor([0., 0.])))
# 3. Create a solver instance
solver = mini_ode.RK4MethodSolver(step=0.01)
# 4. Solve the ODE
xs, ys = solver.solve(traced_f, (0., 5.), torch.tensor([1.0, 0.0]))
🔧 Using Optimizers (Implicit Solvers Only)
Some solvers like GLRK4MethodSolver or ImplicitEulerMethodSolver require an optimizer for nonlinear system solving:
optimizer = mini_ode.optimizers.CG(
max_steps=5,
gtol=1e-8,
)
solver = mini_ode.GLRK4MethodSolver(step=0.2, optimizer=optimizer)
🦀 Rust Usage Overview
In Rust, solvers use the same logic as in Python - but you pass in a tch::CModule representing the TorchScripted derivative function.
Example 1: Load a TorchScript model from file
This approach uses a model traced in Python (e.g., with torch.jit.trace) and saved to disk.
use mini_ode::Solver;
use tch::{Tensor, CModule};
fn main() -> anyhow::Result<()> {
let solver = Solver::Euler { step: 0.01 };
let model = CModule::load("my_traced_function.pt")?;
let x_span = (0.0, 2.0);
let y0 = Tensor::from_slice(&[1.0f64, 0.0]);
let (xs, ys) = solver.solve(model, x_span, y0)?;
println!("{:?}", xs);
Ok(())
}
Example 2: Trace the derivative function directly in Rust
You can also define and trace the derivative function in Rust using CModule::create_by_tracing.
Here we trace the undamped Duffing oscillator y0'' = y0 - y0^3, written as a first-order
system y0' = y1, y1' = y0 - y0^3:
use mini_ode::Solver;
use tch::{Tensor, CModule};
fn main() -> anyhow::Result<()> {
// Initial value for tracing
let y0 = Tensor::from_slice(&[1f64, 0f64]);
// Define the derivative function closure
let mut closure = |inputs: &[Tensor]| {
let _x = &inputs[0];
let y = &inputs[1];
let y0 = y.get(0);
let y1 = y.get(1);
let dy0 = y1;
let dy1 = &y0 - &y0.pow_tensor_scalar(3.0);
vec![Tensor::stack(&[dy0, dy1], 0)]
};
// Trace the model directly in Rust
let model = CModule::create_by_tracing(
"ode_fn",
"forward",
&[Tensor::from(0.0f64), y0.shallow_clone()],
&mut closure,
)?;
// Use an adaptive solver, for example
let solver = Solver::RKF45 {
rtol: 0.00001,
atol: 0.00001,
min_step: 1e-9,
safety_factor: 0.9
};
let x_span = Tensor::from_slice(&[0.0f64, 5.0]);
let (xs, ys) = solver.solve(model, x_span, y0)?;
println!("Final state: {:?}", ys);
Ok(())
}
📁 Project Structure
mini-ode/ # Core Rust implementation of solvers
mini-ode-python/ # Python bindings using PyO3 + maturin
example.ipynb # Jupyter notebook demonstrating usage
📄 License
This project is licensed under the GPL-2.0 License.
👤 Author
Antoni Michał Przybylik
📧 antoni@taon.io
🔗 https://github.com/antoniprzybylik
Metadata
Release files for mini-ode 0.1.6
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| mini_ode-0.1.6-cp313-abi3-manylinux_2_39_x86_64.whl | CPython 3.13 | abi3 | Linux glibc 2.39+ x86-64 | Details for mini_ode-0.1.6-cp313-abi3-manylinux_2_39_x86_64.whl |
Release files / mini_ode-0.1.6-cp313-abi3-manylinux_2_39_x86_64.whl
| Download URL | mini_ode-0.1.6-cp313-abi3-manylinux_2_39_x86_64.whl |
|---|---|
| Size | 582.1 kB |
| Tags | CPython 3.13 Linux glibc 2.39+ x86-64 abi3 |
|
SHA-256 checksum How to use checksums |
7afb6baa1235a65289c6dea14c5d170fd05ff8042713592b02dcca8d1bf54e1c
|
|
BLAKE2b-256 checksum How to use checksums |
c510c650f9e5d96da9e1cdc2470b992856b607c7dd13f33372690a06072c5ef1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.14.2
|
Security for mini-ode 0.1.6
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.