PlanetX Indicator - can this indi be used for trading? | Page 5 | Forex Factory

Options

Go to
Permalinks
Print Thread

Similar Threads

Please help to make this indi into a Multiple Time Frame (MTF) indi 3 replies

Repainting indi into Non-Repainting Indi - Help 2 replies

Consecutive candles indi combined with volume & spread indi 13 replies

Need help to convert this indi into MTF indi 3 replies

How to code an indi that can only be used for certain accounts 7 replies

Attachments: PlanetX Indicator - can this indi be used for trading?
Exit Attachments

PlanetX Indicator - can this indi be used for trading?

  • #81
  • Mar 3, 2022 1:48pm Mar 3, 2022 1:48pm
Quoting ohitsyou
{quote} Also, if you don't object, I'm going to make another flavor of PlanetX that incorporates your idea of overlaying Awesome.
OK, you use it!

I made a video. About 8 minutes. Watch the first 3 bars closely.
I had to compress it to rar. Unpack it and watch.
Attached File(s)
File Type: rar Video_2022-03-03_204516.rar   5.5 MB | 501 downloads
.ex4/.ex5 files can't be fixed or modified / I'm not a coder!
  • #82
  • Mar 3, 2022 2:00pm Mar 3, 2022 2:00pm
Quoting BestTraderEv
{quote} OK, you use it! I made a video. About 8 minutes. Watch the first 3 bars closely. I had to compress it to rar. Unpack it and watch. {file}
Thank you. Yes -- I see the height of bars [0], [1], [2] slightly fluctuate up and down, right? But colors don't change, or do they?
  • #83
  • Edited 2:22pm Mar 3, 2022 2:11pm | Edited 2:22pm
Quoting ohitsyou
{quote} And I have a few questions...
1. You must be using iCustom to retrieve the buffer IDs. Why did you choose to leave out the transition markers?
In my indicator I gave people option to select if they want to see the markers or not (true/false). Because they are confusing and not good for decision making. The most important is chart. If chart setup confirms oscillator then I make decision. Not oscillator confirm chart. Sometimes swing happens before marker, sometimes on marker, sometimes after marker.

Quoting ohitsyou
2. How does PlanetAwesome-Osc fix the Bar[0], [1], [2] issue?
It only calculates (takes data from your indicator and from Awesome) when new bar/candle (ticks) come. And I don't want to see current candle, nor bar in oscillator. They only confuse us.

Quoting ohitsyou
Those bars don't change colors, do they? You're concerned that their heights change -- is that it?
Correct.

Quoting ohitsyou
3. And how is it that Bars [0], [1], [2] could change in unison -- I mean, code-wise?
I don't know your code, so I can't say. I made a video so you can see for yourself.
.ex4/.ex5 files can't be fixed or modified / I'm not a coder!
  • #84
  • Mar 3, 2022 2:17pm Mar 3, 2022 2:17pm
Quoting ohitsyou
{quote} Thank you. Yes -- I see the height of bars [0], [1], [2] slightly fluctuate up and down, right? But colors don't change, or do they?
I did not notice, but they might change the markers when volatility is very low. That's why markers are no good for EA.
.ex4/.ex5 files can't be fixed or modified / I'm not a coder!
  • #85
  • Mar 3, 2022 2:26pm Mar 3, 2022 2:26pm
Quoting BestTraderEv
{quote} I did not notice, but they might change the markers when volatility is very low. That's why markers are no good for EA.
In post #79 (https://www.forexfactory.com/thread/post/13919694#post13919694) I attached a modified version of PlanetX where the buffer array isn't initialized with EMPTY_VALUE at the beginning of the loop. I'm curious whether that fixes the problem in your eyes. If the problem remains then, like you, I will include an option to hide the transition markers.
  • #86
  • Mar 3, 2022 2:29pm Mar 3, 2022 2:29pm
Quoting BestTraderEv
{quote} In my indicator I gave people option to select if they want to see the markers or not (true/false). Because they are confusing and not good for decision making. The most important is chart. If chart setup confirms oscillator then I make decision. Not oscillator confirm chart. Sometimes swing happens before marker, sometimes on marker, sometimes after marker.
That's why I thought about Awesome Oscillator. It gives us more information.
.ex4/.ex5 files can't be fixed or modified / I'm not a coder!
  • #87
  • Mar 3, 2022 2:30pm Mar 3, 2022 2:30pm
Quoting ohitsyou
{quote} In post #79 (https://www.forexfactory.com/thread/post/13919694#post13919694) I attached a modified version of PlanetX where the buffer array isn't initialized with EMPTY_VALUE at the beginning of the loop. I'm curious whether that fixes the problem in your eyes. If the problem remains then, like you, I will include an option to hide the transition markers.
I think it did not change anything.
.ex4/.ex5 files can't be fixed or modified / I'm not a coder!
  • #88
  • Mar 3, 2022 2:38pm Mar 3, 2022 2:38pm
Quoting BestTraderEv
{quote} I think it did not change anything.
You know, I think I found a bug. Initially I implemented a start() function that returned '0'. And later I changed that to OnCalculate() -- but it still returned '0'. The modified version below returns 'rates_total'. I'll bet 25 cents that this modified version doesn't have the Bar [0], [1], [2] problem.

Attached File(s)
File Type: ex4 OIY-PlanetX-Hist.ex4   43 KB | 297 downloads
  • #89
  • Mar 3, 2022 3:07pm Mar 3, 2022 3:07pm
Quoting ohitsyou
{quote} You know, I think I found a bug. Initially I implemented a start() function that returned '0'. And later I changed that to OnCalculate() -- but it still returned '0'. The modified version below returns 'rates_total'. I'll bet 25 cents that this modified version doesn't have the Bar [0], [1], [2] problem. {file}
I'll look tomorrow. Now I show you something:

White line is one bar before information in oscillators.
Anchor of text label is where information from oscillator happened.
1. This was a good marker signal if marker behaved without repaint or was there and later gone. Transition was from your indi and Awesome indi. Of course, other elements (spread, volatility) are important.
2. Signal came from Awesome first. Transition signal was still good, because of chart setup.
3. Early signal came from Awesome. Transition came at 3a where price not good for Buy, but we can wait for good price.
4. At 4 transition signal was perfect. Awesome was a bit late.
5. At 5 Awesome gave early signal at good Buy price.
6. Here we have transition.

You will have lots of questions, I predict...
Attached Image (click to enlarge)
Click to Enlarge Name: [DAX40]M15.jpg Size: 455 KB
.ex4/.ex5 files can't be fixed or modified / I'm not a coder!
  • #90
  • Mar 3, 2022 3:13pm Mar 3, 2022 3:13pm
Quoting BestTraderEv
{quote} I'll look tomorrow. Now I show you something: White line is one bar before information in oscillators. Anchor of text label is where information from oscillator happened. 1. This was a good marker signal if marker behaved without repaint or was there and later gone. Transition was from your indi and Awesome indi. Of course, other elements (spread, volatility) are important. 2. Signal came from Awesome first. Transition signal was still good, because of chart setup. 3. Early signal came from Awesome. Transition came at 3a where price not...
This is beautiful. Thank you, @BestTraderEv...
  • #91
  • Mar 3, 2022 4:37pm Mar 3, 2022 4:37pm
This is turning into a good thread
  • #92
  • Mar 3, 2022 4:52pm Mar 3, 2022 4:52pm
Quoting moodybot
This is turning into a good thread
Thanks, MB. Do you think anyone has noticed yet that I may have too much time on my hands?

And I appreciate you having my back when it comes to my newly commercial friend...
  • #93
  • Mar 3, 2022 5:22pm Mar 3, 2022 5:22pm
Quoting ohitsyou
{quote} Thanks, MB. Do you think anyone has noticed yet that I may have too much time on my hands? And I appreciate you having my back when it comes to my newly commercial friend...
Too much time is dangerous!! As for the thread doom and gloomers what they fail to realise is that working together yields results greater than the collective.

M.
  • #94
  • Mar 3, 2022 5:34pm Mar 3, 2022 5:34pm
Quoting moodybot
{quote} Too much time is dangerous!! ...
Yeah -- well, at least the streets are safer when I'm indoors coding...
  • #95
  • Mar 3, 2022 6:06pm Mar 3, 2022 6:06pm
Quoting YoungET
Reminds me very much of R4M's indi's to which I still use. Nice job!
Same style, same lingo @robots4me
could include R4M-Detective indicator.
  • #96
  • Edited 7:34pm Mar 3, 2022 7:24pm | Edited 7:34pm
Quoting mixedbags
{quote} Same style, same lingo @robots4me could include R4M-Detective indicator.
This happens to me all the time. Whenever I'm out and about people stop me and ask for an autograph. They mistake me for Michael Jordan...

If you prefer Michael Jordan then I'll bin the thread and you can contact him to see if he's willing and available to share his time with you -- it's your call...
  • #97
  • Mar 3, 2022 7:55pm Mar 3, 2022 7:55pm
I've modifed the PlanetX indicator to include @BestTraderEv's idea of overlaying the Awesome indicator. This modified version may also fix the bar [0], [1], [2] problem that some have complained about. It is **not** a repainting problem, and I'll explain more in the next post.

The image below shows a comparison of @BestTraderEv's PlanetAwesome-Oscillator-MTF in the first subwindow, and the modified OIY-PlanetX-Hist-v2.0 indicator in the second subwindow:

Attached Image (click to enlarge)
Click to Enlarge Name: PlanetX-v2.png Size: 36 KB

Attached File(s)
File Type: ex4 OIY-PlanetX-Hist-v2.0.ex4   79 KB | 328 downloads
  • #98
  • Mar 3, 2022 8:11pm Mar 3, 2022 8:11pm
Quoting ohitsyou
{quote} This happens to me all the time. Whenever I'm out and about people stop me and ask for an autograph. They mistake me for Michael Jordan... If you prefer Michael Jordan then I'll bin the thread and you can contact him to see if he's willing and available to share his time with you -- it's your call...
Please bin it!
  • #99
  • Mar 3, 2022 8:32pm Mar 3, 2022 8:32pm
I believe the bar [0], [1], [2] issue that some complained about is fixed in the updated version of the indicator that I posted above (and will later add to post #1). There was a bug in the indicator -- my coding error -- but it was not a repainting error. Not that it really matters, but I'll explain more below for the purpose of being complete and to lay this issue to rest.

I don't know in which MT4 build MetaQuotes added this feature, but to improve performance they added an API called OnCalculate() that may be called with each tick arrival. The previous API was called start(). Both APIs are still supported. I've written many indicators and have used both APIs. The start() API is a bit simpler to use, but OnCalculate() is more robust. In my hands I've never really noticed much difference in performance -- though I haven't ever paid much attention.

When coding an indicator you implement either an OnCalculate() function or a start() function. Whichever one you implement MT4 will call that function each time a new tick arrives. The code inside OnCalculate() or start() is the algebra that implements your algorithm. So, with each tick one of those APIs gets called and the algebraic code gets executed, dynamic buffers get filled and markings are displayed on a chart. This occurs with **every** tick.

There is one really, important difference between OnCalculate() and start() -- and that is the return value. With start() it doesn't really matter what value the function returns -- most indis return the value '0'. But for OnCalculate() it is really important to return the value 'rates_total'.

The return value of 'rates_total' is part of the performance enhancement that minimizes the number of times the algorithm gets executed. When you use OnCalculate() with the return value of 'rates_total' then the algorithm doesn't necessarily get executed with each incoming tick. You may have encountered a "refreshing' problem where you'd see the markings change when you select 'Refresh' from the popup menu. This is most likely caused by OnCalculate() being used but not returning 'rates_total'.

My initial version of the PlanetX indicator used the start() API, and I later switched to OnCalculate() -- but the function continued to return the value '0' instead of 'rates_total'. No question this was a bug -- but it has absolutely nothing to do with repainting. Repainting is due to the way the algorithm (i.e. the algebra) is coded. 'Refreshing' is a charting issue specific to MT4.

So, we now have the following issues we can complain about:
1. Recalcuation of Bar[0].
2. Delayed markings (e.g. fractals).
3. Repainting (caused by algorithm)
4. Refreshing (caused by not conforming to MT4's charting requirements)

Thanks goes to @BestTraderEv for digging a bit deeper and pointing me in the right direction.

The next time you are at a cocktail party you may find this information helpful when you want to impress friends and influence strangers...
  • #100
  • Edited 8:53pm Mar 3, 2022 8:36pm | Edited 8:53pm
Quoting mixedbags
{quote} Please bin it!
Ahhh, I think I remember you now, though you are easy to forget. Your feelings got hurt, right?

Okay -- I'm basically done. I will take your request under consideration. Until then, @mixedbags thank you for your service and I wish you luck in your trading.
1 trader viewing now