Support Board
Date/Time: Mon, 03 Feb 2025 13:53:14 +0000
[Programming Help] - Why does Sierra Chart always start backtests too early?
View Count: 644
| [2019-11-16 23:53:08] |
| j4ytr4der_ - Posts: 944 |
|
In evaluating some potential systems, I'm doing a lot of backtesting. I like to use ATBB as a quick first-pass since it's likely to be the most favorable in terms of results (if the results stink there, they aren't gonna get any better with more detail). But when I run a BBBT, the first trades fire before there is even enough data to generate things like moving averages, etc. Why is this? And is there a way to get the backtest to only start after all the required indicators are actually plotting data? Date Time Of Last Edit: 2019-11-16 23:54:03
|
| [2019-11-17 03:45:02] |
| |
|
This is something that you need to control within the trading system itself. There is no way this can externally be known.
Sierra Chart Support - Engineering Level Your definitive source for support. Other responses are from users. Try to keep your questions brief and to the point. Be aware of support policy: https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation For the most reliable, advanced, and zero cost futures order routing, *change* to the Teton service: Sierra Chart Teton Futures Order Routing Date Time Of Last Edit: 2019-11-17 03:45:09
|
| [2019-11-17 04:02:26] |
| j4ytr4der_ - Posts: 944 |
|
I'm not sure you've understood me, or I'm not understanding you. My system already has logic which tests for things like price above or below a certain moving average. But trades are firing on a backtest, before the moving average is even plotted on the chart, so what value is the system using to determine that it should have signaled a trade? My expectation would be that no trade would be possible, if data that is required for the signal to fire, is not available yet. |
To post a message in this thread, you need to log in with your Sierra Chart account: