This is thread for development, bug reporting, code submissions, different EA builds and ideas for development. Post #1 and #2 will be edited regularly with current news and the most recent and stable version of Phoenix. Some minor notes but full documentation is in the changelog.

Phoenix 6 is now out of beta, and released as stable. The code is from P6B6, and only has a small change to a signal. Settings are in the settings thread. You must load settings files. Current known good settings: M30 USDJPY. Settings to test: P6Rel USDCHF (Rel=released, attached to this post.)

PContour created Phoenix 5.7.3-W, with bugfixes and merged settings. I do not know of any working pairs in the P5 code.

STABLE VERSION: Phoenix 6 - Released
New code template bears fruit. Old style strategy still alive, but new strategies based on RSI and consecutive RSI are included. Will be porting over other contributed signal combinations into Phoenix 6. Feel free to submit your own signal combinations for a free EA.

PREVIOUS STABLE VERSION: 5.7.0
All modes working. Might be a quiet bug in the PeriodGraceHours Trailing Stop code. See 5.7.1 changelog for details. Backtest shows Mode 3 settings of 1.0 1.0 1.7 to be most profitable, default settings are profitable.

TESTING BUILD: 5.7.4
PContour has been graciously maintaining the old code base, and has included some enhancements based on consecutive loss prevention.

PhoenixFund TODO List:
Make a real Website = Half Done
IB Account = Fill out application with 5424 in the Upper Right, or "PhoenixFund"
Open Account to trade (Waiting on wire transfer)
Create letterhead with Logo

I personally like the idea of 3 builds:
Stable - Confirmed to run all modes with real money, verified profitable on at least 2 weeks of live testing and no reported major bugs.
Testing - live testing performed on mostly stable builds to be candidates for "stable" build. Live testing verifies profitability and consistency.
Weekly or Nightly Build - All code submissions combined together so people can backtest the latest features.

Current Stable: Phoenix 6 Released: Some settings unconfirmed, please test and submit reports.
Current Testing: Phoenix 6 Released, Phoenix 5.7.4, testing done by PContour
Weekly build: Phoenix 6

Previous build notes:
5.6.4 Weekly Build
HerbertH Mode3 fix (SL updated on 2 and 3 when 1 TP), Dagnar@FF Consecutive Signals (Ignore Buy/Sell signals less than threshhold, setting of 5 had excellent results), and Daraknor "MaxTrades" option added for mode 1(untested). Details are post #10.
5.6.6 Weekly Build
Includes many code fixes, some minor changes for performance, several errors removed, a great deal of documentation, 3 committed code contributions, and some preferences for people who create settings files. A EURUSD mode was added, but is not currently recommended for live trading. See post #61 for the comple changelog. Default trading behavior has CHANGED. Removed at 327 views to make room. EA still kept at post #61
5.6.7a Weekly Build
Another candidate for stable release. Only change in Mode 3 is behavior for moving StopLoss. Thanks for the log submissions and debugging ideas. Changelog in post #115 of this thread. Removed at 217 views, MQ4 is still at changelog.
5.6.08 Quick Bugfix
Thank you Wackena, Shinigami and Giapel for posting your errors. Debugging mode 3 continues, and it is usable, but the default mode is now Mode 1. Mode 2 and 3 are labeled "testing" and mode 1 is labeled "stable" inside the code. Modified Mode 3 to have accurate SL levels. Removed at 290 views. Changelog still holds original file.
5.7.0 Weekly Build
I was tired of Mode3 not working so I rewrote the entire detection mechanism. After it started working the performance was a lot different, so three settings were added to Mode3 control the TP level. Three optional variables were added to Mode3 section controlling the TP of the different trades. The default 0.5 1.0 1.5 was changed to 0.8 1.0 1.2. More details in the Changelog on post #151
5.7.1 Weekly Build
Added the min/max lot sizing. Changed the functionality of iOSMA to match standard. Added a separate trailing stop variable for graceful close function.
Confirmed new SL is better than the old SL. Deleted old blocks of code that were commented out because they didn't work. Full Changelog on post #177.
5.7.2 Weekly Build
*Will not trade with old settings, settings files are forced to have fast>slow settings. Please create new settings files.*
A separate thread has been created for settings file conversion. Thank you Pcontour!
The focus of this version is trailing stop, breakeven code and optimizations.
Pcontour renamed most of the functions and variables in Phoenix with shorter names. Shorter names helps overcome a limitation of 817 characters in the "Optimization Results" Window.
Full changelog pending me having more time.

Attached Files

	Phoenix_EA_v5_6_03.mq4 (33.8 KB, 1258 views)
	Phoenix_EA_v5_7_0.mq4 (38.2 KB, 2008 views)
	Phoenix_EA_v5_7_3.mq4 (49.2 KB, 1339 views)
	P6 Released.mq4 (35.9 KB, 1354 views)

Phoenix Status Updated Jan 02, 2007
I didn't work as much as I would have liked over the Christmas and New Year holiday, but it gave time for forward testing. 5.7.0 is declared stable, and a new testing version was released. Hendrick is still on vacation. I think I'm full strength and not sick anymore. Thank you all very much for your continued use of Phoenix, suggestions, bugfixes, communication and support. I added a todo list so people know how to contribute time to the project as a whole.

PhoenixFund (through an existing non profit Foundation) was approved as an IB. The paperwork is in review, and I'm mostly waiting and ready to answer any questions that they have. I won't earn anything for setting up the PhoenixFund IB, nor anything from people contributing to PhoenixFund from their own pockets. All of the funds donated or through the IB are used for trading Phoenix, minus banking fees. PhoenixFund will reinvest 50% and donate 50% of the monthly profits (never contributions) to nonprofits who are: document their costs transparently, nonsecular, aligned with the United Nations Development Program goals. I want to write this in a way that anyone who joins PhoenixFund or comes after me will need to follow the same guidelines. I think an "official meeting" along with a resolution is a decent way to do this, but suggestions are great.

I do intend to receive some benefit from my work, but the only benefits will be synergistic, like hosting the PhoenixFund and providing links to commercial services I provide. Forex-TSD.com will continue to be the main communication method for Phoenix, and most of the information will be duplicated. Some info will be better organized as a website than a forum post.
-----
Phoenix Development Plans
We have a (mostly) stable release of Phoenix! I say "mostly" because some features have not had adequate testing and confirmation, but there are no pending bugs in Phoenix 5.7.0. Some community developments for extra broker compatibility were added, variable organization, and a few other changes were added to 5.7.1. If 5.7.1 doesn't have any bugs after two weeks of decent testing (and/or bugs in 5.7.0 are found and confirmed to be fixed in 5.7.1) then 5.7.1 will be declared stable.

Most of my effort on Phoenix for the next week is going to be optimization testing and documentation. The documentation will be based around the new 5.7.1 style for optimization. Any "User Guides" for 5.7.0 style or 5.7.1 style are greatly appreciated.

Phoenix 6 development has begun, but slowly right now. A template with "a lot of useless code" will be released to other developers soon, so we can collaboratively build Phoenix 6. The template method is desired for organization of code, and so people can more easily modify pieces of Phoenix without worrying the entire system will shake. Phoenix Contest, 4 and 5 have made good use of functions, but knowing where to add a new function or new filter indicator is very difficult. The template system will attempt to make that easier. It may be "more code" but the part that a developer needs to pay attention to will be a lot smaller.

Here are a few features that I think are very important for Phoenix 6:
Trend Detection (Bertbin mentioned Turbo_jrsx and Turbo_jevl, I have been looking at Fish.)
Support and Resist Detection
Different Money management options

Here are a few features that I would like to see in Phoenix 6:
Filter Signals (don't enter market if...)
Confirmation Signals (linked to money & trade management)
Support for managed exits
Support for multiple sets of managed trades (several mode3 simultaneously on a single currency)
Easy optional logging
Better Magic Number management - ideally the system would detect if trades are currently open with magic numbers chosen
Weighted intelligent signal management

I have a few more ideas for things that would be nice but I'd like to keep some challenging features for Phoenix 7, building off the features in Phoenix 6. (Going to the next level of self tuning AI)

I would be willing to help out with communications and explanations and such.

Darak

Or we stay "open" as Hendrick wanted and all the "sharks", "crooks" and "thiefs" will always appear...
Or we go "closed"... more comfortable and without all that garbagge people but at least our community will get smaller and smaller and smaller.... Then... nobody...
I think (huuum!) better to stay " open" as Flying Dutchman wanted. Diversity is better than to stay alone...
And not answer to any silly questions, neither PM, neither e-mail... The only answer could be :" Go to the Phoenix forum and work a bit ! All the answer of your questions are there... work!"
100 % agree with you by the way to organize :
1/ Backward testers
2/ Forward testers
3/ Settings searchers
4/ Developpers if you think it's possible
5/ Wise man who transfer to Hendrick all results, wishes, research, ideas

We have also to have the same way to present results, results of week, results of forward test of 2 hours or 2 days are stupid!
And always a synthesis of 5 lines describing what hapenned during the week : Openned at xxhxx GMT It happened that... and that... Good result on yy pair, bad results on zz pair... Next I will go there, test that etc...
Next I will go there, test that etc...
Most of people are not new in Fx : they can express their feelings (and we are not here to flame somebody !)

For my part the statements of Meta are messy... The mix of pips and/or money are sometimes hell. Everybody should talk in PIPS : not in money earned or lost ! And money depends of lots!

Darak, Fikko and others "big heads"

P5 is based on a"group of indicators" searching together an "entry signal" according with settings..
After we have the brutals SL and TP...
Why we hanve'nt a"group of indicators" looking for an "exit signal", even in an upper TM ?
Stupid question ?
(I know that simple question are sometimes the hardest to program...)

Fixes
I think one of our largest challenges to consistent profits is the vast difference between the profits from the same broker started at slightly different times. The 1 trade per currency is likely a decent EA decision for stability and performance, but it makes examining test results very hard. 5 people will get completely different results. 1 person will have amazing profit, 2 will have great profit, 1 will break even and 2 will loose a lot of money.

In order to get a deeper understanding of market signals and effectiveness, we should probably trade on every valid signal. This would probably not be a system to use live, but at this point in time I don't know how to explain how strange the results are for different people aside from "you have different entry times."

I think this is one of the "deeper questions" we will face with this EA. I am going to run a test where max trades = 100 and lot size = smallest possible with money management off and see if the EA explodes, makes billions, or collapses. Hendrick restricted the trades for a reason, but I don't know what that reason is or how often we get trade signals, how accurate each signal is, etc. We are looking at 3 or 5 puzzle pieces, when the picture was made of thousands. We can't see the whole picture yet, and I think we need to. This would also help tell us how effective the consecutive signals fundamentally is. Dagnar had great success in backtest but there is more involved than that.

I do think the consecutive signals is a great idea - but one of my "bug fix" goals is to make Phoenix more reliable between users. I don't like one account going broke while another makes amazing returns on the same data. I consider that a type of bug.

The primary goal for me right now is to merge in bug fixes. The main one is Mode 3 working properly but we may need settings to go with it. I will review and release the code, probably with consecutive signals. An alert for currencies without settings may be good. We will very quickly need to address how Phoenix interprets settings files, which versions, currencies, timeframes, etc. Maybe next week?

Summary for intended release: make max trades a parameter that can be edited. Incorporate Mode 3 changes. Default to Mode 1(?) since it is longest tested. Consecutive trade signals as a feature that can be turned off/on.

Major changes to consider for development
Intelligently processing trades that miss their countertrend peak. I need to examine a lot of data, but it appears from the "extended trades not profitable" discussion that missing the target leaves a trade hanging for a long period of time. Can we detect when that miss occurs? For example: if we receive an incoming sell signal on a buy trade is that an indication we should prepare for exit with a trailing stop? I consider this "tuning" for another version, but I wanted to write it out.

The AccountEquity vs AccountMargin discussion didn't solve the real problem we face with money management: limiting overall risk without crippling the ability to make money when we are doing well. Money management in phoenix should ideally be reactive to two main situations: 1) hitting stoploss without countertrend occuring 2) consecutive losses. I know that wasn't very clear and I will try to think this through more. One concept is to reduce lot size until Win:Loss for the past time period X increases to a certain ratio.

Another idea is to have lot sizes placed based on (Equity - current exposure )> RiskPercent*Equity as a scaling logrithmic curve. (larger trades when exposure low, smaller trades when we have a lot of loosing trades open with big SL values). This idea has a fundamental appeal to me, but I don't know how effective it is. I did the math on how "max risk" is interpreted and what valid values would be. The Risk parameter is not human readable, and doesn't react well.

Separating Buy/Sell code seems valid, interesting, and a direction to explore. I don't now how two 80% accurate trading systems can combine to a 95% accurate system though. The math from http://en.wikipedia.org/wiki/Bayes'_theorem would be much different but I'm too tired at the moment and I lack some information directly on hand. Essentially by determining the probability distribution is significantly against a specific condition, the negative evidence stacks strongly. On the other hand, a Buy only EA may pay good swap.

I thought of this too The best signal to exit may be a counter signal since this system is a countertrend. The countercountertrend would be one signal. Another would be a "strong trend" signal but we may already be at the SL if that happens.

I have been running Phoenix on live account for about two months now. I have account with crown forex (dont use them for now- VERY suspicious company). And FXDD - New York company but filled with marcet sharks who play against you when time comes. Phoenix does ok on crown forex but didnt do good on FXDD. I lost about $400 in the first 3 weeks. It needs a lot of adjustments for live account. The data feed is different. Sometimees Phoenix on FXDD does real stupid things - at sudden jump up in price it sells, sells, sells, and then sells again until all positions hit the stop loss. And hey guys - dont be flattered with the demo account results. I dont want to discourage you - but I can double my demo account with Phoenix in a matter of 2 weeks. Try Phoenix with real amount on demo - like $1000 and you will feel the difference. One thing I noticed - the risk of .05 gives better results than .01

Thank you very much Georgiy. FXDD was recommended to me, but I was skeptical. If you have both demo and live data feeds (recorded not downloaded) I would greatly appreciate them. I would like to compare live vs real for FXDD especially and see how different the two data feeds are.

Would you mind sharing your full trading history? I would like to evaluate it. You can PM if you don't feel like posting.

Weekly build notes:
HerbertH Mode3 fix
This is the Hendrick approved fix for mode 3. There is no change to the buy logic, but the stoploss code has been edited. If position 1 exits at a profit, position 2 has SL = breakeven, position 3 has SL=Position1Profit/2. Now if the first position wins, second position at least breaks even, and the third position will have at least half of first position profit. Most of the code has been edited for Mode3, but most of it was equivalent code. New code looks very clean. No settings to change.

Dagnar@ForexFactory Consecutive Signals
(Ignore Buy/Sell tick signals less than threshhold, setting of 5 had excellent results backtested by Dagnar. Reported 50% more profit EURJPY in Mode 3 v5.6.3. A setting of 1 should not affect trading at all. http://www.forexfactory.com/forexfor...&postcount=875
A setting of 100 and 200 were used with very very good backtested results.
http://www.forexfactory.com/forexfor...&postcount=876
The timeframe is "ticks of confirming signals" not minutes or timeframes. I don't know the new method for approximating intrabar tick data in Build200 backtesting but this setting is very conditional on that method. (This also means Build198 will ahve different results than Build200 for this parameter.) Another variation submitted by Dagnar on the FF forum is based on "consecutive bars for the same signal" which would pick entry signals independent of the intrabar algorithm.

Daraknor "MaxTrades" option
This is just a research option because I am curious. I posted above that people trading the same broker at the same time for the same currency were getting vastly different results. The main reason for this is a slight offset in the trading. I think manual closing or editing the trade signals in any way vastly alters the entire trading behavior from then on. As a matter of curiousity, I would like to see more trade signals. I would recommend a very low max risk if this setting is over 5. I have not tested it at all (cutting edge weekly build), a value of 1 should not change behavior. I thought this was a very useful addition when combined with the consecutive signals option because consecutive signals will automatically stagger the trades (instead of opening 1 trade per tick). This trade change may be explosive - be warned. A large setting is a gamble, but adding code here is easier than writing a ton of code to view the signal output.

Summary: using default values is essentially 5.6.3 with a mode3 fix. We have two parameters to adjust now to research how to increase the trade stability of Phoenix.

Thank you all for contributions, we have many things that would be excellent to add. Out of the design comments so far, how would you like Phoenix to be developed? All comments are welcome, all code contributions are welcome.