nimo23
nimo23
>you are loosing the information about the generic class parameter T. The past has shown that we really don't need such kind of abstraction level. Your solution: ``` NumIndicator with...
>We could eliminate the recursive cache problem, if we are sure that we have the correct warm up period x for each indicator that depends on previous values. Yes, good...
>How do you see us implementing this - just returning NaN directly or should we use the UnstableIndicator to do so? We should just return `NaN` directly from the origin...
@team172011 please close this issue.
>But when returning NaN the user **does not have any change using** or inspecting values for indices lower than the unstable bars value Why should the user be allowed to...
>And this amount of data cannot be set to a fixed value, it depends on further factors than the barCount, such as other Indicators that are used by this Indicator...
>warm-up period -> variable, set by user (has a default?), indicator needs at least x consecutive previous bars to return valid data (return same as unstable period?) If the user...
FYI: https://www.reddit.com/r/algotrading/comments/bbnv8c/how_many_candles_minimum_to_get_an_accurate_ema/
Ok, I think there are misunderstandings due to a lack of information: We need to add the base to avoid minus signs canceling out when dividing. I guess (but I...
For both, it would be good to **just check for existing issues beforehand**, rather than opening a new one and posting your comments, suggestions, or future plans here: https://github.com/ta4j/ta4j/issues/755