Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

get_unstable_period gives 0 for all functions with unstable period #664

Open
TsiVit opened this issue Jul 16, 2024 · 1 comment
Open

get_unstable_period gives 0 for all functions with unstable period #664

TsiVit opened this issue Jul 16, 2024 · 1 comment

Comments

@TsiVit
Copy link

TsiVit commented Jul 16, 2024

Trying to understand why RSI has unstable period (according the docs), I explored that this period given not correct with "get_unstable_period" function

for name in [
            'ADX', 'ADXR', 'ATR', 'CMO', 'DX', 'EMA', 'HT_DCPERIOD',
            'HT_DCPHASE', 'HT_PHASOR', 'HT_SINE', 'HT_TRENDLINE',
            'HT_TRENDMODE', 'KAMA', 'MAMA', 'MFI', 'MINUS_DI', 'MINUS_DM',
            'NATR', 'PLUS_DI', 'PLUS_DM', 'RSI', 'STOCHRSI', 'T3', 'ALL'
        ]:
    print (name, talib.get_unstable_period(name))

ADX 0
ADXR 0
ATR 0
CMO 0
DX 0
EMA 0
HT_DCPERIOD 0
HT_DCPHASE 0
HT_PHASOR 0
HT_SINE 0
HT_TRENDLINE 0
HT_TRENDMODE 0
KAMA 0
MAMA 0
MFI 0
MINUS_DI 0
MINUS_DM 0
NATR 0
PLUS_DI 0
PLUS_DM 0
RSI 0
STOCHRSI 0
T3 0
ALL 0

@mario4tier
Copy link
Member

This works as expected.

By default, TA-Lib does not remove any of the "unstable data", so all settings are zero.

It is up to the user to decide how much of the output should always be removed with talib.set_unstable_period().

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants