Welcome to NexusFi: the best trading community on the planet, with over 150,000 members Sign Up Now for Free
Genuine reviews from real traders, not fake reviews from stealth vendors
Quality education from leading professional traders
We are a friendly, helpful, and positive community
We do not tolerate rude behavior, trolling, or vendors advertising in posts
We are here to help, just let us know what you need
You'll need to register in order to view the content of the threads and start contributing to our community. It's free for basic access, or support us by becoming an Elite Member -- see if you qualify for a discount below.
-- Big Mike, Site Administrator
(If you already have an account, login at the top of the page)
It executed a BUY. And it executed a SELL. Then another SELL was executed without a BUY. As I said the strategy only goes long.
It resulted in a $2500 loss.
I contacted support. Being this is a Saturday, I won't have a reply till Monday. But if it's happened to you, or you read about it happening. What was the outcome?
Thanks.
Mike
Can you help answer these questions from other members on NexusFi?
Okay, but who actually clicked the buttons that created that strategy? I take it to be you?
This is an important point because, before even thinking that a machine could be wrong, 99.99% of the time it's the logic that was wrong.
By that I mean, have you gone back and made 100% sure that whatever you think your strategy should be doing has actually been translated correctly into what the strategy does?
Of course I don't know you and I don't know your level of NT coding expertise, but I know that the above is very frequently one major cause of upset and, as I said before, 99.99% of the time it turns out that what I wanted my platform to do was not what I actually translated into machine code (whether via a wizard such as NT Strategy Builder or via programming language).
In other words, it takes considerable skill to code strategies. Even via builders.
Nope, nothing to do with coding expertise. The routing system is slow. Orders are routed from the strategy (not directly connected to Ninja Trader Brokerage), to Ninja Trader, to Phillips Capital. The strategy thought it was still long.
I can't count how many times I have been a little surprised by exact timing and results of execution initiations.
Upon investigation I might that NT8 and all other parties involved executed their portions of the transaction process exactly as they had planned.
Overall what I learned is that for some parts of the delay "it just is what it is" and no improvements are to be had. For other parts of the transaction process flow I could make some impacts.
What I learned is that to build reliability into my Algo design and operational process I should:
Option A) The fast first simple approach: Add into my design constraint expectations a 1-2 second delay and on average 2-4 ticks of slippage on each side of each transaction.
Option B) Map the end-2end transaction process flow, identify which of the slowest elements of the process flow I can impact and then make changes on my side to improve speed and reliability.
Key process flow elements include Exchange Data Lag, distance from the exchange/Internet lag, hardware executing the Algo, Algo design complexity and the number of built in delays, post submit broker side risk management checking and order execution time, etc..
I got confirmation from the head script writer. And he said NT is not responsible. It says so in the contract I signed. That's cool. But I won't be paying for that lifetime subscription, bought five days ago, on my credit card.
