Symphonie EA

[SteveHopwood]

Everyone, make sure you have the correct version of the Sentiment indi; this is the one in post 1 that Matt modified to remove the scam thingy.

[cuzgeorge]

I understand. But you must admit to go from this... Screenshot 209 (bottom)...... to this Screenshot 210(top) is many improved because it cleans up your chart window dramatically to keep you focused on the big picture price action by making it many easier to read.

Evaluator.

P.S. The indikators are the same but the Matrix just reorganizes them in a easier format for reading the signals.

I do indeed see and likee muchee.

Not going to do anything with this tonight (just gone midnight here in the UK) but will revise the ea again in the morning, to use the combi.

Fabulous contributions Evaluator. Many thanks. If major developments in your trading are happening at FF, I have no problem with encouraging people to keep up with developments there and reporting back here for EA development - I cannot contribute meaningfully at FF because TIT has designated me a Filthy Commercial. Bear in mind, though, that the best brains in the business are here.

Thanks Steve for the great EA again and the time you're throwing into this. A woird of caution on the matrix's. I had installed 4 versions of them, 1.6; 1.7, 1.8 and one that was put out there by another memeber 2.1, i don't think Eval had ever commented on it, but i don't think 2.1 was actually part of his system.
but anyways, the problem i found when looking at the code of all of them, they are very labour intensive on the cpu processor, so with closer inspection you will notice when loading on a chart, it will take a little longer to load than normal. The 'lookbackbar' setting must definately come down from the '3000' mark and i find 300 is a much better number for this.

also, if you need to look back in the past, then a bigger number here is necessary, but at the cost of your processing power. Then, when i tried to compile them, standard, no changes, just messing around; they would come up with an error. was'nt sure what was causing this as i never managed to get to a solution. Never mentioned this as i know there was something wrong with them. Maybe MBKERNEL can check it out, i think Eval prefers the original 1.6, (please correct me Eval, if i'm wrong ), but when it works, it really simplifies the chart as Eval states.

they all worked, just seemed like it would make everything sticky or jerky, like a fuaulty Empty4. never trusted it completely, but as you say, "...that the best brains in the business are here."


Thanks for contributing here too Eval, it would'nt be the same without you.

missed you so much the last couple of days.hehe. Hows the weather in Germany?
regards
cuzgeorge

ps: attached files are all the versions i'm aware of and i've also included the heiken ashi matrix that would come up in the FF posts for Symphonie.
please remember, i think there is something wrong with them in the coding so just watch the stability of Empty4 if you load them.

[SteveHopwood]

but anyways, the problem i found when looking at the code of all of them, they are very labour intensive on the cpu processor, so with closer inspection you will notice when loading on a chart, it will take a little longer to load than normal. The 'lookbackbar' setting must definately come down from the '3000' mark and i find 300 is a much better number for this.

Having looked at the code, I had already decided not to use in in the EA, for the very reason you cite (along with my don't-fix-it-if-it-ain't-bust philosopy).

The problem with custom indis is one that lies at the heart of Empty4. When an EA consults an indicator, the platform loads it into memory, then unloads it again once it has responded to the EA call. This takes time.

Custom indis typically consist of a number of calls to the regular indicators that ship with Empty4, and manipulate the information thus gleaned according to what the coder requires. An indicator such as AllAverages will make a number of calls to standard indicator at each tick; each indi is loaded, used, then unloaded. This takes a long time.

An EA that includes calls to a custom indi such as AA makes the problem a little worse still because it makes a call to AA, then Empty4 loads it into memory, returns the result of the call to the EA, then unloads the indi. Ridiculous, but that is how it works, and is the reason that indis such as AA and VQ slow your machine.

And then, we put the EA on multiple charts.................................

The matrix makes 8 separate calls to the Symphonie indi's. At the start of each candle, our computers would slow to a crawl it would take ages to recover from.

[slowkey]

Steve,
I am encouraged so far. Last 5 trades have closed out with profit. Closed one out my self so I could change settings and put the latest version of the EA on the platform. Some are caught in sideways market moves today and initially I closed out some positions that were in the hole last night that got there because of user error . Very encouraged. Set my break even back to 20. Target just 30 on 5 minutes. Played with exit strategies but going back to exit strategy one for now. I am going to leave it this way except for changing out for any new versions of the EA and indicators. There are 3 positions open right now.

[SteveHopwood]

Steve,
I am encouraged so far. Last 5 trades have closed out with profit. Closed one out my self so I could change settings and put the latest version of the EA on the platform. Some are caught in sideways market moves today and initially I closed out some positions that were in the hole last night that got there because of user error . Very encouraged. Set my break even back to 20. Target just 30 on 5 minutes. Played with exit strategies but going back to exit strategy one for now. I am going to leave it this way except for changing out for any new versions of the EA and indicators. There are 3 positions open right now.

If people are going to start setting breakeven's, we might need a mechanism to stop the ea instantly re-entering should trading conditions still be correct. Let us know how you get on.

[slowkey]

If people are going to start setting breakeven's, we might need a mechanism to stop the ea instantly re-entering should trading conditions still be correct. Let us know how you get on.

[/quote]

Yes, sort of want to see how it behaves doing this too. In my mind wondering if these reentries will occur for losses or gains. If we are truly hitting extremes should be able to get some reentries and gains. Setting break even may help sideways markets and should not see as many reentries in those conditions hopefully. Will let you know.

[cuzgeorge]

If people are going to start setting breakeven's, we might need a mechanism to stop the ea instantly re-entering should trading conditions still be correct. Let us know how you get on.

Yes, sort of want to see how it behaves doing this too. In my mind wondering if these reentries will occur for losses or gains. If we are truly hitting extremes should be able to get some reentries and gains. Setting break even may help sideways markets and should not see as many reentries in those conditions hopefully. Will let you know.[/quote]


Hello all,
Slowkey, i am running exactly what you are, but still running the first version with the changed emotion indi by mbkennel.
it will be interesting to note any differences. i'll be running this until tomorrow morningish-early afternoon and then i'll post results. i'm not going to interfere in the trades taken and we can take it from there. i do however suspect Steve's input on the indis is going to make a difference.


Eval is right, it cleans up the screen alot, and allows for better viewing, but you MUST get used to it first. i battled a bit in the beginning, but find it invaluable now, and don't use the originals for direction. breaking the rules again, but it does give the same signal in theory.

attached are 2 pictures of the error i get at the bottom of the editor when i hit 'compile' dont pay attention to the name of the indi, with my name at the end, it's just for me to differentiate from the original when i was trying to fix it haha, or at least take a look at it

hope the big guns can check the indis out, you'll save the world a lot of electricity if you can solve these issues. again, i hope it's not just my comps having this error.
regards
george

[SteveHopwood]

That is not an error. There is a function within the code that is not actually being used, and so is not needed in the compiled code. Ignore it, or delete the function if it bothers you.

[slowkey]

Thanks George for your input. Steve I am going to set up a second demo on my main computer and run symphonie on the 30 minute time frame using exit strategy two this afternoon. I have always thought this would be a better choice of time frames to use with this system if traded as an EA. I have studied this period more manually. Than I can compare to the shorter period. Manually 5 minute trades nicely but I can look at a chart manually and say no I do not want this signal. Signals might be more reliable on a higher time frame for this EA. I will find out. Just basic setting as laid out by exit strategy two. Now going out and have a very late breakfast.

[Evaluator]

Having looked at the code, I had already decided not to use in in the EA, for the very reason you cite (along with my don't-fix-it-if-it-ain't-bust philosopy).

The problem with custom indis is one that lies at the heart of Empty4. When an EA consults an indicator, the platform loads it into memory, then unloads it again once it has responded to the EA call. This takes time.

Custom indis typically consist of a number of calls to the regular indicators that ship with Empty4, and manipulate the information thus gleaned according to what the coder requires. An indicator such as AllAverages will make a number of calls to standard indicator at each tick; each indi is loaded, used, then unloaded. This takes a long time.

An EA that includes calls to a custom indi such as AA makes the problem a little worse still because it makes a call to AA, then Empty4 loads it into memory, returns the result of the call to the EA, then unloads the indi. Ridiculous, but that is how it works, and is the reason that indis such as AA and VQ slow your machine.

And then, we put the EA on multiple charts.................................

The matrix makes 8 separate calls to the Symphonie indi's. At the start of each candle, our computers would slow to a crawl it would take ages to recover from.

Steve,

That is very interesting about Matrix. I know that Symphonie Matrix only looks to reorganize the signals given by the four Symphonie indikators. Is there a way to optimize the Matrix code and make it preform with less CPU impact? :

As to the EA following Symphonie Matrix i.e. your post;


PostPosted: Tue Mar 20, 2012 12:32 am

Evaluator wrote:I understand. But you must admit to go from this... Screenshot 209 (bottom)...... to this Screenshot 210(top) is many improved because it cleans up your chart window dramatically to keep you focused on the big picture price action by making it many easier to read.

Evaluator.

P.S. The indikators are the same but the Matrix just reorganizes them in a easier format for reading the signals.

I do indeed see and likee muchee.

Not going to do anything with this tonight (just gone midnight here in the UK) but will revise the ea again in the morning, to use the combi.

That seems like double work because Matrix only follow the signals from the four indikators to begin with and why would your make the EA follow Matrix that is just following the 4 indikators? I only included Symphonie Matrix to make your manual reading of Symphonie Signals easier for live testing purposes to let you see at one glance whether the EA matched what one would see in the Symphonie Matrix (i.e. Symphonie order signal)

Lastly, I have found that a very important component of trading Symphonie is multi-timeframe confirmation and direction of trend. This has been a major topic of discussion and that is why I mentioned the Symphonie 60-5 method for trading. It is possible to have the EA use 1 hour timeframe for direction then have the EA only execute 5 min signals in the same direction as the larger 1 hour Symphonie Signal direction? (see my post #8647 on the Symphonie Thread) [Link (http://www.forexfactory.com/showthread. ... ost5470997)]

I think you may find this will improve the results of the EA.

Regards,

Evaluator.