Newbie Questions and Composites.

Forums › ProRealTime English forum › ProBuilder support › Newbie Questions and Composites.

Viewing 9 posts - 1 through 9 (of 9 total)
  • 03/19/2016 at 9:47 PM #3996
    xel

    Hi there.

    Im currently start learning ProBuilder language in order to port some of my indicators from Pine’s TradingView, given the lack of screening functionality of this excellent HTML5 platform, then I found that ProRealTime is another excellent (but more battery hungy for my laptop) application for this purpose with a same cheap EOD quality data and indicator programability.

    Some questions still came to mi mind but in fact just one important:

    1.  ProRealTime have a same kind of functionality as TV to make “Compostie charts” with +, -, *, / operators on the fly..?  (example a relative force chart of: USDMXN/DXY) or…
    2. Does they need to be generated by code…?
    3. If this functionality is present, can we make “virtual symbols” of this own created composites, for example; generate “indexes” for a given sector , industry, exchange, whatsoever..?

    Thanks in advance, an I hope this platform can fulfil this kind of requirements.  I think that keeping in using platforms like AmiBroker with external Data retrieval are from a Windows 95 “old” era, and in some cases and not able to watch from mobile devices.

    Cheers!

    Ricardo M.

    03/20/2016 at 1:29 PM #4011
    Nicolas

    Hello Ricardo, nice to have you on board.

    At the moment, the possibility to make composite instrument is not present in the platform. But I know that multi-symbol coding will be available soon as IT-Finance engineers are working on it. This is something that a lot of people will be glad to have for coding purpose such as “relative strength” between instrument, spread trading, .. and also composite experiment like you do.

    This kind of functionality mean a lot of work in ProRealTime code backend and like any other customers willingness, we must be patient and keep playing with all the possibilities that ProRealTime has to offer actually 🙂

     

    03/20/2016 at 9:15 PM #4013
    xel

    Thanks a lot Nicolas!

    I forgot just another question.  In the other cloud platform (TV), we have the ability to define “functions” inside the code.  From what I have been reading from ProRealTime coding docs; here we have functions that can be written as -separete formula files- and that can be recalled from other’s, much more like in Amibroker, Am I wright here..?

    An actual example from a first code I want to port will be to write this 2 functions already at TVPine’s:

    beta(array,period) =>
    val1 = sum(n*array,period)-(period*sma(n,period)*sma(array,period))
    val2 = sum(pow(n,2),period)-(period*pow(sma(n,period),2))
    calcB = val1/val2

    alpha(array,period) =>
    calcA = sma(array,period)-(beta(array,period)*sma(n,period))

    Where “n” in pinescript is an internal variable that returns “current bar number” and “pow” a given power.

    Thanks in advance!

    😉

    03/21/2016 at 10:28 AM #4027
    Nicolas

    You cannot make function as you named it, because the ProRealTime engine is more efficient while rewriting each time the whole formula. Also there are no arrays to be parsed into function, if you want to calculate a whole group of informations, you’ll have to do it “on the fly”. You can recall other indicators in another one with the “CALL” argument, but it is always a better idea to have only one prorealtime code file with all codes in it.

    I have already transcript pinescript code into Prorealtime, we can work together on your first conversion if you like. Just drop here your code.

    03/21/2016 at 9:36 PM #4054
    xel

    Thanks Nicolas!   I will start playing with the transcript.  I will share it up here, I always like to make them publicly available given the feedback and “improvements” we can have each other.

    03/23/2016 at 7:11 AM #4134
    xel

    Already made my first Transcript from one of my indicators.  You can review it here in favor of what could be cleaned up for speed optimization.

    I already do not wrote SCREENER capabilities (that what I am here indeed).  If you could help with that I will be very gratefully…

    Cheers and thanks for everything Nicolas!

    usdmxnd-14587125134pcl8

    03/23/2016 at 12:04 PM #4148
    Nicolas

    Thank you xel, I reviewed your post and add it to the Library. Very well and documented contribution, thank you.

    If I understand you clearly, now you want to make your indicator a screener? If so, then you simply have to copy/paste your indicator code into a new screener (better do that than use of CALL function) and add conditions for what do you want the screener to fetch for you.

    For example,  a low piercing the lowest wide band :

     

    Get it?

    03/23/2016 at 6:45 PM #4166
    xel

    Yeah, that’s what I was reading at documentation.   My concern it’s much more to input different ways to use this indicator for a screening conditions.  For me is relatively new when I code it at TV’s but given lack of screening, here is a better place to do that kind of research with community.

    One example that comes to mind is implement oscillators like Bollinger’s %B and WideB, then given the existence of two bands, make correlation Oscillators and see the behaviour with price action (volatility scenarios for healthy trend detection).

    Other great use of the bands is when used alongside Bollinger’s.  Given nature of the former one (LinReg), it tend to move “faster” than the Simple Average Bollinger nature, so you can have better control of the trend with both.  This are some ideas!  Here is an example of a Total US Market CAP ETF with both bands applied with a Yearly (52 weeks, or could be 252 days) rolling-back period.

    By the way, I try to setup the “Transparency” of the Coloured area without any visible change.  I like the bands quite shaded to get a cleaner look of the chart for other annotations like trend lines, Fibonacci’s, etc…  Im using ProRealTime 10.2  – 1.8.0_45.  Is this an issue of this version or a normal behaviour of the platform..?

    ¡Saludos desde Méjico!  😉

    VTI-W

    03/28/2016 at 10:07 AM #4498
    Nicolas

    Hey xel, didnt see your message before now. There is no way to add conditionnal transparency as for the 10.2 version. You’ll be able to do it when the prorealtime 10.3 version will be available.

  • Author
    Posts
Viewing 9 posts - 1 through 9 (of 9 total)

Find exclusive trading pro-tools on ProRealCode Marketplace

Similar topics:
cfd autotrading – marketplace vendor – questions, announcements and updates
questions on market data
v12 – questions, problems & praise!

Create your free account now and post your request to benefit from the help of the community
Register or Login