Skip to main content

Validation

HyperionX Validator runs a compiled strategy across one or more instruments and data-series configurations. Use it to compare components, inspect portfolio totals, reopen saved presets, export a summary, and send completed results to performance analysis.

Validation is different from optimization. Optimization selects parameter combinations from historical data. Validator tests the strategy and parameters you assign.

Candidate installer validation pending

The active release-candidate source includes product-owned research defaults and installer-manifest entries intended to correct the earlier clean-install gap. The exact clean, signed installer has not yet passed installation and Validator smoke validation. Until it does, treat historical strategy validation as unavailable on a fresh public installation. Do not import untrusted modules as a workaround. See Install, Update, And Uninstall.

Create A Validator Run

  1. Open Validator.
  2. Select Add instrument for a single configuration, or Add test set to load a saved group.
  3. Choose the connection, instrument, data series, bar type, interval, and date range for each item.
  4. Load historical candles for every item you intend to run.
  5. Select a compiled strategy.
  6. Assign the strategy to each item, or use Apply all when the same strategy and preset should be shared.
  7. Review strategy parameters, commission, leverage, historical fill model, and continuous-futures merge behavior where applicable.
  8. Select Run.

Run is enabled only when the required strategy and historical candles are available for the relevant items. Use Cancel to stop an active run.

Work With Test Sets And Presets

Validator can:

  • Add individual instruments.
  • Load and save test sets.
  • Load and save strategy presets.
  • Apply one strategy configuration to multiple items.
  • Preserve bar type and custom-bar settings in a preset.
  • Preserve backtest leverage, fill model, and continuous-futures merge settings.
  • Re-run changed configurations.

Give each test set one clear purpose. For example, compare one futures strategy across related contracts or one crypto strategy across a defined group of markets. Combining unrelated instruments can make an aggregate curve look smoother without explaining why.

Review Results

Start with the aggregate result, then inspect every component:

  • Net profit and max drawdown.
  • Trade count and average trade.
  • Profit factor.
  • Commission.
  • Long and short contribution.
  • Instrument contribution.
  • Ambiguous historical fills.
  • Performance concentration in one market or date range.

Completed Validator results are saved to the performance-results store. Validator also provides a summary export and a Find Improvements research action.

Find Improvements is an analysis aid. It does not replace out-of-sample testing, playback, simulation, or a review of the underlying trades.

Historical Assumptions

Validator uses candle-based historical fill modeling. See Backtesting for the two current fill models and their ambiguity behavior.

Ordinary Validator and Optimizer runs do not expose a configurable slippage model in the current release. Commission is modeled separately when a commission module is available. Record spread, slippage, liquidity, and market-impact limitations outside the saved result.

Strategy Readiness Checklist

Before assigning a strategy to Validator:

  1. Compile it in Code Lab with no errors.
  2. Confirm it uses the HyperionX.Custom.Strategies namespace and inherits from Strategy.
  3. Keep managed order mode enabled for normal strategies.
  4. Use EnterLong(...), EnterShort(...), ExitLong(...), or ExitShort(...) with managed stop-loss and profit-target helpers where appropriate.
  5. If the strategy deliberately uses direct SubmitOrder(...), verify order action, order type, prices, OCO values, signal names, working-order tracking, cancellation, rejection, partial-fill, and recovery paths.
  6. Guard against duplicate entries.
  7. Verify quantity, exits, stops, targets, commission, leverage, and margin assumptions.

After historical validation, run the strategy in playback or simulation with an explicitly selected LocalPaper account before considering live routing. Playback does not select it automatically; the current release-candidate build rejects external-account order mutations while Playback is active.

Indicator And Workspace Checks

Validator is a strategy-research tool. Use direct application checks for other areas:

  • Load an indicator on a chart with enough bars and watch Logs for runtime errors.
  • Save and reopen a workspace to verify charts, instruments, timeframes, indicators, and window layout.
  • Confirm a connection can load history, receive live updates, and reconnect.
  • Verify manual orders only in the intended paper/test account before live use.

AI-generated scripts require the same compilation, historical review, playback, and simulation checks as hand-written scripts.

Saved-Result Limitation

The results database preserves useful identifying information, headline metrics, and trade artifacts, but it does not currently preserve every setting required to reproduce a run. Keep strategy parameters, commission configuration, starting capital, application version, and research notes separately.

See Performance Database.