Does anyone know if the walk forward scripts are available for WL5? If so how do I get them?
Size:
Color:
All you got to say Abrakadabra. :)
Size:
Color:
Dave Aronow have coded a Walk-Forward Optimization library for WLP5 a long while ago. It was actually functioning with v5.0 but the release of 5.1 broke compatibility and it stopped working.
Size:
Color:
Do we get the functionality back in 5.4?
Size:
Color:
I will see if I can get it up and running again and possibly dynamically link to the assemblies so it will work with any version. Not sure I can do that (easily) though.
Eugene do you know if this is something that will be included in WL 5 in the future (in a more robust fashion than my script)?
Dave
Size:
Color:
Hi Dave. We'll get the basic Optimizer in 5.4. No plans for WFO in 5.4 or 5.5.
Size:
Color:
Cone- any idea if walk forward will be in the next (big) iteration of WL you mentioned to be released next year?
Size:
Color:
No.
Size:
Color:
I'm trying to code some WFO-like functionality around Community.Components runDonor() method. It seems that I can successfully run an external strategy with arbitrary parameter values. Also, using SystemResults I can extract some basic performance metrics such as NetProfit after the strategy is executed. My question is if there's a way to extract any other metrics such as Profit Factor, Exposure or Max Drawdown or I need to code them myself?
Here's the code I have so far (still a very long way to go). As you can see, it is using NetProfit as the sole optimization function.
CODE:
Please log in to see this code.
Details of the Donor class are not important here, it just buys at specific bar and sells the next bar...
Also... Still need to come up with a way to set start/end optimization bars and start/end trading bars.
Size:
Color:
Andrew,
Firstly, there was a WFO library already coded by Dave Aronow of aronowsoftware.com - unfortunately, it's compatible with 5.1 only.
Good news: Wealth-Lab 5's Optimizer, like almost everything else, is extendable. This means, once we have the API documentation, you can code a walk-forward optimizer that will co-exist with the built-in ones.
Size:
Color:
Yes, I did my due diligence and checked before started coding. There is Dave Aronow's WFO library mentioned previously in this very thread, but it is not 5.6-compatible.
As for the API, an open optimization interface would be welcomed as really great news, but I'm afraid we're beyond the point where anybody would take any mention that Fidelity someday publishes the API seriously. I already have two other projects stalled because the API documentation is not available.
Let me ask you this -- is there any contractual obligation preventing MS123 from publishing the API themselves?
Size:
Color:
Wish I could help you, at one time in the past we were publishing it - but the answer is yes.
Size:
Color:
I will see if I can open source the WFO library over the next few weeks but I suspect it will not be very useful as quite a bit has changed since 5.1. It no longer compiles and I doubt I will get time to fix it, then again maybe if I can get it published (cleaned up enough that I'm not embarrassed to let someone see it :P) someone else can take a hack at it.
Dave
Size:
Color:
Dave, I would like to take a look and try to help you to fix the code. Please let me know.
Size:
Color:
Hi everybody. was there any progress with this effort with a WFO?
Size:
Color:
Nope. And I have no plans for WFO.
Size:
Color:
Avishn:
Did you ever get the code for WFO from Dave?
Size:
Color: