+1 888 340 6572
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
feature_request_small.png
Open Feature request MC-226

strategy weighing within a multi-strategy portfolio backtest
action_vote_minus_faded.png
7
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

I would like to have the same control that you get for the whole portfolio from portfolio settings in the main portfolio backtest window, for each strategy. For example, lets say i would like to backtest 8 different strategies, and I want them all to have an equal weighting of $100k for a initial portfolio capital of $1M and 80% total exposure. Right now the only way to do that would be to run a backtest with 1 strategy with a maximum exposure of 100k then duplicate the same backtest for the other 7 and combine the results in a spreadsheet. The reason is that I can control the capital at risk per position, but I cant control it per strategy. I have checked with Andrew at tech support and he concurs that the functionality does not exist currently, and if i want I can submit this feature request. Thanks.

Steps to reproduce this issue

n/a

Comments (1)
icon-mono-settings.png
#0
user-offline.png JoshM (Jura)
May 16, 2011 - 13:52

This would be a great feature to add.

History
sidebar_collapse.png sidebar_expand.png
Issue basics
  • Type of issue
    Feature request
  • Category
    Not determined
  • Targeted for
    Not determined
  • Status
    Under Review
User pain
  • Type of bug
    Not triaged
  • Likelihood
    Not triaged
  • Effect
    Not triaged
Affected by this issue (3)
People involved
Times and dates
  • Posted at
  • Last updated
Issue details
  • Resolution
    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