PRT v11.1 BUGs

Viewing 14 posts - 1 through 14 (of 14 total)

Author

Posts
01/12/2021 at 4:34 AM #157436 quote
AndyY2020
Participant

New
I’ve been using ProRealTime for 5 years now and I have to say I’m really really unhappy with the v11.1 update. It’s terrible and full of inexcusable bugs. The most important being the system is inconsistent with whether it uses the timezone of the chart window or the market trading timezone for constants. In v10.3 and before everything was always in the local timezone you set your chart in yourself. Now

OpenDate, CurrentDayOfWeek, Day, Days, DayOfWeek, Date, OpenDay, OpenDayOfWeek and Today are all set to the timezone of the market being traded.

IntraDayBarIndex still follows the chart window timeframe though. This leads to ridiculous output when you set your chart timezone to one that is different from the market timezone. Set the chart to UK time and trade US30 (through IG index) and the IntraDayBarIndex starts on Sunday night at 23:00 at 0. Then runs 0,1,2,3,0,1,2,3,4 etc but the 0 reset at midnight Sunday still stays as Sunday in CurrentDayOf Week!

I ran the following test script in one of my IG live accounts, backtested on a 15m chart with my chart set to UK time on US30.
```
MyBuySize = 1

//select which constant you wish to test my adjusting the comments bars //
//MyCond = OpenDate <> OpenDate[1]
//MyCond = CurrentDayOfWeek <> CurrentDayOfWeek[1]
//MyCond = Day <> Day[1]
//MyCond = Days <> Days[1]
//MyCond = DayOfWeek <> DayOfWeek[1]
//MyCond = Date <> Date[1]
//MyCond = OpenDay <> OpenDay[1]
//MyCond = OpenDayOfWeek <> OpenDayOfWeek[1]
MyCond = Today <> Today[1]

If (NOT LongOnMarket AND MyCond) THEN
BUY MyBuySize LOT AT MARKET
SET STOP LOSS 50
SET TARGET PROFIT 50
Endif
```
Then when you look at the closed positions record of the backttest report to see what time it opened a position, which is equal to what time it thinks a new day starts, the following results are shown:

OpenDate <> OpenDate[1] is triggered at 05:15.

CurrentDayOfWeek <> CurrentDayOfWeek[1] is triggered at 05:00

Day <> Day[1] is triggered at 05:00

Days <> Days[1] is triggered at 05:15.

OpenDay <> OpenDay[1] is triggered at 05:15.

OpenDayOfWeek <> OpenDayOfWeek[1] is triggered at 05:15.

Today <> Today[1] is triggered at 05:00

These constants always used to trigger at midnight of the timezone of the chart.

This is an unacceptable bug to go live with.

Additional, smaller problems:

1) The backtesting engine is about 1/20th the speed it used to be. It now takes 2-3 minutes to backtest a script that used to take seconds in v10.3.

2) The Help Centre error reporting function does not work and would not allow me to share the above script that way.

3) The redesign is horribly ugly. All the nice easy to use buttons are gone or hidden in smaller sizes in obscure places. Closing a backtest window is now buried in a drop down menu.

4) The window showing which strategies you have running is now so badly laid out it’s almost unreadible. Nice neat windows in v10.3 are now columns only a few milimeters wide with unreadible text. Useful parts like ‘running’ or not running are gone.

5) The results report is now also horrible. The text has been shrunk so small it’s unreadible. % returns are gone.

Please abort this horrible new version and go back to 10.3. You are messing with peoples money when you make these changes and mistakes.

OboeOpt and Kovit thanked this post
01/12/2021 at 8:52 AM #157446 quote
Vonasi
Moderator

Master
AndyY2020 – Welcome to the forums but please re-read the forum rules before posting again in them. Especially this one:
- Always use the ‘Insert PRT Code’ button when putting code in your posts to make it easier for others to read.
Your post has been edited to tidy it up.

Insert-PRT-Code-Button-2.png
01/12/2021 at 10:57 AM #157484 quote

GraHal
Participant

Master

AndyY2020 wrote:

The window showing which strategies you have running is now so badly laid out it’s almost unreadible. Nice neat windows in v10.3 are now columns only a few milimeters wide with unreadible text. Useful parts like ‘running’ or not running are gone.

Click on the spanner / wrench and deselect a few columns and click optimise and you will see all text easily in the columns.

You can see from my workspace that ‘running’ and ‘not running’ is still available.

GH-2.jpg

01/14/2021 at 9:01 AM #157749 quote

PeterSt
Participant

Master

AndyY2020 wrote:

2) The Help Centre error reporting function does not work and would not allow me to share the above script that way.

Andy, can you elaborate on this one ?

3) The redesign is horribly ugly. All the nice easy to use buttons are gone or hidden in smaller sizes in obscure places. Closing a backtest window is now buried in a drop down menu.

Things could be personal, but I am using V11 for over a year now, and yesterday I had to do something in 10.3. No-way I would ever want to go back to that by now “old fashioned” version. Mind you, I am talking about the interface/GUI. I am not judging your other issues here …

5) The results report is now also horrible.

I need to agree with you there. But for one reason only : nothing in that “coding area” is f** saved !!! IOW, once it is not to your liking, you keep on changing it to your likings infinitely. Man, I have better things to do ! … But who is finally bombarding PRT with this ?
(ahem, should be me, perhaps)

01/14/2021 at 10:51 AM #157772 quote

GraHal
Participant

Master

PeterSt wrote:

nothing in that “coding area”

I am confused what we are referring to here?

We need to use the title at the top left of each window?

AndyY2020 – Results Report,

PeterSt – Coding Area

… surely you can’t both be referring to the same window??

01/14/2021 at 8:09 PM #157887 quote

PeterSt
Participant

Master

@GraHal, Coding Area :

ALL what is about coding. Programming / Making your Algos / Systems / Reports of the results / Variables screen / Column widths / … / … / … /
whatever.

If you (guys) don’t notice then there is something wrong with my PRT. But I am afraid your just got used to it. I did not recognize much difference with V10.3. But indeed V11(.1) got even worse.
I seek for high bridges daily. 🙂 … but all together I like it way too much to jump.

?

With the normal (manual) trading environment nothing it wrong. Just nothing that I can see. Possibly this is because I “caused” quite many issues to be solved in that “area” which I don’t attempt at all in the Coding area ? I would be honored.

Edit : PS :
PRT Support over here told me the other day that I cause 294 or so tickets. They must hate me. But I love them. Haha.
Anyway, I am serious …

01/14/2021 at 8:19 PM #157889 quote

PeterSt
Participant

Master

PPS: See attached. I’m really bad (Sent). But all in the best spirits and enormously helpful (hopefully to everybody). Mostly reporting; hardly asking for help. And please not to forget – I think PRT is the best platform out there with the best support anywhere. Still there’s lot to improve, as with any larger software system.

image_2021-01-14_201941.png

01/14/2021 at 8:20 PM #157891 quote

GraHal
Participant

Master

PeterSt wrote:

nothing in that “coding area” is f** saved !!!

Users can at times decry PRT Platform due to incorrect usage (I’ve done it myself! 🙂 ).

Your comment above was made after Andy2020 said … The results report is now also horrible.

I have saved my preferred layout for the Results Report / Detailed Report …. maybe I can help you save yours?

01/15/2021 at 12:49 AM #157899 quote
PeterSt
Participant

Master
PeterSt wrote:

@GraHal, Coding Area : ALL what is about coding. Programming / Making your Algos / Systems / Reports of the results / Variables screen / Column widths / … / … / … / whatever.

@GraHal, please … don’t you recognize *anything* of this ? Example … (attachment) … and this is ONE out of *all* the screens out there (coding and Backtesting environment), … I will try to be exhaustive … this is after the (daily) necessary restart of PRT after 18 hours
1. The height and width of this screen (please don’t forget – it is only one screen example !);
2. The width of the columns in there;
3. The start date applied *hence* the amount of bars in there (always defaults to 10K because the Chart it bases upon does so);
4. Where this form is positioned on the monitor;
5. It feels like many things more because this is not all what is related to this screen. It all combines. See for example #3 and its implications.
I have just been working for 15 minutes to set all in a workable fashion again. Each time I need to restart PRT it is the same thing. And all I do is Save – Exit – Restart. Nothing is saved if it only relates to “coding”.
One thing : I see I just received a new version (Jan 13) and maybe things changed for the better (this too was announced by me 10 or so times). But I am not going to try because it could consume another 15 minutes of sleeping time.

So with the example I gave … is all with this screen saved for you and brought back at a restart ? If Yes, tomorrow I will give you a next example. I am obviously eager to have this fixed.

Thank you !
Peter

image_2021-01-15_002650.png
01/15/2021 at 9:54 AM #157916 quote

GraHal
Participant

Master

PeterSt wrote:

The height and width of this screen (please don’t forget – it is only one screen example !);

Yes I do understand all what you have listed.

The above is my No 1 gripe! Drives me nuts!

As you say, there are many screens that need maximise / minimise buttons including the normal save when closed in a ‘Restore Down’ setting.

I would settle for just maximise / minimise buttons.

Have yoiu suggested above to PRT … I’m sure you have?

I will make a Suggestion to PRT and I will refer to each of the (many) screens that need max / min / save buttons.

PeterSt thanked this post

01/19/2021 at 4:48 AM #158420 quote

AndyY2020
Participant

New

Thank you for your comments.

For me, the point isn’t whether or not it is possible to change settings to get the system back to how it was before the upgrade. The point is the disruption and inconvenience of having to do this. My trading is my work. It’s not ok to log-in to work one morning and find that somebody has decided to completely reorganise my workspace causing me to have to waste hours learning the new arrangement.

The aesthetic issues are one thing. It is still very important that the timezone bug has been introduced now. The var ‘Hour‘ read from a different clock to the var ‘Day‘. This means if you are looking at your system on say UK time but looking at US30, PRT v11 thinks the time on Monday runs:

0:00 Sunday (should be 0:00 Monday), 1:00 Sunday (should be 1:00 Monday), 2:00 Sunday (should be 2:00 Monday), 3:00 Sunday (should be 3:00 Monday), 4:00 Sunday (should be 4:00 Monday), 5:am Monday (should be 5:00 Monday), 6:00 Monday (should be 6:00 Monday), etc, etc to 0:00 Monday (should be 0:00 Tuesday), 1:00 Monday (should be 1:00 Tuesday), 2:00 Monday (should be 2:00 Tuesday), 3:00 Monday (should be 3:00 Tuesday), 4:00 Monday (should be 4:00 Tuesday), 5:00 Tuesday (should be 5:00 Tuesday).

This is an inexcusable bug that totally screws your system if it checks the time of day as a risk parameter before trading.

01/19/2021 at 8:41 AM #158424 quote

GraHal
Participant

Master

AndyY2020 wrote:

5:00 Tuesday (should be 5:00 Tuesday).

I don’t follow what you are saying as the two time / day above read the same??

You don’t need to answer me, but maybe others don’t understand either what you are saying?

Anyway best to report what you are not happy with direct to PRT using the Form below …

https://www.prorealtime.com/en/contact

But be good for us PRT Users to understand first else PRT developers may also not understand what you state on the Form above?

Thanks

01/19/2021 at 1:00 PM #158482 quote

PeterSt
Participant

Master

GraHal wrote:

maybe others don’t understand either what you are saying?

I think I do …

5:am Monday (should be 5:00 Monday)

From there on suddenly all is right (including your quoted Tuesday). But preceding that all is off a day. This is double error; it is not correct and it is not consistent (though to deal with by means of a program (code).

GraHal thanked this post

01/21/2021 at 4:49 AM #158760 quote

AndyY2020
Participant

New

Yes, that’s the problem, It’s the fact that some vars look at the local timezone of your chart settings and some look at the original timezone of the market. When these are set differently you get bad results. Previously everything looked at the timezone you set yourself in your chart/platform. They have changed it in v11 and caused a bad bug as a result.

Say you only want to trade once a day or avoid certain times/days. It’s now impossible to use the vars ‘Day’ and ‘Hour’ in combination because they think a new day starts at different times.
Author

Posts