The Interface

DocumentationIntroduction

The Interface

Four places do the work. The sidebar picks a destination, the Test view runs things, the evaluation under the chart says what happened, and the command palette reaches any of it without the mouse.

The sidebar

Overview holds Home. Two rows of cards, one for each thing you open the app to do: AI Studio, building from blocks, importing a strategy or an indicator you already have, a backtest, a sweep, an audit, launching a deployment, connecting your AI agent, ML Studio and the marketplace. Until they are done, the first steps sit at the front of them; once done or closed, they do not come back. Under the cards, four figures, each with its last ninety days drawn beside it: simulated live P&L, active deployments, backtests and marketplace installs. Beside those, the strategy the audit trusts most, with its equity curve, its figures and the four audit checks. An audit is never made automatically: a backtest is audited when you ask for it in the Audit view, and each audit spends one of the month's. The audited runs are ranked by the audit, never by return.

Lab is where a strategy is made and run.

  • Build is the strategy library and the editor. The indicator library and the plugin folder are here too, under the tabs at the top. AI Studio is a chat beside the workspace it writes into: describe a strategy, and the AI writes the file that runs, any helpers and the notes into a workspace of Build, each change a diff you keep or undo. An indicator goes to your library, a file for MQL5, NinjaScript or another platform is downloaded. Import brings in a file you already have: say which language it is, and it goes to the core that runs it, or to AI Studio to be translated when no core does.
  • Templates, under Build, is a gallery of ready made strategies, filtered by idea. Each card shows the period, the net result, the drawdown and whether the template meets the template rules; a click opens the template's own page. Use template sets the run up in Backtest and starts it, Open sets it up and waits for you, and Fork puts a copy in your library as a workspace.
  • Test is the run bar, the Parameters panel, the chart and the result. It has two modes, Backtest and Optimize, laid out the same way. Every finished run is the Runs tab of the evaluation, the strategy first and then its runs.
  • Audit, under Test, reads a run that is already done.

Resources is what a strategy draws on rather than where it is made.

  • Black Swans lists the market shocks of the last 30 years: stock crashes, currencies, commodities, crypto, banks and credit, and shocks from outside. Filter by kind, instrument or a word, and Test opens Backtest on that market over the event's window. The page says whether the data is ready, loads on the first test, or does not reach that far back: an older event is there to read about.
  • Data is the local cache, the download toolbar and the instrument specifications. It is desktop only, because there is nothing on your own machine for the browser build to manage.
  • Live watches or runs a strategy on live prices. See Live below.
  • Terminal is the Caldex Terminal. It is grayed out with a note until it opens for your account.

Community is Marketplace, Forum and Leaderboard. See Community.

At the bottom of the sidebar sit Settings, this documentation, the Help Center and the Changelog together, with the Bug Report button and the profile menu. The Changelog lists what changed in each version, with a page per version. Ctrl+B collapses the rail to icons and brings it back.

The command palette

Ctrl+K opens a search box over every destination, every setting and every saved strategy. Type a few letters and press Return. It is the fastest way around the app and it is the only one that does not care where you are.

The Test view

Backtest and Optimize look the same, so there is one view to learn. Three parts, from the top: the run bar, the work area (the Parameters panel and the box beside it) and the evaluation.

The run bar holds how and when a run goes:

  • Settings, at the left, opens a small window with how the test runs and nothing about the strategy. The instrument and the timeframe are chosen at its top; below them are four tabs. Account and costs is balance, currency, leverage, lot size, commission, swap and costs over time. Execution is the data accuracy (OHLC, M1 proxy or real ticks), the fill priority, the slip beyond the touch on ticks, and the switches for news and for fetching while the run goes. Portfolio holds the legs. In sample / out of sample sets the part of the period held back from the result. Ctrl+P opens and closes the window without losing the result on screen. See Data and Accuracy.
  • The period as a time bar over the data this machine holds. Drag its handles or type the dates. What is missing is marked, and Start fetches it.
  • Run options, next to Start, shows how and where the run goes in two icons and opens the choice: Visual or Fast (Backtest only) and This machine or Server, with the server minutes you have left. The i beside each explains it in a sentence. Then Start. There is no data source to choose: a run always reads real bars.

The Parameters panel, on the left, holds the strategy at its head and its parameters under it, kept for that strategy only, so each strategy remembers its own. A value outside the range the strategy declares is marked and runs anyway. On Optimize the same rows gain a tick and Min, Max and Step, and the panel's foot holds the fitness, the method and the workers. The button at its head folds the panel to a strip of icons; a click on one opens it there.

The box beside it shows the chart on Backtest and the passes on Optimize.

The evaluation is under the box, with every result tab. See Reading the result.

Ctrl+Enter starts the run.

Presets

A preset is a named set of values you pick in one step. There are two kinds, each behind a Presets button. In the Parameters panel, parameter presets, one list per strategy (on Optimize the file carries the ranges too). In the head of the Settings window, settings presets, one list for every strategy: everything in that window, so the market, the account, the costs, the execution, the portfolio and the split.

A click on a preset applies it at once. A row's pencil renames it and its bin deletes it, which asks first. Under the list: Save as preset (a name already in the list replaces that preset), Import a file and Export as file. Presets are kept on this computer.

An exported preset is a .oqpreset file, JSON inside, to keep or to pass on. Import one with the button, drop it on the window, or double click it in the installed desktop app. Before anything changes, a dialog lists every value the file changes, as it is now and as it becomes, what it does not carry (that stays as it is), keys this app does not know and values of the wrong type (both ignored), and a tier your plan does not have. A parameter preset made for another strategy is refused with that strategy's name: choose that strategy first.

Reading the result

The Evaluation under the box opens on the Overview: the equity curve, the drawdown, the monthly returns as bars, the distribution of the trades and the key statistics first, then the Analysis further down: where the edge lives, the strategy's profile, the win rate as the trades add up, hold time against result and the 3D views. After a split run the Overview starts with both parts side by side. Its other tabs are:

  • Report, the full report.
  • Trades, every position the strategy opened, with entry, exit, reason and result. Fills lists each entry and exit in the order they happened, and during a replay the position open at that bar sits on top with its live mark.
  • Logs, what the engine and the strategy printed, in order.
  • Strategy, the code behind the run, with the assistant beside it.
  • Runs, every finished run, the strategy first and then its runs. Open one, tick two to compare them, or delete one, which asks first.

Audit, at the end of the row of tabs, opens the run on screen on the Audit page.

On Optimize the same evaluation holds the report of the pass you load, with Chart (the loaded passes) and Landscape as its last tabs. A tab that needs a result is grayed until one is on screen.

The chart carries the trades as markers, the indicators the strategy declared, and an optional Buy and Hold benchmark. See Charts and Drawings.

Live

Live has two cards: Live Test, which watches a strategy on live prices and places nothing, and Live Deploy, which runs one on our server or on this machine. Each card chooses what it runs before Start: the strategy, the Instrument with the same picker the Test page uses, the Timeframe and the strategy's Parameters. They start as the Test page has them and change only here; the Test page is not touched. Use the Test settings puts them back. A card keeps its choice for as long as the app runs, and while it runs the fields show what runs and cannot be changed. Live builds its bars from minute candles, so the timeframes are M1 to H4, and an instrument without live prices is refused with a sentence rather than started. The page of a running deployment opens on its price chart, see Charts and Drawings.

Where the prices come from: London Strategic Edge's live stream, with the bid and the ask, a second or less behind the market. It carries forex pairs, gold, silver, crypto, US shares, WTI and Brent crude, natural gas, copper and the index CFDs (S&P 500, Nasdaq 100, Dow, Russell 2000, FTSE 100, DAX, CAC 40, Euro Stoxx 50, Nikkei 225, ASX 200, Hang Seng). While no price arrives, because the market is shut or the stream has a gap, a deployment shows Prices not live and carries on by itself with the next price. For an instrument the stream does not carry, and whenever the stream is not there, Live says "Live data streaming is not available right now" instead of starting. The stream runs on our server, so a Live Test on this computer says the same; Live Deploy on our server is where live prices are.

Appearance

Settings, Appearance carries the theme, the accent color and the text size, and a Chart settings row that opens the dialog for the chart's colors and scales. See Charts and Drawings. Profit green and loss red are never touched by the accent, because a color that means "money" should not change when a color that means "button" does.

The language switch is in the same place. This documentation follows it.

Caldex