One-time buy Signal at System Start
- This topic has 45 replies, 6 voices, and was last updated 1 week ago by
.
-
In this case, opening a position on the first bar in combination with an indicator only works when the “PreLoadBars” are equal to the indicator’s period…
So here, PreLoadBars=36…1 user thanked author for this post.
<span class=”bbp-author-name”>stalba</span> it appears that PreLoadbars = 36 is critical if ‘NOT onMarket’ is used. You use period of 36 in your SuperTrend, hence PreLoadbars = 36 is critical I guess.
Or it appears you could miss out ‘NOT onMarket’ and use PreLoadbars = 100 / whatever … as I posted above … unless anyone has good reason not to do this??
EDIT/ PS
I saw JS last post after I posted mine.
1 user thanked author for this post.
Seems to work now, like you both said either with “36 bars + NOT ONMARKET” or e.g. “100 Bars without NOT ONMARKET”, but I guess if 36 bars are enough, I’d go with the “NOT ONMARKET” version. Next, I will test it with a 1-day timeframe – thanks! 🙏🏼
1 user thanked author for this post.
Without trying the code : I bet you that this is because the code has ran several times in live before the PreLoadBars have passed. Thus, have those at 100 and the code will be run 100 times and EntryFlag has turned 1 long gone …
The catch here is that during the PreLoadBars stage the ProOrder commands are NOT executed. Thus no Buy and no Sell or anything.
Years ago I reported this as a severe bug. I myself don’t notice any more that this is still present. Because see below …
1234567891011PreLoadBars = 1000PreLoadBarsSet = 1000 // Set this redundantly to the line above.[...][...]If BarIndex > PreloadBarsSet then[...] // All of your code here - especially the code which determines and does trading.endif… which is what I apply always since.
During Backtesting this is applied differently by PRT, because there the code is NOT run during the PreLoadBars stage.
What is below for on Lines 4 and 5?
[…][…]That would typically be the calculation of MACDs and all that *require* the preloaded bars (or else them preloaded bars would be in vain 🙂 ).
1 user thanked author for this post.
I think what you said was in the context of this – specific – discussion, where the OP was not seeing triggers for reasons X and how that relates to bars elapsed with respect to preloads and indicator code employed. Your code simply eliminates erroneous triggers and perhaps outcomes given the dataset hasn’t reached required size.
Bit of a waffle there, pls correct if I’ve borked it …
I hope we’re on the same terms with :
A lot can be done in the code with setting flags etc. etc. etc., that code assuming that a Buy at Market (etc.) would have done so. Thus :
123456Once IAmIn = 0 // Mind the Once.If MyBuyCon = 1 thenBuy x Shares at Market // This will not execute when the preloadbars (say 1000) are executed and the code is called a 1000 times.IAmIn = 1 // This is totally unreliable now for the next iteration.endifSadly, in Backtest this can not be noticed and all goes fine.
Please beware : I never use(d) Demo, so I cannot tell whether Demo will show the same behavior as I have testified (towards PRT) for Live. But I assume it is the same, and with that the cause for the off behavior shown in this thread. GraHal actually showcased it accidentally (in any event well done !).
Find exclusive trading pro-tools on 
