+1 888 340 6572 GET STARTED
MultiCharts Project Management
previous_open_issue.png
Go to the previous open issue
previous_issue.png
Go to the previous issue (open or closed)
star_faded.png
Please log in to bookmark issues
bug_report_small.png
Open Bug report MC-1895

Optimization according fitness function in Portfolio Trader is wrong compared to backtesting results

action_vote_minus_faded.png
4
Votes
action_vote_plus_faded.png
next_issue.png
Go to the next issue (open or closed)
next_open_issue.png
Go to the next open issue
Description

Hello,
when strategies are added in portfolio trader and you want to optimize them via portfolio trader you get different values in the optimization report than choosing an optimization result and then backtest it again. So the optimization in portfolio trader it totally misleading. They differences are huge. This must be corrected, because it is a bug. The calculation is wrong here.

Steps to reproduce this issue

Just say inside every strategy you want to trade 0 or 1 contracts then optimize highest Total net profit for choosing a combination of strategies in portfolio trader with genetic optimzation. Use standard settings and you see that in the finished optimization report you get different net profits then with backtest of this chosen trading systems.

Comments (1)
#0
user-offline.png  Andy (andywill)
Jun 18, 2015 - 21:17

I think it is a common problem, because with Forex data I notice it is independent from data, broker or trading system. Reproduction should be easy. There must be just one input to say how many contracts will be traded and then only this input will be optimized between 0 and 1 for all trading systems in portfolio trader.

History
Issue basics
  • Type of issue
    Bug report
  • Category
    Usability
  • Targeted for
    MultiCharts 9.1 (RELEASED)
  • Status
    Released
  • Priority
    Not determined
User pain
  • Type of bug
    Not triaged
  • Likelihood
    Not triaged
  • Effect
    Not triaged
Affected by this issue (2)
People involved
Times and dates
  • Posted at
  • Last updated
Issue details
  • Reproducability
    Not determined
  • Severity
    Normal
Attachments (0)
There is nothing attached to this issue
Commits (0)
There are no code checkins for this issue
Duplicate issues (0)
This issue does not have any duplicates