Phoenix is here!

Quoting 4x4tx

Disliked

Phoenix uses local time. Hendrick's time zone is GMT+2. When you're figuring out his trading times, or his gamble times, convert his time zone to yours, and adjust your settings file accordingly.

Ignored

Quoting hidethereal

Disliked

Most likely because it's Friday. The optional friday trading will be a good feature to have on the new version.

Ignored

Quoting Yardie

Disliked

Oh the Martingale thing (doubling after each loss) is a recipe for disaster IMO. I think the Phoenix Surf function can be useful if you program Phoenix Regular to close those positions when it open a new position (and vice versa).

Ignored

Quoting hidethereal

Disliked

I agree, Martingale has never proven to be successful. This has been tried many times in Las Vegas at the roulette table.

We could add it though and see how it operates. With the option to turn it off.

Ignored

Quoting AZBOfin

Disliked

By extending the Comment function (around line 330) one can see the current calculated time.

,"\n","Local Time= ",TimeHour(LocalTime()),":",TimeMinute(LocalTime() ), " Server Time= ",TimeHour(CurTime()),":",TimeMinute(CurTime())


In my case this is what i get:

Local Time: 16:15
Server Time: 18:15
Time in the Market watch window: 18:15
My computer's local time (system clock): 09:15

I am running the PhoenixEA on a SBFX demo account and all time calculations are based on GMT (localtime() = GMT).
I don't know why, but that's how it is.
In my case LocalTime() <> local time. the localtime() functions returns always GMT.


AZBOfin

Ignored

Quoting smjones

Disliked

Now wait a minute here. the reason Martigale is not successful in LV, is because all games of chance in LV are negative expectancy. The Casino always has an edge and the table limit prevents Martingale from over coming the Advantage
I am not a fan of the Martingale approach, but it is mathematically sound in a fair game and even more so in a positive expectancy game... The real problem lies with do you have enough money to wait out incredible bad luck in a row.

Scott

Ignored

Quoting Sleuth

Disliked

AZBOfin.

I cannot yet decipher what all this means in relation to my question, however you're on the right track to providing an answer to the question I posed. You recognize that our PC's time, displacement from GMT time and our broker's time are likely to all be different and the source to the EA's timing is critical to know in order to evaluate the best times to trade on my PC with my broker and my displacement from GMT.


Much thanks to all of you who have taken the time to respond,

Alan

Ignored

Quoting Sleuth

Disliked

AZBOfin.

I cannot yet decipher what all this means in relation to my question, however you're on the right track to providing an answer to the question I posed. You recognize that our PC's time, displacement from GMT time and our broker's time are likely to all be different and the source to the EA's timing is critical to know in order to evaluate the best times to trade on my PC with my broker and my displacement from GMT.


Much thanks to all of you who have taken the time to respond,

Alan

Ignored

Quoting stockwet

Disliked

The second answer has been answered here and in the manual found on the first post. It is also answered by looking at the code itself. MetaTrader provides two time functions - CurTime() and LocalTime(). The first will get the current time from the server you're connected to. The second gets the time from your local computer's system clock.

Ignored

Quoting Hendrick

Disliked

Before I start my holydays Wednesday next week I will try to finish version 1.2 of <?xml:namespace prefix = st1 ns = "urn:schemas-microsoft-com:office:smarttags" /><st1:City w:st="on"><st1lace w:st="on">Phoenix</st1lace></st1:City>. It’s my intention to remove the Surf function completely as I’m not satisfied with the performance of it. Apart from that I think it’s after all not a good idea to try to make an EA that’s suitable for a ranging as well as a trending market. I think it’s better to focus on the fact that <st1:City w:st="on"><st1lace w:st="on">Phoenix</st1lace></st1:City> is a counter-trend EA that’s doing very well in a ranging market. We better try to improve <st1lace w:st="on"><st1:City w:st="on">Phoenix</st1:City></st1lace> insofar that it avoids the trending markets and gets the most out of a ranging market.<?xml:namespace prefix = o ns = "urn:schemas-microsoft-com:office:office" /><o></o>

<o></o>

How to improve <st1:City w:st="on"><st1lace w:st="on">Phoenix</st1lace></st1:City>?<o></o>

<o></o>

Avoid a trending/volatile market: I think SafePipsDistance and SafeArea are doing quit well. We maybe need a little tweaking.<o></o>

<o></o>

Avoid trading during certain parts of the day: The TradeFrom/TradeUntil will do.<o></o>

<o></o>

Money management is another issue. How to deal with loosing trades? There are 3 different approaches:<o></o>

<o></o>

<st1:City w:st="on"><st1lace w:st="on">Phoenix</st1lace></st1:City> is using a money management function were the number of lots is based on the free margin of your account. If the free margin decreases so will the number of lots and vice versa.<o></o>

<o></o>

After a loosing trade you open a new trade for the same pair and you increase your lots with the intention to level out the first loosing trade. If the second is a loser too you increase your lots again. So with a TP=25 and SL=50 and Lots=1 you get the following summary:<o></o>

<o></o>

First trade 1 lot looser -50<o></o>

Second trade 2 lots looser -100<o></o>

Third trade 4 lots looser -200<o></o>

Fourth trade 8 lots looser -400<o></o>

Fifth trade 16 lots and so on.<o></o>

<o></o>

The idea behind this is that after a couple of losers for the same pair it becomes more and more unlikely that the following trade is a loser too. I’ve never tried this approach, but I like the idea.<o></o>

<o></o>

The third approach is to decrease the number of lots after a couple of losers in a row (for different pairs). The idea behind this is that the EA apparently arrived in a less suitable period and have to wait for better times. Only after a couple of winning trades the number of lots will increase. I think we have sufficient options for <st1:City w:st="on"><st1lace w:st="on">Phoenix</st1lace></st1:City> to avoid these less suitable periods so we leave this approach for what it is.<o></o>

<o></o>

I think I will add the second option (increase the number of lots after a loosing trade) to the next version of <st1lace w:st="on"><st1:City w:st="on">Phoenix</st1:City></st1lace> for those who want to user this.<o></o>

<o></o>

At the end of every week I study all the trades that were made by <st1:City w:st="on"><st1lace w:st="on">Phoenix</st1lace></st1:City>. This is very useful and I’ve noticed that all the JPY-pairs need a different approach. I will tell you more in my next post.<o></o>

<o></o>

This weekend I will make a new version of <st1:City w:st="on"><st1lace w:st="on">Phoenix</st1lace></st1:City>, test it on Monday and post it Tuesday. Stay tuned!<o></o>

Ignored

Quoting wackena

Disliked

Hendrick,

If I read the code correctly in Phoenix v1.1, if using Micro account and MM that calculates, using 5% Risk, the lot size to 0.025, then the code below will return LotMM=0.

lotMM = MathRound(lotMM*10)/10; MathRound(0.025*10) will return 0.

You might consdier using the NormalizeDouble() function to round the lots. You can set number of decimal points needed.

if(Lots>0.1) Lots=NormalizeDouble(Lots,1); else Lots=NormalizeDouble(Lots,2);

Is my assumption above correct and could this code be useful?

Wackena

Ignored

Quoting Jordan Grecco

Disliked

Hello Hendrick,

First post for me and let me tell you , you are doing a heck of a job! Thank you very much for putting in all the time and effort to make this available to us and moreover thanks for taking the time to answer all our dumb and some not so dumb questions ;o)

Also to some of the other guys that are supporting this thread and are being extremely helpful and patient with newbies like me ... Thank you!
Really I mean THANK YOU, I read these posts and see how regular forum readers are also so very helpful to everybody.

I have been following this thread and have implemented version 1 in Metatrader 4. Everything was running fine and I had the little smiley face on the top right hand corner ... however now that version 1.1 is available I tried to run that and I am getting a little X in the place of the smiley face. I have tried for the last three hours, whatever I could and I just can't get it to run. What am I doing wrong or am I forgetting something?

Please Help.

Ignored

Quoting jhathawa

Disliked

Great thread! Learned alot from reading Firebird and Phoenix threads all the way thru today. I have a quick question which has probably been answered but I could not pinpoint it looking back. On the settings for the indicator the two levels (default to 50/-50) come from your "safe area" setting, correct ? Also, under Inputs is a variable called PC with a value of 6. What value is this ? Thx.

Ignored

Quoting AZBOfin

Disliked

look for this line of code in the indicator source:
dResult=iBullsPower(NULL,0,20,PC,pos)+iBearsPower(NULL,0,20,PC,pos);

PC describes the averagin period for the bulls/bears calculation.


now check the source code for the EA:
iTE=iBullsPower(NULL,0,20,6,0)+iBearsPower(NULL,0,20,6,0)

make sure all parameters are the same otherwise the indicator displays not the correct values.

AZBOfin

Ignored