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.

Verify the installed research components

Product-owned research defaults and the Python runtime are recorded in earlier signed releases; the signed 1.1.25 release record adds the Validator features described below. The stable feed still advertised 1.1.23 on September 29, 2026, so use the documentation version map and Help > About to identify the installed contract. Verify the installer signature and first-launch module discovery. If required modules are missing, collect diagnostics and contact support; 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. On builds containing the 1.1.25 Validator changes, review Slippage (ticks) and session-close settings as well.
  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.

Development-source multiple-timeframe cases

The original 1.1.12 workflow used one data-series configuration per Validator item. Reviewed 1.1.27 development source supports multiple timeframe cases within an item and preserves them in the unified strategy-workspace snapshot. Source presence alone does not establish availability in the stable 1.1.23 package or the signed 1.1.25 record. Verify the matching packaged build before depending on this expanded workflow; see the documentation version map.

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.
  • In the 1.1.25 Validator changes, preserve commission, slippage ticks, and session-close execution settings in strategy presets.
  • 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 closed-trade max drawdown.
  • Intrabar-equity max drawdown in builds containing the 1.1.25 summary changes; compare it separately from closed-trade 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.

The signed 1.1.25 release record includes Slippage (ticks) for Validator historical Market and StopMarket fills. It applies an adverse price adjustment; historical Limit fills remain at the limit price. Configure the nonnegative tick count in Backtest properties and save the preset. Zero adds no slippage. The original 1.1.12 baseline did not document this control, and ordinary Optimizer runs still have no corresponding control.

Commission is modeled separately. Tick slippage does not simulate spread, queue position, partial fills, liquidity, or market impact. Retain those assumptions with the result. Confirm the installed version using the documentation version map, since the stable feed currently advertises an earlier version than the signed 1.1.25 record.

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. Do not rely on build-specific external-account guards as a substitute for verifying the account.

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​

Validator result packs from the 1.1.25 changes preserve range/timezone, commission model and serialized parameters, slippage ticks, fill-model, session-close, and continuous-merge metadata. Optional strategy decision diagnostics can also be included when the strategy supplies them. This is not a complete replay package: keep strategy source/revision, full presets, starting capital, application version, and research notes separately. Older records and other result types may lack these newer fields.

See Performance Database.