Holy Graily Bob in a MTF stack

[blazej]

Hi David,

I must admit that idea behind this ea is great. It is simple and effective. I am trading it manually. Most of the trades induced by ea from London open hit theirs SL today on my account with Your setfile in use. I will check it later on, after I will be back home and then I will post the results. I have tweaked the setfile a bit after London session, so will see how it works.

Thanks Steve for explanation.

Thanks once again David for brilliant idea.

[DigitalCrypto]

Steve,

You are correct about the broker being the problem. Stupid FIFO rules.

I fully appreciate your shell code. It has everything that is needed and nothing more. Please disregard the error on my part. I wasn't paying attention. I've only had an hour of sleep.

You are correct. I've seen poorly coded EAs chew through an account in microseconds. My first ever script was a trade closure routine that would take a couple minutes to run. It damn sure wasn't your code. I don't mess with nothin exceptin the lot sizes. And I admit I remark the top two lines of the hud and put the version above the broker time cause I'm too blind to read the small print.

It looks like what happened is simple. We got a yellow wave and while Empty4 was initiating a close it got a green arrow and immediately tried to send a trade in the middle of the trade closure. This of course failed because FIFO says hell no and this caused the flag to fire "Too soon to trade" so that hung the trade closure up. It then fired again trying to open a long on the same position and once again hung up the closure routine.

On my Traders Way account the same trade worked nicely, zero errors. Again thank you for making code that works on FIFO accounts.

Much appreciated,
David

[DigitalCrypto]

Hi David,

I must admit that idea behind this ea is great. It is simple and effective. I am trading it manually. Most of the trades induced by ea from London open hit theirs SL today on my account with Your setfile in use. I will check it later on, after I will be back home and then I will post the results. I have tweaked the setfile a bit after London session, so will see how it works.

Thanks Steve for explanation.

Thanks once again David for brilliant idea.

That set file is for v1a. We're using v1b. I won't be updating them until later. You're welcome

[DigitalCrypto]

Here is a note to all of you new to using so-called Expert Advisors.'

What do you think about Python for FX EAs/Algo?

Are you kidding me?! You quoted his entire post for a one line off topic question? Don't bring this off topic crap into this thread.

[DigitalCrypto]

@Steve,

If there is a blue wave and an arrow on the same candle is it considered a blue wave, trend arrow or something else?

Thanks,
David

[SteveHopwood]

@Steve,

If there is a blue wave and an arrow on the same candle is it considered a blue wave, trend arrow or something else?

Thanks,
David

It looks first for a trend arrow, then a blue wave, then a yellow wave. Once it finds something, it stops looking.

Should, say, a trend arrow then a yellow wave appear on the same candle the chances are that the conditions that created the arrow have disappeared, so the EA will not find the arrow and the yellow wave will take precedence. If the yellow wave conditions subsequently disappear, the EA will cease to find them and change its display of the signal it found earlier.

Confusing as Hell until you remember to change time frames briefly to remove the signals that are no longer appropriate.

It is probably too late by then because the EA will already have acted on the information it was presented with - the reason some users prefer to act only on the close of a candle.

The HgiReadDelaySeconds input has two purposes:

• save cpu by calling HGI once a minute.
• gives a temporary signal time to disappear so the EA is no longer working with outdated information.

The higher the time frame being traded, the higher HgiReadDelaySeconds should be.

[DigitalCrypto]

This makes sense. I'm just reviewing some charts and noticed that there was a red trend arrow and a blue wave appeared over it but then no trade was taken. It is as I suspected. Since I am not trading said blue waves it didn't enter the trade until after the push down and a pull back correction. Which of course is totally fine.

Everything is working quite nicely here. I am very pleased with your work.

[SteveHopwood]

This makes sense. I'm just reviewing some charts and noticed that there was a red trend arrow and a blue wave appeared over it but then no trade was taken. It is as I suspected. Since I am not trading said blue waves it didn't enter the trade until after the push down and a pull back correction. Which of course is totally fine.

Everything is working quite nicely here. I am very pleased with your work.

The bot will only look for a blue wave if you have told it to trade blue waves. If not, they will not even come into the frame for an opposite signal close.

If a signal appears on your chart but no trade was taken, then here are the likely causes:

• the signal disappeared before the bot read HGI. Refresh the chart and see if the signal remains. Most times it doesn't.
• the spread was too wide at the time for the bot to trade. You have no way of knowing whether this was the case or not.

Bear in mind also that the signal shown on your chart has no relationship to the market at the time the signal was generated. You have no way of telling where the market was at the time.

HGI is purely a here-and-now thingy. You can glean nothing useful from looking back in time. HGI might have generated the signal at any point of time during the candle; you have no way of knowing when that was. All you know if a signal remains on the chart after you refresh it with a tf change then back again is this: the conditions that generated it remained in force at the close of the candle.

And that the market may have moved several hundred pips in the time; or not; you will not know.

And that the conditions that generated the signal might have vanished the instant the next candle formed. You have no way of knowing.

[DigitalCrypto]

Makes sense. I've an idea for a blue wave strategy but it needs some testing beforehand.

Thank you for the clarification on all this.

[DigitalCrypto]

My latest test for Blue Wave will be an HGBAM setup with the following pairs and settings

FirstTimeFrame = M30
StackingTimeFrame = M5

Pairs
EUR - AUD/CAD/JPY/NZD
GBP - AUD/CAD/JPY/NZD

StopLoss 40+5

The following set file is for testing NOT production. I am not running this live, yet.

HBAM305.set

Lot sizes are standard rules per Steve 0.01 per $1k USD

EDIT: Forgot to mention this is trading Long and Short.