snailbeard wrote:Hi Andy,

I have now had a chance to study the CSS code and some comparisons of charts using the different versions of CSS on H4 and H1. So far, these observations only apply to AUDCAD & AUDUSD for the last month, so there is a danger of curve fitting to these pairs.

What I observed on H4 for Baluda's CSS was the best overal trend direction and for seeing a weakening of the trend. This appears to give an effective hint before a reversal, (when the lines change direction and move towards each other) so it can suggest clearing the pending orders which could trigger and run to stop loss because of a weakening trend.

However, for reducing drawdown on trades which would still be good trades but could significantly retrace: the 10.5 CurrencySlopeStrength on H1 gives crossovers sooner than H4. Due to lagging on H4 one has to anticipate a crossover by looking for the lines turning in towards a cross over, and conversley, the more the lines are moving apart the less the chance of an end of trend pivot.

If there are multiple pairs to trade then CSS can be used to suggest and prioritise trades which are more promising.
Many of my Alpari pendings get cancelled because of margin limits, so in that situation it makes sense to pick only the best pairs.

Also I noticed that RSI triggers with tight thresholds might be difficult to combine with another lagging indicator because they can often be out of phase.

If the pending orders are removed while RSI is in the correct position, RSI can move past the threshold, then too late according to RSI, H1 CSS crosses suggesting a better time to open an order.

I am experimenting with some code that I have derived from variations on CSS to see if it can work along side the other trade logic.

However, first of all. I have mystery to solve of very few trades, even with useCss = false.
I'll try the same EA on another broker account in case that makes a difference...

kwchau wrote:Hi Andy,
Please excuse my so so English standard, I don't fully understand this statement :

"also the parameter extern bool useOneDailyTrade = true; , which only allows 1 trade per day to be opened if the trades for that specific pair is 0."

Does it mean that for example, on a particular day, if there is no open position for EURUSD, it will not open more than 1 trade. If there is already one EURUSD open position, it will add multiple positions. If my interpretation is correct, I just wonder why it does not allow opening of multiple positions on the same day if there is no open position initially.

MrLong wrote:

kwchau wrote:Hi Andy,
Please excuse my so so English standard, I don't fully understand this statement :

"also the parameter extern bool useOneDailyTrade = true; , which only allows 1 trade per day to be opened if the trades for that specific pair is 0."

Does it mean that for example, on a particular day, if there is no open position for EURUSD, it will not open more than 1 trade. If there is already one EURUSD open position, it will add multiple positions. If my interpretation is correct, I just wonder why it does not allow opening of multiple positions on the same day if there is no open position initially.

Hi,

If we have no trades rolling for EURUSD, the EA will take a trade and add to those trades, but if the EURUSD trades have all closed, the EA will not take anymore EURUSD trades until tomorrow.

Andy

snailbeard wrote:Hi Andy,

I have now had a chance to study the CSS code and some comparisons of charts using the different versions of CSS on H4 and H1. So far, these observations only apply to AUDCAD & AUDUSD for the last month, so there is a danger of curve fitting to these pairs.

What I observed on H4 for Baluda's CSS was the best overal trend direction and for seeing a weakening of the trend. This appears to give an effective hint before a reversal, (when the lines change direction and move towards each other) so it can suggest clearing the pending orders which could trigger and run to stop loss because of a weakening trend.

However, for reducing drawdown on trades which would still be good trades but could significantly retrace: the 10.5 CurrencySlopeStrength on H1 gives crossovers sooner than H4. Due to lagging on H4 one has to anticipate a crossover by looking for the lines turning in towards a cross over, and conversley, the more the lines are moving apart the less the chance of an end of trend pivot.

If there are multiple pairs to trade then CSS can be used to suggest and prioritise trades which are more promising.
Many of my Alpari pendings get cancelled because of margin limits, so in that situation it makes sense to pick only the best pairs.

Also I noticed that RSI triggers with tight thresholds might be difficult to combine with another lagging indicator because they can often be out of phase.

If the pending orders are removed while RSI is in the correct position, RSI can move past the threshold, then too late according to RSI, H1 CSS crosses suggesting a better time to open an order.

I am experimenting with some code that I have derived from variations on CSS to see if it can work along side the other trade logic.

However, first of all. I have mystery to solve of very few trades, even with useCss = false.
I'll try the same EA on another broker account in case that makes a difference...

pathenry wrote:I know this sounds like a daft question but can i override trade times? ie, 24 hr trading?

nonlinear wrote:

snailbeard wrote:Hi Andy,

I have now had a chance to study the CSS code and some comparisons of charts using the different versions of CSS on H4 and H1. So far, these observations only apply to AUDCAD & AUDUSD for the last month, so there is a danger of curve fitting to these pairs.

What I observed on H4 for Baluda's CSS was the best overal trend direction and for seeing a weakening of the trend. This appears to give an effective hint before a reversal, (when the lines change direction and move towards each other) so it can suggest clearing the pending orders which could trigger and run to stop loss because of a weakening trend.

However, for reducing drawdown on trades which would still be good trades but could significantly retrace: the 10.5 CurrencySlopeStrength on H1 gives crossovers sooner than H4. Due to lagging on H4 one has to anticipate a crossover by looking for the lines turning in towards a cross over, and conversley, the more the lines are moving apart the less the chance of an end of trend pivot.

If there are multiple pairs to trade then CSS can be used to suggest and prioritise trades which are more promising.
Many of my Alpari pendings get cancelled because of margin limits, so in that situation it makes sense to pick only the best pairs.

Also I noticed that RSI triggers with tight thresholds might be difficult to combine with another lagging indicator because they can often be out of phase.

If the pending orders are removed while RSI is in the correct position, RSI can move past the threshold, then too late according to RSI, H1 CSS crosses suggesting a better time to open an order.

I am experimenting with some code that I have derived from variations on CSS to see if it can work along side the other trade logic.

However, first of all. I have mystery to solve of very few trades, even with useCss = false.
I'll try the same EA on another broker account in case that makes a difference...

I had three trades using CSS last week on demo. But I think this EA is highly broker dependent. I am running it on two broker now to assess differences.