+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
feature_request_small.png
Open Feature request MC-2418

Expand the performance variables

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

Hi guys

I'm trying to work with some performance metrics using the custom criteria or even using a CustomFitnessValue set from within the .NET code. Unfortunately not all the performance values are readily available within the custom criteria script or even the SignalObject class. It would be nice if these values are computed and exposed so a trader could compute more complex performance metrics, some of these values are exposed on the performance report already they are just not available within the coding environment:

Account Size Required
Annualized Rate of Return
Average Trade Drawdown per Trade
Largest Losing Trade
Largest Winning Trade
Long Trade Count
Open Position P/L
Percent of Time in the Market (can be exposed potentially as the count of bars in trades and count of bars in back test - that would be bar count on Data0)
Return on Account
Return on Initial Capital
Return Retracement Ratio
Select Total Net Profit
Select Gross Profit
Select Gross Loss
Select Profit factor
Short Trade Count
Total Commission
Total Slippage

Kind regards

Comments (0)
There are no comments
History
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 (0)
There are no items
People involved
Times and dates
  • Posted at
  • Last updated
Issue details
  • Resolution
    Not determined
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