Announcement
Collapse
No announcement yet.
Partner 728x90
Collapse
NinjaTrader
Replay speed - is its reliability algorithmically proven?
Collapse
X
-
No I didnt do any fancy stuff.. I cant imagine what would be an effect of using a timer on replay or backtest
I am asking purely to reduce number of questions I have to resolve to match backtest with live r/t.... 2 weeks and still nowhere :S
But thank you!
Comment
-
OK.. What I am trying to do is not to match executions from backtest to live as it is well known that markets behave not as you expect them
I am trying establish the facts:
a. non-time bars and indicators on them has to match historical and live.
b. bid/ask flow recorded from live feed must match flow in backtesting.
say if I have bar closed at 15:51:34 at price 1790.25 on live and the next ticks were as follows - bid 1790.25 ask 1790.50 ask 1790.75 - I would expect that backtesting will "replay" internally same data and give me same sequence of ticks during backtest.
I cannot ask for the same timing as time maters not in things like backtest and replay....
Most important for me is to make 100% match between bars, indicators and sequence of bid/ask/last ticks everywhere - backtest, replay, simulation...
What would make backtest which is fed from historical data which was recorded from live not to match sequence of bid/ask messages if it was recorded on the same PC ?
Would you agree?
Comment
-
Dierk I need to know then what can I expect exactly.
If I have bid and ask historical data and I have 1 tick of last, bid and ask TFs added to a strategy for backtest......
you are saying they will not match replay.
can you explain why?
is it because backtest cannot correctly synchronise bid/ask with last or number of bid/ask ticks in historical data reduced by Ninja or backtest doesnt use every bid/ask tick? or what?
how exactly backtest and replay sync different tick timeframes with each other and the with chart time?? Is there internal milliseconds timestamps or all ticks have 1 sec granularity? Do you keep a sequential number within tick records? If Bid/Ask/Last stored separately - how do you know what tick was after what?
I mean my question perhaps look annoying but I have to know the principles. If I got the answers there would be much less questions in future
Lets do it once. I am not going to open debates on what is good or what is bad. I just need to know what my options are... No critics. I promise
Comment
-
>>If Bid/Ask/Last stored separately - how do you know what tick was after what?
They are stored separately for backtest and OnBarUpdate() is triggered based on their timestamps down to 1 sec granularity. Meaning anything below 1 sec granularity will not be synchronized properly. However:
- all bid/ask/last are processed though and nothing is dropped just the sequence might be unexpected.
- bid/ask/last "ticks" in itself (meaning all bid, all ask, all last) are perfectly in sequence
Replay is different: all bid/ask/last are replayed in their EXACT sequence (although timestamps are rounded to 250ms granularity).
Comment
Latest Posts
Collapse
| Topics | Statistics | Last Post | ||
|---|---|---|---|---|
|
Started by Geovanny Suaza, 02-11-2026, 06:32 PM
|
0 responses
606 views
0 likes
|
Last Post
|
||
|
Started by Geovanny Suaza, 02-11-2026, 05:51 PM
|
0 responses
353 views
1 like
|
Last Post
|
||
|
Started by Mindset, 02-09-2026, 11:44 AM
|
0 responses
105 views
0 likes
|
Last Post
by Mindset
02-09-2026, 11:44 AM
|
||
|
Started by Geovanny Suaza, 02-02-2026, 12:30 PM
|
0 responses
560 views
1 like
|
Last Post
|
||
|
Started by RFrosty, 01-28-2026, 06:49 PM
|
0 responses
561 views
1 like
|
Last Post
by RFrosty
01-28-2026, 06:49 PM
|

Comment