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 an algo or an indicator you already have, a backtest, a sweep, going live, 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 algos, 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 the three views a run passes through.

  • 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 a canvas: describe a strategy or an indicator, pick the language, and the file lands on the canvas. Python and C# save straight into the library; MQL5, Pine Script and the rest are written for the platform that runs them. 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.
  • Test is the run bar, the chart and the result. It has three modes, Backtest, Optimize and Audit. On Backtest the box switches between the chart and the Runs, every finished run, the strategy first and then its runs.
  • 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.

Community is Marketplace, Forum and Leaderboard. See Community.

At the bottom of the sidebar sit Settings, this documentation and the Help Center together, with the Bug Report button and the profile menu. 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

Three parts, from the top: the run bar, the box and the evaluation.

The run bar holds everything that decides a run:

  • Settings, at the left, which names what runs (the strategy, the instrument and the timeframe) and opens a small window. The strategy, the instrument and the timeframe are chosen at its top; below them are five tabs. Parameters are the strategy's own, kept for that strategy only, so each strategy remembers its own. 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.
  • Visual or Fast, where the run executes (This machine or Server, with the server minutes you have left beside it) and Start. There is no data source to choose: a run always reads real bars.

The box shows the Chart or the Runs, switched at its head. The runs are every finished run, the strategy first and then its runs. Open one, tick two to compare them, or delete one, which asks first.

The evaluation is under the box. See Reading the result.

Ctrl+Enter starts the run.

Presets

A preset is a named set of settings you pick in one step. The Parameters tab keeps parameter presets, one list per strategy. The Account and costs tab keeps account presets, one list for every strategy: everything in the settings window that is not a parameter, so the account, the costs, the execution, the portfolio and the split.

The row at the head of each tab picks a preset, which applies it at once. Beside the list: Save as preset (a name already in the list replaces that preset), Rename, Delete, Export as file and Import a 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. Its other tabs are:

  • Report, the full report.
  • Trades, every position the strategy opened, with entry, exit, reason and result.
  • Positions, the positions of the run, with a live mark during a replay.
  • Logs, what the engine and the strategy printed, in order.
  • Strategy, the code behind the run, with the assistant beside it.
  • Analysis, and after a split run In / out of sample.

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 colour and the text size, and a Chart settings row that opens the dialog for the chart's colours and scales. See Charts and Drawings. Profit green and loss red are never touched by the accent, because a colour that means "money" should not change when a colour that means "button" does.

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

OrionQuant