Library "ReduceSecurityCalls" This library allows you to reduce the number of request.security calls to 1 per symbol per timeframe. Script provides example how to use it with request.security and possible optimisation applied to htf data call. This data can be used to calculate everything you need and more than that (for example you can calculate 4 emas with one function call on mat_out).
ParseSource(mat_outs, o) Should be used inside request.security call. Optimise your calls using timeframe.change when htf data parsing! Supports up to 5 expressions (results of expressions must be float or int) Parameters: mat_outs: Matrix to be used as outputs, first value is newest o: Please use parametres in the order they specified (o should be 1st, h should be 2nd etc..) Returns: outs array, due to weird limitations do not try this :matrix_out = matrix.copy(ParseSource)
Notas de Lançamento
⋅
v2 fix some issues
Updated: ParseSource(mat_outs, o) Parsedata function, should be used inside request.security call. Optimise your calls using timeframe.change when htf data parsing! Supports up to 5 expressions (results of expressions must be float or int) Parameters: mat_outs: deprecated o: Please use parametres in the order they specified (o should be 1st, h should be 2nd etc..) Returns: outs matrix (pine is weird, so now woks as intended)
Hi. Nice work. I got a question. the "ifSecurity" function, the way it's used with the "if barstate.isfirst or timeframe.change(inp_tf)" ends up being the same as using the "nonRepaintingSecurity"? It looks that way, but I'm not sure if it has the same effect.
f4r33x
⋅
@Gero_PT, Hi! Due to the recent breaking changes in pine i am not sure that "IfSecurity" hack works now. Originaly, this was a wrapper for request.security() to manage it to work inside if statements.
It looks that way, but I'm not sure if it has the same effect.