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)
I am working on a strategy that averages down. I am running into a problem. For some reason, after it averages down more than two times it seems or it could be that the fill executions are greater than the original number of orders, the number of contracts in the target are greater than the number of contracts in the position. Can anyone shed some light on why this is happening and what to do to resolve it?
Can you help answer these questions from other members on NexusFi?
Best way to troubleshoot is via the output window. Write print() statements when adding to a position and evaluate the current position size, and the bar # you are adding to, so you can hunt down any problems.
When the condition for long entry is true, 12 orders are set up at once at different intervals. Frequently, just after the entry signal is triggered, and even after some fills, the condition is no longer true and the orders are cleared. Then, the condition becomes true again and the orders are back, but those that have already been placed are ignored. Could this setting up of the orders, removing the unfilled orders, and then putting them back cause the buys and sell targets to get out of whack? If so, can someone point me in the right direction as to how to handle the orders properly if this is not the best way?
NT has something built in called TraceOrders. In #init put "TraceOrders = true;" and then open your output dialog box and it will print debug statements on all order handling.
