Files
foxhunt/ml
jgrusewski 7ba64b2ef7 feat(ml): MAMBA-2 device fix + PPO batch size optimization + CUDA 12.9 migration
Critical Fixes:
- MAMBA-2 device mismatch fixed (3 methods: train_batch, validate, calculate_accuracy)
- PPO batch size increased 64→512 (fixes explained variance -23.56→+0.58)
- CUDA 12.9 migration complete (Runpod driver 550 compatibility)

MAMBA-2 Device Fix (ml/src/mamba/mod.rs):
- Added .to_device(&self.device)? calls in train_batch (L1216-1219)
- Added device transfers in validate (L1829-1831)
- Added device transfers in calculate_accuracy (L1856-1858)
- Training validated: 2 epochs, 40.35s, 171,900 params

PPO Optimization (ml/src/ppo/ppo.rs, ml/examples/train_ppo.rs):
- Changed default mini_batch_size from 64 to 512
- Gradient variance reduction: 88%
- Explained variance improvement: -23.56 → +0.58
- Training time: 33.0s (10 epochs), stable convergence
- All 59 unit tests pass

CUDA 12.9 Migration:
- Dockerfile.runpod updated to CUDA 12.9.1 + cuDNN 9
- All 4 binaries rebuilt with CUDA 12.9 (75MB total)
- Uploaded to Runpod S3: s3://se3zdnb5o4/binaries/
- Compatible with Runpod driver 550 (CUDA 13.0 requires driver 580+)

Training Validations:
- DQN:  15s training
- MAMBA-2:  40.35s training (device fix validated)
- PPO:  33.0s training (batch size fix validated)
- TFT: ⚠️ Memory leak investigation ongoing (+1216MB growth)

Test Results:
- ML tests: 1,337/1,337 pass (100%)
- Workspace tests: 3,196/3,196 pass (100%)
- PPO unit tests: 59/59 pass (100%)

🤖 Generated with Claude Code
Co-Authored-By: Claude <noreply@anthropic.com>
2025-10-26 11:14:33 +01:00
..

ml Crate

The ml crate provides the core machine learning capabilities for the Foxhunt High-Frequency Trading (HFT) System. It encompasses a suite of advanced models for sequence prediction, reinforcement learning, and time series analysis, optimized for low-latency inference and robust model management within a high-frequency trading environment.

Features

  • Advanced Model Suite: Implementation of cutting-edge ML models tailored for HFT.
  • Low-Latency Inference: Highly optimized inference engine designed for real-time market data processing.
  • GPU Acceleration: Leverages CUDA/cuDNN for high-performance, GPU-accelerated model inference.
  • Dynamic Model Management: Supports hot-swapping and versioning of models for seamless updates.
  • Cloud-Native Storage: S3-based model storage and caching for reliable and scalable deployment.
  • Experimentation & Monitoring: Built-in support for A/B testing and performance monitoring of deployed models.

Models Implemented

This crate includes specialized implementations of various machine learning models, each optimized for specific HFT challenges:

  • MAMBA-2 State Space Models: Efficient sequence prediction, crucial for forecasting market movements, order flow, or short-term price trajectories in dynamic HFT scenarios.
  • Deep Q-Learning (DQN): A reinforcement learning algorithm for discovering and executing optimal trading strategies, learning directly from market rewards and penalties.
  • Proximal Policy Optimization (PPO) with GAE: A robust policy gradient reinforcement learning method, often employed for more complex, continuous action spaces in trading agents, offering stable and efficient learning.
  • Temporal Fusion Transformer (TFT): An advanced transformer-based architecture for multivariate time series forecasting, adept at handling complex temporal dependencies and integrating exogenous variables for precise price or volume prediction.
  • Liquid Networks: Biologically inspired neural networks offering high adaptability and robustness to changing data distributions, making them suitable for the non-stationary and volatile nature of financial markets.
  • Transformer-based Order Book (TLOB) Analysis: Utilizes transformer architectures to process granular, high-dimensional order book data, identifying intricate patterns and predicting short-term price movements, liquidity shifts, or order imbalances.

Architecture

The ml crate is designed with the following key architectural components to ensure performance, reliability, and maintainability:

  • Inference Bridge: A dedicated, low-latency communication channel facilitating seamless prediction delivery from ML models to the core trading_engine.
  • Model Registry: A centralized service for managing, versioning, and deploying ML models. It supports hot-swapping, allowing new model versions to be deployed without service interruption.
  • Performance Monitoring & Distillation: Real-time tracking of model efficacy, latency, and resource utilization. Includes mechanisms for model distillation to create smaller, faster models suitable for extreme low-latency environments.
  • Ensemble Methods: Integrates capabilities for combining predictions from multiple models, often incorporating confidence scoring, to enhance overall prediction robustness and accuracy.

Usage

To use the ml crate, you'll typically interact with the ModelRegistry to load models and then use the InferenceEngine trait to make predictions.

use ml::{InferenceEngine, ModelRegistry};

#[tokio::main]
async fn main() -> Result<(), Box<dyn std::error::Error>> {
    // Initialize your application configuration
    let config = /* Your application configuration object */;

    // Instantiate the ModelRegistry
    let registry = ModelRegistry::new(config).await?;

    // Load a specific model by its identifier and version
    let model = registry.load_model("mamba2-v1.2.3").await?;

    // Prepare the current market state or features for inference
    let market_state = /* Your current market state object */;

    // Run inference using the loaded model
    let prediction = model.predict(&market_state).await?;

    println!("Inference result: {:?}", prediction);

    Ok(())
}

Testing

To run the tests for the ml crate, use the standard Cargo test command:

cargo test --package ml

Documentation

Comprehensive API documentation for the ml crate can be found on docs.rs/ml.