+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-1768

Saving of Optimization and Backtesting Results with Porfolio (.pws) file

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

Currently, Optimization and Backtesting Results are not saved with the .pws file.

Basically, all the time spent setting up the tests and then generating these results is lost as soon as the portfolio is closed. This is a severe restriction on the real-world ability to conduct and document a test campaign for a portfolio.

Just as the results of Optimization and Backtesting in a workspace are saved in a .wsp file, so I suggest that the results Optimization and Backtesting in a portfolio be saved in the .pws file.

The single symbol usability of MC was dramatically and permanently enhanced at the point when the saving was added to workspaces. In effect, this unlocked the promise of the platform from the single-symbol testing point-of-view.

Doing the same for portfolios would be a similar and hugely positive advance.

Steps to reproduce this issue

Not saving is the current behavior as of MC 9.0 Release.

Comments (2)
#0
user-offline.png  Harvester (harvester)
Oct 16, 2014 - 08:51

The new portfolio features of MC 9 have the potential to be a game changer.  Being able to save optimization results is essential to making that a reality. A lot of time and effort goes into optimization campaigns, and being able to save your work for comparative analysis is really a basic requirement.
i definiely vote to add this saiving functionality to the .pws file structure.

#0
user-offline.png  supergordon (supergordon)
Oct 03, 2015 - 11:17

Having the ability to save these reports is a basic requirement

History
Issue basics
  • Type of issue
    Feature request
  • Category
    Usability
  • Targeted for
    Not determined
  • Status
    Under Review
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
  • Resolution
    Not determined
  • Severity
    Critical
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