Hi, ok. There is however, one major misunderstanding. Yes, it is like a batch system. But it is not over the various strategies, but over a list of datasets.
I did this implementation, because I do repeat the whole list of data sets for all changes to strategies and I further transfer this into an Excel sheet for tracking and comparison, as JBT does not provide any analysis capabiilities. But if you do not work this way, it is probably not too useful to you. Klaus On 1 Okt., 20:40, nonlinear5 <[email protected]> wrote: > > status information would be helpful. > > Is the code: > > - under consideration, > > - rejected > > - accepted > > - forgotten.. > > ? > > > As pointed out earlier. If modifications are necessary to get it into > > future releases, I will do it > > Klaus, thanks for your proposal. One of my goals is to keep the JBT > source base compact and focused. If there is an enhancement which adds > complexity to the code and provides marginal benefit, I'd rather not > make it part of JBT. Estimating from my usual work flow with JBT, it > looks like your proposed enhancement would save me about 30 seconds a > day by allowing me to backtest all of the strategies in one shot, as > opposed to one at a time. This doesn't seem significant enough for the > added complexity. -- You received this message because you are subscribed to the Google Groups "JBookTrader" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/jbooktrader?hl=en.
