React by the tick in m1?
- This topic has 11 replies, 3 voices, and was last updated 11 months ago by
.
-
Multiple Time Frame support only allows using more than one TF, provided it’s a time-based one.
Ticks cannot be mixed with 1-minute TF.
1 user thanked author for this post.
You guessed it – not possible.
But maybe your focus is on arrays while they may bring you hassle only (in PRT that is). I would say (estimating what you are after) :Open[0] is the open of the current last candle (you can never know anything about the momentary built candle). Open is the same ( [0] can be omitted for the current last candle).
Open[1] is the open of the previous candle. Open[2] the open of the one prior again.With Close and High and all it is the same. No arrays required.
This works the same for each variable you define. Suffix it with e.g. [3] and you have its value from 3 bars (candles) back.
Same for system functions (which PRT tends to call constants) like PositionPerf. Want the gain from 2 candles back ? write PositionPerf[2].
On a different subject, it seems that you may confuse ticks with TimeFrame. If you work with a TF of 1 minute, in your terminology (as it seems !) you have 1 tick per per minute. It is fine to think so. But it is not great once you realize that there’s also real ticks, which represent buys and sells on the instrument. They occur in unpredicted fashion, and may occur 100+ times per second. Or only once per two hours.
The units of the chart can be set to Ticks as well, per your own definition. Each tick, or once per 10 ticks, or once per 560. It defines the bar. But you can not AutoTrade which such a unit.As per your own description, it seems that you want a TF of 1 minute, but like to be in control per e.g. 1 second. Less than one second is not possible. In that case, define your chart in a TF of 1 second, and use the TimeFrame command in the code to set it to a multiple of the TF of the chart. E.g. 1 minute or 60 seconds (both works out to the same). So investigate the TimeFrame command. For example TimeFrame(1 Minute, UpdateOnClose). All your further commands (like Averaging math) under the last TimeFrame command now work subjective to that set TF.
Hope this helps !
Peter2 users thanked author for this post.
As pointed out, complex structures, such as STRUCT, UNION etc… are not supported.
It is rumoured that FUNCTIONS will be supported in the future (at present not in v12). You can still use indicators to sort of mimic them.
Monodimensional arrays are already supported.
1 user thanked author for this post.
Also I was under the impression that on a 1 tick chart, every new quotation tick would update the chart, but if I understand correctly : even then the chart will only be updated every seconds?
From your stance the answer should be Yes indeed. Still from deeper down wishes (again, if I read well) there is a better fitting answer :
Any Indicator (compare Strategy vs Indicator) will update by the tick. But it can only be used like that visually. This is what you want for manual trading.
This goes automatically.
An Indicator can show on the Price pane and in its own (horizontal) pane.And then I’d have to disappoint again, because no AutoTrading can use that; the smallest level remains at the one second.
With 1 second charts there’s a downside : less backtesting data. And way longer backtesting times (progressively longer).
Lastly one hint : I myself have been excessively using 1 second charts (up to 6 seconds) in order to get real scalping running. I could not do it effectively. Effectively : more profitable then an e.g. the 1 minute chart. Of course this relates to my (or one’s) scalping capabilities, but there’s more than that and this is trailing. So what I’m saying is that with good trailing there’s much much more to gain and I could not do that with 1 second charts. Also not when all math is done in the e.g. 1m TF of 5m or longer. So it is exactly the detail of the 1s – which Yes allows you to interfere at any level – but it is too complicated to get it right (even as a die hard programmer). So the hint in this realm is Stop and Limit pending orders, because they to the work for you automatically. And code your own trailing of course.
Per this means I “achieve” 25-30 full trades per day on one System. This is not explicitly scalping, but the aim *is* as many trades as possible. And Yes this is a goal in itself because of the now more possibilities of better gain (due to the Trailing).Don’t forget to decently go about with Spread (take into account a sufficient number of points) or else it will kill you when Live.
1 user thanked author for this post.
Find exclusive trading pro-tools on 
