bbta 0.3.0

python bindings for banta

BanTA Technical Analysis Library

中文文档
banta is a high-performance technical analysis indicator library that supports both state-caching and parallel computation modes. It aims to provide a highly flexible, high-performance, and user-friendly indicator framework.

• State-Caching Mode: Updates and caches on each candle, eliminating the need to recalculate historical data. Indicator results are globally reused, similar to TradingView.
• Parallel Computation Mode: Computes all candles at once without caching. New candles require a full recalculation, similar to TA-Lib.
• NaN Compatibility: Intelligently skips NaN values in input data, resuming calculations with the previous state.
• Rigorous Testing: Each indicator is validated with unit tests under various conditions and compared against results from common indicator libraries.
• Lightweight & Dependency-Free: Pure Go implementation with zero external dependencies.

Supported Indicators

Consistency Comparison with Common Indicator Platforms

banta	MyTT	TA-lib Class	TA-lib Metastock	Pandas-TA	TradingView
AvgPrice	✔	✔	✔	✔	✔
Sum	✔	✔	✔	✔	✔
SMA	T1	✔	✔	✔	✔
EMA	T1	T1	✔	✔	T2
EMABy1	✔	T1	T2	T2	T3
RMA	--	--	--	T1	--
VWMA	--	--	--	✔	✔
WMA	✔	✔	✔	✔	✔
HMA	--	--	--	✔	✔
TR	--	✔	✔	✔	--
ATR	T1	✔	✔	T2	T3
MACD	T1	T2	T1	✔	T3
RSI	T1	✔	✔	T2	T3
KDJ	T1	T2	T1	T3	✔
Stoch	--	✔	✔	--	✔
BBANDS	✔	✔	✔	✔	✔
Aroon	--	✔	✔	✔	T1
ADX	--	✔	✔	T1	T2
ADXBy1	--	T1	T1	T2	✔
PluMinDI	--	✔	✔	--	--
PluMinDM	--	✔	✔	--	--
ROC	✔	✔	✔	--	✔
TNR/ER	--	--	--	--	--
CCI	✔	✔	✔	✔	✔
CMF	--	--	--	✔	✔
KAMA	--	✔	✔	T1	✔~
WillR	--	✔	✔	✔	✔
StochRSI	--	✔	✔	✔	✔~
MFI	✔	✔	✔	✔	✔
RMI	--	--	--	--	✔~
CTI	--	--	--	✔	T1
LinReg	--	--	--	✔	?
CMO	--	✔	✔	✔	T1
CMOBy1	--	T1	T1	T1	✔
CHOP	--	--	--	✔	T1
ALMA	--	--	--	✔	T1
Stiffness	--	--	--	--	✔
PercentRank	--	--	--	--	✔~
CRSI	--	--	--	--	✔~
CRSIBy1	--	community	--	--	--
DV	--	--	--	--	--
UTBot	--	--	--	--	✔
STC	--	--	--	--	✔

--  This platform does not have the indicator  
✔  Consistent with this platform's results  
✔~ Mostly consistent with this platform's results (minor deviations)  
Ti Inconsistent with this platform's results  

How to Use (State-Caching Mode)

import (  
	"fmt"  
	ta "github.com/banbox/banta"  
)  

var envMap = make(map[string]*ta.BarEnv)  

func OnBar(symbol string, timeframe string, bar *ta.Kline) {  
	envKey := fmt.Sprintf("%s_%s", symbol, timeframe)  
	e, ok := envMap[envKey]  
	if !ok {  
		e = &ta.BarEnv{  
			TimeFrame: timeframe,  
			BarNum:    1,  
		}  
		envMap[envKey] = e  
	}  
	e.OnBar(bar)  
	ma5 := ta.SMA(e.Close, 5)  
	ma30 := ta.SMA(e.Close, 30)  
	atr := ta.ATR(e.High, e.Low, e.Close, 14).Get(0)  
	xnum := ta.Cross(ma5, ma30)  
	if xnum == 1 {  
		// ma5 cross up ma30  
		curPrice := e.Close.Get(0) // or bar.Close  
		stopLoss := curPrice - atr  
		fmt.Printf("open long at %f, stoploss: %f", curPrice, stopLoss)  
	} else if xnum == -1 {  
		// ma5 cross down ma30  
		curPrice := e.Close.Get(0)  
		fmt.Printf("close long at %f", curPrice)  
	}  
	kdjRes := ta.KDJ(e.High, e.Low, e.Close, 9, 3, 3).Cols  
	k, d := kdjRes[0], kdjRes[1]  
}  

Core Concept

Traditional technical analysis libraries like TA-Lib and Pandas-TA are widely used and highly optimized for performance, making them extremely fast when computing hundreds or thousands of candles at once.
However, when your trading bot uses these libraries in live trading, every new candle requires passing in hundreds of historical candles. If you're running multiple symbols or operating on 1-minute or even 1-second timeframes, the computational delay can become unbearable.
Many are familiar with TradingView, which uses Pine Script—an event-driven technical analysis engine. It doesn't recalculate historical candles upon receiving a new one but instead reuses cached results.
This is the philosophy behind BanTA: event-driven computation, processing each candle as it arrives while leveraging cached results.

How State Caching Works in BanTA

In BanTA, state caching revolves around the Series sequence type. Most return values are sequences, and the Series struct includes a Data []float64 field that records the indicator's values across candles.
For example, e.Close is the closing price sequence, and e.Close.Get(0) retrieves the current closing price as a float64.
Calculating a moving average is straightforward: ma5 := ta.SMA(e.Close, 5), which returns another sequence.
Some indicators like KDJ return multiple fields: kdjRes := ta.KDJ(e.High, e.Low, e.Close, 9, 3, 3).Cols, where Cols contains an array of sequences (e.g., K and D lines).

How to Use (Parallel Computation)

import (  
	"github.com/banbox/banta/tav"  
)  

func main(){  
	highArr := []float64{1.01, 1.01, 1.02, 0.996, 0.98, 0.993, 0.99, 1.0, 1.02}  
    lowArr := []float64{0.99, 1.0, 1.0, 0.98, 0.965, 0.98, 0.98, 0.984, 1.0}  
	closeArr := []float64{1.0, 1.01, 1.0, 0.99, 0.97, 0.981, 0.988, 0.992, 1.002}  
	sma := tav.SMA(closeArr, 5)  
    ma30 := tav.SMA(closeArr, 30)  
    atr := tav.ATR(highArr, lowArr, closeArr, 14)  
    xArr := tav.Cross(ma5, ma30)  
}  

Note

For research purposes, we recommend using parallel computation to compute indicators in bulk. For live trading or event-driven backtesting, state-cached indicators offer higher efficiency.