V12 – Odd or Annoying Happenings!?
Forums › ProRealTime English forum › ProRealTime platform support › V12 – Odd or Annoying Happenings!?
- This topic has 113 replies, 11 voices, and was last updated 1 month ago by druby.
-
-
09/26/2024 at 6:00 PM #23809609/26/2024 at 6:30 PM #238098
In my case of > 5 / 34 Sets etc then I will have to delete Sets down to < 5 and then I could do a Save from optimiser results table and choose the 2nd / lower option and this will give me a new System with my preferred variable values.
However, now I know what that > 5 Sets is all about then I could continue regardless until I hit some new maximum 100, 200 or whatever, but around 20 to 40 Sets for me would seem to get my Systems all fully optimised and ready to Test.
If I thought that having > 5 Sets in some way slows everything down (optimisation etc) then I would keep to < 5 Sets.
Can’t help thinking that it must affect something, even if only file size what with 34 Sets of maybe 11 or so variable values (400 values-ish) having to be retained in each of my files?? I doubt PRT will tell us?
It would make sense if the Warning about > 5 Sets would show when we save Set 6 Sets in the Definition of Variables window?
Thinking about it, I will try from now on to keep to < 5 Sets as I would not want PRT / IG to take away the new maximum for Running Systems on Demo Accounts. It’s so good to work on a System and then at the end put it straight to Test as a Running Systems and not have to juggle Systems to keep to 25 max Running as previously.
09/26/2024 at 8:02 PM #238107You could say, it’s all been a ‘storm in a teacup‘! 🙂
I got to thinking … how did I manage to get anything optimised without using SETS?? I checked and SETS are in v11 also and I never used SETs at all until about 3 weeks ago after PeterSt referred me to them. Roberto says he never uses SETs also.
I just did some tests and if we close the Definition of Variables window after each time we change variable values then optimisation runs fine … one does not have to use SETs at all.
I am saying above in case anybody reads the last 10 to 15 posts on this Thread and thinks … ‘wtf is GraHal on about, I’ve never used SETs and I’ve never had any problem whatsoever’?
I know … you were all too polite to tell me! 😀
09/26/2024 at 8:12 PM #23810809/26/2024 at 9:39 PM #238110Found how to display ‘Optimizer Report’ if closed, it appears in the system’s chart pane, top Left corner, name label pulldown list for the system, usually were configure lives.
However, only appears in list if one of the optimise variables is set to optimise. If all fixed then does not show.
Couldn’t find any thing about set limits.
1 user thanked author for this post.
09/27/2024 at 11:46 AM #23813909/27/2024 at 12:23 PM #238142Haha nice one druby!
Changing a System from using SETs to not using SETs is a frustrating task in itself … there is no easy way that I have found.
I’ve had to delete all SETs (in one System only up to now! ) which still then leaves the default SET, but with values I don’t want. So then I had to input all latest preferred min, max and step values and the fixed values taken from optimisation table which I had left open so as to see the values which I did want in the DofV Table
Neither of the Save options (from opti results Table) are useful (imo) to revert back to no SETs as the top option (as you pointed out druby) gives the values all listed after ONCE and no values in the DofV Table. The 2nd option provides values in DofV Table as a named SET … so this is no good as a way to get rid of SETs from a System!
Wish I’d stuck to my original way of optimising, but some good has come of it!! I now know how to consistently avoid the weirdness that I was moaning about here https://www.prorealcode.com/topic/v12-odd-or-annoying-happenings/page/5/#post-236431 plus in several posts above this linked post.
Also a few of us have had a healthy, friendly discussion which has lead to a better understanding of the PRT Platform.
09/27/2024 at 12:48 PM #238143Aha if we use Save (from the optimise results table) and select the 2nd option and name the file Default set then the values appear as Default set(1) and, up to now, appear to NOT have the restrictions of a SET.
Hard to explain so I wont try, but I just wanted to state above to, hopefully, close the loop on SETs!! 🙁
09/27/2024 at 2:14 PM #238146I was being serious when I said ” don’t look!’ haha
This is what I think is going on with the sets re: error message.
If you create sets from the ‘definition of variables’ window, limit unknown, sets can be created, even if you close the ‘optimise report’ window.
The same happens if you create sets from the optimise window’s via ‘save results’.
However, if you have a total of 5 or more sets including default created, then if the ‘optimise report’ window is closed for ANY reason and then re-opening either by, a new optimise run or from the system name label pull down list, or other, the error message about 5 sets is displayed when trying to use the create new set from the ‘optimise report’ window. The only way to get rid of error message is to delete the sets down to below 5.The error message persists even if sets reduced below 5, (even if you end up with just the Default set) , until ‘optimise report’ window is closed and the reopened via the pulldown list or re-optimise run.
Creating further sets from the ‘definition of variables ‘ window can still be done regardless if error message is in affect, however you can’t create any new sets from the ‘save results’ option.If you don’t use the save results option, ” don’t look!’ , then you would never see the error message and create all the sets as usual, barring a unknown limit which I think you pushed to at least 34.
Regards.
1 user thanked author for this post.
-
AuthorPosts
Find exclusive trading pro-tools on