Scalping New York

[celte83]

Still getting trades going against the previous candle direction..

Hi,
Not for me. All is right in the rules.
Graph in H1 ? !
16 pairs Open London
Cheers
jf

[TableTop]

Still getting trades going against the previous candle direction.. Am I the only one? This is on a clean fresh installation!

15 pairs traded on the London opened and all followed the rules.

EDIT: The above is true on my live account. However, I've just noticed that I have a different set of trades. So my demo account opened CADCHF long at 0805 while the previous candle was down.

[celte83]

after passing at 0.07 cents from the 100 target, the basket is closed at -165.
Perhaps it would be useful to complete the money management. With a BE etc...?
Notice that it was the pairs with CHF that made us lose the most
Now let see NY
Santé

scalpy 1 juin London.PNG

NY opened with 14 pairs
TP hit after 20mn

[TableTop]

15 pairs traded on the London opened and all followed the rules.

EDIT: The above is true on my live account. However, I've just noticed that I have a different set of trades. So my demo account opened CADCHF long at 0805 while the previous candle was down.

Following up with NY open trades.

Live - all correct (essentially OOTB settings - fixed TP).
Demo - some inconsistencies - 3 that should have been filtered out by the 240 MA, and 1 that opened in the wrong direction. I am testing the dynamic TP on demo.

[celte83]

NY

scalpy 1 juin NY.PNG

[paulbt38]

Trades opened perfectly at London open, ended up at BE. Next trades opened perfectly at 13:05 and closed at tp within 15 minutes. I am running OOTB except on 0.01 lot sizes and therefore tp of 3. However got another set of trades opening at 14:00 and will look for breakeven after 55 minutes and autoclose after 1 hour 55 mins?

Anyone else have this? I know people were looking to trade multiple hours in the early versions but I thought with the current version and trading hours set for 7,12 UTC that this wouldn't happen?

Paul

PS - It did close at TP though so nice pips

[SteveHopwood]

Live Scalpy is turned off until Monday. I shall leave the demos running just to see what happens.

This week:

Last week.png

Since going live on May 16th:

cumulative live.png

[SteveHopwood]

This is weird. I set up an H1 chart with a 960 period moving average, set to exponential and price close, then dragged all of today's trades on to it one by one - or two by two when the same pair had traded twice.

<Note to noobs. Dragging orders onto a chart automatically changes it to the pair in question.>

30 trades today. None of them were taken on the 'wrong' side of the EMA but 5 were taken after the previous candle moving in the 'wrong' direction. 3 of these closed in profit.

I also looked at the 'wrong' charts to see if two candles ago closed in the 'correct' direction and we are not quite waiting long enough for new candles to form. Nope. Besides, if a pair does not receive a tick inside 5 minutes then it is dead, not asleep.

The code is so simple that I do not see how it can be wrong - especially as we see the correct setups most of the time.

Bloop spotters, please have a look to see if I have missed anything. It is easy to follow. Do a search for this command:
getDirection(symbol, TradingTimeFrame, pairIndex);

You can see the correct pair symbol and time frame being sent. I always send pairIndex because of the number of times I don't bother and then find I need to, so it is not relevant here.

Go to:
void getDirection(string symbol, int tf, int pairIndex)

The code is so basic that it cannot possibly be wrong.

Then do a search for:
//Confirm a long signal

The 'symbol' variable has not changed since the getDirection command, so go to:
bool confirmLongSignal(string symbol, int pairIndes)

Again, code so simple and clear. What can go wrong? The short signal confirmation function is directly underneath.

Ideas, anyone?

[pivotter]

we always assume that per request all data is correctly retrieved, but if from iClose or iOpen the retrieved value is a zero instead of the correct value you would also get a wrong candle direction.

We can test it with print the retrieved values.

[biobier]

What about calling refreshrates in before? https://docs.mql4.com/series/refreshrates