When backtesting P.CONTEST I can't get the result the contest is showing (28 476.80 Equity). I wonder why...backtesing always shows way worse results.
Anybody else experiencing this?
Anybody else experiencing this?
Hi Tom!
Well, it seems that you are one of those that have better results with Mode 3 than others. I think we will keep this Mode <?xml:namespace prefix = st1 ns = "urn:schemas-microsoft-com:office:smarttags" /><st1:metricconverter w:st="on" ProductID="3 in">3 in</st1:metricconverter> for now. Tomorrow is Sunday so I have the whole day to investigate Mode 3 because I think it needs improvement! Thanks for your contribution Tom (what are your “testing-plans” for next week?)<?xml:namespace prefix = o ns = "urn:schemas-microsoft-com:office:office" /><o></o
<o
I will prepare 1, 2, 3 modes separately on 3 terminals.
Do you have any suggestions ?
- #729
- Nov 11, 2006 5:18pm Nov 11, 2006 5:18pm
Reading through the thread, there was a suggestion on providing an option (or new mode if you will) for scaling down as the person raising the point observed that often times price will initially move against the opening position with Phoenix before it finds its groove. I think somehow that got misunderstood into scaling up, or adding to the position as price moves in the desired direction. Or, maybe there was no connection between the two ideas...
Anyway, I'd like to renew the suggestion for at least one scaled out entry at a user-defined threshold (e.g. 20-30 pips). I would keep the SL and TP the same as the initial Classic position, just add an additional entry at a more attractive price. With the superiod win/loss % and profit factor ratios of Phoenix Classic, this could really tally up the pips.
What do you think Hendrick and gang?
Bill
Anyway, I'd like to renew the suggestion for at least one scaled out entry at a user-defined threshold (e.g. 20-30 pips). I would keep the SL and TP the same as the initial Classic position, just add an additional entry at a more attractive price. With the superiod win/loss % and profit factor ratios of Phoenix Classic, this could really tally up the pips.
What do you think Hendrick and gang?
Bill
Just a quick recap of the development of the next version of <st1
<o
Other additions are:<o
<o
- closing trades after a certain amount of hours (seems to work for a couple of pairs).<o
- moving your SL to breakeven when your trade is in profit.<o
<o
... And so on and so on.<o
<o
I think <st1:city w:st="on"><st1
<o
And now a very small critical remark:<o
<o
When the new <st1:city w:st="on"><st1
<o
And let be honest, in the Contest <st1:city w:st="on"><st1
- #733
- Nov 12, 2006 1:40am Nov 12, 2006 1:40am
Hendrick,
I just have a question about the signals Phoenix generates. During this week I've seen that depending when I oppen the EA, the buy/sell position opened varies. For example, this week I opened the EA in one computer and a few minutes later it opened a sell position in USD/JPY. Then I decided to start Phoenix in my second computer and a few moments later it opened a buy position in USD/JPY.
So I had a buy and sell position for USD/JPY in two different computers at the same time!
In the comments on the Championship website, someone called "Freaky" wrote this:
Hi Hendrick,
I use your EA since 2 weeks. It gives me 8 TP in a row! GREAT.
I've made an indicator showing the signals made by Phoenix.
Here it goes:
If you see the picture and if those signals are right, it seems that Phoenix can give two or more opposite signals with little time diference. And this is similar to what happened to me during last week.
Could you clear this to me?
Thanks a lot!
I still haven't used this indicator, but looking at this picture my first impression is that <?xml:namespace prefix = st1 ns = "urn:schemas-microsoft-com:office:smarttags" /><st1:City w:st="on"><st1
lace w:st="on">Phoenix</st1lace></st1:City> is generating too much signals. A solution to this could be to build in some sort of mechanism that will flatten out the number of signals. But on the other hand <st1:City w:st="on"><st1lace w:st="on">Phoenix</st1lace></st1:City> needs to make decisions in a very short time when it has to deal with spikes. One time I noticed that <st1:City w:st="on"><st1lace w:st="on">Phoenix</st1lace></st1:City> reacted as fast as lightning to a spike and made a profitable trade in only 20 seconds. So I'm not sure at this moment what will be the best solution for this. I will study this indicator closely in the coming week. Thanks!<?xml:namespace prefix = o ns = "urn:schemas-microsoft-com:office:office" /><o></o><o
> </o>
- #734
- Nov 12, 2006 1:54am Nov 12, 2006 1:54am
Hi there,
I feell like I am tuned to this threads after reading it for a few hours
and looking for a little feedback
Thank you for clarifying that post about you 'going private' and I understand now that
inspiration you have created will stay where it is now.
I found the place with your buddy buddies (FF) and it is inspirational I'll tell you
About ideas for new developments in Phoenix
I just have this wild gess that you already maybe doing this in Phoenix
as you mentioned about 'your little secret'. Sure averybody have to have some
and I do not want to break it.
I just had these in may head and do not know how to (MQL)
.
So... It is about natural laws again.
As you have signal1.. signal2..signal 3....
I am gessing that combination of these sinals let you follow natural laws of repeatable patterns
and it is just have to be timed in sync with real pair price movement in 'wave like' fashion
It is great and will lead to great success as long as we in sync.
I am maybe totally off on this but this is the reason to have all timeframes signals to see whole picture
as m15 maybe missing the view of some big turn.
Still looking for your feedback on higher time frame Signal(s) within m15
As I understand Phoenix development will continue ...thank you very much
My post #620 about this on f-tsd did not really touched anybody
Just tell me if it is so 'out of line' that I will not become annoying and go some place else
One thing to say 'No' and another to ignore it
Maybe it is not possible in MQL technically??
thanks again hendrick
I am at your feet
and you can write to corner_house at fastmailDOTfm
lace w:st="on">Phoenix</st1lace></st1:City> with "time". I think that the Contest version is now completely in sync and this explains also why others don't get the same results. For me it's still a mystery how to get <st1:City w:st="on"><st1lace w:st="on">Phoenix</st1lace></st1:City> in sync. It has maybe to do with the time you put the Phoenix EA to your chart. I've noticed that the best time to do so is Sunday before the market opens or start <st1:City w:st="on"><st1lace w:st="on">Phoenix</st1lace></st1:City> an hour after a big news event. So picking the right time to start <st1:City w:st="on"><st1lace w:st="on">Phoenix</st1lace></st1:City> seems to be very important. I will follow your suggestion about the higher time-frames. Maybe you can do some tests yourself next week. Start <st1:City w:st="on"><st1lace w:st="on">Phoenix</st1lace></st1:City> at different times and then study your trades at the end of the week to see if you can find something. Thanks for your contribution. I think this issue of the right start time will become more and more important in the coming weeks.<?xml:namespace prefix = o ns = "urn:schemas-microsoft-com:office:office" /><o></o><o
> </o>
Well, I think you're absolutely right about the synchronization of <?xml:namespace prefix = st1 ns = "urn:schemas-microsoft-com:office:smarttags" /><st1:City w:st="on"><st1
This can be explained in the following way. The signals for entering positions appears very often, however if Phoenix has already opened a position, it ignores all signals until this position is closed.
So, you have one position. When you put another Phoenix it opens position, that is different to the first one. However, later, the first position or second one is closed, and if there are not any new signals for entering and the last position is also closed, new positions will be opened at the same time by the same signals.
- #736
- Nov 12, 2006 3:52am Nov 12, 2006 3:52am
Hendrick, I've been studying during last week this problem of when Phoenix should be put on a chart with the help of two terminals and 16 charts. There can be difference if you put EA now and 15 minutes later, for example. However, this difference dissapears in 2 or three trades. After 1 trades, now Phoenix 5 on my computer opens positions exactly as Phoenix 4 Contest in the championship.
This can be explained in the following way. The signals for entering positions appears very often, however if Phoenix has already opened a position, it ignores all signals until this position is closed.
So, you have one position. When you put another Phoenix it opens position, that is different to the first one. However, later, the first position or second one is closed, and if there are not any new signals for entering and the last position is also closed, new positions will be opened at the same time by the same signals.
></o>