Perhaps sharing the mq5?No limitation whatsoever except when the user defines one for the spread in the settings
New EA SyTRAGE - My first MT5 scalper !
- Thread starter Symphoenix
- Start date
Hi Syphoenix,
I know that you've got to fix certain element in your code these days but, if you can explain more the money management...
Yseterday, I made some profit with 16 orders (version 1.4 and 1.5 ; 14 win/2 loss). But for exemple, I had two orders on EURGBP (not at the same time) ; one with 1.05 lot (win), the other with 3.05 lot (win too). My account demo is with 100.000 deposit.
Sy-Trage is a scalper, ok ; but perhaps a grid/martingale too ???
Thanks for reply and felicitation for your great job and sharing it.
I know that you've got to fix certain element in your code these days but, if you can explain more the money management...
Yseterday, I made some profit with 16 orders (version 1.4 and 1.5 ; 14 win/2 loss). But for exemple, I had two orders on EURGBP (not at the same time) ; one with 1.05 lot (win), the other with 3.05 lot (win too). My account demo is with 100.000 deposit.
Sy-Trage is a scalper, ok ; but perhaps a grid/martingale too ???
Thanks for reply and felicitation for your great job and sharing it.
- Credits
- 0
- Credits
- 0
Salut Jean-Léon !
Thanks for your kind words.
SyTrage started as a scalper but is now more an opportunist
It spots inefficiency on the short-term range by confronting different pairs between them and generates a deviation score.
If this score is larger than the sigma setting, it opens 3 positions on each of the 3 pairs which have the biggest potential.
The lot size is determined either by the EA or by the user. I suggest letting this EA do what it does the best : balancing !
Because that's what you noticed... MT5 considers a position as a group of deals on the same pair resulting from orders. It's quiet disturbing at first for a MQL4 coder.
Indeed, a position is an aggregate of several deals on the same pair. That's led to some misinterpretations
So SyTrage occasionnally increases the size of a position but it is not at the core of its philosophy, which is more mosquito-inspired (take and go)
BOOOUAAAF !...
I think I got rid of the nasty bugs...
BUT don't use this EA live as I doubt these results are rock solid.
Cheers
Yes Symphoenix, you're right ! There was indeed a glitch on the last version !
Thanksand bravo for this very great job !
zaenal arifin
New Member
- Credits
- 0
This is my review for this thread:
Goooood
Goooood
Speak french Syphoenix ?Salut Jean-Léon !
Thanks for your kind words.
SyTrage started as a scalper but is now more an opportunist
It spots inefficiency on the short-term range by confronting different pairs between them and generates a deviation score.
If this score is larger than the sigma setting, it opens 3 positions on each of the 3 pairs which have the biggest potential.
The lot size is determined either by the EA or by the user. I suggest letting this EA do what it does the best : balancing !
Because that's what you noticed... MT5 considers a position as a group of deals on the same pair resulting from orders. It's quiet disturbing at first for a MQL4 coder.
Indeed, a position is an aggregate of several deals on the same pair. That's led to some misinterpretations
So SyTrage occasionnally increases the size of a position but it is not at the core of its philosophy, which is more mosquito-inspired (take and go)
fredolaboulette
New Member
- Credits
- 0
Jean Leon I think so
- Credits
- 0
Oui, bien sûr !
Magnifique, mon anglais étant parfois déficient, nous pourrons toujours nous comprendre dans cette belle langue !Oui, bien sûr !
- Credits
- 0
If you want to speak in french maybe it's better to do it via PM.
Just thinking about the others here
Just thinking about the others here
I have similar result even with 99% backtast. I Will try to optimize
Agree with you : [email protected]If you want to speak in french maybe it's better to do it via PM.
Just thinking about the others here
A+
kurniawanasep
New Member
- Credits
- 0
- Credits
- 0
You can't use this EA for now because you have a suffix "!" after the name of the pairs.
Soon, I'll offer the possibility to adapt the names...
- Credits
- 0
I've discovered the OnBookEvent that allowed further optimisations.
For now, each currency is analyzed only when a new tick is incoming on the pair where the EA is placed.
With the OnBookEvent, the coder can build a panel of currencies to watch and whenever a new tick is incoming on any of the pairs considered, the EA kicks in.
The only bad thing is that it is not BTable !
So, here's a highly experimental build "BEE - BookEvent Edition" which implements the OnBookEvent...
Only for the adventurers
For now, each currency is analyzed only when a new tick is incoming on the pair where the EA is placed.
With the OnBookEvent, the coder can build a panel of currencies to watch and whenever a new tick is incoming on any of the pairs considered, the EA kicks in.
The only bad thing is that it is not BTable !
So, here's a highly experimental build "BEE - BookEvent Edition" which implements the OnBookEvent...
Only for the adventurers