Awesome Oscillator
-
Is there a way to write an ea that creates an alert message every time the awesome oscillator changes color (from red to green or green to red) using the awesome oscillator indicator or would I need to use more basic indicators like moving averages?
Thank you
-
http://fxdreema.com/shared/Xth7sKzyc
It looks that some block like "Indicator changes direction" is needed
-
that works except that it detects color change one bar too late but if you set candle ids to 0 & 1 in the first condition blocks, it doesn't work. "Indicator changes direction" block is a good idea but in the meantime, maybe there is a way to detect oscillator properties (i.e. color)? Thanks
-
This is built-in indicator and it does not have buffers from which to get color information. It looks that the only thing that one can get is the level.
0 and 1 in the first block, 1 and 2 in the second - it works and some "wrong" signals will appear.
-
I found this post but not sure if the information can be incorporated into a custom block: http://www.metatrader4.com/forum/1202
-
This function gets the value from Awesome indicator: http://docs.mql4.com/indicators/iao It's pretty simple, no indicator parameters at all.
-
what about this to detect the color change? http://fxdreema.com/shared/CYZhCBB2b
(It's not working correctly) -
__This function gets the value from Awesome indicator: http://docs.mql4.com/indicators/iao It's pretty simple, no indicator parameters at all.[/quote:2kvbnaok]
So isn't this the same as the ea you wrote using condition blocks?
-
I don't understand why you want to use MA to detect color change of Awesome. Obviously the color is changed when Awesome reverse it's direction, or if you compare 3 candles - the one in the middle is above/below the other two. But what role have MA here?
By the way, blocks with lower number are executed first, so block 1, then block 7, then block 26.
-
I read that Awesome Oscillator = ma5 - ma34 so I was trying to recreate it... because I haven't figured out how to draw an arrow as soon as Awesome Oscillator changes direction (in current bar)...
I thought blocks were executed from top to bottom?! Does the number priority also apply to connected blocks, for example in an ea if block 10 is at top and block 9 is connected underneath, it will execute block 9 nevertheless? And what if you have parallel sets of blocks side by side (for example two separate conditions with a series of blocks connected after each condition but the 2 conditions are independent of each other and not connected to anything above) that you want to run at the same time but the numbers of the set on the left side come before those on the right - will it run the set on the left side first and then come back up and run the set on the right?
-
There is also included custom indicator Awesome.mq4, so it can be used as well. It has 3 buffers - one for the overall values and 2 separated for the green and red histograms. Then "Indicator appear" may help.
There is no matter where the block is located, what matters is it's ID number - lower numbers are executed first. Blocks on top level means that there are no other blocks connected to their inputs, or you can imagine that "on Tick" button is a block and is connected to them with invisible connection lines.
But if location makes more sence, I can think about it. I can imagine that blocks have no visible IDs and they are executed depending on where they are - top first, or if they are on the same level - left first. Does this sound like something that should be like that?
-
thanks for that info. on Awesome.mq4 - I'll check it out
I wrote this ea (screenshot attached) assuming that blocks were read from top to bottom. Strangely, it seems to work as expected. Are the block numbers ignored if they are connected to blocks above them (ex. block #2 is located physically below #1206157 (before normalization) but they are connected)?
I was wondering what role block numbers had so thanks for the clarification. Having structured this ea with location in mind, I think location is a good option since it helps organize things visually. I think execution by block number should stay an option since building ea this way would take less time. Maybe there could be 2 "modes" to build ea - by location or by number.
......
EA Execution Order.png -
Now only IDs matters. When the final project builds IDs are considered. Blocks position data is used only to draw blocks on the web page and when copy/paste blocks. Maybe it's better to have an option to normalize IDs concidering their location, so the user will see the result of this immediately and will still be able to position blocks anywhere.
I still don't know why block IDs starts to grow without reason
-
but aren't IDs disregarded if they are connected to other blocks? Otherwise, what explains that above ea is working from the top to the bottom?
__Maybe it's better to have an option to normalize IDs concidering their location, so the user will see the result of this immediately and will still be able to position blocks anywhere.[/quote:18lpglyp]
great idea. Or maybe to auto-arrange blocks from top to bottom (or according to different layout templates that user can select/upload) on the page based on block ids.
Maybe the block IDs grow when you copy and paste a large number of blocks from a different project?
-
This will execute block 1 first, then 2, then 3, 4, 5, 6, 7, 8, 9, 10: http://fxdreema.com/shared/UAhPkCTub
It's possible, I tend to think that it is javascript problem when creating a new block, and I checked javascript functions many times, but it's truly possible to happen while copying blocks, I have to investigate that.
-
__This will execute block 1 first, then 2, then 3, 4, 5, 6, 7, 8, 9, 10: http://fxdreema.com/shared/UAhPkCTub
[/quote:2wwfoop9]In what order will these blocks execute?: http://fxdreema.com/shared/XbYGw0Ghd
-
3, 10, 9, 7, 5, 8, 2, 1, 4, 6
-
__There is also included custom indicator Awesome.mq4, so it can be used as well. It has 3 buffers - one for the overall values and 2 separated for the green and red histograms. Then "Indicator appear" may help.[/quote:1nd2v0k1]
this ea catches some of the color changes but there are lots of incorrect arrows. Any suggestions?: http://fxdreema.com/shared/Il2GQvOC
-
Yes, use Candle 1, 2, 3... or whatever, but not 0. These signals are not "incorrect", they just happened for the current candle, and as you may know the current candle is changing.
