Optimization Module Reference

HyperionX optimization is not only a grid search. The platform has separate concepts for strategy parameters, optimizers, fitness scoring, money management, commissions, validation, and performance metrics.

Module Categories

Category	Purpose
Optimizers	Decide how parameter combinations are searched.
OptimizationFitnesses	Score and rank results.
MoneyManagements	Control sizing and capital behavior.
Commissions	Model fees and costs.
Strategies	Provide the logic being tested.

Strategy Parameters

Use [HyperionXProperty] for values that should appear in optimization and validation workflows.

[HyperionXProperty]
[Display(Name = "Fast Period", GroupName = "Parameters", Order = 1)]
public int FastPeriod { get; set; }

Keep parameter ranges realistic. A large search over meaningless values produces noise, not edge.

Fitness Scoring

A fitness module should rank results by the behavior the trader actually wants. Net profit alone is not enough.

Useful inputs include:

• net profit
• max drawdown
• profit factor
• Sharpe
• trade count
• average trade
• largest loss
• consecutive losses
• commission and slippage
• stability across nearby parameters

Closely Guarded Island Penalty

HyperionX research should penalize isolated winners. An isolated winner is a parameter set that looks strong but is surrounded by weak neighboring values.

Example:

Fast	Slow	Stop	Target	Net Profit	Neighbor Quality
17	43	38	74	$42,000	Weak
18	43	38	74	$4,500	Weak
17	44	38	74	-$1,200	Weak
16	42	36	70	$31,000	Strong cluster

The first row has higher profit, but its edge is fragile. A professional optimizer should prefer stable clusters over one lucky island.

The exact production formula can remain proprietary. The public concept is:

research score =
    base performance score
    - drawdown penalty
    - low-trade-count penalty
    - fee/slippage sensitivity penalty
    - isolated-neighbor penalty

This gives HyperionX a testing advantage because it rewards durable behavior instead of curve-fit peaks.

Walk-Forward Workflow

A robust workflow:

1. Optimize on in-sample data.
2. Select stable parameter regions, not only the top row.
3. Test selected parameters out of sample.
4. Roll the window forward.
5. Aggregate the out-of-sample results.
6. Review degradation, drawdown, and trade distribution.
7. Only then test in playback or simulation.

Commission And Slippage

Commission models and slippage assumptions should be active before trusting backtest results. A system that only works with zero fees is not a production system.

For crypto, futures, equities, and broker-specific routing, the commission model should account for:

• maker/taker fee differences
• minimum commission
• exchange fees
• account type
• leverage costs where relevant
• expected spread/slippage

Money Management

Money management modules should separate entry logic from sizing logic. This lets the same strategy be tested with:

• fixed quantity
• fixed notional/USD size
• percent of equity
• volatility-adjusted sizing
• drawdown-based reduction
• account-specific limits

This separation is important for multi-client or multi-account strategy deployment.