MultiCharts Easter Sale has jumped in! Up to 50% off Explore offers
+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-612

Portfolio Backtester removes uncompiled signals from portfolios

action_vote_minus_faded.png
1
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

In the 7.0 Release version, the Portfolio Backtester has unexpected behavior concerning signals that aren't compiled. Specifically, it will remove signals from a saved portfolios if the signals aren't compiled. 
For example, do the following:
1. Create a portfolio with an existing entry signal and an exit signal. Note that both signals will appear in the TreeView list in the left of the Portfolio Backtester, underneath "Strategy 1: Signals" (or whatever the name of the strategy is).
2. Backtest the portfolio to conform that it works. (The particular results aren't important.) 
3. Save the portfolio workspace, and close the file.
4. Edit either the entry signal or exit signal in the PowerLanguage Editor, so that that signal is no longer in a "compiled" state. This could be as simple as typing an extra space in the script.
5. Open the earlier workspace that you saved. The uncompiled signal will no longer appear in the TreeView list. If you compile the signal, it still will not appear in the strategy.
This behavior is unexpcted, in that the uncompiled signal is just deleted from the portfolio strategy, without any indication. 
It would make more sense for the signal to remain in the strategy, with an error message being generated if the user attempts to run a backtest without compiling the signal. E.g., if the user attempts to run a backtest using an uncompiled signal, the Portfolio Backtester could raise a modal dialog box saying something like: "Signal [name of signal] is not compiled. Please compile the signal before running a backtest."

Steps to reproduce this issue

See above.

Comments (0)
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 (3)
People involved
  • Posted by
    user-offline.png  Xyzzy (Xyzzy)
  • Owned by
    Not owned by anyone
  • Assigned to
    Not assigned to anyone
  • Subscribers
    0 subscriber(s)
    Click here to show the list of subscribers
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