Zigzag Bollinger Band

[snailbeard]

Cable and CSS

In the attachment, I have marked the entry price at the nearest H4 candle to the M15 entry.
I have also added levels (CSS indicator) to indicate where currency strength is weak, moderate or strong.

One of the failed buys occurred while CSS was a weak 'buy' and the other failed 'buy' occurred while CSS was indicating a strong buy.

Another observation is that the green H4 Bollinger moving average (BMA) has a variable slope which can also be weak, moderate or strong. The first trade is against the BMA and the second is with it. Both indicators are of course lagging derivatives of price movements, so perhaps it is not surprising that they give similar information.

Does the CSS indicator provide information to help avoid entering bad trades?
For this particular way of trading I don't think it helps and would perhaps block some profitable trades.

[snailbeard]

Since CSS did not help in eliminating two losing trades which were going in the general price direction, what other information might produce a better out come?

In the following attachement I have labelled the entry-prices, stop-loss and first target prices (in white) (and I have also labelled a counter trade in red).

The first important observation is that both trades move in the right direction. Secondly, they almost reach the first target profit before price swings back, passes the entry point and drops down to the stop-loss.

If the trades had not come close to the target then they could have been described as flawed entries, but as they were significantly in profit, it would be better to describe them as good trades with flawed exits.

Rather than experiment with another layer of trade filters, it could be beneficial to look at profit locking. The code that I had previously inherited for profit locking does not work well with the partial-exit mechanism but it looks like its time to develop a robust profit-locking method. This should be more straight forward in a modern language like C++/C#/Java.

[snailbeard]

House of Cards
=============

MetaTrader4

fixme:ntdll:server_ioctl_file Unsupported ioctl 24000 (device=2 access=1 func=0 method=0)

abnormal program termination

============================

Yes, more headaches and perhaps it is time to call it a day for this dinosaur.

Perhaps I could write a very simple script which just reads orders from a file and writes progress to another file, then the workhorse program could be completely independent of the dinosaur.

I wonder if anyone else has tried this?

[snailbeard]

Aussie is going the wrong way!

Well if snailbeard is selling the Aussie then the Aussie should respect that and not go up!
It looks like the Aussie has been lifting weights all morning, but perhaps it will start to wilt a bit in the afternoon.
The Aussie has crept up to some channel and perhaps now it will have some respect for the weight of other currencies pushing against it!

I had a historical look at Friday's chart (audjpy), I was looking for clues to the direction. Since the previous day was heavily down and the early morning consolidation had a slight downward aspect to it. So if you were watching for some indication of a new move, would you have seen the midday breakout to the buy side and would you have considered it to be a true breakout or a false breakout?

And is the same thing happening again just as I write this?

Friday's chart:

[dudest]

Hey SB,

I was also short last week ( SL was missed by a whisker, twice! )

Closed the shorts for BE today morning.

Have a sell limit set at the top of the current H4 range when price is done going up

Cheers

audusdh4.png

.

[snailbeard]

Thanks Dudest, glad to read the Aussie didn't bite you

It has not been a good month for old timer snailbeard EA version 02/12/13, which dug it self into a grave with GU (and others)

The SB Forward and backward tests are not exactly the same of course but pretty close to each other (I was just checking that the bad results showed in ST as well as FT)

ST_SB-v02Dec13-proven-worse-than-SB13Dec13.png

However, new kid on the block SB v13Dec13 survives difficult trading conditions and gets a vote of confidence (for now).

[snailbeard]

An injection of steriods has this patient leaping out of bed this morning. Could Aussie be ready to leave the hospital?

[SpiderX]

An injection of steriods has this patient leaping out of bed this morning. Could Aussie be ready to leave the hospital?

Hi,

Stocks crashed last night and people ran to buy gold for safety.
Seems like Aussie picked up pace along with gold.

Cheers

[snailbeard]

Hi SpiderX,

Maybe Gold is finding support but perhaps the ones rushing to buy it are the same ones who bought it at 1900?

I'm investing in coffee beans
about 1Kg every couple of months.

Heres Gold in perspective

[snailbeard]

THE wind was a torrent of darkness among the gusty trees,
The moon was a ghostly galleon tossed upon cloudy seas,
The road was a ribbon of moonlight over the purple moor...

At least the attached chart might look like that.

Did I previously say in a post that I had fixed ALL the bugs in SB, I hope I didn't say it because it is not true,
I finished my trading for the morning and decided to investigate why SB had bought usdcad (not just once but twice) yesterday.
It had correctly determined the longer term swing but had got the short term outlook upside down.
It can be difficult making decisions based on zigzag pivots due to the repainting aspect of the most recent pivots. I have been thinking of adding some consistency checking into the zigzag code.

Since the script is already 'full' I can't add any more arrays and it is tripping over the latest DLL, so I have been toying with the idea of letting PT3 translate the whole script into C#.

At the weekend I found a .Net bridge for Empty4 (TradePlatform.Empty4_3.6) which provides scripts to interface to .Net indicators and EAs. I also found serval other sources of C# relating to trading which might save some development time.

Since I have not had time to try this out it could time consuming.
As a temporary fix to the existing script I could add some candle checking logic.