I'm programming a stop and reverse strategy. A reverse order is placed after the initial position is closed via a filled stop and the associated target order is canceled. A reverse order is placed (via a market order) and is accepted. Once the reverse position state is 'Filled', I place a stop and target order using the entry name of the reverse order. Both the stop and target orders are accepted and in the 'Working' state.
For some trades using the back-tester, my stop and target orders are then canceled. The trace messages I get are:
"Cancelled pending exit order, since associated position is closed"
There's a couple of issues with this:
1. The stop and target orders are 'Working' not 'Pending'.
2. The stop and target orders are associated with the reverse position which is not closed, it's still open (now without a stop or target order).
A position that is closed is the initial position that got stopped out before the reverse position was put on. The stop and target orders that are canceled are not associated with that initial position (which has a different entry name).
I've searched through the forum, looking for related problems and see in this thread:
that Ninja has some internal signal tracking issues. My problem seems related to the issue detailed in that thread.
I'll wait for the next maintenance release before spending hours trying to create a minimum strategy that can reproduce the problem.
Regards,
David
dbw451
For some trades using the back-tester, my stop and target orders are then canceled. The trace messages I get are:
"Cancelled pending exit order, since associated position is closed"
There's a couple of issues with this:
1. The stop and target orders are 'Working' not 'Pending'.
2. The stop and target orders are associated with the reverse position which is not closed, it's still open (now without a stop or target order).
A position that is closed is the initial position that got stopped out before the reverse position was put on. The stop and target orders that are canceled are not associated with that initial position (which has a different entry name).
I've searched through the forum, looking for related problems and see in this thread:
that Ninja has some internal signal tracking issues. My problem seems related to the issue detailed in that thread.
I'll wait for the next maintenance release before spending hours trying to create a minimum strategy that can reproduce the problem.
Regards,
David
dbw451
Comment