Blue Cross in Backtesting & AutoTrading Window??
Forums › ProRealTime English forum › ProRealTime platform support › Blue Cross in Backtesting & AutoTrading Window??
- This topic has 10 replies, 3 voices, and was last updated 2 years ago by PeterSt.
-
-
08/08/2022 at 5:48 PM #19876208/08/2022 at 5:54 PM #19876408/08/2022 at 6:06 PM #198766
Odd thing … all 3 of those Systems have variables in the optimisation window and yet the blue cross only shows on 1 System.
Also I’ve never seen the blue cross before today and I haven’t ‘been to specsavers’ and got new glasses! 😉
08/09/2022 at 5:03 AM #198774Glad that someone asked the question, as I never knew either and saw them since using PRT, with or without glasses.
It means that you have parameters in the Optimization form with a not-fixed value like you see in the 1st attachment. Thus the system containing such a line (this one varies from 1 to 10) will bear that blue cross.
Would that parameter be defined like you see in the 2nd attachment, then it will not cause a blue cross.
And if a parameter is defined like you see in the 3rd attachment, then that also will not cause a blue cross.
It means that you have variables in the optimization window, it has always been there!
Now often all is about langue and where I deem this wrong, it would be correct if you’d translate that to “if there’s a parameter which varies in the optimization window” it would be clear.
And since this language problem exists – when I make a title-description of a topic that depends on my outlay, Nicolas responds that my title-description is not meaningful.
And thus my title was changed intoFixed period different than in the result window during optimization
While I had made that title something like :
Fixed parameter is different than the result window during optimzation
and probably slightly different because this still does not make sense to me as how I would write it regarding the content of that topic. And if a mod did not do that then it was auto-translated ?
OffTopic :
PS: Only per this topic I can understand that something happened to that title and why. So thank you, GraHal !
1 user thanked author for this post.
08/09/2022 at 7:09 AM #198778I thought your original title was something like … ‘Is Anybody Dislexic on Here’ ?
I understand now re the blue cross, still weird I’ve never seen it before, something changed with the last update 25 Jul 22.
Reason I say above is … when I optimise (in the last week or so) results nearly always show in that ‘multi-TS-result Table’ along with previous opti runs. I think this deserves a separate Topic, so I’ll end it there!
1 user thanked author for this post.
08/09/2022 at 7:26 AM #198779I thought your original title was something like … ‘Is Anybody Dislexic on Here’ ?
Great thanks for that, no matter is is offtopic. You are correct, it sure
I understand now re the blue cross, still weird I’ve never seen it before, something changed with the last update 25 Jul 22.
You still seem to have an update from Jul 25 (not the first time you mention this date). Maybe it’s nothing, but I’m still on June 22. So maybe I (or others) don’t see exactly what you see.
Fact is that I never understood what this blue cross was for and have been tempted a dozen times to ask. Now I finally know.The important of it should be that you can’t give this to ProOrder. Although … somewhere a couple of months back I told that this would lead to erroring out at the start of the System (hand over to ProOrder). But later I found this not to be true. I know must assume that it will take the value of the “fixed column”. And with this, the danger exists that you never saw the varying columns still active, chose one of the results (virtually because you did not fixate it) and *then* your system will behave differently from what you thought.
So this should act as a warning sign “don’t give to ProOrder !!” (while it surely accepts it).Btw, to me it shows as a screen with a cross in it. The correlation with a screen (monitor ? form ? window ?) I don’t see as such. But I am sure this is a great day to find out (just coming from working the garden for several hours in a still great temperature 🙂 ).
was something like that.08/09/2022 at 7:50 AM #198780Attached my latest version – 25 Jul 22.*then* your system will behave differently from what you thought.
I agree, but maybe due to another scenario I experience where incorrect values can be passed to ProOrder.
Above occurs when the coding window is still open – even after fixed / chosen values have been entered in the fixed column in the optimiser (variable values not enabled any longer) – the intended fixed values do not appear at red arrowheads in image 2.
Other values appear and are passed to ProOrder … I only noticed this a month or two back so I may – in the past – have – unknowingly – passed many Systems to ProOrder with wrong values! I always do a double check now as a safeguard!
Above deserves (another) separate Topic (for the benefit of others) but I haven’t the time to document it all!
08/09/2022 at 8:16 AM #19878808/09/2022 at 8:48 AM #198794Above deserves (another) separate Topic (for the benefit of others) but I haven’t the time to document it all!
Teaser !
Other values appear and are passed to ProOrder …
As in “different” values ?
But save the answer for your separate topic, please (I know, you are watching Coronation Street, so take your time – hahaha)1 user thanked author for this post.
08/09/2022 at 9:13 AM #198798As in “different” values
Yes different values!!!
I’m not sure that I will do a separate Topic as I often feel I spend lots of time typing all exact with screenshots and a comprehensive explanation etc etc. At the end of it, I kinda feel … what’s the point, not many post on here (except us 2! Oh I see ‘TempusFugit’ has an Issue now) with werid Issues? It be good to add bits to other’s original posting now and again? Okay … moan over!! 🙂
If I do separate Topics in future it will be a bald statement (100 words ish with a screenshot or two) of what I experience and I’ll leave it at that. Maybe you do well to try the same gig Peter!? 😉
08/09/2022 at 9:23 AM #198801Same gig, same gag.
But it never is for nothing because there is at least one who benefits : me.** In any event this is how I post the issues : hoping that someone will benefit from it (read : not lose money).
**): I am sure others too, but maybe not many.
-
AuthorPosts