TGIM / EVALUATION

Understand the setup.
Review the evidence.

A useful evaluation starts with an identified build and a repeatable setup. Keep the source version, inputs and assumptions together, then review chart behavior, alerts and execution as separate stages.

TGIM evaluation concept showing a source-version folder and settings checklist beside separate simulation, alert and order records
TGIM ERIAN v1.7.4 RC7

Inspect the chart. Follow the test record.

Three views of the supplied EURUSD research setup: the chart, the Strategy Tester overview and its individual trade records. Each image opens at its original 1920 × 1080 resolution.

Screenshots supplied November 11, 2026 · TradingView · EURUSD · 30-minute chart

TGIM ERIAN v1.7.4 RC7 on a 30-minute EURUSD TradingView chart, showing ZAG direction changes, trade markers, rail readings and a status dashboard.
Chart and signal view. TGIM ERIAN v1.7.4 RC7 on the EURUSD 30-minute chart, with directional markers, reference rails and the build dashboard. Open full-resolution image ↗
TradingView Strategy Tester overview for TGIM ERIAN v1.7.4 RC7 on EURUSD, showing historical test statistics and the cumulative performance curve.
Strategy Tester overview. The supplied TradingView Strategy Tester capture, with the test overview and cumulative performance curve. Open full-resolution image ↗
TGIM ERIAN EURUSD Strategy Tester trade list, showing individual entries, exits, prices, position sizes and recorded test outcomes.
Trade-by-trade detail. Individual entries and exits displayed in the supplied EURUSD Strategy Tester trade list. Open full-resolution image ↗

These captures show a historical simulation as supplied. The exact source, inputs, active period and test assumptions belong in the evaluation record; no independent reproduction or live execution verification is claimed.

From research to a decision

What to include in an evaluation record.

Historical simulations, alert checks and execution records answer different questions. Review each stage against its own evidence.

  1. Reproduce an identified configuration

    Retain exact build/source hash, inputs and Properties, chart type, symbol, data source, timeframe, active trading period, capital and sizing. Reproduce the complete trade list rather than matching a headline statistic.

  2. Stress the assumptions

    Add realistic commissions, spread and slippage; inspect fill and intrabar behavior, losing and flat periods, open trades and parameter sensitivity. Evaluate untouched periods and conditions beyond the selected sample.

  3. Separate alerts from execution

    A chart condition, a server alert, receiver acknowledgment, broker acceptance and an actual fill are distinct events. A later paper/demo comparison needs timestamped evidence for the stages actually tested.

  4. Agree the right scope

    Review the specific current build and proposed use before access or deployment. No screenshot grants a license, proves an execution connection is safe or promises future results.

Choose your next step

Explore TGIM—or bring your own rules.

TGIM licensing and custom software engineering are different offers. Start with the one that matches the rights and work you need.

Trading can result in loss of capital. Hypothetical results have important limitations, including the benefit of hindsight and differences from real execution. Past performance is not a reliable prediction of future results. Atlas is independent of TradingView and OANDA; naming a platform or data source does not imply sponsorship.

Read TradingView's strategy simulation documentation ↗