Atlas Liaison GroupConnecting you with what's next.

TradingView is where our trading ideas go to work

A chart is easy to explain after the move. The harder question is what you would have seen one candle earlier. At Atlas, TradingView is essential to our TGIM research because it lets us mark that moment, write down a rule, replay the chart and inspect what the rule actually did. Those steps belong together whether you trade by hand or eventually automate part of the process.

Atlas may earn a commission if you subscribe through our TradingView links.Open a TradingView 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.
View full-size chart

Start with a chart you can come back to

Suppose you want to study the first return to a prior session high. Open the exact symbol and exchange or data feed you intend to follow. Set the session, time zone and candle interval. Mark the previous high before the next session begins. Save the layout and record those settings alongside a screenshot. Tomorrow you can reopen the same setup and tell whether price actually reached the level you drew.

For our futures work, a continuous chart is useful for exploring history. For a particular session we also record the dated contract being reviewed. For forex we record the feed. Two screenshots labeled EURUSD or ES can tell different stories when they cover different sessions or contract histories. A watchlist gets you back to the symbol. A saved layout and a journal entry tell you which question you were asking.

Give each indicator a job

On a TGIM chart we might use a higher interval to establish direction and a shorter interval to observe a return to a reference level. Before adding another overlay, ask what decision it would change. If the only purpose of a moving average is to define direction, write down what counts as a change of direction. If a marker signals a retest, decide whether a touch is enough or the candle must close back across the level.

Pine Script gives us a way to make that wording testable. An indicator can mark the chart or expose an alert condition. A strategy can submit simulated orders to TradingView’s broker emulator. When developing TGIM we compare the chart marker, the simulated order and the trade list. They answer three different questions about the very same candle.

Replay a decision before you score it

Pick a historical point using Bar Replay. Write down your level, the condition that would count as a signal and the observation that would invalidate it. Advance the bars. Save one example that behaved as expected and one that failed. The failed example is often where you discover two people could read your original rule differently. Revise the wording, then try a fresh period you have not already inspected.

Read past the Strategy Tester headline

Before interpreting a backtest, open its properties and trade list. What size was simulated? Which commissions and slippage assumptions were used? Was the order placed on a bar close and filled on the next bar? Find a trade whose fill you can explain from the chart, then inspect a losing sequence. A profitable total can coexist with a drawdown that makes a rule unusable for your account.

Take one rule from the chart into rehearsal

Our last step is to compare the intended signal with what arrives in real time. Set an alert on the chosen symbol and interval. Record its timestamp, then compare that event with a paper-trading record or a test receiver. With a webhook workflow, keep the alert log, the receiver response and the order record distinct. Seeing the alert fire proves one specific thing. The receiving system and the broker each have their own evidence.

Explore Bar Replay on TradingView

Keep working with the chart

Platform documentation

Explore TradingView plans