Optimiser – Positions of Variables affects Result!
Forums › ProRealTime English forum › ProRealTime platform support › Optimiser – Positions of Variables affects Result!
- This topic has 34 replies, 6 voices, and was last updated 2 years ago by GraHal.
-
-
06/03/2022 at 11:23 AM #194536
Yep more weirdness!
I don’t want this to turn into an all day event (again) so apologes if below is lacking in detail.
I have this in my code …
12EntryL = Close > Average[A21,B21](close)EntryS = Close < Average[A22,B22](close)- I had A21, B21 and A22 and B22 in that order in the optimiser (attached Image 1) … Result – good.
2. I deleted (by accident) A21 and added it back in at the bottom (attached image 2 ) Result – none /zero / flat line!!
3. I got my Algo going again by redoing the order (as in 1. above) and finished off what I was doing.
4. To double check, I then deleted A21 again and added it back in at the bottom (attached image 2 ) … Result -none /zero / flat line!!
Beware there are some weird happenings in use of the optimiser this week!!
06/03/2022 at 12:02 PM #194544Weird!
What happens if you remove A21 from the optimizer and replace A21 with 15 in your code?
06/03/2022 at 12:20 PM #1945485. I did it again for a 3rd / 4th time … deleted A21 and added A21 = 15 at the bottom … results as in 2. and 4. in my OP (zero / flat line) .
6. Leaving A21 = 15 at bottom of the code, whilst at same time replacing A21 in the code with 15 gives the same good results as having A21,B21 A22, B22 in order in the optimiser.
7. Deleting A21 from the optimiser, whilst at same time replacing A21 in the code with 15 gives the same good results as having A21,B21 A22, B22 in order in the optimiser.
06/03/2022 at 12:24 PM #19454906/03/2022 at 12:48 PM #194551GraHal, why are you always breaking everything? Can’t we have a calm week for once? 😉
1 user thanked author for this post.
06/03/2022 at 1:51 PM #194556I experienced the very same with an Indicator, yesterday. In the end I had removed all parameters and hard-coded the variables in de Indicator code, and the result remained zero.
I think this happened earlier this week just the same (I even mentioned it somewhere ?).Something can mess up in there and it can only be solved by copying the code to a new instance (in this case Indicator). I did that this morning and all worked again.
Might someone at PRT have the slightest idea of solving issues : this one is related to how parameters are passed; I think internally this is more fixed than it should be, and when a sequence is changed, the internals don’t come along, and the lot remains broken.
And when do we notice ? After one hour ? two ? never ?06/03/2022 at 2:02 PM #194557I did not move this topic.
Have you tried to close the platform, then open it anew?
06/03/2022 at 2:09 PM #19455806/03/2022 at 2:12 PM #194560The weirdness is spreading!! 🙂
I think Roberto was only saying that he did not move the topic. It is in ProBuilder all right.
Nevertheless the weirdness IS spreading. 🙁 But careful for the ghosts. 🙂
06/03/2022 at 2:13 PM #19456106/03/2022 at 3:07 PM #19456306/03/2022 at 3:45 PM #19456706/03/2022 at 9:04 PM #19458706/03/2022 at 10:59 PM #194592Done, but the correct forum should be ProOrder.
06/06/2022 at 9:14 AM #194750Done, but the correct forum should be ProOrder.
I don’t think so.
PRT need to see it if we have any hope of a fix?
That was Mr Opportunistic speaking. Still it is the only chance we have, as it seems. 🙁
1 user thanked author for this post.
-
AuthorPosts