Menu
Sister Sites

Options

Bookmark Thread

First Page First Unread Last Page Last Post

Print Thread

Similar Threads

Trading multipair triangles, no stoploss 78 replies

'Blessing' EA Modification Wanted 3 replies

Single, Few Pair Traders (1-4) vs. MultiPair Traders (8-20) 0 replies

Coding Request for Multipair MTF ADR Dashboard 2 replies

trying to make a multipair buy and sell script 6 replies

Attachments: Blessing Multipair EA
Exit Attachments

Blessing Multipair EA

Quoting richard96816
{quote} Why not. The reason you have code to use at all is because of Blessing's long tradition of open source. You have something else, possibly nefarious, in mind?
Why not?...
1) because I have an MQL4->MQL5 converter, so the "source" is basically unchanged
2) because the objective of the exercise was to help Ursinho spot errors much faster than he would have if relying on forward-testing

The reason you have code to use at all is because of Blessing's long tradition of open source.
- that's great... but who are you to presume that I even use Blessing at all? (for the record, I don't)

You have something else, possibly nefarious, in mind?
- sad to see you belittle yourself with that snide comment
Quoting fxtrue
1) because I have an MQL4->MQL5 converter, so the "source" is basically unchanged 2) because the objective of the exercise was to help Ursinho spot errors much faster than he would have if relying on forward-testing
1) already thought so ;-)
2) really appreciate it, thanks alot

And more of all I would be happy if we could focus on the code and settings. Battles are wasted time and energy.
I'm attaching my edited source code version of "gamma" (for MT4) plus a compiled MT5 version.

Please note that the following:

1) there are almost 40 edits / fixes in this version - several of which are critical (they can be located by searching for "fxtrue")

2) I would appreciate my changes being carried through to all new versions of BlessingLite - particularly as many are needed for the MT5 version and I don't have time to waste re-implementing the same fixes over and over

3) there is a potentially-serious underlying issue with incorrectly initialised variables (they intermittently equate to EMPTY_VALUE and result in erroneous values further down the computational chain - sometimes causing 'divide by zero' critical errors) - I have applied fixes to the places I have identified, but the code would benefit greatly from someone trawling through it and finding the root causes

4) the edited source code compiles happily in MT4 and *appears* to run happily in MT5... but I promise nothing, so use entirely at your own risk

So, have fun and report any oddities you discover
Attached File(s)
File Type: ex5 BlessingLite_3_v3.9.6.34_gamma_fxtrue.ex5   788 KB | 978 downloads
File Type: mq4 BlessingLite_3_v3.9.6.34_gamma_fxtrue.mq4   134 KB | 1,305 downloads
First of all: thanks again for your help, fxtrue! That's the cooperation I was hoping for. Thumbs up and many pips for you!

Quoting fxtrue
3) there is a potentially-serious underlying issue with incorrectly initialised variables (they intermittently equate to EMPTY_VALUE and result in erroneous values further down the computational chain - sometimes causing 'divide by zero' critical errors) - I have applied fixes to the places I have identified, but the code would benefit greatly from someone trawling through it and finding the root causes
This is an issue in the "original blessings" already. I was really surprised when I did the transmission to the multi-pair and went through the code.
No secure against divide by zero. Variables declared, never got initial values (even if it is a zero) yet used.
I thought -as the program was open such a long time and was coded by professionals- that this would not appear in a ...09 version anymore.

This weekend I was playing with setfiles of the "original blessing" and you cannot believe how often the EA crashed because of zero divides.
Quoting ursinho4711
... This is an issue in the "original blessings" already. I was really surprised when I did the transmission to the multi-pair and went through the code. No secure against divide by zero. Variables declared, never got initial values (even if it is a zero) yet used. I thought -as the program was open such a long time and was coded by professionals- that this would not appear in a ...09 version anymore. This weekend I was playing with setfiles of the "original blessing" and you cannot believe how often the EA crashed because of zero divides.
I'm not sure about that 'coded by professionals' claim. Version .09 has been around quite a long time. It works surprisingly well when it works. I think there's been a realization by many that it needs to be rewritten. But that's a big job, given the poor debugging tools available and many other factors. I think most folks tend to respect the code and try to make as few changes as possible. That's a common approach taken by 'professionals' when fixing bugs or making small changes on someone else's code.

Code produced by groups is problematic, especially without coherent rules.

Blessing still needs a complete rewrite. I'm too busy using it. That may change. If you see errors that can be easily fixed please point them out when it's convenient. I am admittedly more a user than a writer on this project and my time is sometimes limited.

Thanks.
Quoting fxtrue
I'm attaching my edited source code version of "gamma" (for MT4) plus a compiled MT5 version. Please note that the following: 1) there are almost 40 edits / fixes in this version - several of which are critical (they can be located by searching for "fxtrue") 2) I would appreciate my changes being carried through to all new versions of BlessingLite - particularly as many are needed for the MT5 version and I don't have time to waste re-implementing the same fixes over and over 3) there is a potentially-serious underlying issue with incorrectly initialised...
Hi,fxtrue
I would like to try optimize the setting value
for MT5 version BlessingLite_3_v3.9.6.34_gamma_fxtrue.ex5
Could you please help to modify a little for me can testing?
all indicator has an option on the setting value, MA, CCI, Bollinger bands, stochastic, MACD
Can possible add setting with all value of indicators more like time frame and shift value
and all code Period() or _Period change it to ENUM input for select on setting (dropdown like on smart grid setting)
if you can help to modify a little testing optimize version will be great, I can try to optimize the best value for everyone.
Thank you
Quoting muggle
{quote} Could you please help to modify a little for me can testing?
I'm sorry, but I have to decline - the last thing I want to do is create yet another fork of Blessing, but I'm happy to create MT5 versions of whatever Ursinho releases.
Quoting ursinho4711
I was really surprised when I did the transmission to the multi-pair and went through the code. No secure against divide by zero. Variables declared, never got initial values (even if it is a zero) yet used.
The core issue is that Blessing was originally coded by "enthusiastic amateurs" prior to build 600 of MT4 (when "strict" came into being) and those earlier versions of MQL4 were very tolerant of sloppy coding, so variables would be automatically initialised if the coder forgot to do it, and variable types were not enforced. This meant that double types were often used in place of integer parameters and integers were used for dates and/or booleans, so calculations that should have returned "int" values might have unplanned decimal portions, "decimal" results may have been unwittingly truncated, etc. ....fun times
Quoting fxtrue
....fun times
I already learned more than thirty years ago not to do things like that. But these times were also fun (more than today)
  • Post #330
  • Quote
  • Edited Feb 13, 2020 1:45am Feb 12, 2020 9:20pm | Edited Feb 13, 2020 1:45am
Thank you Mike McKeough, the Blessing Development Group, ursinho4711 and fxtrue (and everyone) for the work you've put into this. I've been testing it live for the second day now... interesting. I basically used your set file settings ursinho4711, with some exceptions (nano account). I'll attempt to keep you posted with results and any potential suggestions. I've never done any coding (unless you count a year back in 7th grade, in which I really don't remember a thing), or even really even looked into a code. The last two days, however, I actually took the moment to open up this EA, and take a look at it's guts. It's very interesting how it's all laid out and is seemingly in "layers." It shows how much time was really put into this.
Quoting ursinho4711
Remember that post? https://www.forexfactory.com/showthr...7#post12551567 Well, I used the settings and made a backtest from 01.Nov.2019 to 10.Jan.2020. 5 Minutes timeframe, for all 28 pairs. What can I say: that already looks like the winner to be tested on the Blessing-Multipair. Can't wait for Sidney open... Here are the results: {image}
hi ursinho, account size did this test perform on?
As a cautionary heads up (I'm not quite sure what happened, yet), I had the settings set for 10 trades at once. I went away and came back to my computer to see more than 20 active trades. I then went into the properties and changed the setting to ***NO NEW TRADES***, turned it to True, and after hitting ok, it immediately Closed ALL the trades. It was not ***CLOSE ALL NOW***, but no new trades. So, not sure what happened there. After reloading chart with EA and getting 25 more trades, I had to just turn all entries to disable to stop more trades. I didn't even think there could be more than 15 at once. Hmm... Will do more testing.
Quoting Dowde
As a cautionary heads up (I'm not quite sure what happened, yet), I had the settings set for 10 trades at once. I went away and came back to my computer to see more than 20 active trades. I then went into the properties and changed the setting to ***NO NEW TRADES***, turned it to True, and after hitting ok, it immediately Closed ALL the trades. It was not ***CLOSE ALL NOW***, but no new trades. So, not sure what happened there. After reloading chart with EA and getting 25 more trades, I had to just turn all entries to disable to stop more trades....
Hi Dowde, thanks for the feedback!

Number of trades is still from the "old" blessing and relates to one pair, not all pairs of the list. So if you have list of 28 pairs there could be 280 trades.
We should install a new parameter "pairs at once".
"No new trades" should not close all, just not allow new trades (as the name sais). That's a bug, thanks for reporting it. At the moment, this is what I also do, is to set all entries to disable, as you did correctly...
Quoting ursinho4711
{quote} Hi Dowde, thanks for the feedback! Number of trades is still from the "old" blessing and relates to one pair, not all pairs of the list. So if you have list of 28 pairs there could be 280 trades. We should install a new parameter "pairs at once". "No new trades" should not close all, just not allow new trades (as the name sais). That's a bug, thanks for reporting it. At the moment, this is what I also do, is to set all entries to disable, as you did correctly...
The NO NEW TRADES entry controls the ShutDown variable.

To be precise, it stops allowing trades once the basket is closed and the number of open trades drops to zero.

The intent is to allow the current basket, if any, to run to completion.

There are all kinds of ways of controlling your level of trading and the impact on your account. None of them is really perfect for all situations. (Other than simply keeping a surplus of extra cash in your account! Which is a very good idea.)

MinMarginPercent may be helpful. There are various other controls that could be added. Some multi-pair EAs provide quite a list of selections.
Hello. You can publish the template, the best template that is working, and the optimal time frame to place the Ea.
[quote=ursinho4711;12744909]{quote} 1)

Here are those to files we should work with and code in the Blessing Multi pair.

Cheers.
Attached File(s)
File Type: mq4 RSIOMA Alert.mq4   3 KB | 395 downloads
Attached File(s)
File Type: mq4 RSIOMA.mq4   6 KB | 423 downloads
It's nice having all the entry possibilities. So far I've only been using MA and Stochastic with decent results. It would be interesting if we, with the EA, had the ability to Enter a trade only when two or more of the parameters were met, e.g., MA and Bollinger both hit. Obviously, this may give us more precise trades...
Quoting Dowde
It's nice having all the entry possibilities. So far I've only been using MA and Stochastic with decent results. It would be interesting if we, with the EA, had the ability to Enter a trade only when two or more of the parameters were met, e.g., MA and Bollinger both hit. Obviously, this may give us more precise trades...
You can it's just possibile by Ea
Emmanuel,

where would one find Evolution? I’ve tried but the links on his website don’t work...

thankyou.

Quoting emmanuel7788
{quote} Blessing3 is open source. however BlessingPro is not and become a commercial product by jtatoday. the newer versions like Evolution are all non-open source.
Never Givin' Up..
By using this setting BlessingV24beta-XUSUSDTest.set.txt , can we trade GU by replace xususd wih GU ?
0 traders viewing now