Skip to main content

​
Generator

The Generator explores strategies at scale (random search by default), evaluates them on your history, and always saves them to the Databank. Compute runs as a background job on your TPA.
Strategy Generator page

Generator form. Click to zoom.

You need a symbol downloaded under Market data and a linked, online TPA. Without data or an agent, the job will not start or queuing will fail.

​
Typical flow

  1. Open Generator.
  2. Pick a symbol (already downloaded) and date range (empty = full available history).
  3. Set attempts (n), risk/costs, and workers.
  4. Click Generate and follow progress on the page or in Jobs (the phase switches to Generating when search starts).
  5. Review viable strategies in the Databank (the top-K updates live during the run).
You can keep navigating — the job runs in the background.

​
Data

Partial coverage or a missing symbol is called out in the UI with a link to Data.

​
Engine and filters

The Engine & filters card covers random search and optional run filters.
  • Fast mode (on by default): first explores short windows of history; what lands in the Databank is retested on your full period. Turn it off for full evaluation from the first candidate (slower).
  • Attempts: how many candidate strategies to explore.
  • Min trades / max leaves: minimum viability and entry-rule complexity.
  • Min. profit factor and Max. drawdown (%): optional; empty = off. The DD cap aborts that candidate if it is hit during the simulation.
  • Genetic evolution from an already saved strategy is done in Databank → Evolve. See Strategy detail.

​
Exit / order types

Opt-in by probability (0 = never):
  • Break-even, time exit, reverse / opposite signal
  • Pending Stop/Limit orders
  • Entry trigger edge (false→true pulse) vs re-enter while the signal stays true
  • Force edge on multi-TF when HTF leaves exist (better MT parity on sticky signals)
  • Max entries/day (0 = no run-level cap)
These mechanisms export to MQL with backtest parity when applicable.

​
Risk, costs, and validation

​
Workers and memory (OOM)

Workers evaluate in parallel. Each extra worker copies data and caches in RAM. With long series (M1 / multi-TF), 2–4 workers can exhaust memory.
  • Start at 1.
  • Increase only if you have spare RAM and stable runs.
  • If the job dies with OOM / process-pool errors, lower workers or shrink range/n.

​
Saving and live Databank

Every run from the Generator persists to the Databank (there is no toggle to turn saving off).
  • Update databank every (seconds): incremental top-K flush while the job runs (min ~5 s; default ~60 s).
  • What you see during the run is the same top-K that remains at the end (by Sort by and Top).
  • With TPA, mid-run flush feeds the Databank while the agent executes the job.
During an active generation, the Databank may show a live job and refresh on its own. When the run finishes, open the Databank to filter, sort, and open each strategy.

​
Reset and draft

  • Reset restores generator defaults (does not change global Settings).
  • The form draft is stored in the browser per user; switching accounts should not inherit another user’s draft.

​
Presets and multi-TF

Saving/loading presets and timeframe randomization: Presets and multi-timeframe.

​
Next