how to pass in custom input values?

[gbarton]

Greetings,
Great project you have here! I have been messing around with it and I am curious how one can pass in custom input values for when the indicator is run? Say something simple like:

/*==[ Equivalent PineTS ]==*/

//
//'My EMA Cross Strategy';

const emaLength = input.int(9, "Default ema length");

let ema9 = ta.ema(close, emaLength);
let ema18 = ta.ema(close, 18);

let bull_bias = ema9 > ema18;
let bear_bias = ema9 < ema18;

let prev_close = close[1];
let diff_close = close - prev_close;

let _oo = open;
_oo = math.abs(open[1] - close[2]);

How do I set this up so I can pass in 12 for emaLength?
Thank you!

[alaa-eddine]

hi @gbarton this is not supported yet but I'll introduce it in a near future.
right now I'm preparing the next release that will introduce the possibility of running PineScript code directly.

for the custom input values, there will be a possibility to pass them by code, and also using QFChart (the visualization layer for PineTS) ==> https://quantforgeorg.github.io/QFChart/demos/full.html

it's in the roadmap, but I'm prioritizing PineScript source support

[gbarton]

Oh that's interesting ok, removing the half step of converting would be awesome. Which branch are you doing the new work on? I have time coming up over the holidays and would not mind helping. Do you have any issues on the work open for discussion?

[alaa-eddine]

the current working branch is this https://github.com/QuantForgeOrg/PineTS/tree/transpiler/pine
the implementation is stable but I still need to add some unit tests for better coverage

you can check a unit test here where we run macd pinescript directly
https://github.com/QuantForgeOrg/PineTS/blob/transpiler/pine/tests/indicators/macd-pinescript.test.ts

as for contributions, one of the things that are easy to contribute and have true value, is implementing more market providers, currently PineTS only supports binance, adding support of https://alpaca.markets/ and https://massive.com/ APIs (or others) would make it possible to use PineTS with stock markets as well, not just cryptos.

plus alpaca provides very good data for backtesting (this is planed for future releases once new-full pinescript compatibility is achieved)

[gbarton]

ok will look at alpaca and see if I can make another provider. I had questions about providers, I wrote a postgres one that had paging built in before your latest pagination update came out. What made you chose to expose the pagination in the run vs in the provider?

[alaa-eddine]

@gbarton runtime pagination can use the provider pagination when available.
but it also allow handling realtime data, when you turn on pagination and you don't specify the end date, PineTS can keep querying the provider and returning a page with a single entry containing just the latest bar updated.

this allows handling realtime market data