Difference between revisions of "Chart Backtesting VS Portfolio Backtesting"
Jump to navigation
Jump to search
Abeloglazova (talk | contribs) |
|||
| (16 intermediate revisions by 5 users not shown) | |||
| Line 1: | Line 1: | ||
| − | + | MultiCharts and [[Portfolio_Trader|Portfolio Trader]] serve different purposes, and backtesting on charts and in Portfolio is not supposed to match. Still there are some recommendations that can help bringing the backtesting on charts and in Portfolio as close to each other as possible. | |
==Instrument settings== | ==Instrument settings== | ||
| Line 5: | Line 5: | ||
<br><div style="background-color: #E3FBE5;">'''Important:''' Portfolio workspace should contain only 1 symbol in the [[Data_Numbers|'''Data 1''']] column!</div> | <br><div style="background-color: #E3FBE5;">'''Important:''' Portfolio workspace should contain only 1 symbol in the [[Data_Numbers|'''Data 1''']] column!</div> | ||
| − | # [[Changing_Symbols| | + | # [[Changing_Symbols|Only one symbol]] from one [[:Category:Built-in_Data_Sources|data source]] must be used and they must be identical in both the MultiCharts Chart and the Portfolio Trader; |
# The following parameters should be set identically: | # The following parameters should be set identically: | ||
#* Chart type - regular or [[:category:Non-Standard_Chart_Types|non-standard]]; | #* Chart type - regular or [[:category:Non-Standard_Chart_Types|non-standard]]; | ||
| Line 11: | Line 11: | ||
#* [[Quote_Field|Quote Field]]; | #* [[Quote_Field|Quote Field]]; | ||
#* [[Sessions]]; | #* [[Sessions]]; | ||
| − | #* [[Chart_Resolution#Build_Volume_On_Selector|Build volume on]] (if the strategy uses volumes in | + | #* [[Chart_Resolution#Build_Volume_On_Selector|Build volume on]] (if the strategy uses volumes in its calculations); |
#* [[Data_Range|Data Range]]* - should be specified as From…To and not Days/Bars Back; | #* [[Data_Range|Data Range]]* - should be specified as From…To and not Days/Bars Back; | ||
#* [[Time_Zone|Time Zone]]*. | #* [[Time_Zone|Time Zone]]*. | ||
| Line 25: | Line 25: | ||
The following strategy settings should also match: | The following strategy settings should also match: | ||
| − | # on the | + | # on the '''Properties''' tab: |
#* [[Strategy_Properties#Setting_Costs.2FCapitalization|Commission Rule]]; | #* [[Strategy_Properties#Setting_Costs.2FCapitalization|Commission Rule]]; | ||
#* [[Strategy_Properties#Setting_Costs.2FCapitalization|Slippage]]; | #* [[Strategy_Properties#Setting_Costs.2FCapitalization|Slippage]]; | ||
| Line 34: | Line 34: | ||
# on the '''Backtesting''' tab: | # on the '''Backtesting''' tab: | ||
#* [[Limit_Order_Execution_Assumptions|Backtesting assumptions]]; | #* [[Limit_Order_Execution_Assumptions|Backtesting assumptions]]; | ||
| − | #* [[Realtime-History_Matching|Realtime-history matching]]. | + | #* [[Realtime-History_Matching|Realtime-history matching]]; |
| + | #* [[Bar Magnifier]] and [[Precise_Backtesting|Extended backtesting]] are unavailble for Portfolio, so on the chart it is required to disable these options. | ||
| − | + | ==Portfolio Trader specific settings== | |
| + | The following settings are unavailable on charts, therefore they need to be configured so that they don’t influence Portfolio backtesting. In the [[Portfolio_Settings|'''Money Management Settings''']] section: | ||
| + | * Exposure = 100% | ||
| + | * Max % of Capital at Risk per Position = 100% | ||
| + | * Margin value = 0 | ||
| + | * Max Potential Loss = 0 | ||
| + | <br> | ||
| + | |||
| + | <div style="background-color: #ff9999;"> '''NOTE:''' Even with all of these recommendations implemented there’s a possibility that the backtesting results in both applications will not match. This is related to the code’s specific and one should review the strategy’s code to find the reason for the discrepancy. An example of how to do that can be found [[Why_an_Order_Was_or_Was_Not_Executed|'''here''']]. </div> | ||
[[Category:FAQ]] | [[Category:FAQ]] | ||
Latest revision as of 13:51, 10 August 2023
MultiCharts and Portfolio Trader serve different purposes, and backtesting on charts and in Portfolio is not supposed to match. Still there are some recommendations that can help bringing the backtesting on charts and in Portfolio as close to each other as possible.
Contents
Instrument settings
Important: Portfolio workspace should contain only 1 symbol in the Data 1 column!
- Only one symbol from one data source must be used and they must be identical in both the MultiCharts Chart and the Portfolio Trader;
- The following parameters should be set identically:
- Chart type - regular or non-standard;
- Resolution;
- Quote Field;
- Sessions;
- Build volume on (if the strategy uses volumes in its calculations);
- Data Range* - should be specified as From…To and not Days/Bars Back;
- Time Zone*.
*Data Range and Time Zone for Portofio are specified in the common Data settings.
Signal settings
- Signals’ inputs on the chart should match those in Portfolio precisely;
- Intra-Bar Order Generation has to be disabled on charts, because this mode is not available in Portfolio.
Strategy settings
The following strategy settings should also match:
- on the Properties tab:
- Commission Rule;
- Slippage;
- Init Capital (for Portfoio this parameter is specified in the common Portfolio Settings);
- Maximum number of bars study will reference;
- Position limits;
- Trade size;
- on the Backtesting tab:
- Backtesting assumptions;
- Realtime-history matching;
- Bar Magnifier and Extended backtesting are unavailble for Portfolio, so on the chart it is required to disable these options.
Portfolio Trader specific settings
The following settings are unavailable on charts, therefore they need to be configured so that they don’t influence Portfolio backtesting. In the Money Management Settings section:
- Exposure = 100%
- Max % of Capital at Risk per Position = 100%
- Margin value = 0
- Max Potential Loss = 0
NOTE: Even with all of these recommendations implemented there’s a possibility that the backtesting results in both applications will not match. This is related to the code’s specific and one should review the strategy’s code to find the reason for the discrepancy. An example of how to do that can be found here.
