Exit Prioritization (EP) is a nice feature introduced in b34. Unfortunately, it doesn't remember the new setting.
Easy to check: Open Prefs | Backtest | Other Settings... change EP from the default 'Neutral (Random)' to something else... close and reopen Prefs... it'll be back to Neutral.
Hope this gets fixed soon.
Easy to check: Open Prefs | Backtest | Other Settings... change EP from the default 'Neutral (Random)' to something else... close and reopen Prefs... it'll be back to Neutral.
Hope this gets fixed soon.
Rename
I see it, thanks.
Can someone explain Exit Prioritization to me? I'm not sure how that factors into backtesting. I was previously using another platform and never had heard of exit prioritization.
QUOTE:
Hope this gets fixed soon.
Dion's fix confirmed and coming in B35.
QUOTE:Yes, we just added that help for Build 35.
explain Exit Prioritization
Thanks for the answer.
Is there anyway for a backtest to accurately see whether the stop or limit would get filled? Access to historical intra-day data?
Is there anyway for a backtest to accurately see whether the stop or limit would get filled? Access to historical intra-day data?
Not currently. We have “Granular Processing” that can use intraday data to determine which entries would fill in the case of multiple candidates, but haven’t applied that to exits processing yet. It’s on the roadmap to extend it to exits, though.
If you can extend Granularity to include Daily data for Weekly (or higher scale) strategies that would be awesome.
Your Response
Post
Edit Post
Login is required