We are happy to announce the MultiCharts Easter Sale! Learn more
+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-2000

Enable option to throw out results of first backtesting trade AND customize Strategy Performance reports

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

1.  Throw out results of first trade
The first trade shown on backtesting results doesn't always have the proper criteria to enter the trade.  I might be wrong about this but this is what it visually appears to be when I backtest most strategies.
That being said, if you listen to people like Curtis Faith in "Way of the Turtle" and other sources, they always recommend throwing out the first trade results from your analysis.
Would be nice to have a switch allowing your backing results to show this.
2.  Run standard report versus customized Strategy Report
There are only a handful of initial metrics I like to look at when first trying to validate a system (signal).  It would be nice to be able to create different reporting settings for both Strategy and Portfolio backtesting results to see in one clean one pager the key criteria before looking any further into the results.  It would be ideal to be able to select what those criteria are.
3.  It would also be nice to be able to "program" or calculate other metrics that may not be included as standard in the reports as well.

Steps to reproduce this issue

N/A

Comments (0)
There are no comments
History
Issue basics
  • Type of issue
    Feature request
  • Category
    Performance
  • Targeted for
    Not determined
  • Status
    Not Reviewed
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
    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