Gday: a D1 Stochastic OB/OS trading robot

[ROBST3R]

i don`t have no new trades in 2 days! Over 23 pairs.
Some of you got the e/u trades and some others with their new candle!
Someone else experiencing this?

[SWG123]

i don`t have no new trades in 2 days! Over 23 pairs.
Some of you got the e/u trades and some others with their new candle!
Someone else experiencing this?

I just loaded it on Cowboy Go Markets, 26 pairs. It immediately opened an EJ buy and GCAD sell.

[ROBST3R]

i don`t have no new trades in 2 days! Over 23 pairs.
Some of you got the e/u trades and some others with their new candle!
Someone else experiencing this?

I just loaded it on Cowboy Go Markets, 26 pairs. It immediately opened an EJ buy and GCAD sell.

gbp/cad opened on 20december so it`s logical that these didn`t opened again:) Euro/jpy opens and closes directly! How can this happen? i have the newest ea

I see the take profit and stoploss are on 0 now!

edit: With the passage of time, I am evolving a system whereby setting the first input in a block of inputs turns off that feature. This cuts down on a few Usexxxx inputs.

The TakeProfit and StopLoss inputs override everything else. If > 0, Gday uses these to calculat sl/tp regardless of your other settings. You turn these off by setting them to zero.
If TakeProfit or StopLoss respectively are set to zero, then Gday looks at the Volatility calculations:

[SWG123]

i don`t have no new trades in 2 days! Over 23 pairs.
Some of you got the e/u trades and some others with their new candle!
Someone else experiencing this?

I just loaded it on Cowboy Go Markets, 26 pairs. It immediately opened an EJ buy and GCAD sell.

gbp/cad opened on 20december so it`s logical that these didn`t opened again:) Euro/jpy opens and closes directly! How can this happen? i have the newest ea

I see the take profit and stoploss are on 0 now

Yes, I thought it would wait for a new daily candle - Steve? :

[SteveHopwood]

Yes, I thought it would wait for a new daily candle - Steve? :

I did forget to explicitly declare ChillOutShelley as 'false' but mql4 booleans default to false when created, unless coded differently. If ChillOutShelley is not explicitly selected by turning to 'true', then Gday automatically operates StrictDisciplinarianShelley.

Just in case it is possible for a boolean to be created 'true', I have added this to the code in the post 1 update. This is no big deal, so I don't suggest people rush to download. Only an idiot runs an EA without first making sure s/he both understands and has checked the key inputs, so users should have noticed this and made their own choice of adherence mode, so I assume that is not the case here.

I can see nothing in the code that will allow a trade at any other time of day than the open of the new D1 candle, unless ChillOutShelley is explicitly selected. If this happens to anyone, delete your current version and redownload.

[SWG123]

Yes, I thought it would wait for a new daily candle - Steve? :

I did forget to explicitly declare ChillOutShelley as 'false' but mql4 booleans default to false when created, unless coded differently. If ChillOutShelley is not explicitly selected by turning to 'true', then Gday automatically operates StrictDisciplinarianShelley.

Just in case it is possible for a boolean to be created 'true', I have added this to the code in the post 1 update. This is no big deal, so I don't suggest people rush to download. Only an idiot runs an EA without first making sure s/he both understands and has checked the key inputs, so users should have noticed this and made their own choice of adherence mode, so I assume that is not the case here.

I can see nothing in the code that will allow a trade at any other time of day than the open of the new D1 candle, unless ChillOutShelley is explicitly selected. If this happens to anyone, delete your current version and redownload.

Hmm. I explicitly selected StrictDisciplinarianShelley. Set file attached.

[gaheitman]

Yes, I thought it would wait for a new daily candle - Steve? :

I did forget to explicitly declare ChillOutShelley as 'false' but mql4 booleans default to false when created, unless coded differently. If ChillOutShelley is not explicitly selected by turning to 'true', then Gday automatically operates StrictDisciplinarianShelley.

Just in case it is possible for a boolean to be created 'true', I have added this to the code in the post 1 update. This is no big deal, so I don't suggest people rush to download. Only an idiot runs an EA without first making sure s/he both understands and has checked the key inputs, so users should have noticed this and made their own choice of adherence mode, so I assume that is not the case here.

I can see nothing in the code that will allow a trade at any other time of day than the open of the new D1 candle, unless ChillOutShelley is explicitly selected. If this happens to anyone, delete your current version and redownload.

Hmm. I explicitly selected StrictDisciplinarianShelley. Set file attached.

Was the history updated for each of the pairs before you attached the EA? I've always wondered what would happen if you had the ea configured and saved it as the default template and then started opening new charts. I think the EA would see the new bars appear, but I'm not certain.

[SWG123]

[/quote]Was the history updated for each of the pairs before you attached the EA? I've always wondered what would happen if you had the ea configured and saved it as the default template and then started opening new charts. I think the EA would see the new bars appear, but I'm not certain.[/quote]

No, I just created and applied the template like I normally do. It was a brand new Empty4 install, I've never used Cowboy Go Markets before. However I do think there could be a problem with the data feed as I've since had a buy trade open on EU and it shouldn't be valid. I'm going to delete, download another platform and start again.

At least the false trades were profitable

[SteveHopwood]

At least the false trades were profitable

The code that separates to two adherence rules is so simple that a child could code it.

I notice that init() in scoobs has a 1 minute sleep time on startup. I have not asked him why; maybe he is giving the platform time to sort out all its wrinkles before unleashing the code.

Never mind exactly how this works if you are not a coder; in outline, this is how Gday stops a trade being sent until the new candle forms:

• Declare a variable OldBars that is equal to the number of bars on the D1 chart.
  Do not allow a trade until there is a new candle, meaning that OldBars no longer equals the bars on the chart. Therefore a new candle has formed, so the new day has dawned.

Maybe it is possible for the charts to be incorrectly populated, or for it to be possible in some way for the function that counts the bars to return an incorrect result until the EA has got going properly? No idea really. Empty4 is such a turd that anything is possible.

Any takers for a 1 minute sleep on startup? Any other suggestions, George?

[gaheitman]

At least the false trades were profitable

The code that separates to two adherence rules is so simple that a child could code it.

I notice that init() in scoobs has a 1 minute sleep time on startup. I have not asked him why; maybe he is giving the platform time to sort out all its wrinkles before unleashing the code.

Never mind exactly how this works if you are not a coder; in outline, this is how Gday stops a trade being sent until the new candle forms:

• Declare a variable OldBars that is equal to the number of bars on the D1 chart.
  Do not allow a trade until there is a new candle, meaning that OldBars no longer equals the bars on the chart. Therefore a new candle has formed, so the new day has dawned.

Maybe it is possible for the charts to be incorrectly populated, or for it to be possible in some way for the function that counts the bars to return an incorrect result until the EA has got going properly? No idea really. Empty4 is such a turd that anything is possible.

Any takers for a 1 minute sleep on startup? Any other suggestions, George?

Well, I've been infatuated with the bars != Bars logic since I first saw it, but it does seem susceptible to this kind of error. Especially on a brand spankin' new account. Perhaps the safer, less sexy CurrentBarTime != Time[0] is a better bet for this sort of thing.