is it possible to process indicator using live data
library looks great but i have one question lets say i am subscribed to some feed and every second i am getting new Candle is it possible to calculate indicator value on that candle. instead of reprocessing all candles again?
I achieved this by using the StartIndex, EndIndex parameter to indicator Compute function
Great can you please give some example i am just getting started will be great help.... Thankyou
It’s open source software bro, you have to work it out :D
okay thanks :)
just allow me to ask one more question please
for example if i am using following code
var closes = new List
so if i add another close in closes list i can get value by index bit it again processing all array right. so i wanted to know does the indicator cached the previously calculated value and process just the new value.
It’s. it my project so I don’t know, but I suggest try it out :D
@softdev021 the value is re-computed, there's no caching mechanism in indicator computation.
Also related to #29
I'm looking for the same as @softdev021. It would be nice if indicators, that base on previous values, had a parameter to pass "starting point", which would be a previous value of that indicator. Thanks for your great lib !
@andrzej-suwala it sounds good but the effort to complete this feature is not trivial, I might have to spend some time to work on it, it would be a great help if you guys could create a PR for the feature 😄
@andrzej-suwala it sounds good but the effort to complete this feature is not trivial, I might have to spend some time to work on it, it would be a great help if you guys could create a PR for the feature 😄
thanks IppKarl actually problem is suppose we are running some bot for very long period now obviously candle count will increase. hence processing time of indicator also increases due to which one can miss the entry point when placing trade via bot automatically. if you can achieve this it will be great...
This is an interesting and highly desired feature. The current design is a very functional approach. This would require holding state. And the two designs conflict.
I would definitely like to see this come to play, but we would need to come up with a solid stateful design so that calculations are performed on the new elements and not on the old.
I would like to see a proposal come forward.
I wrote a bot using binance API + this lib, watching ~125+ assets real time, analysing with major indicators realtime, no need to do that as @lppkarl mentioned. It's only using 30 threads and ~250mb of ram. Just cache the candlestick data on file system or on some doc db to prevent refetch. It's fast enough. Just be sure to use async programming..