You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hmm, I assume you mean programmatically, and I'm not sure if that's available. Would have to look through some of the Abstract API features in the underlying C library.
Yes, I just wanted to see if it was possible programmatically. If its not I guess I will just have to find the values myself. Thank you for the quick response
Sadly, no: TA-Lib C has no min/max for continuous outputs such as RSI. Bounded indicators give their range on their ta-lib.org page, e.g. RSI (0 to 100) and WILLR (-100 to 0).
Pattern outputs (CDL*) do declare their exact values in output_flags: 0, or a sign times 100, plus 80 with "Weak Pattern" and 200 with "Confirmation Pattern" (see the output flags). #778 corrects those descriptions; it takes effect with the next TA-Lib C release.
Activity
mrjbq7 commentedon Nov 2, 2016
Hmm, I assume you mean programmatically, and I'm not sure if that's available. Would have to look through some of the Abstract API features in the underlying C library.
dawhitefish commentedon Nov 2, 2016
Yes, I just wanted to see if it was possible programmatically. If its not I guess I will just have to find the values myself. Thank you for the quick response
mrjbq7 commentedon Nov 2, 2016
You might look through the
output_flagsof the Abstract API:The
output_flagsis an enum with these possibilities:https://github.com/mrjbq7/ta-lib/blob/master/talib/abstract.pyx#L496
mario4tier commentedon Oct 23, 2026
Sadly, no: TA-Lib C has no min/max for continuous outputs such as RSI. Bounded indicators give their range on their ta-lib.org page, e.g. RSI (0 to 100) and WILLR (-100 to 0).
Pattern outputs (
CDL*) do declare their exact values inoutput_flags: 0, or a sign times 100, plus 80 with "Weak Pattern" and 200 with "Confirmation Pattern" (see the output flags). #778 corrects those descriptions; it takes effect with the next TA-Lib C release.Describe every TA-Lib C flag in the abstract API