michaelhryu wrote:morgb wrote:Pippopotamus wrote:Surprised to see that with default settings Max,"sixths,"are preferred to ChaserL,"sixths." Morgb, can you explain?
Yeah I think in the beginning with earlier versions of the beast, there was only the 1 way to select the sixths lines, then the chaserL option was added. I guess i just stuck with what worked for me early on.
No real reason per say, probably forgot to change the option
The beast is truly a marvel - I've never seen anything like it for puling in regular money, as long as your safe with the options and trust it.
Looking forward to testing the new version, if nothing comes of it cool.
but with the beast you never know!!!!
Are you two talking about "UseMax" and "UseChaserL" settings under -BarCount-? What is the difference between the two, please?
I am going to attempt to answer this one, as it concerns IMHO a critical part of "The Beast".
As some you will know, TB started life as macman's test EA. It was originally designed by me to be very fast & lightweight, nothing like the monster it became -
The key to the EA was to be how many bars were used in the look back routine, to decide how the EA should react to the current market situation. As you all know, we can't predict the future, so the best we can do is base the actions of our EA on a
relevant past period.
My original concept was to have a dynamic system to adjust the look back period for every pair.
For instance we might find a currency pair behaves similarly most years in the summer quarter, so we could set that currency pair to use that look back period. If a currency pair is 'flavour of the month' (safe haven) for instance, we might want a substantially shorter look back period etc.
When Steve asked if it was OK to release the original into the forum (then on FF), I agreed, hoping that the idea of a dynamic input routine would be taken up. However it was not to be and instead ever increasing bits were bolted onto an unfinished concept.
OK, enough of the history lesson, let's look at the code.
Firstly the reference to Max is slightly wrong, so don't bother to try and look it back, as Max supplied a routine for adjusting ReEntryLinePips (part of Recovery), nothing to do with the look bar bars used.
The statements like this one below use my default number for bar count & BTW the bar count for AUDNZD should probably be 120 not 20 - my bad ...
if (StringSubstr(Symbol(), 0, 6) == "AUDNZD") { BarCount = 20; }
Just out of interest, here is a complete set of optimised results from early 2011:
if (StringSubstr(Symbol(), 0, 6) == "AUDCAD") { BarCount = 142; }
if (StringSubstr(Symbol(), 0, 6) == "AUDCHF") { BarCount = 196; }
if (StringSubstr(Symbol(), 0, 6) == "AUDJPY") { BarCount = 98; }
if (StringSubstr(Symbol(), 0, 6) == "AUDNZD") { BarCount = 76; }
if (StringSubstr(Symbol(), 0, 6) == "AUDSGD") { BarCount = 170; } //not optimised
if (StringSubstr(Symbol(), 0, 6) == "AUDUSD") { BarCount = 104; }
if (StringSubstr(Symbol(), 0, 6) == "CADCHF") { BarCount = 176; }
if (StringSubstr(Symbol(), 0, 6) == "CADJPY") { BarCount = 72; }
if (StringSubstr(Symbol(), 0, 6) == "CHFJPY") { BarCount = 107; }
if (StringSubstr(Symbol(), 0, 6) == "CHFSGD") { BarCount = 170; } //not optimised
if (StringSubstr(Symbol(), 0, 6) == "EURAUD") { BarCount = 161; }
if (StringSubstr(Symbol(), 0, 6) == "EURCAD") { BarCount = 217; }
if (StringSubstr(Symbol(), 0, 6) == "EURCHF") { BarCount = 292; }
if (StringSubstr(Symbol(), 0, 6) == "EURGBP") { BarCount = 224; }
if (StringSubstr(Symbol(), 0, 6) == "EURJPY") { BarCount = 221; }
if (StringSubstr(Symbol(), 0, 6) == "EURNZD") { BarCount = 131; }
if (StringSubstr(Symbol(), 0, 6) == "EURSGD") { BarCount = 170; } //not optimised
if (StringSubstr(Symbol(), 0, 6) == "EURUSD") { BarCount = 209; }
if (StringSubstr(Symbol(), 0, 6) == "GBPAUD") { BarCount = 34; }
if (StringSubstr(Symbol(), 0, 6) == "GBPCAD") { BarCount = 214; }
if (StringSubstr(Symbol(), 0, 6) == "GBPCHF") { BarCount = 192; }
if (StringSubstr(Symbol(), 0, 6) == "GBPJPY") { BarCount = 50; }
if (StringSubstr(Symbol(), 0, 6) == "GBPUSD") { BarCount = 150; }
if (StringSubstr(Symbol(), 0, 6) == "NZDCAD") { BarCount = 276; }
if (StringSubstr(Symbol(), 0, 6) == "NZDCHF") { BarCount = 300; }
if (StringSubstr(Symbol(), 0, 6) == "NZDJPY") { BarCount = 298; }
if (StringSubstr(Symbol(), 0, 6) == "NZDUSD") { BarCount = 214; }
if (StringSubstr(Symbol(), 0, 6) == "SGDJPY") { BarCount = 170; } //not optimised
if (StringSubstr(Symbol(), 0, 6) == "USDCAD") { BarCount = 117; }
if (StringSubstr(Symbol(), 0, 6) == "USDCHF") { BarCount = 269; }
if (StringSubstr(Symbol(), 0, 6) == "USDHKD") { BarCount = 170; } //not optimised
if (StringSubstr(Symbol(), 0, 6) == "USDJPY") { BarCount = 233; }
if (StringSubstr(Symbol(), 0, 6) == "USDSGD") { BarCount = 170; } //not optimised
So, if you are not running your own optimisation routine and updating these numbers as the market changes, and as far as I know, nobody is - then the "UseMax" input is a simple default.
BTW the information in the CAT section on my website at fx-works.com comes from my own version of TB, which was being optimised quarterly.
Later Chaser added a routine ("UseChaserL") which uses CCI to add some dynamic content into the look back bars being used. However as it simply uses the last 720 (hourly) bars, irrespective of what the market is doing as it's basis, it too is a best guess.
When you see posts by traders saying they have been profitable using x,y & z currency pairs, they are effectively saying that these currency pairs best fitted the look back bars being used - either CCI 30 days (720 hours) or my default values.
Before even more routines are added, it might be an idea to take a step back and see if we can improve TB in this area. This is a new forum and there are some brilliant minds around here, so I look forward to seeing some creative thinking. It is also possible that the system as it is now is good enough - I don't know.
You now have a bit more information to add to your knowledge of The Beast ... so go forth and conquer
