Skip to content
Permalink

Comparing changes

Choose two branches to see what’s changed or to start a new pull request. If you need to, you can also or learn more about diff comparisons.

Open a pull request

Create a new pull request by comparing changes across two branches. If you need to, you can also . Learn more about diff comparisons here.
base repository: ml4t/specs
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: v0.1.3
Choose a base ref
...
head repository: ml4t/specs
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: v0.1.4
Choose a head ref
  • 2 commits
  • 3 files changed
  • 1 contributor

Commits on Sep 3, 2026

  1. feat: FeedSpec carries vwap_col so a feed can declare a volume-weight…

    …ed price (#13)
    
    * feat: FeedSpec carries vwap_col so a feed can declare a volume-weighted price
    
    ExecutionPrice.VWAP has existed in ml4t-backtest since the enum was written and
    has never had a column to read: there is no vwap_col anywhere in the feed
    contract, so the broker resolved it to the close and, under next_bar execution,
    to the open. Neither substitution was reported.
    
    vwap_col defaults to None rather than to a guessed column name. Open, high, low,
    close and volume all have conventional names worth defaulting to; VWAP does not,
    and a consumer asking for it is asking for a price no other column approximates.
    The close is not a worse VWAP, it is a different quantity, so a feed that does
    not carry one must say so and let the consumer refuse.
    
    Refs ml4t/agent-workspace#1017.
    
    * fix: preserve VWAP columns in market data specs
    stefan-jansen authored Sep 3, 2026
    Configuration menu
    Copy the full SHA
    b17105b View commit details
    Browse the repository at this point in the history
  2. Configuration menu
    Copy the full SHA
    b309466 View commit details
    Browse the repository at this point in the history
Loading