Orphan Systems
Forums › ProRealTime English forum › ProRealTime platform support › Orphan Systems
- This topic has 9 replies, 4 voices, and was last updated 6 years ago by Despair.
-
-
05/29/2018 at 8:15 AM #71550
Just noticed 2 Orphan Systems on Demo Platform.
I definitely recall checking yesterday and all Systems running showed the Auto-System ‘cog’.
My settings in Options are as per attached and I haven’t made any changes external to the PRT Platform (it’s Demo so be pointless / no reason to).
Anybody else ever get this Orphan phenomenon??
05/29/2018 at 9:36 AM #7155605/29/2018 at 10:05 AM #71563Ive had this happen once in live, where the algo shut it self down, but the trade continued. The SCARY part was that the algo somehow failed when it was gonna set my stop loss SO IT NEVER DID! lol 😛
I checked the trade and went like “WAIT wheres my stop???” and i checked PRT and algo had stopped but trade was live…
05/29/2018 at 10:14 AM #71564Welcome to my world. I had this (in real money trading) many times. In all various forms. Strategy stopped and left trade open, opened orphan trade out of the strategy while the strategy was still running and so on. I reported this issue several months ago but never got an explanation or even solution to the problem.
This is one of the problems why I don’t think it is very smart to use PRT for real money trading.
05/29/2018 at 10:19 AM #71565@Despair: What do u use (without promoting it ofc!! haha) and does it use the same easy coding language?
Why and for what do u still use PRT? Is it better to backtest and shit using PRT, but u run the systems live on another platform?
Can u copy paste the codes in or do u gotta convert them?
how long have u been using something else than PRT? Any problems so far?
Pro’s and cons?05/29/2018 at 10:42 AM #71567I’m in the progress of switching to matlab. This works great so far but (now the answers to all your questions):
1.) Matlab uses matlab (obviously) as language and not Probuilder. Matlab is a multi-purpose programming language specialist on array processing. Matlab is surely much more complex then Probuilder but offers also much more possibilities.
2.) Right now I’m still running a few strategies on PRT (the ones that I haven’t converted yet). Also it PRT. is great to quickly test an idea (as long as it is simple). Another thing that is nice is to have the visual capabilities of PRT. So I can use it to track my matlab strategies (when my matlab strategy places a trade vie IG’s API the trade pops up in the PRT chart. Anyway I will lose this on the long run when I transfered all my strats to PRT they will sooner or later ask for payment for PRT since no trades are placed and then it is over for my PRT usage (I will definitely not pay for it).
3.) As I wrote above math is a programming language but no trading platform. So if you want to run backtests or whatever you will have to program this yourself.
4.) Copy/paste definitely will not work. 🙂
5.) I started to have a closer look at matlab hmm maybe 3-4 months ago when it became more and more obvious that there are too many problems running live with PRT. The first time I was not really motivated because it seemed simply too much work. Especially the communication with IG I was a little bit unsure how easily I could fix but now a few weeks ago an error in PRT caused a bigger loss in my account (still under investigation form PRT and IG) and this was for me the point where I said to myself that this has to stop.
Since then I made great progress. Programmed two toolboxes one for IG and one for IB which handle the broker communication and much more.
So for me it was the right choice to switch but I can tell that it is a big step since you virtually have to program all yourself and have no inbuilt functionality which for example PRT offers. So if you don’t feel comfortable with bigger programming tasks this is probably not the right choice for you.
And of course, there will be also problems BUT the big difference is simply that if you program everything yourself you can also debug every aspect and when there occurs an error you can fix it. When an error occurs between PRT and IG you can report this error to PRT and wait for them to solve it. Well and I’m a little impatient so I prefer to fix it myself.
1 user thanked author for this post.
05/31/2018 at 1:38 PM #71857Hello,
In order to allow us to analyze your platform, please send us a technical report by following these instructions:
- As soon as you encounter the issue, go to the “Help” menu on the ProRealTime toolbar.
- Click on “Technical support”
- Select “Code”
- Give as many details as possible, explain the issue you are having in the text box and mention the name of the code you are referring to.
- Click “Send report”
This will send us a report containing technical information concerning your platform, which will allow our technical team to run a diagnostic analysis of the issue you have come across.
Regards,
Carine
05/31/2018 at 1:42 PM #7185806/01/2018 at 1:04 PM #71943please send us a technical report
I agree with Despair>
Rightly or wrongly I have got into a way of thinking there is no point sending Technical Reports as there is little or no ‘closing of the loop’ (as we used to say when I was a QA Manager! 🙂 ).
I will however try and remember next time to send a Technical Report.
It would encourage users to send Reports if an acknowledgement email (with a copy of what we use valuable time to type) is sent back to the originator. Ooops I’ve said this many times also, but nothing seems to change??
06/01/2018 at 7:16 PM #71987 -
AuthorPosts