Pathfinder swing TS
Forums › ProRealTime English forum › ProOrder support › Pathfinder swing TS
- This topic has 2,004 replies, 6 voices, and was last updated 1 year ago by Gianluca.
-
-
10/10/2017 at 3:37 PM #4894110/12/2017 at 12:44 AM #4906810/12/2017 at 6:24 AM #4907010/12/2017 at 11:03 AM #4909510/12/2017 at 11:04 AM #4910010/12/2017 at 11:06 AM #4910310/12/2017 at 11:18 AM #49110
In the last few codes i moved the accumulation part to the month parameter.
The advantage is that you can turn them on and of in the specific period if you want to use them in the part above of the code it is either on or off
for the whole period. When you now want to use it for the next period, you change saisonalPatternMultiplier to 0//1 and tradeInPeriod = 0. You can leave the
rest as it is. In the new period you change saisonalPatternMultiplier to 1/1 and tradeInPeriod = 1 and optimize the rest for that period. The advantage is that
when the whole year is finished you change them to 1 or whatever it should be for that period and you’re done.
(it could also be 0 if you do not want trades in that period)
10/12/2017 at 11:47 AM #49118Hi Oskar,
Sorry to hear that it didn’t worked out for you as you thought on forehand. Probably overwhelmed by the profit on your demo-account in July you were
disappointed by the actual results of the real live trades the following months. The BT’s showed otherwise unfortunately. They didn’t count in all the short covering
in september/october. And with stops at 8 or 9 percent and candles withoutprofit at 18, won’t help unfortunately. But this is what swing trade is about i think.
Stopped out after every move, that is also not working i can assure you. The problem is that you have to have deep pockets. Like David :-). I think he had
great months. I can assure you that the road is long to find what you exactly want and what suits you. Changing to smaller timeframes won’t help you i’m affraid.
I guess you are 30, so time enough to figure it out. Before you know it you post here your own codes.
Best of luck.
Patrick
10/12/2017 at 12:13 PM #4912110/12/2017 at 12:28 PM #4912210/12/2017 at 2:37 PM #49139Oskar
as you have worked with pathfinder why not try to “customize” the version for 4 hour PF on other timeframes like 1 hour or so?
i have run on demo since end of july v7 on dax 1 hour with the same settings as 4 hour and its looking good so far
(i should have optimized it for 1 hour but have no time, maybe when we get the new price engine?)
10/12/2017 at 3:34 PM #49150Hi Dajvop and WP01,
Are you going to use V3 from now on without exception?
The problem is, all our already optimized algos (From lets say March to October now) are not like for like with version 3, which means we have to optimize all periods again as we cant just take our optimized parameters from V2 into V3.What is your opinion about that?
Best regards
10/12/2017 at 3:40 PM #4915210/12/2017 at 3:53 PM #49157Hi O-jay8,
I’m going to use V3 as template now. The one i posted earlier today which is prepaired for the upcoming months. I’m also affraid we have to do
the former months again. If you add every month the data in the new version than you have eventually a full year.
You guys also use your own version with different parameters. It can not be copied one on one. I usualy try to avoid accumulation. I’m fine with the lower result if
it has lower DD, but that didn’t work for the last couple of months. I’ve already took it slowly and didn’t run anything new in october besides the algo’s that already ran from september.
I have no idea what the best way is to move foreward.
10/12/2017 at 3:55 PM #49158I am still working with both v2 and v3 since, as you say, the results are different depending on which version you use.
If I get a good result in backtest with v3 I keep it, if it doesn’t work with v3 then I try v2, and that usually works. At least so far.
-
AuthorPosts
Find exclusive trading pro-tools on