V12 – Odd or Annoying Happenings!?
- This topic has 113 replies, 11 voices, and was last updated 1 month ago by
.
-
Redundant means ‘not needed‘,
Uh-ohh … Redundant(ly) is the most negative term (most often used in ICT) for matters which are obtained more than once, and which must be maintained more than once.
In this case it must be set more than one time. Or “selected” it you will.Below two screenshots;
In the 2nd you can already see that the default (“standaard”) has been selected (I did not do that) while the 1st screenshot shows what has been saved with the System, and what has been loaded there. This is the opposite situation from what you have, because you will have the default stored and the QuickOut from my case, added newly.3rd SS : The ProOrder tab shows the one which was saved again (and will use that).
Then finally to your Parameter form … see 4th SS. There we have it once again. This will take the setting from the Editor’s main form, it will also go back to the Editor if you change it with the Parameters, but … don’t ask me where this can go wrong because all is redundant indeed.
The least we could wonder is what happens if you use the Backtest button at the bottom of the part of the form which you see in the 3rd SS, and which set it will take.Might it be so that you still don’t recognize all this, then you asked the wrong question. Haha.
But never mind in that case. 😉 I tried.1 user thanked author for this post.
Thank you PeterSt for drawing my attention to the tab ‘Optimisation Parameters Set’ … I had only ever used a few times when first available, but now I use the tab to end / clear the ‘locked-in loop’ I mentioned a few posts up.
To prevent the opti parameters ever getting into the locked-in loop; I try and remember to use the tab for each new set of variable values that I optimise.
Cheers
PS
There was no 4th SS in your post above, but I guess it does not matter now.1 user thanked author for this post.
Wow… ask them to replicate on real acconts!!! 🤣🤣🤣
As you can see from my 5min, 15min, 1h and Daily charts, the 5-minute ghost prices were actually real prices on the higher charts, just quoted BEFORE, not in those 3 candles with those 1-bar trades. Something weird must have happened in the software dealing with the construction of bars and their prices!
Apart from that , why are EU times on my charts tagged as UTC+2 while yours seem to be tagged UTC+0 (yours should have been UTC+1, shouldn’t they have been?). Are you using a custom TZ?
1 user thanked author for this post.
I can’t see it in Roberto’s charts (not at first glance that is) but the three pictures you showed, GraHal, all clearly testify of error in the data. Thus the low price is on a straight line and the high price is too.
I think I asked this before (few weeks ago ?) : did anyone actually check whether the data in IG Live is the same as in IG Demo ?Edit : If you envision the top triangles as the Ask and the bottom triangles as the bid, then both are stuck for a while. Your autotrading CAN trade on this, but in erroneous form. This can only be explained by you looking at your own code. But I think you will be able to see it.
PS: I don’t feel quiet really, but most passing these days here is about old stuff that does not get answered upon / solved anyway. Call me numb by now. But also : I think I have it all under control (ahem). The Auto systems are running (IG as well as IB), but in lower “profile” hence a smaller number of Systems (left the profitable – ditched the losing).
1 user thanked author for this post.
Find exclusive trading pro-tools on 
