Platform V12 – Your Biggest Annoyance Currently??
- This topic has 33 replies, 6 voices, and was last updated 1 month ago by
.
-
It is looking like another 12 months before we have v13 (beta?) so we still have a chance to get it right this time and to make sure our annoyances don’t appear in v13??
So please keep it short and sweet … what is the ‘biggest annoyance’ you currently experience using the PRT Platfrom v12?
For me, it is having to drag down the Definition of Variables (DoV) window several times to see the scroll bar and the number of combinations – see attached for example of DoV window.
During, for example, 10 optimisation runs, I need to drag down the top of the DoV window around 40 times … hence my annoyed feeling of … when is this bug ever going to get fixed … we have been higlighting this bug / Issue for several years over several previous versions!
If anybody knows if this will be fixed in v13, please let us know and put us out of our misery??
3 users thanked author for this post.
I wish ALL windows and scales, no matter if it’s a backtest, screener or indicator, performance dashboard, optimization, chart, variables (included backtest variable window etc…) were always saved on exit so that you don’t have to readjust them every time!
4 users thanked author for this post.
I’m not as advanced as you guys but I’d like to look at a way to better manage CLI prints, ordering them that kind of thing. (Along the lines of what Roberto’s saying)
1 user thanked author for this post.
Finding back the by the system/broker killed orders which first end up nicely in the top pane (completely useless – or allow to restart them from there !), to next end up somewhere, almost untraceable – worse than when the top pane was not there. With one killed system … maybe barely doable. With more systems ? extremely painful and prone to making mistakes.
1 user thanked author for this post.
Was only one entry allowed ? 😉
The sheer fact that after 18 hours – which factually has become 16 – a prompt occurs with the 18 hour message, and when that occurs during typing elsewhere (e.g. a Word document) and that with your record breaking typing speed of 500+ per minute, you hit the space bar before you know it, and
- the platform closes
- almost always in anomaly because at rebooting it from that situation omits all the lists you had on screen. No way to restore that other than manually because that state got saved.
Additionally, when you do not hit the spacebar abusively and nicely answer “later please”, the popup message disappears all right waiting for it to re-popup, but meanwhile the platform receives and maintains to have the focus, waiting for your speedy input to spread everywhere. I just had to kill 4-5 forms/popups I never saw before because of the “hot keys” triggering those subsequently. All I did was typing my name under an email I was finishing. Eh … this is dangerous.
P-E-T-E-R
1 user thanked author for this post.
worse than when the top pane was not there.
I agree, I’ve just had 14 Systems stopped and it’s a right faff / annoyance to get them all running again.
Of late, 95% of my stopped Systems are for ‘too many retries’ … how about you??
I think PRT tried to solve a problem (by introducing the top pane for stopped Systems) but they introduced an even worse problem.
What can we Suggest to PRT as a best solution re stopped Systems?
How about …
- Keep the top pane.
- All stopped Systems gain a tick in the box when they appear in the top pane.
- The tick remains in the box when the System dissappears down to the non-running Section.
- We can then easily restart Systems with ticks in boxes.
OR if we want to5. For ticked Systems, we can rework the code with a fix for the stopped reason (if we can remember what the reason was??)
I often make a brief 1 or 2 word note in the Comments column … but not when 14 Systems have ALL been stopped for ‘too many retries’ as just happened !!! )Better ideas most welcome??
I think 1,2,3,4 are a good idea. 5 won’t easily apply. Yea, if we could change the code directly AND maintain the statistics data connected – that would be great.
About the too many retries – we have talked about that a couple of times before : 19 out of 20 thrown outs are about too many retries of something. That what is found here (just hover) :
Hi #GraHal, had another look around this, if you activate and/or put the letter ‘Z’ as the first letter in the comments field of a system that your going to run, or running. Then when it get stopped and you ok the ‘Reason for stopping’ box, it ends in the ‘not running’ section. Then if a, or all your stopped systems end up back in the ‘not running’ section, if you index by the comments column in reverse order, all the ‘Z’ comments are at the top. If its set not to clash with other comments, then all the stopped systems are at the top of the list grouped. These can individually or grouped restarted. ‘Z’ appears to be the highest character in the list, but not checked every one. If a system is no longer required to be run , just remove the ‘Z’.
Regarding, the solution choice, I think a simple solution is to be able to restart the stopped system from the ‘stopped’ area. Mostly the stopped system are stopped not by choice. Its already possible to look at why stopped and close box to avoid ‘Acknowledge’ ing the reason. But the right click on the system shows a yellow ‘start’ icon, I presume this is yellow until its acknowledged, but then vanishes into the ‘not running’ area. If you could restart it straight from the ‘stopped’ area that would solve that problem if the systems does not need editing.
But if before, it just dumped them in the not running pane like it does now, there’s no further benefit, unless before you could see the stopped systems in the not running pane and treat accordingly.
Yes, druby, above is what used to happen and yes we could see the stopped Systems (in the non-running pane) as the yellow warning showed against non-running Systems until we clicked on the yellow warning etc.
1 user thanked author for this post.
What I would really love to see is … the reason for stoppage to automatically appear in the Comments column or better still a separate column.
More than happy if a code is used, for example … > retries (used for IG reason ‘retries exceeded the allowed number’ or whatever the full text is).
I guess above is asking too much?
Let’s keep thinking on what we want out of this? Also what is easy and practicable for PRT to implement?
One thing we agree on … the ‘top pane’ currently serves no useful purpose that we can determine??
Worse still the ‘top pane’ – in it’s present form – is a faffing annoyance??
1 user thanked author for this post.
Hi #GraHal, had another look around this, if you activate and/or put the letter ‘Z’ as the first letter in the comments field of a system
druby, I just tried it on two stopped systems, and it works marvelously.
I would have no further 1,2,3,4(,5) needs. I wish we found you sooner. Haha.Thank you !
1 user thanked author for this post.
Find exclusive trading pro-tools on 
