spotdespot wrote:

forexdj wrote: Does anyone know what could be the cause? I've gone through the thread and the UG twice but I havent been able to figure out why.

Ala! Kumbe! (just looked up your signature ).

I have it too and it is marked as a re-entry trade but it doesn't make sense to me either. I didn't notice until you highlighted it - good spot. I would have expected a valid re-entry trade to have opened at the OPEN of the same candle which it opened at the high of.

Something a bit odd there. I am not sure how to try to track it down to be honest. Anyone else any ideas?

Cheers,
Dave.

forexdj wrote: Analogue ama digital? Hahaha! Nice to know am not the only one from our beautiful country here!
How is BASA treating you? Have you tracked down what caused the strange trade yesterday?

spotdespot wrote:

forexdj wrote: Analogue ama digital? Hahaha! Nice to know am not the only one from our beautiful country here!
How is BASA treating you? Have you tracked down what caused the strange trade yesterday?

I am actually from the UK but your signature intrigued me so I wanted to find out what it meant!

Apart from the discussions in the previous posts we didn't find out definitively what caused it. It is worth keeping an eye out to see if it happens again.

Cheers,
Dave.

SteveHopwood wrote:

spotdespot wrote: I can't think of any reason why any Main or Re-entry trade would open part way through a H4 candle - whatever the settings. For me that is the main mystery.
.

If the spread widens beyond MultiplierToDetectStopHunt * AverageSpread, BASA (and any other ea coded from later versions of my shell) will hang up its hat with a "EA suspended during a massive spread event" or some such wording. It will continue to monitor open trades but will not attempt to send new trades until the spread returns to within acceptable bounds.

This all happens within void CheckForSpreadWidening(), so the code to tell BASA that a new candle is not reached at the end of start(). So far as BASA is concerned, it is looking at a new candle even though that candle may be some minutes old.

Shouldn't be a problem, but we can monitor this and change if need be.

forexdj wrote: I have noticed another strange trade opening behaviour this evening. Today, my trading machine was off from 7am to 5pm. I switched it on and opened Empty4, then I loaded the BASA template at 5:32pm and immediately it took 4 trades. EURJPY, EURNZD, GBPNZD and NZDCHF.
Am still digging the UG and google for the reasons for such trades. Who has a clue for what might have happened?

milanese wrote:
If you switched off your Empty4 and after some time you reload it, there are a lot of ticks incoming at the same moment, this causes the strange behaviour of BASA..

Cheers

Tommaso

forexdj wrote:I have noticed another strange trade opening behaviour this evening. Today, my trading machine was off from 7am to 5pm. I switched it on and opened Empty4, then I loaded the BASA template at 5:32pm and immediately it took 4 trades. EURJPY, EURNZD, GBPNZD and NZDCHF.
Am still digging the UG and google for the reasons for such trades. Who has a clue for what might have happened?

SteveHopwood wrote:

fxozgirl wrote: Also, I run all my BASA EA's with RunInSpreadDetectorMode set to true to try and avoid these spikes. The EA won't trade if it detects a rapid widening of the spread

You don't need to do this. After the first run, the function keeps a running tally of the spread and recalculates the average every 500 ticks. BASA, and any other ea using this feature, avoids adding a huge spike event that would skew the calculation by pausing during a massive spread event - hence the screen message when this happens.

All you are doing by running with RunInSpreadDetectorMode set to true is clogging up your cpu when you restart your platform - details in the User Guide.

Those of us with GP, the enormous "Widest since loading" happens at 10.00 London time when the liquidity providers make their swap calculations. Not impressed. At least the figures show up. Some time ago, Cowboy Cowboy IBFX Aussie emailed all their 'valued clients' (i.e. people they consider too thick to spot what they are up to) to explain that they were disallowing trading for, I think, one minute at 10.00 pm London time. They dressed it up as wanting to give their dimwitted, oops sorry valued clients time to pause and reflect. Or some such equally moronic wording - don't remember the details.

Definitely nothing to do with hiding the fact that they do ridiculous things to their spread whilst calculating swap. A computerised process that takes a fraction of a second given the power of the computers that brokers own. Not running a brokerage from the kind of lappy I am using to type this, I suspect.

SteveHopwood wrote:

spotdespot wrote: I can't think of any reason why any Main or Re-entry trade would open part way through a H4 candle - whatever the settings. For me that is the main mystery.
.

If the spread widens beyond MultiplierToDetectStopHunt * AverageSpread, BASA (and any other ea coded from later versions of my shell) will hang up its hat with a "EA suspended during a massive spread event" or some such wording. It will continue to monitor open trades but will not attempt to send new trades until the spread returns to within acceptable bounds.

This all happens within void CheckForSpreadWidening(), so the code to tell BASA that a new candle is not reached at the end of start(). So far as BASA is concerned, it is looking at a new candle even though that candle may be some minutes old.

Shouldn't be a problem, but we can monitor this and change if need be.

SteveHopwood wrote:

forexdj wrote:I have noticed another strange trade opening behaviour this evening. Today, my trading machine was off from 7am to 5pm. I switched it on and opened Empty4, then I loaded the BASA template at 5:32pm and immediately it took 4 trades. EURJPY, EURNZD, GBPNZD and NZDCHF.
Am still digging the UG and google for the reasons for such trades. Who has a clue for what might have happened?

BASA thinks it is at the start of a new candle if you switch on whilst a candle is forming. If those trades would have been correct at the start of the candle then this is not a problem. If they were not correct, then it is.

It would be the work of seconds to add code to force BASA to wait for the open of a new candle at loadup.

Also, I can add a 30 second wait before jumping into life. Have a look at those trades and work out if they were correct had it been the open of a new candle.