Would someone be willing to comment on if they use a secondary data series (i.e., 1 range) in your backtesting code to enter a position? I clearly get why one would need to use the secondary data series to determine if the position was stopped or targeted, however what are the consensus reasons for using the secondary data series for backtested entry orders?
Also, I've seen quite a few futures.io (formerly BMT) posts that allude to being careful with using the secondary data series (i.e., "just be aware there are many caveats to doing so"). I'd wonder if some of the more experienced members would help out by pointing out the best practices for using a secondary data series for back testing order execution (entry or exits). What do we need to watch out for? What has worked for you? What should we avoid? What must we make sure we do? NT7 backtesting limitations are a little like the dark corner in Gramma's house that used to scare the crap out of you as a kid--but after just shining a flashlight in the corner did you see that there were just a bunch of applesauce jars and that everything was fine. I'm looking for some "flashlight" advice to bring some of these backtesting issues into the light so that we don't have to be scared of backtesting because we will understand how it works--and more importantly how we need to work with it.
I realize this thread is pretty old, but I believe my questions are still relevant. Hopefully some of the "old" timers will chime in.