Skip to main content

HX109 Performance Database And Reporting

HX109 teaches how HyperionX turns a strategy run into a research record. Results should not live only in a screenshot or a temporary window. They need to be saved, inspected, compared, exported, and reproducible.

Lesson 1: Performance Windows​

HyperionX performance views can show more than a single net-profit number.

Teach users to inspect:

  • Summary.
  • Trades.
  • Orders.
  • Analysis.
  • Drawdown.
  • Pain level/risk views.
  • Portfolio views where applicable.
  • Long/short splits.
  • Tooltips for trades and drawdown points.

The goal is to understand how a strategy made or lost money, not only whether the final number is green.

Lesson 2: Saved Performance Results​

Saved performance results should preserve enough context to rebuild the run.

Required context:

  • Strategy name and version.
  • Instrument and provider.
  • Data series type/value.
  • Date range.
  • Strategy parameters.
  • Commission/slippage assumptions.
  • Quantity, leverage, and margin assumptions.
  • Long/short results.
  • Trades and orders.
  • App/build version where available.

If a saved result cannot answer "what exactly was tested?", it is not useful research.

Lesson 3: Optimizer Database​

The optimizer database is for comparison and reproduction.

Teach:

  • Save the optimizer test name.
  • Save period definitions.
  • Preserve in-sample, out-of-sample, and simulation periods.
  • Preserve optimizer parameter ranges.
  • Preserve fitness metric and optimizer type.
  • Reopen saved results before changing the strategy.
  • Compare stable parameter regions, not only one best row.

Do not overwrite historical research records without a reason.

Lesson 4: Portfolio Review​

Portfolio-level results can hide weak components.

Review:

  • Aggregate equity curve.
  • Instrument-by-instrument contribution.
  • Long and short contribution.
  • Max drawdown by component.
  • Trade count by component.
  • Commission by component.
  • Whether one symbol explains most of the profit.

Portfolio views are useful only when users drill down into the parts.

Lesson 5: Exports​

Export is part of support and research workflow.

Useful exports include:

  • Performance reports.
  • Optimizer results.
  • Trade lists.
  • Order lists.
  • Logs.
  • Chart datasets where supported.
  • Screenshots or chart images where supported.

Exports should not expose API keys, wallet secrets, account secrets, or protected credentials.

Lesson 6: Result Review Checklist​

Before trusting a result:

  1. Confirm the data range.
  2. Confirm the provider/instrument metadata.
  3. Confirm commission and slippage.
  4. Confirm quantity and leverage.
  5. Confirm trade count.
  6. Confirm drawdown and pain level.
  7. Confirm long and short behavior.
  8. Confirm out-of-sample behavior.
  9. Save the result.
  10. Reopen the saved result and verify it still explains the test.

Completion check:

  • User can open a performance result and explain summary, trades, orders, and drawdown.
  • User can save optimizer/performance results with enough metadata to reproduce them.
  • User can compare portfolio components instead of trusting the aggregate alone.
  • User can export research/support artifacts without leaking secrets.