Hi.
I would like to suggest that MC implement an "Optimization Settings Library".
For each signal, the user would be able to define optimization setups (all the input settings as here):
and store named setups in a library for later recall.
The point is that optimization setup, by its nature, is a tedious process. Anytime the user goes thru this process, being able to save the results so as not to have to repeat that setup the long way in the future is a very big timesaving convenience.
Suggestion: Optimization Settings Library
- Andrew Kirillov
- Posts: 1589
- Joined: 28 Jul 2005
- Has thanked: 2 times
- Been thanked: 31 times
- Contact:
I note that this situation persists in MC 6.0 Beta 2.
This is one of several key items pertaining to real-world usage of the MC backtesting capabilities that needs/deserves completion/enhancement prior to (IMO) turning all development attention elsewhere (e.g. manual trading, etc.).
Optimization/analysis speed/efficiency can be thought of as having two components - machine speed/efficiency and operator speed/efficiency. Both of these depend heavily on platform design and capabilities.
MC's use of multiple cores for optimization puts it out in front of many competitors from the machine speed/efficiency POV.
However, MC's current non-implementation of necessary operator efficiency features substantially undoes the machine advantage.
It is within MC's grasp to create a truly superb optimization experience, but you need to finish the job if that's what you want to provide.
A single programmer, focused on these items, could get them done in a reasonably short amount of time.
IMO, leaving these items undone indicates an incomplete understanding of what's needed in the field to create a superb optimization experience for the customer, or else a failure of commitment to provide that experience.
This is one of several key items pertaining to real-world usage of the MC backtesting capabilities that needs/deserves completion/enhancement prior to (IMO) turning all development attention elsewhere (e.g. manual trading, etc.).
Optimization/analysis speed/efficiency can be thought of as having two components - machine speed/efficiency and operator speed/efficiency. Both of these depend heavily on platform design and capabilities.
MC's use of multiple cores for optimization puts it out in front of many competitors from the machine speed/efficiency POV.
However, MC's current non-implementation of necessary operator efficiency features substantially undoes the machine advantage.
It is within MC's grasp to create a truly superb optimization experience, but you need to finish the job if that's what you want to provide.
A single programmer, focused on these items, could get them done in a reasonably short amount of time.
IMO, leaving these items undone indicates an incomplete understanding of what's needed in the field to create a superb optimization experience for the customer, or else a failure of commitment to provide that experience.
The enhancement you suggest would delay implementing manual trading. Manual trading is more important. A large number of us are discretionary traders.This is one of several key items pertaining to real-world usage of the MC backtesting capabilities that needs/deserves completion/enhancement prior to (IMO) turning all development attention elsewhere (e.g. manual trading, etc.).
You already can trade via MC, but we can't.
- Bruce DeVault
- Posts: 438
- Joined: 19 Jan 2010
- Location: Washington DC
- Been thanked: 2 times
- Contact: