Hi,
I would like to not user-friendly representation of the parameter in the backtest results.
Example:
It is common, that strategy has many parameters. It looks like this:
In backtest/optimization results, the parameters are represented like this:
Problem is readability of these text values.
As you see, when one wants to look what's the vale of some optimized parameters,
it is really detective and uncomfortable work. One is not easily able to read the value
assigned to the parameter in the optimization.
I undestand, that sorting by ABC produces predictable order, but is is really not logical
nor useful in this context. It requires amount of detective and annoying work each time
user wants to extract some value.
Important is to understand - that current ABC order of the exported parameters is really not useful
for human reading and interpretation of the backtest results. The related parameters are not grouped together (as in Properties window), which results in extreme chaotic bunch of unrelated (ABC sorted) parameters.
I suggest 2 possible elegant solutions:
Solution A:
Use the same order as is in the Properties window, so the user can easily locate the proper parameter depending on simple look. If the parameter is 1st in Properties window,
then it is 1st in the output parameters.
Solution B:
Use the key-value format, where key are individual properties and value its value.
The should be also exported in the order of how they are visible in the Properties window.
The solution B is superior above A, because, it has both benefits:
Example of the key-value format:
AtrCandleBodyIndicator_Period = 10 / Bar_CloseNearExtreme_InPercentOfHeight = 65 / ScaleIn_UseFixedStoploss = false / ... and so on...
We should be focused on achieving the 2 primary goals:
I would like to not user-friendly representation of the parameter in the backtest results.
Example:
It is common, that strategy has many parameters. It looks like this:
In backtest/optimization results, the parameters are represented like this:
Problem is readability of these text values.
As you see, when one wants to look what's the vale of some optimized parameters,
it is really detective and uncomfortable work. One is not easily able to read the value
assigned to the parameter in the optimization.
I undestand, that sorting by ABC produces predictable order, but is is really not logical
nor useful in this context. It requires amount of detective and annoying work each time
user wants to extract some value.
Important is to understand - that current ABC order of the exported parameters is really not useful
for human reading and interpretation of the backtest results. The related parameters are not grouped together (as in Properties window), which results in extreme chaotic bunch of unrelated (ABC sorted) parameters.
I suggest 2 possible elegant solutions:
Solution A:
Use the same order as is in the Properties window, so the user can easily locate the proper parameter depending on simple look. If the parameter is 1st in Properties window,
then it is 1st in the output parameters.
Solution B:
Use the key-value format, where key are individual properties and value its value.
The should be also exported in the order of how they are visible in the Properties window.
The solution B is superior above A, because, it has both benefits:
- User can easily locate parameter by visual look - for example 1st parameter in Property window will be also the parameter in the output.
- User can easily verify, that he is looking at the right one parameter, because it has
- name of the parameter before the value:
Example of the key-value format:
AtrCandleBodyIndicator_Period = 10 / Bar_CloseNearExtreme_InPercentOfHeight = 65 / ScaleIn_UseFixedStoploss = false / ... and so on...
We should be focused on achieving the 2 primary goals:
- easy orientation (pairing name of the property with its value)
- quick visual matching parameters in the Properties window with the parameter in the text output (to know, which one(s) should be changed to improve backtest results)
Attached Files
Comment