You can also put together simple VBscripts that control AB optimizations/WFs as OLE. And in your AFLs, as Mike points out, you can do custom backtester routines that write whatever statistics you want, to file.
--- In [email protected], "Mike" <sfclimb...@...> wrote: > > I believe that the answer to all your questions is yes. > > Your AFL can do some of the work itself using fopen/fputs/fclose to write > values to disk at the appropriate point (see ActionEx of Status function), > which may then be read by your automation upon completion of the AFL. > > http://www.amibroker.com/guide/afl/afl_view.php?name=status > http://www.amibroker.com/guide/afl/afl_view.php?name=fopen > http://www.amibroker.com/guide/afl/afl_view.php?name=fputs > http://www.amibroker.com/guide/afl/afl_view.php?name=fclose > > Or, your automation code can itself call the Export method on the Analysis > object which you may then read in and parse. > > http://www.amibroker.com/guide/objects.html > > Mike > > --- In [email protected], "h3po" <h3pooo@> wrote: > > > > Hi, I have one more question: > > > > Will it be possible to control Amibroker as a COM server from a client > > application to.. > > > > 1) Run an Optimization and 2) get access to the optimal parameters wrt a > > chosen performance metric (i.e. get access to the data in the output window > > from the optimization), and then > > > > 3) run a Walkforward validation and 4) get access to the performance metric > > (eg CAR/MDD) from this WF validation... > > > > ...all from a client application via out-of-process OLE/COM ? > > > > Regards, > > Ole > > >
