# Agent 154: DbnSequenceLoader Dtype Fix

## Mission
Add F64 conversion to batch data loader tensor creation to ensure consistent dtype across all ML models.

## Resource Constraint
**CODE CHANGES ONLY - NO COMPILATION**

## Files Modified

### 1. `/home/jgrusewski/Work/foxhunt/ml/src/data_loaders/dbn_sequence_loader.rs`

**Changes:**
- Added `DType` to candle_core imports (line 32)
- Added `.to_dtype(DType::F64)?` to input tensor creation (lines 601-602)
- Added `.to_dtype(DType::F64)?` to target tensor creation (lines 608-609)

**Before:**
```rust
use candle_core::{Device, Tensor};

// ...

let input = Tensor::from_slice(
    &features,
    (1, self.seq_len, self.d_model),
    &self.device
)?;

let target_tensor = Tensor::from_slice(
    &target,
    (1, 1, self.d_model),
    &self.device
)?;
```

**After:**
```rust
use candle_core::{DType, Device, Tensor};

// ...

let input = Tensor::from_slice(
    &features,
    (1, self.seq_len, self.d_model),
    &self.device
)?
.to_dtype(DType::F64)?;

let target_tensor = Tensor::from_slice(
    &target,
    (1, 1, self.d_model),
    &self.device
)?
.to_dtype(DType::F64)?;
```

### 2. `/home/jgrusewski/Work/foxhunt/ml/src/data_loaders/streaming_dbn_loader.rs`

**Status:** ✅ Already fixed (linter/previous agent applied the changes)

The streaming loader already has:
- `DType` imported in candle_core imports (line 42)
- `.to_dtype(DType::F64)?` applied to both input and target tensors (lines 488-491)

## Technical Details

### Why F64?
The ML training pipeline uses F64 (64-bit floating point) for all model computations to ensure:
- Consistent precision across all models (MAMBA-2, DQN, PPO, TFT)
- Proper gradient computation during backpropagation
- Compatibility with downstream training operations

### Impact
This fix ensures that tensors created from f32 feature vectors (extracted from market data) are properly converted to F64 before being passed to the training pipeline. Without this conversion:
- Type mismatch errors occur during model forward passes
- Training fails with dtype incompatibility errors
- Gradient computation fails

### Location Context
Both loaders create sequences from DBN (Databento) market data:
- **dbn_sequence_loader.rs**: Batch loader (loads all data at once)
  - Line 597-602: Input tensor creation in `create_sequences()` method
  - Line 604-609: Target tensor creation in `create_sequences()` method

- **streaming_dbn_loader.rs**: Streaming loader (memory-efficient, on-demand loading)
  - Line 488-489: Input tensor creation in `create_sequence()` method
  - Line 490-491: Target tensor creation in `create_sequence()` method

## Verification

### Files to Verify
1. `/home/jgrusewski/Work/foxhunt/ml/src/data_loaders/dbn_sequence_loader.rs`
   - Check line 32: `use candle_core::{DType, Device, Tensor};`
   - Check lines 601-602: `.to_dtype(DType::F64)?` after input tensor creation
   - Check lines 608-609: `.to_dtype(DType::F64)?` after target tensor creation

2. `/home/jgrusewski/Work/foxhunt/ml/src/data_loaders/streaming_dbn_loader.rs`
   - Verify line 42: `use candle_core::{DType, Device, Tensor};`
   - Verify lines 488-491: Both tensors have `.to_dtype(DType::F64)?`

### Testing
To verify the fix works correctly:
```bash
# Run data loader tests
cargo test -p ml --lib data_loaders

# Run full ML integration tests
cargo test -p ml --test e2e_ensemble_integration
```

## Status
✅ **COMPLETE** - F64 dtype conversion added to both DBN sequence loaders

## Time Spent
5 minutes (as per mission constraint)

## Notes
- The streaming_dbn_loader.rs was already fixed (likely by a linter or previous agent)
- Only dbn_sequence_loader.rs required manual modification
- Both loaders now have consistent F64 dtype handling
- No compilation was performed as per mission constraint