Centralization of queries and suggestions on ProRealTime

Forums › ProRealTime English forum › ProRealTime platform support › Centralization of queries and suggestions on ProRealTime

Viewing 15 posts - 211 through 225 (of 359 total)
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24
  • 04/10/2018 at 10:35 AM #67885
    JC_Bywan

    I don’t remember having modified any option to access or hide this, maybe this short PRT video will be more helpful, from 1mn33:

    https://youtu.be/eH6xxYJFMbE?list=PLGw_ZtCHrQ9jS4MSAz67rdmuxka7Kyvrr&t=93

    2 users thanked author for this post.
    avatar robertogozzi, avatar GraHal
    04/10/2018 at 11:27 AM #67888
    robertogozzi

    Perfect, thank you Noobywan.

    04/19/2018 at 9:08 AM #68752
    SebTrades

    Here are a few wishes for improvements of the ProRealCode language (and programming interface) :

    1/ It would be much more efficient to let us declare variable to optimize directly in the code, in the following way :

    Once Var1 = [1;20][1]   if I want to find the optimum value of Var1, between 1 and 20 with a step of 2

    Once Var2 = [6] means that I want Var2 to be set at 6, but anyway to show it in the optimization window result

    This is exactly the syntax that is used to summarize the list of variables to optimize.

    The idea is not to remove the detailed pop-up window for newbies; keep it, it’s pedagogical for those who are not familiar with the syntax.

    But for those who are regular programmers, it would be faster to allow also the other way.

    2/ It would be nice to have a command like REPORT (in indicators) for showing the result of a variable in the back-test optimization results table.

    3/ Choice of optimization

    The current back-test optimization selects the top100 results by profit.

    It would be interesting to select the kind of optimization expected : 1/ Absolute Profit (like now) 2/ Profit/Drawdown ratio 3/ Drawdown value

    4/ Let us change the order of variables to optimize by simply dragging them in the variables definition window.

    (Instead of having to delete/re-create)

    04/19/2018 at 9:09 AM #68753
    SebTrades

    Here a few of my ideas on how to improve the user interface on PRT BackTest :

    1/ How about making a unique window that contains code, optimization report, and detailed report? All-in-1, with 6 tabs : Code, Optimization Report, Results Summary, Stats of closed positions, List of orders, List of closed positions

    2/ Optimisation Results :

    2.1/ Make columns width auto-adaptative, based on the number of digits of the content (and not based on the title). For title, use 2 or 3 lines to display all or enough of it using automatic text break to next line.

    2.2/ Show the progress bar of the back-test in the title bar of the optimization report (instead of separate window).

    2.3/ Add to progress bar the information about how many tests have been processed / total number of tests to process + estimation of time left + warning if time left < session remaining time.

    3/ In the Code Editor :

    3.1/ When doing a find/replace, pressing replace looks forward to find the searched text, replaces it… and stays there.

    Suggested improvement :  look forward to find the searched text, replace it and position the search on the next occurence [or alert that there is no more occurence and propose to restart from the beginning of the code]

    3.2/There should 2 buttons for making the code become a comment / a comment reverting to code, with the latter really removing all ‘/‘ preceding the code (sometimes can be more than 2 if it was inserted manually)

     

    04/19/2018 at 9:11 AM #68754
    SebTrades

    Add a RANDOM function in the language

    04/19/2018 at 7:37 PM #68843
    GraHal

    I recently re-started trading on 25 Systems on my wife’s Demo CFD account. They had been stopped a while ago by the stupid valid until date (I do understand the logic of this from IG’s point of view).

    12 of the Systems were rejected due to min lot size too low!

    Now I have to copy the System paste it into the Backtesting window, change Lot size 1 to Lot size 2 and then prepare for Auto-Trading again!  As if all the faff was not bad enough, my man gripe is that I now have lost all the Performance History on the 12 Systems and I start from 0 gain again!

    Come on PRT can’t you make it so that Lot size can be changed directly in the ProOrder AutoTrading Window so that Performance History can be retained with the System??

     

     

     

    1 user thanked author for this post.
    avatar Vonasi
    04/20/2018 at 3:02 PM #68877
    Vonasi

    It is frustrating to start a strategy backtest and then find the results to be fantastic only to realise that you forgot to turn tick by tick testing on.

    When we test our coded strategies it would be great if PRT could automatically detect whether tick by tick is needed or not. The only time it is needed is if there are SET order instructions or STOP and LIMIT orders that mean that positions open and close mid candle. A simple check for these words in the code would enable it to be automatically turned on or off. This would save newbies a lot of confusion and reduce the risk of them putting what they think are great strategies live when they are in fact awful strategies but they just did not notice the ‘ProBacktest in tick by tick mode’ tick box.

    06/13/2018 at 1:35 PM #73095
    pableitor

    I’d like to test a few strategies on multiple instruments at the same time , it would be great getting the combined results of these backtests in just one chart.

    07/01/2018 at 8:20 AM #74977
    Vonasi

    Following on from my experience here:

    https://www.prorealcode.com/topic/tick-by-tick-not-working-correctly/

    I would like a warning message if a back test with tick by tick data turned on is attempted while not connected to PRT as the results returned are not done with tick by tick and could lead someone to believe they have a good strategy when in fact it is not a good strategy.

    07/13/2018 at 7:52 AM #75893
    GraHal

    Great idea and so obvious bearing in mind the 25 x System limit we have on Demo Forward Test? It might even reduce the load on the overworked PRT Servers!?

    In the Trading System Description box (image 1) we need the ability to add an image (not just text).  We can then add a screen shot of Backtest results (image 2).

    Then after 1 month / 6 months /  whenever (depending on System Timeframe) we run the Backtest again and check how the new BT results compare with the old results.  A close match will be an indication of consistency of performance and maybe, just maybe translate into consistent Forward Test Results.

    Okay I know, currently, we could laboriously write out the BT results in text but it’s so much faffing and it feels like stepping back in time 25 years when there are so much easier ways of doing things!?

    GraHal

    07/15/2018 at 10:31 PM #76060
    Roberto S.

    Hi, I would like to create an indicator able to draw a candle in the past (maybe just changing the color).
    Let’s take for example the “Master candle”: if the last 3 candles are inside the 4th previous candle, I want to update that candle in a different color.
    Unfortunately I can’t and the only way I could think as a workaround is to draw something else (e.g. a drawSegment).
    In order to fix this, I think you could allow a 5th parameter to the drawCandle command. By default it could match the barIndex value. But if the developer want to change the 4th previous candle, he could write:
    drawCandle(open[3], high[3], low[3], close[3], barindex -3) coloured (0, 0, 255)

    What do you think?
    Regards
    R

    07/17/2018 at 8:29 AM #76109
    David

    Optimisation completion notification.

    When optimisation is complete receive a sound and/or email notification.

    08/06/2018 at 10:10 AM #77619
    GraHal
    1. The optimiser needs to allow for setting the Range and Step before clicking Add.
      Reason: I often find myself setting up Labels – ABCD for TP and SL  2 for Longs and 2 for Shorts. I don’t want 1 to 10 in steps of 1 (rarely ever do need this set up) but I do want 10 to 100 in steps of 10 and I want it 4 times! 🙂  So I end up having to change the default 1 10 1 and change it 4 times over to 10 100 10 4 and it’s all faffing / frustrating.
    2. It would also be good if the order of the Labels  could be changed by a click up click down thingy to move the order.
    3. Also be good if favourite Ranges and Steps could be stored so we not need to enter the same figures time after time after time … we could just select the saved set from our personal data.
    4. Alternative to above (maybe even better?) would be 2 drop downs with selectable Ranges and Steps … yeah that has to be easier for PRT to arrange than 3. above?  In fact if you do this No 4 idea then you don’t even need to do No 1. above at all! 🙂
    08/06/2018 at 11:11 AM #77626
    Leo

    I would like to Launch my backtest in my Computer and not in the PRT Server…

    I still not knowing why the backtest is remote.

     

    10/12/2018 at 2:15 PM #82650
    Vonasi

    I find having to extend the validity of ProOrder strategies running live to be very annoying. I understand the need for an expiration time/date to ensure that strategies are not left unattended for long periods and are shut down if they are. I think it would be better if every time we open our platform the expiration date is increased – that way there is a direct link between activity and the expiration date.

    Even if when we open the platform we were automatically asked if we wanted to extend the expiration it would be less annoying than finding all your strategies have been stopped just because you forgot to extend them. Restarting them all is a tiresome repetitive process

    The new email feature when getting close to an expiration date is a good new feature but it is still open to potential problems if someone does not read their emails in time or reads them but does not have access to the platform immediately and then forgets to extend them so I think activity based extending is a better solution.

  • Author
    Posts
Viewing 15 posts - 211 through 225 (of 359 total)
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24

Find exclusive trading pro-tools on ProRealCode Marketplace

Similar topics:
buy on certin dates, not on technical singal
coding error on prorealtime
prorealtime issues on ig
trailing stop on ib – stop repositioning on dax
10ema/30ema crossover on weekly charts?
2 accounts limitations on ib
array support resistance buy on midlevel
automatic trading on ib stocks and etf
bollinger %b does anyone have the exact code as used by prorealtime
build ea bassed on indicatir

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