Great! Any specific post, or just generally since we met here?

s.

Two instances of CIX used simultaneously as a practical answer?

Top: short term, very reactive, RSI normalization (this is for entry timing by anticipating swing reversal)

Bottom: medium term, timeframe normalization (this is for selection of which pairs to trade)

Combined SELL entries are at the orange lines.

s.

I’m afraid you’re right!

It’s a question of the individual strategy preferred: fishing for exact swing reversals under controlled conditions or ‘good old’ waiting for confirmation. Like one of the ‘great’ traders said: I’m satisfied to cut the middle 30 or 40 % of a swing and let the others fight for the rest. I don’t remember who it was, but I…[Read more]

Not confused! I just think you found a stable and well-balanced set of parameters for your system to work at optimum performance.

s.

Using MAs for trading, we always have to find some balance between two antagonistic mathematical methods: integration and differentiation.

Applying the MA (integration) to prices always introduces a certain amount of lag. Choosing a state of the art adaptive filter instead of a simple SMA can reduce the amount of lag while at the same time…[Read more]

Most CS indicators are lagging to some extent. And so do my early attempts to code a CS. All those discussions with @gg53 about this topic convinced me that this is not necessarily so, and my latest CIX is tuned to be much more reactive than every CS I coded earlier. But ok, it’s a bit choppy now. And since we want to calculate a slope, ‘some’…[Read more]

Thanks for this:

I also experimented with VZO settings different than the defaults suggested in Khalil’s article. I found that VZO 4 … 8, limits around 60 looked interesting, so very much similar to your suggestion.

I will certainly try your breakout, anticipating the reversal! I’m curious how the exact timing will meet CIX and CLEAR.

s.

Thank you for yout hints!

Re. enumerations: yes, all trading decisions can be represented by one common enumeration instead of indicator-specific enums. That would be even easier to read and maintain. I will modify my functions in that way.

Re. higher and lower TFs: I fully support your view. Just at the moment I would like to stay with one TF…[Read more]

A little motivational post regarding backtests with Offline CIX.

This is the result of a 4 months backtest run on EURUSD H4. Simple entry combination of just CIX and CLEAR, no VZO yet.

Purposefully hardly any trade management yet, because I wanted to get an idea about the entry quality. It’s 1 % risk per trade, 1.0 ATR SL and TP, with moving SL…[Read more]

Thank you for clarifying:

In my Penguin_CIX.mqh, it looks like this, because I prefer to work with enumerations in such cases:

enum CIX_TRADE {
CIX_TRADE_NONE,
CIX_TRADE_BUY,
CIX_TRADE_SELL
};

Called like this:

CIX_TRADE cixEntry = getCixEntry(symbolIndex, tf, CIX_INDI_NAME, cixSmoothing, cixTrendDepth, Prefix, Suffix);

The rest…[Read more]

Call For Coders

It’s still too early to publish my latest CIX full version – there’s some code cleanup to do.

But if anybody would like to backtest our EA prototype based on CIX data, I’ve got something to offer: the Offline Version of CIX 4.3.

It works like this: I equipped the full version with a csv export interface, that dumps timestamps as…[Read more]

How about currency strength to identify ‘no trend’ intervals?

s.

@gg53,

I’m afraid that this won’t be enough. The circumstances kapybara & forexdj reported will prevent the EA from opening trades. The error occured in functions BuyStop and SellStop. So this particular check has to be made before an entry, but during trailing as well.

s.

Hi kapybara,

Thanks for reporting! According to your output, the error should NOT occur on your GP account, where Stop level in points ( MODE_STOPLEVEL ) = 0. On MaxFx the case is clear with Stop level in points ( MODE_STOPLEVEL ) = 10

As a workaround, please try setting your parameter StopOrdersBuffer to a value greater than the account…[Read more]

@VlanFx: maybe it would be a good idea to cut the function from my above posted script and integrate it in the EA. Calling the function once during OnInit() might support debugging.

s.

Hi @kapybara & @forexdj !

Thanks for reporting. Obviously the problem occurs when functions BuyStop() and SellStop() are called for an entry:

double stopLevel = MarketInfo(sym, MODE_STOPLEVEL) * point;
if (price - ask <= stopLevel) {
Print(__FUNCTION__ + " Price " + price2String(price) + " too close to current price " + price2String(ask) + " Min…[Read more]

Hi @kapybara & @forexdj !

Thanks for reporting. Obviously the problem occurs when functions BuyStop() and SellStop() are called for an entry:

double stopLevel = MarketInfo(sym, MODE_STOPLEVEL) * point;
if (price - ask <= stopLevel) {
Print(__FUNCTION__ + " Price " + price2String(price) + " too close to current price " + price2String(ask) + " Min…[Read more]

Hi @kapybara & @forexdj !

Thanks for reporting. Obviously the problem occurs when functions BuyStop() and SellStop() are called for an entry:

double stopLevel = MarketInfo(sym, MODE_STOPLEVEL) * point;
if (price - ask <= stopLevel) {
Print(__FUNCTION__ + " Price " + price2String(price) + " too close to current price " + price2String(ask) + "…[Read more]

Hello, this is not EA error, it is your trading account limitation (stoplevel 30 pips), try to set “StopOrdersBuffer” property 30+ pips.

Great Anti. Number 1 : the previous candles are bearish (2 red candles before the white engulfing bar). While at number 2:   all previous candles are white (all 3 white candles in a row, including the engulfing bar). But i can be wrong though …   Edit : i am agree that to discuss only high probability pattern, not to discuss many pa…[Read more]