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

backtest API available to trigger optimization from Signals and save optimization results on disk

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

One good use-case is - for Walk-Forward, currently there is no way of processing / handling the data optained for a walk-forward optimization. The API should make available saving all that data to disk for further external processing.
The API should be accessible from Signal code and should be working both on past / historic data and also as a "live-running" strategy (switching a strategy to live data should not impair triggering backtests from the API).

Steps to reproduce this issue

FR

Comments (3)
#0
user-offline.png  Guest (Guest)
Jun 02, 2016 - 19:04

great feature. no one else has it. brilliant differentiator!

#0
user-offline.png  Guest (Guest)
Jun 02, 2016 - 19:22

this has been asked for Ninja and Ami ... it's just a matter of time.

#1
user-offline.png  Alex MultiCharts (Alex MultiCharts)
Apr 27, 2017 - 12:09
  1. Saving functionality is planned for MultiCharts 11.
  2. Access to the API should be available later, but only in MultiCharts .NET.
History
Issue basics
  • Type of issue
    Feature request
  • Category
    Usability
  • Targeted for
    MultiCharts 11.0 (RELEASED)
  • Status
    Partially Implemented
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