rupweb
11 Oct 2012, 16:01

would need to be able to access the tick database... then run it through the test framework with different parameters.

Thanks for the suggestion about doing this. Could run a backtester and simply store all the ticks in a flat file and use that as the DB in VS...

rupweb
19 Sep 2012, 13:32

yep i mean exactly that... automating the robot parameters

rupweb
19 Sep 2012, 13:31

really need "ordercomment"... thx!

rupweb
14 Sep 2012, 18:29

Is there any way to automate back testing and produce a report on the results?

ie set stop loss to 25, run test & write report... set it to 26, run test & write report... set it to 27, run test & write report...

etc?

Thanks

rupweb
14 Sep 2012, 18:06

Thanks Qingyang2005, yes OnPositionOpened and then             

Trade.ModifyPosition(openedPosition, GetAbsoluteStopLoss(openedPosition, StopLoss), GetAbsoluteTakeProfit(openedPosition, TakeProfit));

But what I want to see is the return from the Trade method, it goes to the server then not sure how to capture the response, think it's void.

Also would like step-by-step code execution of the .cs robot, is that possible in VS?

rupweb
14 Sep 2012, 16:36

Hi Qingyang2005... hehe the fact you point out the editor is not up to VS standards does make me laugh... I have also been cutting and pasting and so on, working manually. But I guess that for me the editor has most of the functionality needed. What I would like is an OnPositionModified method so that once a Trade is placed then just as soon as my stops and takeprofits are bolted to the Trade I can easily see the result, which at the moment I find I cannot, but I know it IS working.

cheers, Rupweb.

There Is No Signal

rupweb
14 Sep 2012, 12:24

I had the same problem with "trace" through logs (turning the trace on or off) so I changed the Bool to int.

Then you'd have TradeHowManyTimes and use that, instead of TradeOnce (or make TradeOnce set to 1 or 0).

my 10 cents...

rupweb
14 Sep 2012, 12:22

As far as I can tell it does... but I want to be sure that backtesting is done tick by tick, rather than - for example - bar by bar